Re: Starting project EuphoriaVista Interpreter
- Posted by mattlewis (admin) Jan 03, 2009
- 1279 views
- Most new programs targeting the MS Vista and later are meant to be written in "dot net" (.NET) a compiled executable format with a program compress inside it similar to Euphoria's *.il method. [Sun's Java uses a similar technique to produce Java class files.]
I think that MS would *like* for everyone to use .NET, but I don't think that there's any danger of native code going away. Having said that, I did have a mostly working (mostly, as in, not all features of euphoria were supported) MSIL version of ooeu working. It outputted MSIL code which used an assembly written in C# that served as the 'back-end.' It was horribly slow, due to the way I emulated euphoria's datatypes. There's probably a better way.
- 64-bit Operating Systems. A newer data type "long long" or "__int64" is used extensively, and the standard method for calling functions is different, but uniform across all function calls.
At some point, euphoria will likely make the jump to 64 bits, but I think there's a lot of work to be done before that. And 64-bit operating systems aren't ready for prime time, other than in the server room.
- Euphoria v3.1.1 still uses the "functionA" version of the Windows API. Many older libraries use outdated machine code that wont work on Vista.
I think you must be thinking of win32lib. It will take a fair amount of work to make it work with unicode. [shameless plusg]I'd recommend using wxEuphoria, since it already does unicode.[/plug]
Matt
