<div><span class="gmail_quote">On 22/06/07, <b class="gmail_sendername">stephane ducasse</b> <<a href="mailto:stephane.ducasse@free.fr" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">stephane.ducasse@free.fr
</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
it would be good but<br> - the harvesting team should harvest them</blockquote><div><br> </div><div>Harvesting team?</div><br><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
- you should pay attention that the speed is not dropping</blockquote><div><br class="webkit-block-placeholder"></div><div>Is there a test suite or something I can keep running to check that sort of thing? My gut feeling is to go for clarity first, then (ideally) worry about optimization once I can run stuff against a profiler.
</div><br><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"> - I would focus a set of clearly identified packages and see how it<br>goes.</blockquote><div>
<br> </div><div>I just opened a new project, ran SLint against OmniBrowser-*, OB* and OR* and started in on the long methods (the usual suspect is turning out to be O[BR]Cmd*#execute).</div><div><br class="webkit-block-placeholder">
</div><div>SLint also throws up a whole host of dubious uses of isKindOf, which I'd like to replace with testing methods on the various nodes, but I'm scratching my head to come up with names. An 'isBehaviorOrTrait' test wrote itself though.
</div><div><br class="webkit-block-placeholder"></div><div>Incidentally, I'm finding the CodeFinder to be an absolutely indispensable tool for deciding when to pull out a method: Just write a CodeFinder query matching the potential method fragment and run it to find out if multiple methods are doing the same thing.
</div></div>