1. Re: Error: file name for OPEN is too long
Greg Haberek wrote:
>
> My $0.031415926535897
>
> To not just work around, but *FIX* the 255-character limitation, especially
> *within* the interpreter itself, we need to start using/supporting Unicode
> natively.
> I threw together some code for using the Unicode file routines in the Windows
> API to get around this, but it's a total hassle having to manaually peek/poke
> multibyte character strings. :(
Yeah, it's a big job, though. When it was brought to my attention that you
couldn't use the native sprintf() with unicode chars, I had to roll my own
inside of wxEuphoria. At first, I tried taking the eu code and beefing it
up to use wide chars, etc, hoping to transfer whatever I did back to the
interpreter once I got it working.
That idea went down in flames. Eventually, I just grabbed the minimum, and
replaced most of the interesting bits with wxWidgets::wxString calls.
Once you start delving into all of the areas that need to be upgraded,
it really gets overwhelming. And, of course, what about DOS, Win95 and
Win98 without the special unicode libraries?
There are a lot of questions that need to be answered, and a whole lot more
work that will need to be done. The short term solution is probably having a
special library for doing unicode stuff. EuCOM has basic unicode string
support. wxEuphoria now supports unicode, and will allow easy conversion
between wide chars and UTF8.
Also, the next version of euphoria will have peek2/poke2 routines, so that
will make the MB strings a bit easier to deal with.
Matt
