On Sun, May 31, 2015 at 1:47 PM, stepharo <[email protected]> wrote: > Oki > > You see when you browse the code you wonder if you should pass a class tag > or a method protocol. So I will update the comment.
> To me category is a bit too much overloaded. There are 848 methods containing the string 'category', some of which are not related to cleaning packages. So I'm curious what sort of general approaches might be useful to scope this cleaning: * manually identify by looking through code * rename all methods to something like #packageTag, and leave halt in the place of the old #category method, to fail-early for external users of #category. * add MetaLinks to 'category' methods which look back through a couple of stack levels to search for parameters that are strings matching package names. cheers -ben > > Stef > > Le 31/5/15 07:35, Tudor Girba a écrit : > > Hi, > > This is not dead code, only the default Pharo debugger does not make use of > it. > > It is used in the GTDebugger for helping group actions by their category. > The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <[email protected]> wrote: >> >> Hi andrei and others >> >> we have >> >> DebugAction>>category >> >> ^ category ifNil: [ self defaultCategory ] >> >> DebugAction>>defaultCategory >> >> ^ nil >> >> And I tried to browse the senders by scoping the search to the Debugger* >> packages >> and I got no sender. >> >> I have no direct user either. >> So do you know if this is deadcode? >> >> Stef >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >
