From bc2fb68098faaf09393437a7743285d2af71d102 Mon Sep 17 00:00:00 2001 From: Martin Mares Date: Sun, 31 Oct 1999 17:47:47 +0000 Subject: Parse CLI commands. We use the same parser as for configuration files (because we want to allow filter and similar complex constructs to be used in commands and we should avoid code duplication), only with CLI_MARKER token prepended before the whole input. Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files. The first argument specifies the command itself, the remaining two arguments are copied to the help file (er, will be copied after the help file starts to exist). This macro automatically creates a skeleton rule for the command, you only need to append arguments as in: CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM { cli_msg(0, "%d$ stolen", $3); } ; Also don't forget to reset lexer state between inputs. --- nest/config.Y | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'nest/config.Y') diff --git a/nest/config.Y b/nest/config.Y index 91cdad11..64594625 100644 --- a/nest/config.Y +++ b/nest/config.Y @@ -182,6 +182,11 @@ password_list: } ; +/* Core commands */ + +CF_CLI(TEST LEDS, , [[Flashes each LED times]]) NUM { cli_msg(0, "%d", $3); } ; +CF_CLI(TEST, 1, 2) { cli_msg(0, "OK"); } + CF_CODE CF_END -- cgit v1.2.3