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

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Wed, 25 Aug 2010 17:51:39 +0200, Georg Bauhaus wrote:

> On 25.08.10 16:56, Dmitry A. Kazakov wrote:
>> Certainly and without any doubt it is
>> possible to provide an abstraction which would work for Posix, Unix,
>> Windows, VMS, MacOS and name what OS.
> 
> It is not actually possible to provide a common abstraction
> for *new* and *existing* file names.  While "broken", the file
> names do exist.  Just a few examples illustrating a variety of file
> naming fun:
> 
> - Names created in NTFS that end in a '.'
>
> - Two names in existing ext2 directories that contain
>  "mutually exclusive" characters (via incompatible encoding)
> 
> - Names containing characters that are special in Windows but
>  not in POSIX.
> 
> - Names with spaces in them

You don't get the point. See A.13(9)

> Wide_Wide_String can't cure these,

It is, because any file name can be represented by Wide_Wide_String.

>>>  And since there is no single, well defined,
>>> portable οΏ½ for file names,
>> 
>> It is same as to say that there is no portable Integer type.
> 
> If in the real word, I/O of "broken" integer values is a
> reality.

What does this have to do with the point?

You seem to wish file names checked statically. Does Ada.Directories this?
Why then you pose this silly requirement?

> Can't just raise an exception
> because of a faulty name!

See A.13(9)

> Almost all WWW documents are broken by your taxonomy.
> Google is rich...

I don't understand what you are talking about.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de