Re: [Pharo-users] super super

Worst than that :) In theory I can refactor the super code and commit, but SmalltalkHub does not let me commit even I have RW access... So I have to knock at the Philippe's or Masashi's door so they can commit it for me. It's annoying to bother busy people. Anyway enough small talk ;) Le

Re: [Pharo-users] super super

yes, something like factoring out in its own method a chunk of code in super super method I want to access from my subclass. Le 21/01/2017 à 19:32, Sebastian Heidbrink via Pharo-users a écrit : > Now I am wondering what you guys are meaning by "hooks"? -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] super super

--- Begin Message --- Hi Hilaire, I had this once, too. No time to refactor or rethink my subclass structure. Now I am wondering what you guys are meaning by "hooks"? Something like this? A ClassExtension? SuperSuperClass - methodIWantToReach - myExtendedMethod ^self

Re: [Pharo-users] super super

Out of curiosity, wouldn't it be better to temporarily duplicate the code in your class and talk with the upstream owner? (That would be my usual approach.) Peter On Sat, Jan 21, 2017 at 06:04:12PM +0100, Hilaire wrote: > Agree on the hook. However the super class are not mine. Not an ideal >

Re: [Pharo-users] super super

Yep, it is the first situation I face where I need it in 10 years of Smalltalk/Pharo. Otherwise I will refactor super class package, may be I should Le 21/01/2017 à 11:19, stepharong a écrit : > pay attention and to not use it. It is evil to use that in plain domain > code. -- Dr. Geo

Re: [Pharo-users] super super

Agree on the hook. However the super class are not mine. Not an ideal situation Le 21/01/2017 à 11:19, stepharong a écrit : > No and I'm happy that this is like that. > I think that it means that you need to create special hooks in the super > superclass. -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] super super

Thanks Henrik Le 15/01/2017 à 22:33, Henrik Nergaard a écrit : > menu perform: #isMorph withArguments: #() inSuperclass: ProtoObject. "Error > #isMorph not implemented" -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] super super

ithArguments: #() inSuperclass: ProtoObject. "Error #isMorph not implemented" Best regards, Henrik -Opprinnelig melding- Fra: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] På vegne av Hilaire Sendt: 15 January 2017 21:42 Til: pharo-users@lists.pharo.org Emne: [Pharo-user

Re: [Pharo-users] super super

You should be able to call super super, as high up as you need to go. At least you can in VA Smalltalk. Brad Selfridge 913-269-2385 > On Jan 15, 2017, at 3:42 PM, Hilaire wrote: > > Hi, > > Is there a way from an instance to access a method situated 2 layers up > in the

[Pharo-users] super super

Hi, Is there a way from an instance to access a method situated 2 layers up in the class hierarchy? A kind of super super. Thanks Hilaire -- Dr. Geo http://drgeo.eu