9 Jul
2018
9 Jul
'18
7:10 p.m.
When we did cisco CLI support in our router product,
syntax for all
the commands was factored out. So for example
show.ip
help IP information
show.ip.route
help IP routing table
exec cmd_showroutes()
show.ip.route.ADDR
help IP address
verify verify_ipaddr()
exec cmd_showroutes()
etc. This was a closed universe of commands so easy to extend.
Perhaps something similar can be done, where in a command src dir
you also store allowed syntax. This can be compiled to a syntax
tree and attached to the binary using some convention. The cmd
binary need not deal with this (except perhaps when help or verify
required cmd specific support).
This sounds like a resource fork on a file. Much like MacOS (pre X) had for all files. It
was a convenient way to keep data that defined the application associated with the
application. You could also edit it to customize it for your own use if you wished.
There were a great many good things about the MacOS of old.
David
_______________________________________________
COFF mailing list
COFF(a)minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff