Age | Commit message (Collapse) | Author | |
---|---|---|---|
2000-04-28 | Fixed a couple of nasty CLI bugs which were triggered on long or multi-part | Martin Mares | |
outputs. It took a whole evening to hunt them down, but now the CLI seems to work fine. Now I run three BGP connections with several thousand routes! | |||
2000-04-01 | Include "lib/string.h" instead of <string.h>. It should give us bzero() | Martin Mares | |
and other non-portable functions on all systems. | |||
2000-03-04 | Enabled short continuations. | Martin Mares | |
1999-12-06 | Implemented echoing of log messages to CLI connections. Just try `echo all'. | Martin Mares | |
1999-12-01 | Reset temporary parser data before parsing, not afterwards. This enables | Martin Mares | |
deferred CLI command handlers to store their temporary data in the CLI parsing pool. | |||
1999-11-30 | Remember protocol instance in proto_config and use that for | Martin Mares | |
`show protocols <name>'. | |||
1999-11-30 | Don't use continuation shortcuts until real client is written. | Martin Mares | |
1999-11-17 | Command line interface now works. | Martin Mares | |
1999-10-31 | Parse CLI commands. We use the same parser as for configuration files (because | Martin Mares | |
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. | |||
1999-10-31 | The CLI I/O functions work as desired. | Martin Mares | |
1999-10-29 | First steps of the Command Line Interface: I/O routines. | Martin Mares | |