"copy class"
or "copy category"
functions are very helpful when creating experimental versions
of new classes - they allow for very quick class duplication.
So, instead of modifying any existing class, it is better to either create a copy of
an existing class, or to create a new empty one and copy some methods over from the original one.
Then test & debug the new class for perfection.
When done, you can override the old class with the class "class rename"
function.
This approach is especially suggested when you modify classes which are used by
the system itself, since bugs in those may lead to subtile errors or even crashes.
(just consider modifying ScrollBar
to make it err somewhere; since the Debugger
uses scrollBars too, it may have problems coming up. As a result, you
might be forced to quit smalltalk and restart your session).
We suggest that you save a snapshot image BEFORE starting to modify any critical system class - actually, its a good idea to do regular snapshots in any case.
Since the source information in a method is simply the filename+filePosition, this information is wrong after such a change.
A recompile (using stc) followed by a relink of the smalltalk executable, should give you a version with correct (up-to-date) source information. (however, the demo version does not include stc - here you have to undo any outside world editing, and only change methods from within the SystemBrowser).
We recommend use of the sourceCode manager, which is able to access a classes
sourcecode from the source repository, and does not need source files.
Here, the above problems are unlikely to occur (unless someone changes the classes
version identification manually ...)
Copyright © 2000 eXept Software AG, all rights reserved
<info@exept.de>