mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
431767d04b
This is based on the discussion in zeek/zeek#2668. Using &default with tables can be confusing as the default value is not inserted. The following example prints an empty table at the end even new Service records was instantiated. type Service: record { occurrences: count &default=0; last_seen: time &default=network_time(); }; global services: table[string] of Service &default=Service(); event zeek_init() { services["http"]$occurrences += 1; services["http"]$last_seen = network_time(); print services; } Changing above &default to &default_insert will insert the newly created default value upon a missed lookup and act less surprising. Other examples that caused confusion previously revolved around table of sets or table of vectors and `add` or `+=` not working as expected. tbl_of_vector["http"] += 1 add tbl_of_set["http"][1];
21 lines
509 B
Text
21 lines
509 B
Text
# @TEST-DOC: Ensure &default_insert is copied with a table.
|
|
# @TEST-EXEC: zeek -b %INPUT >out
|
|
# @TEST-EXEC: btest-diff out
|
|
# @TEST-EXEC: btest-diff .stderr
|
|
|
|
global tbl: table[count] of string &default_insert="<default>";
|
|
|
|
event zeek_init()
|
|
{
|
|
tbl[0] = "no-default";
|
|
local copy_tbl = copy(tbl);
|
|
print "copy_tbl[0]", copy_tbl[0];
|
|
print "copy_tbl[1]", copy_tbl[1];
|
|
print "copy_tbl", copy_tbl;
|
|
print "tbl", tbl;
|
|
|
|
assert 0 in copy_tbl;
|
|
assert 1 in copy_tbl;
|
|
assert |copy_tbl| == 2;
|
|
assert |tbl| == 1;
|
|
}
|