OpenEuphoria

Re: Euphoria 2.5

• Posted by Robert Craig <rds at RapidEuphoria.com> Sep 07, 2004
• 611 views

Vincent wrote:
> I was just wondering what new features you implementing in version 2.5?

- a complete open source Euphoria interpreter written in Euphoria
  and 100% compatible with the official RDS interpreter (but slower)
- $ feature
- crash handler
- namespace improvement
- "-con" option in translator and binder will give you
  a Windows console mode .exe
- totally new binder
  - quick start-up - parsing has already been completed
  - fairly small .exe - you bind with the back-end only,
    not the full interpreter
  - shared front-end - no possibility of glitches or 
    differences with interpreter
  - better shrouding since the shrouded intermediate language,
    not the (shrouded) source is stored in the .exe
  - option to have full ex.err debug information when your user
    causes a crash (but your source is still not in the .exe)
- the usual assortment of bug fixes, documentation fixes,
  small translator code-gen improvements, trivial enhancements etc.

> And when you plan to release the alpha version of Euphoria 2.5?

I'm getting closer. I don't have a specific date in mind.
This project keeps getting more and more complicated. It takes
time to fully test all components on all platforms. 
Hopefully in a month or so I'll be very close, but I think it's
better for me to test things well and handle a small number of
bug reports, than put out something quick and sloppy and get flooded
with reports.

> Also I'm aware that you have written the initial interpreter in 70/30 hybrid
> code. 70% being Ansi C, and 30% being Euphoria, my question is how will that
> effect speed since the main interpreter is no longer 100% C coded like version
> 2.4
> and below? 

The front-end (scanning/parsing) is now written in Euphoria. 
It's translated by EtoC to C, compiled, and linked with the 
hand-coded back-end. The back-end is in carefully hand-coded C as before 
for full speed. So theoretically the front-end (only) is a bit
slower. But you won't notice it unless you have a very old machine,
and a very large program, and you watch the start-up time carefully.

> And for the Eu to C v2.5 translator that I believe you said would be
> written in 100% Euphoria code, how will that effect the compadability with
> various
> C/C++ compilers?

The fact that it's now written in Euphoria has no effect on 
compatibility with C compilers. It outputs the same C code
as before (except for a few bug fixes and performance improvements).
It takes slightly longer to run (an extra few seconds), 
but the subsequent C compiles still take a lot longer than the 
translation step.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com