Re: Euphoria 2.5 Will Break Existing Code
Hello Al,
Let us see 2.5 released, if it will break
or it will not break only knows God ...
But for now your files:
allyoop.e
compile.exw
formulas.e
formulas.txt
have no any reason to be broken.
Only demo1.exw may be devided on two parts,
as Juergen suggested.
This demo has about 100 lines of code,
pure second part may have about 10 lines
from those 100.
Plus some correction in readme for 2.5.
You can also at least to update your package
and include interpreter 2.4 into this package.
It may forever work perfectly as currently
designed.
Just IMHO, sorry.
Regards,
Igor Kachan
kinz at peterlink.ru
----------
> From: Al Getz <Xaxo at aol.com>
> To: EUforum at topica.com
> Subject: Euphoria 2.5 Will Break Existing Code
> Sent: 15 feb 2004 y. 18:00
>
> Hello,
>
> Robert Craig wrote:
> -------------------------------------------------------
> >In the next release, with the clearer separation between
> >front-end and back-end, the interpreter will also
> >process the include (and all other source)
> >before it executes any code.
> >It will be simpler this way. I don't think a lot of
> >people are actually using the above "dynamic" include
> >technique, although it has been discussed on this list
> >from time to time.
> --------------------------------------------------------
>
> That breaks code, as in my AllyOOP program...
>
> Excerpt from AllyOOP readme:
>
> Basic discription:
> AllyOOP compiles formulas typed into an ordinary text file
> into function calls using 'Eval(i,x)' and stores them in an
> include file. The include file can then be included in the
> program, or this can be done on the fly by calling AllyOOP()
> and then including 'Formulas.e'. One demo for creating
> a dynamic include is enclosed with this package.
>
> Al
|
Not Categorized, Please Help
|
|
