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

Feelings? You quote the perlfaq, I point to man perl. I spot a contradiction.

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

My conclusion is simple: no wonder people keep thinking Perl is an acronym.

And, considering you seem to care deeply about the fact people think Perl is an acronym, why don't you fix the documentation? Or at least, send in a patch.

Replies are listed 'Best First'.
Re^9: Web-designing using PERL
by chromatic (Archbishop) on Mar 26, 2012 at 22:18 UTC
    And, considering you seem to care deeply about the fact people think Perl is an acronym...

    I don't. Sometimes "Perl" stands for something. Sometimes it stands for something else. Sometimes it stands for nothing.

    What's difficult to understand about both pieces of documentation? The name of the language is not "PERL".

[reply]
      The name was never my point. But you don't seem to get them, stuck in your ideas.

      My point is, considering the main documentation, presented to you when you type in man perl or perldoc perl strongly suggests it's an acronym.

      Really, if the main documentation starts its description with Perl officially stands for Practical Extraction and Report Language, you can scribble all you want in a CPAN maintained piece of documentation, but people will keep thinking Perl is an acronym, and I will keep correcting people who jump up and down because they remember a bit of trivia and slap people in the face with it.

      Again, either fix the bloody documentation, or shut up when someone thinks PERL is an acronym.

[reply]
[d/l]
[select]
        ... people will keep thinking Perl is an acronym...

        So what? People think all kinds of silly things; that's why they ask questions on here when their misunderstandings create buggy programs.

        The name of the language isn't "PERL". The documentation is clear. The only place it refers to "PERL" is to say that that's not the name of the language.

        (If "PERL" were the name of the language, the documentation you quoted would likely say "PERL stands for...". It doesn't. QED.)

[reply]
        "Again, either fix the bloody documentation, or shut up when someone thinks PERL is an acronym."

        Wow. Would you please go back to coding JAVA and leave us alone?

[reply]
Re^9: Web-designing using PERL
by Anonymous Monk on Mar 26, 2012 at 23:42 UTC
    "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!"

[reply]
      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.

[reply]
        "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.

[reply]

In Section Seekers of Perl Wisdom