Re: strange behaviour of utf-8 files

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

"Stoik" <staszek.goldstein@gmail.com> wrote in message 
news:7464679c-6b98-4e23-a337-83b671473553@googlegroups.com...
> Thanks for your comments. It is obviously a question of having a different 
> encoding in the
> editor and the compiler. I forgot to add the -gnatW8 switch to the 
> compiler (this should be
> a default, I believe).

Ada 2012 requires compilers to accept UTF-8 source code. But given that Ada 
source code historically is Latin-1, it's very unlikely that compilers would 
change the default setting. The effect would be to break the compilation of 
much existing source, a step that most compiler vendors would never take.

Speaking as a vendor, Janus/Ada has a number of default switches that would 
never be the default choices today. But changing the defaults breaks 
*everyone's* build scripts; it's just so disruptive that it's not something 
that we would do unless there was no other choice. It makes command line use 
of compilers with an extensive history harder than we would like, but that's 
the price of having customers that go way back.

If UTF-8 files were somehow identified as such, we could have friendlier 
defaults -- but since the use of the BOM is optional (and discouraged in 
recent Unicode standards), and there are no encoding attributes in common 
file systems (Windows, Linux) -- there really isn't much that we can do. 
This is going to remain a mess for a long time to come, I fear.

                                          Randy.

P.S. Truth-in-advertising: Janus/Ada *only* takes Latin-1 input; it has no 
support for any other encoding (of course it supports Wide_String at 
runtime). That will have to change as we migrate to Ada 2012, but it 
probably will be a while before that happens (not a lot of demand).