OpenEuphoria

Re: Multi-Platform Support

• Posted by Daniel Berstein <daber at PAIR.COM> Mar 14, 1999
• 769 views

At 11:15 AM 14-03-1999 , you wrote:
>Robert
>
>  I think that the users should develop their own DLL's if they want to
>  interface to wxWindows. I think you should spend more time developing
>  new low level functions like get segemnt of a allocted memory block,

Segments in Euphoria? Well on Win32 that makes no sense... on Dos32
neither! Euphoria (for DOS32) runs over the Causeway DOS extender, giving a
flat address space to the interpreter. Any alloted memory is (I belive)
handled by Causeway, so at it's best Euphoria might "publish" some
Causeway's memory managment routines. Something that I'm not sure anyone
could properly use without Causeway documentation (it's a commencial
product, http://www.devoresoftware.com/cwwmain.htm).

>  (match binary) binary search of a memory block, etc. In other words
>  give the user more and easier to use tools so the user can extend the
>  language. This is something that the user can't do because he does not
>  have access to the source code. Why spend your valuable time on a
>  a interface that all users may not use or need. Just give us more tools
>  and capabilty at a lower level. That is something everyone can use.

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.

BTW Rob:

I was playing with EXE packers (my best choice is ASPack,
http://www.entechtaiwan.com/aspack.htm) and was unable to compress bounded
Euphoria programs (thinking about the Eu installer). The appended source is
trimmed out and the exe ask for the file to run. Then I tried compressing
pdexw.exe, so the bounded program use the already shrinked interpreter.
Same result. Have you any idea of how to make it work. The later method
should have worked... why it doesn't?


Regards,
          Daniel  Berstein
         [ daber at pair.com ]