Prev: Can "perldoc" take input from a pipe?
Next: Print a separator between each iteration of a foreach loop
From: Charlton Wilbur on 15 Apr 2008 13:04
>>>>> "GE" == Gordon Etly <get(a)bentsys.com> writes:

GE> Yes, we all know that, and that is not the point I have tried
GE> to make.

GE> What is so wrong with adding to that list,

GE> "PERL" refers to "Practical Extraction and Report Language"
GE> ?

It does not reflect the usage patterns of the core Perl developers or
Perl experts. The correct usage and the rationale behind it are found
in the Perl FAQ, and no amont of railing and rationalization on your
part will change either.

Simply put: using 'PERL' marks you as someone clueless and ignorant;
if by chance you aren't clueless and ignorant, you're stubborn and
resistant to correction. There's little to be gained by interactions
with such people.

So, your choice is to continue insisting on the validity of 'PERL,'
and wind up in more and more killfiles; or to conform to community
standards and usages. The latter seems more satisfying, no doubt, but
when you do need help, if you have chosen that path, you're much less
likely to get help. Except from other cranks and novices, of course,
but that's not the help you generally want.

GE> That IS how acronyms work, whether people like you want to
GE> admit it or not.

And people often make inferences about the education level, class, and
status of a person from his or her use of language. You've had it
pointed out that one of your usages marks you as either a novice or a
crank; you can continue using it if you see fit, but it is a
deliberate choice at this point and no longer an error.

There are other windmills at which it is more fun to tilt, no doubt.

Charlton



--
Charlton Wilbur
cwilbur(a)chromatico.net
From: Gordon Etly on 15 Apr 2008 21:00
Charlton Wilbur wrote:
>>>>>> "GE" == Gordon Etly <get(a)bentsys.com> writes:
>
>> Yes, we all know that, and that is not the point I have tried
>> to make.
>
>> What is so wrong with adding to that list,
>
>> "PERL" refers to "Practical Extraction and Report Language"
>> ?
>
> It does not reflect the usage patterns of the core Perl developers or
> Perl experts.

I understand that, honestly I do, but that is not what I was asking.
Quite simply, 'perldoc perl' gives an expansion, and my question is why
it should be wrong to use "PERL" as a short hand for that expansion,
since the expansion is found in the official docs?

--
G.Etly


From: Uri Guttman on 15 Apr 2008 23:51
>>>>> "GE" == Gordon Etly <get(a)bentsys.com> writes:

GE> I understand that, honestly I do, but that is not what I was asking.
GE> Quite simply, 'perldoc perl' gives an expansion, and my question is why
GE> it should be wrong to use "PERL" as a short hand for that expansion,
GE> since the expansion is found in the official docs?

why don't you just shut up about this already like you said you
would? all the people who want to use PERL are those who never help
others here. when is the last time you posted an answer to any perl
questions here? you have no standing in the perl community (here or
elsewhere) so why should your opinion matter? the retronym/backronym of
PERL is known. it is only used as a JOKE in the title and the PERL
spelling is because of the man page macros. larry doesn't use PERL. no
decent perl hacker says PERL. only the lame defenders of it here and who
never show up when real help is asked for defend its use. this isn't 12
angry men and you aren't henry fonda. there is no life on the line but
your reputation is. do you want to be known as someone who defends silly
and unsupported stuff like PERL and for nothing else? just drop this
already (don't even reply if you can help it) and move along. maybe you
will do something in the future to regain what little reputation you
might have had. but until then keep quiet. you are just digging a bigger
hole and you are about to stop seeing any sky above you.

uri

--
Uri Guttman ------ uri(a)stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
From: Uri Guttman on 15 Apr 2008 23:54
>>>>> "JWK" == John W Krahn <someone(a)example.com> writes:

JWK> There are some papers at the supermarket that have articles about the
JWK> existence of Bigfoot. It's written down so it must be true. There are
JWK> some books that say that the moon landings were faked. It's written
JWK> down so it must be true. There are some books that claim that the earth
JWK> was created in six days. It's written down so it must be true.

damn you!! you have ruined my decade by exposing my beliefs to
ridicule. i will have to start using PERL from now on!

uri

--
Uri Guttman ------ uri(a)stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
From: Charlton Wilbur on 15 Apr 2008 23:31
>>>>> "GE" == Gordon Etly <get(a)bentsys.com> writes:

>> It does not reflect the usage patterns of the core Perl
>> developers or Perl experts.

GE> I understand that, honestly I do, but that is not what I was
GE> asking. Quite simply, 'perldoc perl' gives an expansion, and
GE> my question is why it should be wrong to use "PERL" as a short
GE> hand for that expansion, since the expansion is found in the
GE> official docs?

It's not *wrong*. It will just mark you as either a novice or a
crank, because people who are not novices will have learned that
'PERL' is widely considered incorrect, and people who are not cranks
do not insist on rationalizing usage that is widely considered
incorrect.

If you do not want people to react to you as if you were a novice or a
crank, don't use 'PERL.' Otherwise, carry on. This is the advice
that the FAQ is giving you, if you only have the wit to read it.

Charlton




--
Charlton Wilbur
cwilbur(a)chromatico.net
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Can "perldoc" take input from a pipe?
Next: Print a separator between each iteration of a foreach loop