On Sun, Apr 22, 2012 at 3:53 PM, [email protected] <[email protected]>wrote:
> Ok. > > Looks like there is still a lot of dirty corners under the hood by looking > at this list of senders... > Indeed. But the first step is to identify them, right? So at least we know those dirty corners ;) > > Phil > > 2012/4/22 Mariano Martinez Peck <[email protected]> > >> >> >> On Sun, Apr 22, 2012 at 11:55 AM, Stéphane Ducasse < >> [email protected]> wrote: >> >>> we use self flag: #fixMe >>> you can then query either #fixMe or flag: >>> >>> and yes this is a good idea to mark things and create bug entries. >>> >>> Stef >>> >>> >>> On Apr 22, 2012, at 11:18 AM, [email protected] wrote: >>> >>> > While looking around in the image, I am in need of knowing where I >>> found thngs that either puzzle me or are "wrong" (well, a code smell). >>> > >>> > What I do is that I put pragmas in there like this (not that this >>> sample is meant to be representative) >>> > >>> > privCleanTextConstants >>> > <fixme> >>> > TextConstants TextSharedInformation removeKey: #DefaultTextStyle. >>> > TextConstants TextSharedInformation removeKey: >>> #DefaultMultiStyle. >>> > TextConstants TextSharedInformation removeKey: >>> #DefaultFixedTextStyle. >>> > TextConstants TextSharedInformation removeKey: StrikeFont >>> defaultFontKey. >>> > >>> > Smalltalk allClasses select: [:c | c sharedPools includes: >>> TextConstants] thenDo: [:c | c compileAll ]. >>> > >>> > And I can then find back the things with: >>> > >>> > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. >>> > pc collected size. "(Print It: 1)" >>> > pc collected explore. >>> > >>> > And then finding back the Class and Method Name >>> > >>> > Building upon that, why not do what is done in other environments >>> (well, I've got that in PHP, Java, ...) and use: >>> > >>> > <todo:do this and that> or plain <todo> >>> > <fixme: this and that> or plain <fixme> >>> > <issue:issue#> >>> > >>> >> >> As Stef said, we usually use #flag: Normal cases are #flag:todo, >> #flag:fixMe, etc .. and the browser is aware of that and shows you a flag >> in the icon of the method. >> >> >> >> >>> > And have a specific tool to help the navigation (explore is fine for a >>> moment but...) >>> > >>> > This would allow us to have an idea on the technical debt inside the >>> system, broken down by areas if we start leveraging Packages. >>> > >>> > What I do not know is how much stress this would put on the system. >>> Are pragmas eating a lot or a just markers? >>> > >>> > Phil >>> > >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: [email protected]| > Web: > http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > > -- Mariano http://marianopeck.wordpress.com
