OpenEuphoria

Re: Requests for Eu 2.5

• Posted by "Mike Nelson" <MichaelANelson at worldnet.att.net> Jan 16, 2004
• 486 views

Andy Serpa wrote:


> It would be nice to be able to optionally save the intermediate
> already-parsed Euphoria files (I think you called it IR code previously)
> that could be run be the interpreter, but skipping the parsing step.
> That would be especially nice for cgi scripts to get the most speed and
> the least overhead...
>

I would also like to see this.

I would like to the IR specs published when they are finalized--I would be
willing to have this done as part of the source code license, but I'd prefer
it free for all. I envision any Eu program being allowed to generate IR
code. This  would be a boon to scripting because your program might well
need only a limited parser rather than the full Eu interpreter parser,
leading to easier maintainabiltity. It would also allow for highly
customized script languages to be handled more easily.

I wonder if the front end and the back end shouldn't be separate programs.
The front end would generate IR code in memory and shell to the back end,
passing the size and address of the memory block. The back end could also be
invoked directly on an IR file.

I would be willing to pay a fairly decent sum ($100 or so) for a Eu
Professional Edition that would allow me to bind a program with an alternate
front end and/or an alternate back end.

-- Mike Nelson