OpenEuphoria

(no subject)

• Posted by Alan Oxley <fizzpop at icon.co.za> Dec 14, 2004
• 1158 views

Irv said: 

I'm surprised you didn't see the problems with this idea:

1. It prevents Rob from ever fixing even the smallest bug in the 
"official" release - which, as we know, tends to be the *only* release 
for a year or two. Very puzzling to get a message saying you need "2.5" 
when you *are* running 2.5, but the library which is reporting the error 
was written for the previous (un-bug-fixed)  crc.

2. How do we ever guess the crc's of versions 2.6, 2.7, .... etc. so that 
our programs can also run on those? Crystal balls don't work, you know.

My reply:
You said it yourself - if the official is the only release, then the CRC
won't change? But consider if the convention of "2.5.01" is used,
or even (possibly less usable) return a string "Euphoria vx.x 12th December
2004".

Whats the problem with generating and storing a CRC for every release? There
are not THAT many! Why would you want to test for future versions, if
they don't exist..? The reason for testing is to ensure your code is
compatible with a feature that does not (yet) exist? Sorry, I don't get this.
Also, there is no reasons why two or more CRC's cannot return the same
EU version like "2.5" if what the CRC's identify are known bugfixes from Rob.

I'd still like Rob to give us a proper function though, as first prize.
My suggestion is mostly aimed at testing for earlier releases without 
having to change them.

Regards
Alan