Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'd think that scrubbing code of cusswerds should be de rigeur, because they can be a bit viral, and, in OSS, can reflect badly on the developer(s). So a Perl script to scrub such epithets from the source is probably a good idea.

    A Cautionary Tale:
    My opinion arises from a personal faux pas: during a fit of pique while bug-killing a particularly befuddling bit of code, I inserted some F-bombs into some diagnostics (the cause turned out to be a bug in Perl, btw, so the F-bombs may have been well deserved).

  • It's more of a problem in a language like Perl where the source is available and inspectable at runtime. Imagine if your webhost (or sysadmin) accidentally changes the error reporting behavior to allow exceptions to become visible to the user, and now they see the few lines of code around the exception... and it says something they find offensive or unprofessional. Heck, what if it says:

    # The following code is totally insecure and we
    # probably lose lots of customer credit card
    # info because of it!

    I try

    --
    rjbs
  • I once had some silly placeholder text accidentally make it into a print catalog. Often while working on this very large book if we didn't have a product description or photo we'd put something there just to take up some space on the layout... and to crack each other up. One product, "Nipple Clamps", nothing weird - something to do with guns IIRC, didn't have a description so I put in something like "Ow. That's gonna leave a mark!". Although that page and several other were actually changed later, the doc