Re: My first test of github: cpros - lightweight Ada command processor

[reinert <reinkor@gmail.com>]

Thanks, this was something. 

Before I dive deeper into it, by "command processor" I did here mean something with an interactive functionality, for short:

1. read a command from terminal and the possibility to process 
   it (and one normally gets a response on the terminal or a graphical window -
   or some hardware response, robot movement etc).

2. read command lines form a file (for example by a command like 
   "do <commandfile> <arg1> <arg2> ... <argN>" and process the commands in 
   sequence.  This "command file" may include another 
   "do <another_command_file" etc indefinitely deep.

3. Some arithmetic, operations for concatination (string handling) 
   etc may be included. A "delay" (generally timing) may be included.

In other words something with a scripting functionality.  I am not sure
this should be called "parsing"?

Could it be argued that such a "command processor" could be included in a standard Ada package? Yes, some smartass' may argue that this is easy to
program and do oneself, but such functionality may help development and
testing of programms?

reinert


On Tuesday, September 26, 2017 at 11:55:22 AM UTC+2, Brian Drummond wrote:
> On Mon, 25 Sep 2017 10:53:19 -0700, reinert wrote:
> 
> > Funny with comments about readability.
> > 
> > By the way: are there practical and light-weight command processors in
> > Ada?
> > Maybe even some with easy readable code?
> 
> What do you mean by "command processor"? If you mean something to parse 
> an executable's command line, there's the Generic Command Line Parser, 
> GCLP at 
> https://launchpad.net/gclp
> 
> I've used it a few times, and like it.
> 
> -- Brian