On 18 Dec 2012, at 10:05, dimitris chloupis <[email protected]> wrote:
> There is no such thing as too lengthy comments or too many comments as far as > me is concerned > Actually I would prefer if all that effort you are asking here would be spent > on documenting those libraries in the first place. Trying to figure out > Morphic by reading code is definetly not fun. Euh, I am not sure what your remark has to do with what I wrote about a specific feature, although I can understand your frustration with Morphic. All the open source code that I wrote is clean, unit tested and documented. I don't think you can ask anybody to start documenting something like Morphic… > From: Sven Van Caekenberghe <[email protected]> > To: A friendly place where any question about pharo is welcome > <[email protected]> > Sent: Tuesday, 18 December 2012, 10:43 > Subject: [Pharo-users] Nautilius Method Source Pane Coloring > > Hi, > > The way Nautilus colors method source panes is absolutely great: if reminds > you of paying attention to long methods in a gentle way. > > However, right now the metric is 'number of characters in method source', > while it should be more related to complexity. > > For example, using long names for variables or messages will be counted as > negative towards this metric. Worse even, lots of comments, which is good > most of the time, also counts as negative. > > Number of nodes in the AST would be one solution, but maybe a too expensive > one. > > Maybe quickly scanning for tokens while skipping whitespace and comments and > then counting the tokens would be doable ? > > Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
