OpenEuphoria

Re: Euphoria 3.2 compatibility

• Posted by Matt Lewis <matthewwalkerlewis at ?mai?.com> Apr 24, 2008
• 667 views

Jeremy Cowgar wrote:
> 
> So, with this in mind, the current SVN (be it 3.2 or 4.0) will break things
> if the user, say, defines min, max or say, remove as a global in one file and
> then also includes sequence.e. Because their file and sequence.e define those
> functions.

sequence.e is a new file, so there's no backward compatibility involved.  It's
messing around with misc.e that will break some stuff.  That's always been
a troubling file to me.  It deserves to be broken up.  Anyone using any
routines that were moved from there (most likely to break:  sprint, reverse)
will have to change code to include the new functions.

I think this break in compatibility is probably the best argument for bumping
the major version number.
 
> So, we are breaking some things. Since peek2s is a built-in, it is not
> breaking
> anything. Correct?

Correct.

Matt