diff options
| author | John Thacker <johnthacker@gmail.com> | 2024-01-23 09:21:01 -0500 |
|---|---|---|
| committer | John Thacker <johnthacker@gmail.com> | 2024-01-24 01:00:32 +0000 |
| commit | ffbf7ff5408774faf80c9a3fd178463914ac5cc7 (patch) | |
| tree | 125692e1457f8bdb0672da5c13bc1a5542cf7a03 /doc/release-notes.adoc | |
| parent | 5c972dd0753685777140a3ea834a5dd0c8adc137 (diff) | |
dfilter: Allow semicolons to separate macro name from arg list
Instead of requiring ${macro:arg1;...;argN}, allow the format
${macro;arg1;...;argN}.
The semicolon isn't used anywhere else, it's simple to support,
and already used in the macro syntax. It's easier to remember
if all the separators in a macro are the same.
The colon is allowed in literals, which is why it's not used
between the arguments in the macro argument list, and allowing
it after the name makes the grammar more complicated, including
tokenizing when having pop-ups of potential field matches in
the display filter line edit (#19499.)
Update the documentation for this. Also edit the documentation
for macro syntax in a few places where it implies that whitespace
in macro arguments would be ignored; in fact, it's significant.
Diffstat (limited to 'doc/release-notes.adoc')
| -rw-r--r-- | doc/release-notes.adoc | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/release-notes.adoc b/doc/release-notes.adoc index b2233fd803..16aa24cbe0 100644 --- a/doc/release-notes.adoc +++ b/doc/release-notes.adoc @@ -73,9 +73,15 @@ The following features are new (or have been significantly updated) since versio ** Added new display filter functions to test various IP address properties. Check the wireshark-filter(5) manpage for more information. + ** Display filter macros can be written with a semicolon after the macro + name before the argument list, e.g. `${mymacro;arg1;...;argN}`, instead + of `${mymacro:arg1;...;argN}`. The version with semicolons works better + with pop-up suggestions when editing the display filter, so the version + with the colon might be removed in the future. + ** Display filter macros can be written using a function-like notation. - The macro `${mymacro:arg1; ...; argN}` can be written - $mymacro(arg1, ..., argN)`. + The macro `${mymacro:arg1;...;argN}` can be written + `$mymacro(arg1,...,argN)`. * Display filter functions can be implemented as libwireshark plugins. Plugins are loaded during startup from the usual binary plugin configuration directories. See the |