Re: Idea for documentation makeover

new topic     » goto parent     » topic index » view thread      » older message » newer message
_tom said...
  • An idea for a documentation makeover. This look can be achieved without rewriting the current documentation.

cmd_parse

parses command line options and optionally calls procedures based on these options.

cmd_parse( S1opts , O2parse_options = {} , S3cmds = command_line() )

include cmdline.e 
namespace cmdline 
public function 
Arguments:

S1 opts
a sequence of records that define the various command line switches and options that are valid for the application: See Comments: section for details
O2 parse_options = {}
an optional list of special behavior modifiers: See Parse Options section for details
S3 cmds = command_line()
an optional sequence of command line arguments. If omitted the output from command_line is used.


  • Any ideas or suggestions?

I'm not a fan of the O2 / subscript stuff. I guess those are stand ins for object and sequence? What happens when a parameter is a UDT?

Matt

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu