Re: Command Line on windows

["RasikaSrinivasan@gmail.com" <RasikaSrinivasan@gmail.com>]

On Sep 12, 8:25 am, Gautier <gaut...@fakeaddress.nil> wrote:
> Not solving your problem, but you'd prefer to use Ada.Command_Line which
> is standard and with Ada strings instead of C strings.
> _________________________________________________________
> Gautier's Ada programming --http://sf.net/users/gdemont/
>
> NB: For a direct answer, e-mail address on the Web site!

unfortunately ada.command_line says the behaviour is implementation
defined.

in fact the following is a test of my original attempt :

with Text_Io; use Text_Io;
with Ada.Command_Line;

procedure Test_Cli is
begin
   Put_Line(Ada.Command_Line.Argument(1));
end Test_Cli ;

this when compiled with gnat - produced results similar to
gnat.command_line. That is why I thought gnat.command_line might work
better.

   function Get_Argument (Do_Expansion : Boolean := False) return
String;
   --  Returns the next element on the command line which is not a
switch.
   --  This function should not be called before Getopt has returned
   --  ASCII.NUL.

the do_expansion led me to believe i could turn it off.

any other ideas?

of course specifying for example "*.adb" (within quotations) does
disable it but i guess that is the unix behaviour expected.

thanks, srini