Skip to content
Snippets Groups Projects
  1. Nov 26, 2019
  2. Mar 20, 2019
  3. Feb 07, 2018
  4. May 31, 2017
  5. May 16, 2017
  6. May 15, 2017
  7. Jun 08, 2015
  8. Dec 26, 2012
  9. Jul 18, 2012
  10. Oct 10, 2011
  11. Sep 11, 2011
  12. Jul 03, 2011
  13. Feb 21, 2010
  14. Jul 14, 2009
  15. May 31, 2004
  16. Jun 08, 2000
  17. Jun 07, 2000
  18. Jun 03, 2000
  19. May 30, 2000
  20. Apr 28, 2000
  21. Apr 01, 2000
  22. Mar 04, 2000
  23. Dec 06, 1999
  24. Dec 01, 1999
  25. Nov 30, 1999
  26. Nov 17, 1999
  27. Oct 31, 1999
    • Martin Mareš's avatar
      Parse CLI commands. We use the same parser as for configuration files (because · bc2fb680
      Martin Mareš authored
      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.
      bc2fb680
    • Martin Mareš's avatar
      The CLI I/O functions work as desired. · b9672a84
      Martin Mareš authored
      b9672a84
  28. Oct 29, 1999
Loading