Re: Multi-Platform Support
At 02:38 PM 14-03-1999 , you wrote:
>> What would be great is see an Euphoria compiler. I've said on the past that
>> an Euphoria compiler wouldn't speedup THAT much code execution, but it do
>> have many benefits. An .obj output would do the job. I don't expect a small
>> company like RDS develop their own linker, librarian, resource compiler,
>> etc. The Lcc32 free compiler comes with those tools already. I can imagine
>> building Euphoria coded DLLs, mixing Eu code with C/Pascal/Asm, etc.
>
>You cant compile a language meant to be interpreted.
>All 'compiling' really is, is do some/a lot/huge amount of optimization at
the cost of 'compile-time'.
>Take the JIT-technology for Java, is it interpreted or compiled ? Hard to
tell.
>What you want is a way to effectively communicate in *any* or (preferably)
*all* ways.
I know it makes little sense building such a compiler if it were for speed.
But the power of mixing and combinig Euphoria with other tools/languages
makes it very, very interesting. I also remember Rob curriculum said that
he worked many years developing compilers... he must have some expierience
with code generation ;)
>I am in favor of being able to bind to a DLL. Off course we would need a
new procedure which we use to define the exact
>arguments and pointers/value issues. (if structures and arrays were
available btw, the pointer/value issue would be even less of
>a problem)
>I'm under the impression though, that object and library files are
compiler dependant and exist in many flavors, but I might be
>wrong. (let's hope so)
I think you are wrong (but not sure). I know that Borland's libs and
Microsft's are supposed to be incompatible, but have never heard of
compatibility problems with OBJs. If we could have OBJ output of our
Euphoria code we would also need an RTL (mainly the sequence engine and
garbage collector), these are usually distributed as libs, but a bunch of
objs would work fine. A couple of make files for popular tools (Watcom C++,
VC++, Borland C++, etc..) and we are ready. The linker will then make your
EXE or DLL. Cool!
Another alternative would be to generate ASM code, the developer compiles
it with it's favorite assembler (NASM comes to mind,
http://www.web-sites.co.uk/nasm/) and then links it with the RTL OBJs.
One little thing: It should only be for Win32 (and Linux), I belive
distribution of CAUSEWAY as OBJ would be against their license. Unless RDS
change Causeway for freely distributable dos extender (like WDOSX,
http://www.geocities.com/SiliconValley/Park/4493, works with Watcom).
Regards,
Daniel Berstein
[ daber at pair.com ]
|
Not Categorized, Please Help
|
|
