GNU Mailutils |
|
General-Purpose Mail Package |
Official GNU Software |
Syntax: require string; require string-list;
The require statement informs the parser that a script makes use of a certain extension. Multiple capabilities can be declared using the second form of the statement. The actual handling of a capability name depends on its suffix.
If the name starts with ‘comparator-’, it is understood as a request to use the specified comparator. The comparator name consists of the characters following the suffix.
If the name starts with ‘test-’, it means a request to use the given test. The test name consists of the characters following the suffix.
Otherwise, the capability is understood as a name of an action to be used.
The require
statement, if present, must be used before any other
statement that is using the required capability. As an extension, the GNU
sieve allows the require
and any other statements to be
interspersed.
By default the following actions and comparators need not be explicitly required:
Example:
require ["fileinto", "reject"]; require "fileinto"; require "comparator-i;ascii-numeric";
When processing arguments for require
statement, GNU libmu_sieve
uses the following algorithm:
#searchpath
directive.
LTDL_LIBRARY_PATH
.
LD_LIBRARY_PATH
).
The value of LTDL_LIBRARY_PATH
and LD_LIBRARY_PATH
must be a
colon-separated list of absolute directories, for example,
‘"/usr/lib/mypkg:/lib/foo"’.
In any of these directories, libmu_sieve
first attempts to find
and load the given filename. If this fails, it tries to append the
following suffixes to the file name:
libmu_sieve
executes its
initialization function (see below) and again looks up the name
in the symbol table. If found, search terminates successfully.
libmu_sieve
then
issues the following diagnostic message:
source for the required action NAME is not available
This document was generated on January 2, 2022 using makeinfo.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.