OpenEuphoria

Re: Unicode Euphoria?

• Posted by Aku <akusaya at gmx.net> Apr 23, 2007
• 483 views

CChris wrote:
> This would be a desirable step forward. However, it may not be as easy 
> technically.
> 
> For instance, open() directly calls C code in the standard library, so you'd
> 
> need to build a separate Eu version, I think. I didn't investigate further -
> 
> see the thread on accented characters in directories under Windows. The 
> relevant function in be_runtime.c is EOpen(). I guess puts() and
> friends are coded the same.
> 
> Additionally, the way Windows supports Unicode is different on 9/Me and NT
> based
> systems. I don't know if this is an issue, but remember there are still
> quite a few people using 98.
> 
> Again, I'm just saying hat it is a tad more involved technically than it
> would look at first glance. But it would be a desirable improvement.
> 

That's why I said to override the built-in function.
AFAIK, eu built in functions can be overridden by just declaring a function
with the same name. For example

function open(sequence nf, sequence mode)
    return CreateFileW(nf, ...)
end function

About windows support, Windows XP is released in 2001, 6 years has passed, 
I don't think we should keep being stalled because of that, yes?

Because if it is possible without too much work, maybe we can develop a
"unicode compability layer" for euphoria which contains:

- replacement files for get.e, file.e, machine.e etc to support unicode.

- a new library file (e.g. eunicode.e) to override built-in functions.

Then as much as possible old programs will run unchanged
(except addition of eunicode.e).