OpenEuphoria

Re: Detecting the Eu version

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Dec 14, 2004
• 548 views

On Mon, 13 Dec 2004 19:02:26 -0800, Derek Parnell
<guest at RapidEuphoria.com> wrote:

>> Still hoping Rob will at least comment on
>> 
>> 	with 2.5
>> 
>> and hoping he will agree the '.' will distinguish it adequately from
>> historical stamping statements.
>> 
>
>However this only deals with the situation in which the entire program
>is incompatible with an earlier version. To deal with the situation
>where only part of the code is imcompatible we might additionally need
>a run-time function to return the Euphoria version.

Why? Is there something to prevent with statements in include files?


>I would suggest the machine_func() could be easily adapted for this
<snip>
>    if version() >= 2.5 then
<snip>
It doesn't matter how you code it, it won't get executed in time.
(It was possible in 2.4, it is not in 2.5) The user will see eg:

C:\EUPHORIA\INCLUDE\FILE.E:183
Syntax error - expected to see an expression, not an illegal character
          find(path_name[$], {' ', SLASH}) do
                         ^

instead of:

This program requires Euphoria 2.7 or later.

OK, you can bind/translate and the problem goes away, but that may be
a problem for people releasing open source, and is no longer an option
for anyone releasing library components such as win32lib.


BTW, I am not asking for a single source which "needs" 2.5 to somehow
run on 2.4.  Now that would be silly.

Regards,
Pete