Re: Porting Euphoria
Mathew Hounsell writes:
> Give me any small code fragment and I will translate it.
Ralf writes:
> Robert, I have to admit this looks 'do-able'. If are able to
> keep your basic classes' code hidden, and provide a
> simple tojava.ex program in the /bin directory, I don't have
> to explain how useful this can be.
There's no question that it's technically "do-able"
(although a lot of work) to convert Euphoria code
into any other language "X".
The resulting code in language X would be larger and
slower than what an X programmer would write by hand,
but it would work.
The main issues for RDS are business ones.
Any effort in this area would almost certainly
involve revealing, perhaps indirectly, our algorithms
for making a fast Euphoria interpreter, and we might
also have to provide the algorithms used in all
of the library routines (although putting them in a
*machine-code* .DLL would help - byte codes aren't
very secure). The translator would have to be limited
in the PD edition to translating 300 statements maximum.
Another issue is that once people translate their
Euphoria program into language X, they might
decide that it's easier just to modify the
language X code and forget about using the translator.
Maybe they'll decide to start learning language X, and
abandon Euphoria.
Translating to Java would restrict you to doing things that
are possible in Java. Last time I checked, that does *not*
include peeking and poking directly into memory,
dos_interrupts, and all sorts of stuff that's specific to
a particular operating system.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
|
Not Categorized, Please Help
|
|
