Lines Matching refs:command

22 2. Replace the line on which a command occurs with some other text as directed
23    by the command. The replacement text can span multiple lines.
28 A command should be listed on a line by itself, and should not span more than
29 one line. The first token to appear on the line is the command name prefixed
30 with ``%%``. For example, a line with the ``include_file`` command should start
36 syntax. Before performing the action corresponding to the command, the header
61 Sub-sections below describe the commands currently available. Under each command
62 is the description of the arguments to the command, and the action taken by the
63 header generation tool when processing a command.
68 This is a replacement command which should be listed in an input ``.h.def``
78   This command instructs that the line on which the command appears should be
80   command.
85 This is not a replacement command. It is an error to list it in the input
87 ``include_file`` command (the ``.h.inc`` files). A common use of this command it
98   line on which this command is listed.
103 This is a replacement command which should be listed in an input ``.h.def``
104 file. The header file generator will replace this command with the public API of
107 of how the header generator replaces this command with the public API.
115   The header generator will replace this command with the public API to be exposed