dave_m

• About: I'm an amateur Perl geek and the author of ClamTk, a GUI written in gtk2-perl.

Recent Actions

• Posted #!/usr/bin/perl -evil to dave_m

  I came across some Perl used for defacing websites. Not the standard stuff that adds a picture or scriptkiddie text, but adds an iframe to a website that was used (probably unknowingly) with the Eleonore Exploit Kit.

  The Perl just globs standard html files (e.g., html, asp, php, etc), open…

• Commented on Commenting on comments
  Thanks for clarifying. I'm not going to stress about my 14% then. :)...
• Posted Commenting on comments to dave_m

  This statement is on my Ohloh page for ClamTk:

  "Across all Perl projects on Ohloh, 28% of all source code lines are comments. For ClamTk, this figure is only 14%.

  This lack of comments puts ClamTk among the lowest one-th…

Recent Actions from dave_m

Comment Threads

• mirod.myopenid.com commented on Commenting on comments

  Does the 28% figure also include the POD? That would both make sense and make it quite meaningless IMHO.

• Erez Schatz commented on Commenting on comments

  I agree, ohloh's metrics harks of pointy-hair managers who count lines of code, or number of check-ins but not what is actually written in them. I don't want to know how many lines of comment a project written in a less verbose language like Java or C# would require (less verbose syntax == more verbose code) to satisfy such a ratio.

• Shlomi Fish commented on Commenting on comments

  Like other people here, I'm also not a fan of excessive commenting. Like Martin Fowler says in the book Refactoring, often the need of a comment is indicative that the code is not clear or factored enough. So I think that Ohloh measurement is silly and should be ignored, because it's not indicative of the real world worth of your code.

Responses to Comments from dave_m