Re: Euphoria 3.2 compatibility
Larry Miller wrote:
>
> I'm sure some people have considered this but many have not: Euphoria 3.2 or
> 4.0 in it's present form WILL cause many existing applications to break. There
> are 2 main causes.
>
> 1. Some programs use include files such as math.e, sequence.e, string.e, etc.
> Euphoria 3.2 adds these file to standard includes. This will cause errors if
> they define the same functions.
>
> 2. Many programs include files that define functions such as max(), min(),
> etc.
I think this is a reason to release it as 4.0. Then, instead of moving the
functions back to misc.e, remove the includes in misc.e of math and sequence,
since 4.0 is a major release.
Yes, undoubtedly, *any* new function added to Euphoria either core or
include/???.e *will* cause code to break. Even before I started on the standard
library this was going to happen, because, a few functions were added: peeks,
peek2s, peek2u, peek_string and poke2. Those are functions that many people use
already but are not part of 3.1, thus 3.2 before the standard library would have
broke many apps as well.
So, I am in strong favor of 4.0. In addition to 4.0, I can create an "Upgrade"
manual that states incompatibilities and what to do to make your app work in the
new Euphoria.
--
Jeremy Cowgar
http://jeremy.cowgar.com
|
Not Categorized, Please Help
|
|
