Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

  (email not shown publicly)

Journal of Alias (5735)

Thursday June 11, 2009
10:45 AM

Source code should look professional...

[ #39116 ]
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • That commit threw out a lot of useful information. When someone comments "I don't know what this fucking function is doing when I call it", the confusion is important.

    If you think that having "naughty" words is not okay in your source, fine (thanks, nanny). But please don't remove useful information just to delete the f-word.

    • Agreed. And he was totally inconsistent. Sometimes he'd just replace the naughty word, sometimes he'd remove the entire comment. He even removed an entire debug line because of a naughty word.

    • I agree with the sentiment of the committer, but I also agree that the commit has thrown out useful information. Removing comments which at least give the reader an understanding of what's the author was thinking, just seems weird. Rewriting them would have been fine (and is what happened for most of them). As an example, the code goes from having the following:

      if (pmi == NULL) {
          /* Server response is *really* f*****d up,
           I guess we just pretend it never happened? */

  • ... Ned Flanders could write all our code.

  • It's really too bad that "professional" now means to most people "unoffensive". I wish people would just say "unoffensive" when that's what they mean.