On Jun 26, 2012, at 7:04 PM, Andrew P. Black wrote:
On 25 Jun 2012, at 08:50 , Graham McLeod wrote:
There still remains the question of how the system allowed the situation to arise in the first place tho..
Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker.
Yes! As far as I know, there is no bug reported regarding any problems with this... we are, though, completely rewriting this part of the system for 2.0: -> the old system change notifycation mechanism will be replaced with a new system base on Announcements. -> the old class builder will be replaced by one based on the work in the context of first class Slots (see the OOPSLA Paper of Toon and Camillo: http://scg.unibe.ch/scgbib?query=Verw11b&display=abstract ) -> instead of recompiling, we will just change the offsets of the iVars on the level of the bytecode intermediate representation of the new pharo compiler. This is not yet in 2.0... but we are woking on it. Marcus -- Marcus Denker -- http://marcusdenker.de