OpenEuphoria

Re: Missing library

• Posted by Tommy Carlier <tommy.carlier at pandora.be> Jul 14, 2004
• 764 views

Kat wrote:
> On 13 Jul 2004, at 13:07, Tommy Carlier wrote:
> > posted by: Tommy Carlier <tommy.carlier at pandora.be>
> > Pete Lomax wrote:
> > > <guest at RapidEuphoria.com> wrote:
> > > >As it stands, not even Euphoria can programatically retrieve its own 
> > > >version, can it?
> > > 
> > > This has been discussed before. You can try opening a %EUINC% file,
> > > should start with eg "-- Euphoria 2.4". But in general you are right,
> > > there is no way to properly do this.
> > 
> > I have an idea for an easy-to-use/easy-to-implement versioning system for
> > the
> > next version(s) of Euphoria: have the interpreter set an environment
> > variable
> > with its version, like EUVER="2.5 beta". That way, programmers can easily
> > access
> > the version-info and no new function has to be created. If the variable
> > can't be
> > found, the program knows its version 2.4 or earlier. No extra function means
> > backward compatibility.
> 
> Jeeze, you might as well say everyone hasto write code in their program to 
> check all the stuff you write to the envvars, and then update all their 
> contributions in the archives! Why not go further, and say they haveto include
>
> the interpreter that their app was written to use??
> 
> Can two play this game?
> Kat

:D
I really enjoyed this one. But it's not quite the same.

I wrote my sarcastic comments on your message, because you were attacking me
while I had done nothing wrong.

You are *attempting* to write an equally sarcastic comment on my innocent
message that is not attacking anybody, just suggesting something.

There is a big difference between your:
> Perhaps not all the required files are included in the .zip file?
> (*They should be*, else ...)

And my:
> *I have an idea* for an easy-to-use/easy-to-implement versioning system for...

--
tommy online: http://users.pandora.be/tommycarlier
Euphoria Message Board: http://uboard.proboards32.com