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.
  • Here's a timeline:
    1. I write an Acme module.
    2. Randal decides that the instructions in the README aren't good enough for the world at large, and mails me to request I change the perfectly reasonable install process of my module.
    3. I give him a civil, unequivocal reply, refusing. (What's that? A civil reply? But Randal didn't post that [perlmonks.org]. Funny!)
    4. Randal refuses to take no for an answer and tries to be The Champion Of All CPAN Users.
    5. I detect a whiff of hypocrisy and post the now-famous reply back to him.
    6. Randal pro
    • Since a couple of people have asked me: I think Randal should not have posted the correspondence. I also feel that instead of giving the reply that you did, you could have chosen not to respond or to have responded in a different manner. Admittedly, I sympathize with getting irritated and sending out an email that reflects that. However, when I've done that, if it has an effect at all it's usually bad. Now because of what you have written, some people will have a bad opinion of you (and some will think