mirror of
https://github.com/zeek/zeek.git
synced 2025-10-16 21:48:21 +00:00
Improve documentation of Bro script statements
Added more documentation of the "delete" statement. Removed some other text that was probably more confusing than helpful.
This commit is contained in:
parent
374e61ee20
commit
c1d7337a73
1 changed files with 11 additions and 7 deletions
|
@ -277,16 +277,25 @@ Here are the statements that the Bro scripting language supports.
|
||||||
.. bro:keyword:: delete
|
.. bro:keyword:: delete
|
||||||
|
|
||||||
The "delete" statement is used to remove an element from a
|
The "delete" statement is used to remove an element from a
|
||||||
:bro:type:`set` or :bro:type:`table`. Nothing happens if the
|
:bro:type:`set` or :bro:type:`table`, or to remove a value from
|
||||||
specified element does not exist in the set or table.
|
a :bro:type:`record` field that has the :bro:attr:`&optional` attribute.
|
||||||
|
When attempting to remove an element from a set or table,
|
||||||
|
nothing happens if the specified index does not exist.
|
||||||
|
When attempting to remove a value from an "&optional" record field,
|
||||||
|
nothing happens if that field doesn't have a value.
|
||||||
|
|
||||||
Example::
|
Example::
|
||||||
|
|
||||||
local myset = set("this", "test");
|
local myset = set("this", "test");
|
||||||
local mytable = table(["key1"] = 80/tcp, ["key2"] = 53/udp);
|
local mytable = table(["key1"] = 80/tcp, ["key2"] = 53/udp);
|
||||||
|
local myrec = MyRecordType($a = 1, $b = 2);
|
||||||
|
|
||||||
delete myset["test"];
|
delete myset["test"];
|
||||||
delete mytable["key1"];
|
delete mytable["key1"];
|
||||||
|
|
||||||
|
# In this example, "b" must have the "&optional" attribute
|
||||||
|
delete myrec$b;
|
||||||
|
|
||||||
.. bro:keyword:: event
|
.. bro:keyword:: event
|
||||||
|
|
||||||
The "event" statement immediately queues invocation of an event handler.
|
The "event" statement immediately queues invocation of an event handler.
|
||||||
|
@ -532,8 +541,6 @@ Here are the statements that the Bro scripting language supports.
|
||||||
end with either a :bro:keyword:`break`, :bro:keyword:`fallthrough`, or
|
end with either a :bro:keyword:`break`, :bro:keyword:`fallthrough`, or
|
||||||
:bro:keyword:`return` statement (although "return" is allowed only
|
:bro:keyword:`return` statement (although "return" is allowed only
|
||||||
if the "switch" statement is inside a function, hook, or event handler).
|
if the "switch" statement is inside a function, hook, or event handler).
|
||||||
If a "case" (or "default") block contain more than one statement, then
|
|
||||||
there is no need to wrap them in braces.
|
|
||||||
|
|
||||||
Note that the braces in a "switch" statement are always required (these
|
Note that the braces in a "switch" statement are always required (these
|
||||||
do not indicate the presence of a `compound statement`_), and that no
|
do not indicate the presence of a `compound statement`_), and that no
|
||||||
|
@ -604,12 +611,9 @@ Here are the statements that the Bro scripting language supports.
|
||||||
if ( skip_ahead() )
|
if ( skip_ahead() )
|
||||||
next;
|
next;
|
||||||
|
|
||||||
[...]
|
|
||||||
|
|
||||||
if ( finish_up )
|
if ( finish_up )
|
||||||
break;
|
break;
|
||||||
|
|
||||||
[...]
|
|
||||||
}
|
}
|
||||||
|
|
||||||
.. _compound statement:
|
.. _compound statement:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue