Re: DOS Options

[Jeffrey Creem <jeff@thecreems.com>]

Charles H. Sampson wrote:
>      I've been using GNAT 3.15p for a long time to write DOS-like
> project utiities to run on my Wintel desktop.  I've just come up with a
> case where I'd like to implement optional parameters.  Since the utility
> is DOS-like, I want to use the DOS form of optional parameters: attached
> to the name of the command, separated by the '/' character.
> 
>      I don't see how to do this.  Command_Line.Argument doesn't accept a
> value of 0, which I remember as being the substring of the command line
> from the first non-blank up to the first suceeding blank.  The note in
> A.15 says that Command_Name is the equivalent of argv (0), but in GNAT
> that's really just the command name, options stripped off.
> 
>      Does anybody have any suggestions?
> 
>                         Charlie
> 

I don't know what you mean about remembering 0 being the first substring 
  of the command line? Remember from where?

ada.command_line.argument(1) certainly returns the first argument to the 
program regardless of whether it is DOS, Unix, etc. It even appears to 
handle the degenerate case of no space between the command and the 
argument.

Perhaps I am missing the point of your question. since

my_command /option_1 /option_2
and even
my_command/option_1 /option_2

work such that ada.command_line.argument(1) returns /option_1
and ada.command_line.argument(2) returns /option_2

But since this is the most obvious thing I assume I am not really 
understanding your problem.