Re: Command Line on windows

[Keith Thompson <kst-u@mib.org>]

Jean-Pierre Rosen <rosen@adalog.fr> writes:
> Gautier a �crit :
>>> any other ideas?
>> Maybe look in the run-time library sources (body of
>> GNAT.Command_Line and further). I guess it calls a GNU function that
>> expands the wildcards and there is an option or another function
>> that doesn't.
>> If you find something, I'm curious about the solution (same problem
>> for the zipada / unzipada utilities).
>> G.
> AFAIK, the problem is not with Gnat, but with cygwin. It does the
> expansion as Unix would have done, to ease portability for Unix
> applications. Well, this is an explanation, but no solution...

I don't think the original poster mentioned Cygwin.

If he is using Cygwin, the solution is to escape the wildcard:

    some_command "foo*"
    some_command 'foo*'
    some_command foo\*

But if he's not using Cygwin, he's probably invoking the command from
a Windows command prompt -- and in that case I don't know of a
solution.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Nokia
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"