Skip to content
This repository was archived by the owner on Oct 13, 2025. It is now read-only.

Commit 0aae052

Browse files
committed
Remove spicy:: prefix name recommendation
This seems to be stale and no longer recommended. I did not update the analyzer examples which use it, or explanation of what happens if you do use it, since those are more prevalent and reflect current use.
1 parent 2625284 commit 0aae052

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

devel/spicy/reference.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,7 @@ file that looks like this::
5454
PROPERTY_N;
5555

5656
Here, ``ANALYZER_NAME`` is a name to identify your analyzer inside
57-
Zeek. You can choose names arbitrarily as long as they are unique. As
58-
a convention, however, we recommend name with a ``spicy::*`` prefix
59-
(e.g., ``spicy::BitTorrent``).
57+
Zeek. You can choose names arbitrarily as long as they are unique.
6058

6159
On the Zeek-side, through some normalization, these names
6260
automatically turn into tags added to Zeek's ``Analyzer::Tag`` enum.
@@ -900,7 +898,7 @@ Accessing Zeek Variables from Spicy
900898
You can access Zeek-side global variables from inside Spicy, which is
901899
particularly handy for configuring Spicy analyzers from Zeek script
902900
code. The :ref:`zeek <spicy_functions>` module facilitates this
903-
through a set of functions coverting the current value of Zeek
901+
through a set of functions converting the current value of Zeek
904902
variables into corresponding Spicy values. For example, let's say you
905903
would like to provide a Zeek script option with a ``count`` value that
906904
your Spicy analyzer can leverage. On the Zeek side, you'd define the

0 commit comments

Comments
 (0)