On Thu, May 3, 2012 at 2:15 PM, Benjamin < [email protected]> wrote:
> That a problem that right now you have to remove the inst var, add it > higher in the hierarchy and recompile everything :s (which is done normally > when you have changed the description) > You have to recompile everything the same because the ivar offsets should've changed :) > > But allowing duplicated inst var may lead to java style issues :s > > I not really have better idea now ;s > > My 2 cents, > > Ben > > On May 3, 2012, at 2:03 PM, Marcus Denker wrote: > > > > > On May 3, 2012, at 2:01 PM, Stéphane Ducasse wrote: > > > >> > >> On May 2, 2012, at 2:12 PM, Marcus Denker wrote: > >> > >>> Issue 5738: do allow the same ivar in the hierarchy > >>> http://code.google.com/p/pharo/issues/detail?id=5738 > >> > >> Do we really want to let the user define instance variables duplicated > in the class hierarchy? > >> I think that this is not really a good move. But I did not browse the > issue because I do not have internet. > >> > > How then do you move a variable up in the hierarchy? > > > > Marcus > > > > > > -- > > Marcus Denker -- http://marcusdenker.de > > > > > > >
