Your implication that ECL should "note the error and then continue to
compile" somehow reminds a recent thread (probably on sage-devel)
where it was reported that some spkg sends compiler warnings to /dev/
null.
Unless you can *prove* that the special circumstance ("static typing
error in which a program which, in some circumstance, would do a list
operation on an argument which is an integer") can not occur, one
must assume that it is indeed a bug (not of ECL).
It is an impressive achievement of ECL to finally find it, after 35
years!
After being pointed to it by ECL, you might be able to cook up an
example in which the "suspicious" line of code will definitely be
executed, as you say, for the first time ever. Perhaps you will even
be able to trigger the error, and then fix it.
Simon
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
