[BUG] [FIX] class-side inst var def'n (was RE: deficience in Squeak)

Peter van Rooijen squeak at vanrooijen.com
Sat Nov 22 11:00:40 UTC 2003


From: "Scott Wallace" <scott.wallace at squeakland.org>
> At 2:47 AM +0100 11/22/03, Andreas Raab wrote:
> >  > Recently I defined a class X and gave it a class instance variable. A
> >>  message popped up saying something like "X is an existing class in the
> >>  system, changing it is not recommended. Proceed anyway?".
> >>  Turns out there was nothing special going on anyway (at least not that
> >>  I've noticed).
> >
> >What it means is that you were defining a NEW class where one with the
same
> >name already existed in some other category. Typically this is a lethal
> >problem - I would go sofar as to claim that the browser shouldn't allow
this
> >at all. What you're doing in this case is dumping an existing class
> >definition because there's no way for you to see that class' definition
at
> >the point where you change it.

Andreas,

I did not receive your post, only saw this part quoted in Scott's message.
In my case I had just defined the class myself (without any warning, I
wasn't using an existing class name), and my browser was pointing to it.

It would seem that Scott's analysis that this is a bug is in fact correct.

> Of course Andreas is correct about the general point here.
>
> However, what's showing up in the particular case that Ye Yuan
> mentioned at the start of this thread is in fact an actual and
> long-standing bug that shows up whenever you try redefine a
> class-instance-variable structure on the class side of a browser.

[snip description of the bug]

Regards,

Peter




More information about the Squeak-dev mailing list