Re: 2.4 Official Release - machine level exception
On Sat, 12 Jul 2003 00:43:52 -0500, gertie at visionsix.com wrote:
>Hmm, that might explain why some programs only run with trace, and crash=
=20
>without trace. I think i'll delete all those assignment ops.
BTW, It's only subscripted assignment ops, Kat.
I spent pretty much all of Thursday on this, anyone running on 2.4
should not be worried at all (IMHO), since it identifies the line it
is having a problem with interpreting correctly (2.4 tells you about
the machine level exception), and virtually any change you make to the
code makes it go away.
In contrast, a global edit (which I accept may be a valid option for
pre-2.4 users) just might introduce a much more annoying bug, or
indeed move a previously working subscripted assignment op in 3rd
party code onto a critical boundary. (rare, but possible)
Same deal, I think with library authors: even if we assume zero
introduced typos, if they chose to remove subscripted assignment ops
they are just as likely (being highly unlikely in either case) to stop
users' code working as to help them any.
Just my tuppenceworth,
Pete
|
Not Categorized, Please Help
|
|
