Re: What about a glob standard method in Ada.Command_Line ?

["Randy Brukardt" <randy@rrsoftware.com>]

"Georg Bauhaus" <rm-host.bauhaus@maps.futureapps.de> wrote in message 
news:4c75bc6d$0$6973$9b4e6d93@newsspool4.arcor-online.net...
...
> You said, "You just do not need patterns in directory search."
> Did this refer to the Pattern : String parameter of
> (Start_)Search?   If so, I fully agree.
>
> Here is what I wanted Matcher : access function (...) to be.
>
> 1. get rid of implementation-defined Pattern : String

It's not implementation-defined if it is null; that is defined to match 
everything (always).

I'm not sure why we didn't give it a null string default (that seems like 
the logical thing to have done, since you often want to return everything). 
(I thought we had given it such a default, but that is definitely not the 
case.)

> 2. do with the names what I want after they have been read:

Why is such a Matcher routine necessary? You might as well just test the 
file name returned; there is going to be more overhead in the callback 
routine than in a direct test, and there is no way for the OS to help.

The reason there is an implementation-defined pattern parameter is that some 
OSes (Windows, for instance) can take the pattern directly and only return 
matches -- in this case, the Ada runtime can potentially be more efficient 
than writing the code explicitly. If the code has to be written explicitly, 
it might as well be part of the user program. There wasn't any intent to 
support anything here that the OS doesn't support directly (on POSIX 
systems, it would make sense to only support the null string pattern, 
although I think actual implementations do more). Programs that want to be 
as portable as possible ought to only use Pattern => "" in Start_Search.

                                Randy.