in reply to Re^8: Web-designing using PERL
in thread Web-designing using PERL

"You seem to be certain one is wrong, and the other right, yet, you're not sending a patch to fix it."

But neither are you. You are, however, getting some down votes. Perhaps next time you quote things like "except when it doesn't" and "but don't tell anyone I said that" you will realize that, how do you limeys say it ... someone is takin the piss outta ya. "Chill, Winston!"

Replies are listed 'Best First'.
Re^10: Web-designing using PERL
by JavaFan (Canon) on Mar 26, 2012 at 23:51 UTC
    Why should I send in a patch? I do not care whether people think PERL is an acronym, or whether it should be spelled PErl or PeRl or perl or Perl. I think the documentation gives people every reason to think Perl is an acronym, and the documentation has been doing that since perl 1.0.

    I do care about people getting flak for thinking so.

    As for any potential downvotes, if I cared about them, I would have posted as an Anonymous Monk.

      "Why should I send in a patch?"

      Because you have better spent your time.

      "I do care about people getting flak for thinking so."

      You mean you are just looking for an excuse to vent your frustration. Break karma by breaking the karma of those breaking karma. Again, writing a patch would have been a better use of your time. Have you grown up yet, because you display the emotions of a 5 year old even though you are clearly an adult.