OpenEuphoria

Re: Requests for Eu 2.5

• Posted by "Juergen Luethje" <j.lue at gmx.de> Jan 16, 2004
• 493 views

Rob wrote:

<snip>

> At the moment I've just finished converting many thousands
> of lines of C code to Euphoria. The E to C Translator,
> which was formerly written 100% in C, is now written
> 100% in Euphoria. The new Translator is successfully
> translating large programs such as Judith's IDE
> (93,000 lines). The Translator even translates *itself*
> successfully.

This sounds great! I'm curious about the next Euphoria release.

In the current version of the translator, there is still that glitch
concerning abort(). When the argument to abort() is not 0, translated
programs are not compatible with interpreted programs. When the
following program:
     puts(1, "Hello!")
     abort(1)
is interpreted, it terminates immediately, as expected.

When translated and compiled, a console window pops up, showing a
blank line, and "Press Enter..." on the next line, waiting for the
user pressing [Enter], before it closes the window.

Firstly, I think interpreted programs and translated/compiled programs
should be as compatible as possible.

Secondly, this behaviour often is not desired by the programmer, and
s/he is not able to change it (except by changing the translated C code).
For me, abort(1), abort(2) etc. currently is unfortunately completely
useless in compiled programs.

I would appreciate it very much, if abort() would work in
translated/compiled programs exactly the same way as it currently works
in interpreted programs. If the programmer wants her/his program to
prompt the user, it is *very* easy to write the appropriate Euphoria
statements into her/his program her/himself. But the difference then is:
The programmer has the control what happens in her/his program, not the
translator. Actually the bottom line, why I started to write computer
programs, is that I want to have as much control about what my computer
does as possible. So I want any programming language to *give* me
control.

> Next, I'll get the Interpreter working using 30% Euphoria
> and 70% C. It will share the new Euphoria-written
> front-end (parser and scanner) with the Translator.
>
> Things are going faster on this than I expected,

Sorry, but your words make me curious: 
Will the new Euphoria version probably be released this year?

> and it's going to be very useful to have all this
> stuff written in Euphoria. The speed of the Euphoria
> code is at least as good as I expected, and I can use
> profiling to analyze the hot spots, something that
> wasn't easy in C.

Regards,
   Juergen

-- 
 /"\  ASCII ribbon campain  |    |\      _,,,---,,_
 \ /  against HTML in       |    /,`.-'`'    -.  ;-;;,_
  X   e-mail and news,      |   |,4-  ) )-,_..;\ (  `'-'
 / \  and unneeded MIME     |  '---''(_/--'  `-'\_)