As we saw a few weeks ago, having a method that was "removed" because it no longer compiled can cause VM Traps. In my case, I was filing in code which (unwittingly) removed a class instance variable. At the end of the file in, there was initialization which attempted to store into the no longer present instance variable. Needless to say, that got me a GPF 53 and my image died. At the end of this, I had no evidence of what went wrong, just the GPF error.
Requested feature:
Change the "removing methods that don't compile" to replacing them with a CompiledMethod that will throw an error, reporting the compiler error that would have previously removed the method. Whether the new method retains the original source as its source, as a comment, or not at all is not a concern. Having execution that doesn't match the apparent source could cause confusion, so comment it out or replace it with the error code are probably better choices.
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To post to this group, send email to
[hidden email].
Visit this group at
http://groups.google.com/group/va-smalltalk.
For more options, visit
https://groups.google.com/d/optout.