OpenEuphoria

Re: Accented characters in identifiers

• Posted by Robert Craig <rds at RapidEuphoria.com> Apr 06, 2007
• 709 views

CChris wrote:
> Currently, Eu interprets characters with the most significant bit set as
> opcodes. Only old shrouded files store Eu opcodes this way.
> 
> Isn't it time to remove that restriction, so as to be able to use non 
> english identifiers in programs? Other languages frequently use accented
> characters.

Yes, I agree. I'll do that fairly soon, if nobody objects.
Others, such as Igor Kachan, have also mentioned the lack of support
for the higher ASCII codes for non-English languages.

The 3.0 open source version of Euphoria does not have the
ability to decrypt files that are both "shrouded" and "encrypted".
"shrouding" used to mean just conversion of keywords and 
built-in names to single-byte codes and converting variable
and routine names to short meaningless identifier names. 
With version 2.0 came the option to also "encrypt".
In 2.5, a whole new binder/shrouder was developed where 
conversion to byte-codes no longer occurred, but a form of 
IL encryption continued, for bound executables only.

> Is anyone running these legacy shrouded files?

I believe there are very few files out there
that are "shrouded", but not also "encrypted" or bound 
into an executable, so there is little point now in 
maintaining support for the single-byte codes (in scanner.e).

Note that executable programs that were "bound" with the interpreter, 
pre-3.0, are not affected, since they contain the required 
interpreter version. The only breakage here would be very old, 
probably pre-2.0 (1997 or earlier) files, "shrouded", 
but not "encrypted".

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com