zeek/scripts/base/frameworks/analyzer
Benjamin Bannier d5fd29edcd Prefer explicit construction to coercion in record initialization
While we support initializing records via coercion from an expression
list, e.g.,

    local x: X = [$x1=1, $x2=2];

this can sometimes obscure the code to readers, e.g., when assigning to
value declared and typed elsewhere. The language runtime has a similar
overhead since instead of just constructing a known type it needs to
check at runtime that the coercion from the expression list is valid;
this can be slower than just writing the readible code in the first
place, see #4559.

With this patch we use explicit construction, e.g.,

    local x = X($x1=1, $x2=2);
2025-07-11 16:28:37 -07:00
..
__load__.zeek dpd->analyzer.log change - rename files 2025-06-03 16:32:52 +01:00
dpd.zeek Fix a typo. 2025-06-05 17:51:54 -07:00
logging.zeek Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
main.zeek Analyzer failure logging: tweaks and test fixes 2025-06-03 15:56:42 +01:00
README More bro-to-zeek renaming in scripts and other files 2019-05-16 02:36:41 -05:00

The analyzer framework allows to dynamically enable or disable Zeek's
protocol analyzers, as well as to manage the well-known ports which
automatically activate a particular analyzer for new connections.