mirror of
https://github.com/zeek/zeek.git
synced 2025-10-03 15:18:20 +00:00
Improve how primary/top-level BIFs get initialized
This commit is contained in:
parent
1bbae2368d
commit
4a8640d702
6 changed files with 67 additions and 52 deletions
|
@ -277,6 +277,7 @@ extern std::vector<CallInfo> call_stack;
|
|||
// This is set to true after the built-in functions have been initialized.
|
||||
extern bool did_builtin_init;
|
||||
extern std::vector<void (*)()> bif_initializers;
|
||||
extern void init_primary_bifs();
|
||||
|
||||
inline void run_bif_initializers()
|
||||
{
|
||||
|
@ -310,11 +311,6 @@ using function_ingredients [[deprecated("Remove in v4.1. Use zeek::detail::funct
|
|||
constexpr auto check_built_in_call [[deprecated("Remove in v4.1. Use zeek::detail::check_built_in_call.")]] = zeek::detail::check_built_in_call;
|
||||
constexpr auto render_call_stack [[deprecated("Remove in v4.1. Use zeek::render_call_stack.")]] = zeek::render_call_stack;
|
||||
|
||||
// TODO: these are still here because of how all of the bif code gets included in Func.c. There could be a
|
||||
// renamed version inside the namespace, but the way that the code gets included complicates the matter. It
|
||||
// might need to be revisited after everything is namespaced everywhere else.
|
||||
void init_builtin_funcs();
|
||||
|
||||
// TODO: do call_stack and did_builtin_init need to be aliased?
|
||||
|
||||
// These have to be implemented as actual methods due to function overloading breaking the use of aliases.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue