On the top you can specify whether each function you want listed:
is a C function
is a function-like macro
has a writable declaration
has a read-only declaration
is visible in the whole project scope
is visible only in a file scope
has a definition body.
As is the case in file queries,
next comes a series of metrics CScout collects for each
defined function.
For each metric (e.g. the number of comments) you can specify
an operator ==, !=, < or > and a number
to match that metric against.
Thus to locate functions containing goto statement
you would specify
Number of goto statements != 0.
On the left of each metric you can specify whether that metric
will be used to sort the resulting file list.
In that case, the corresponding number will appear together with
each file listed.
A separate option allows you to specify that files should be sorted
in the reverse order.
Similarly to the identifier query,
you can also specify whether the specified properties should be treated
as a disjunction (match any marked),
as a conjunction (match all marked),
as a negation excluding all identifiers matching any property (exclude marked), or
as an exact match specification matching only identifiers that match
exactly the properties specified (exact match)
In addition you can specify:
That the function should have a specified number of direct callers.
A regular expression against which function names should match
(or not match)
A regular expression against which the names of calling functions should match
(or not match)
A regular expression against which the names of any called functions should match
(or not match)
A regular expression that filenames in which functions are declared occur should
match (or not match)
A query title to be used for naming the result page.
The title will appear on the result document annotating the
results, and will also provide you with a sensible name when creating a
bookmark to it.