Re: Ada.Command_Line and wildcards
- From: "Alex R. Mosteo" <devnull@xxxxxxxxxxxxxx>
- Date: Thu, 22 Feb 2007 12:02:07 +0100
gautier_niouzes@xxxxxxxxxxx wrote:
This is an OS (shell) issue, surely?
Alas, no.
I forgot to mention: I tested both programs on both Windows 98 and XP.
It would be in unix. There, wildcard expansion is a shell matter. Windows only
half-faked it.
What I mean is that if your code is to be run outside of a windows platform,
you'll not see wildcards in your arguments (unless you quote them, as someone
else has pointed elsethread).
But if gnat is deliberately doing expansion to emulate unix behavior, I guess
that should be documented in windows platforms...
In both systems, the OA-compiled program gives "*.adb" and the GNAT-
compiled the list of files with ".adb" extension.
To Adrian, enclosing with '"' works, thanks, but then the syntax
differs from the usual one for a command-line tool...
I am just suprised by the GNAT behaviour, for two reasons:
- I did not find (or missed) something about it in the RM (95)
- there is also a GNAT.Command_Line that explicitely intends to do
wildcard expansions; so why also GNAT's Ada.Command_Line should do it,
silently ?
G.
.
- Follow-Ups:
- Re: Ada.Command_Line and wildcards
- From: Martin Krischik
- Re: Ada.Command_Line and wildcards
- References:
- Ada.Command_Line and wildcards
- From: Gautier
- Re: Ada.Command_Line and wildcards
- From: (see below)
- Re: Ada.Command_Line and wildcards
- From: gautier_niouzes
- Ada.Command_Line and wildcards
- Prev by Date: Re: real_time.clock is not monotonic
- Next by Date: [OT] Broken threading (was RE: real_time.clock is not monotonic)
- Previous by thread: Re: Ada.Command_Line and wildcards
- Next by thread: Re: Ada.Command_Line and wildcards
- Index(es):
Relevant Pages
|
Loading
