zeek/scripts/policy/misc/loaded-scripts.zeek
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

40 lines
898 B
Text

##! Log the loaded scripts.
@load base/utils/paths
module LoadedScripts;
export {
redef enum Log::ID += { LOG };
global log_policy: Log::PolicyHook;
type Info: record {
## Name of the script loaded potentially with spaces included
## before the file name to indicate load depth. The convention
## is two spaces per level of depth.
name: string &log;
};
}
# This is inefficient; however, since this script only executes once on
# startup, this should be ok.
function get_indent(level: count): string
{
local out = "";
while ( level > 0 )
{
--level;
out = out + " ";
}
return out;
}
event zeek_init() &priority=5
{
Log::create_stream(LoadedScripts::LOG, Log::Stream($columns=Info, $path="loaded_scripts", $policy=log_policy));
}
event zeek_script_loaded(path: string, level: count)
{
Log::write(LOG, Info($name=cat(get_indent(level), compress_path(path))));
}