10 Commits

Author	SHA1	Message	Date
Martin Mares	221135d6bf	Include "lib/string.h" instead of <string.h>. It should give us bzero() ... and other non-portable functions on all systems.	2000-03-31 23:30:21 +00:00
Martin Mares	c7814f01fc	Enabled short continuations.	2000-03-04 21:26:19 +00:00
Martin Mares	34350a5270	Implemented echoing of log messages to CLI connections. Just try `echo all'.	1999-12-06 12:34:45 +00:00
Martin Mares	f611f0ee82	Reset temporary parser data before parsing, not afterwards. This enables ... deferred CLI command handlers to store their temporary data in the CLI parsing pool.	1999-12-01 15:07:56 +00:00
Martin Mares	1d2664a4d4	Remember protocol instance in proto_config and use that for ... `show protocols <name>'.	1999-11-30 14:04:09 +00:00
Martin Mares	10b5baaef3	Don't use continuation shortcuts until real client is written.	1999-11-30 12:56:52 +00:00
Martin Mares	ffb59d243a	Command line interface now works.	1999-11-17 12:00:21 +00:00
Martin Mares	bc2fb68098	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.	1999-10-31 17:47:47 +00:00
Martin Mares	b9672a845f	The CLI I/O functions work as desired.	1999-10-31 15:43:44 +00:00
Martin Mares	7d3aab1c16	First steps of the Command Line Interface: I/O routines.	1999-10-29 12:10:10 +00:00