Re: Why no Ada.Wide_Directories?

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

"ytomino" <aghia05@gmail.com> wrote in message 
news:418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com...
> Hello.
> In RM 3.5.2, Ada's Character/String types are not UTF-8 but Latin-1
> (except Ada.Strings.UTF_Encoding).
> I'm afraid that is violation of the standard even if the
> implementation accepts UTF-8.

Say what?

Ada.Strings.Encoding (new in Ada 2012) uses a subtype of String to store 
UTF-8 encoded strings. As such, I'd find it pretty surprising if doing so 
was "a violation of the standard".

The intent has always been that Open, Ada.Directories, etc. take UTF-8 
strings as an option. Presumably the implementation would use a Form to 
specify that the file names in UTF-8 form rather than Latin-1. (I wasn't 
able to find a reference for this in a quick search, but I know it has been 
talked about on several occasions.)

One of the primary reasons that Ada.Strings.Encoding uses a subtype of 
String rather than a separate type is so that it can be passed to Open and 
the like.

It's probably true that we should standardize on the Form needed to use 
UTF-8 strings in these contexts, or at least come up with Implementation 
Advice on that point.

                                       Randy.