[BUG] Monticello - loading class changes
dway at riskmetrics.com
Tue Dec 9 05:28:50 UTC 2003
On Monday, December 8, 2003, at 07:20 PM, Avi Bryant wrote:
> On Dec 8, 2003, at 4:05 PM, Doug Way wrote:
>> Avi Bryant wrote:
>>> I'm not used to Squeak complaining the instant I add the instance
>>> variable, only the next time I modify the method. Has this changed?
>> At first I thought this was due to a recent update which affected
>> variable definitions (5569), but it looks like it's done this since
>> 3.6, at least. But only for block variables, not method temporaries,
>> as Chris said.
> Do we *want* it to do that?
Yeah, I'm not sure. I just tried it in 3.2 and the behavior is still
the same, so it's been like this for awhile.
It is sort of annoying that it warns you about the block variables and
not method temporaries. Both or neither would make more sense.
> Seems like this would show up with any kind of code update (it must be
> possible to trigger this problem using changesets as well, right?).
> And whatever the code is that does the recompilation seems to handle
> the shadowed temp var methods just fine (it will update any other inst
> var refs if the order has changed, so it's not like those methods just
> get ignored).
More information about the Squeak-dev