Re: Caselessness...

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

My best guess would be that it would amount to a representation issue. In
the same way that you could, for example, represent the reserved words in an
editor with a different language, you could probably represent identifiers
in some alternate way. The trick would be that you probably have to go both
directions - you have to be able to read the validation suite and compile
it, which means your representation issue comes between the viewer and the
underlying ASCII character set. So imagine an editor that read the ASCII
text and changed the representation for the viewer in some way. Likewise,
what the viewer types is translated to some underlying ASCII and compiled.
So in a sense, my preprocessor suggestion is kind of an answer - except
you'd need something that transformed in both directions so you could
properly handle the validation suite. Remember that the validation suite has
probably got tests in it to insure that character case doesn't matter, since
this is in the standard.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"FGD" <presbeis@look.ca> wrote in message news:3BCB3E2A.1070001@look.ca...
> I think you're still reacting to that other thread which I wanted to
> avoid by starting a new thread...
>
> My question is technical: Is the "loophole" I mentionned possible within
> the Ada language specs? (I don't really care if it can be done with a
> preprocessor, or even if it is desirable to do so with or without a
> preprocessor...)
>