Prev: Can "perldoc" take input from a pipe?
Next: Print a separator between each iteration of a foreach loop
From: Peter Wyzl on 16 Apr 2008 06:43
"Gordon Etly" <get(a)bentsys.com> wrote in message
news:66l1e2F2l411pU1(a)mid.individual.net...
> 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?

Because by convention among those in the community, 'perl' refers to the
binary and 'Perl' refers to the language and PERL is a joke and refers to
neither.

If you want to engage with those knowlegeable in a subject, you should adopt
their conventions. If not....your call...

P

From: Gordon Etly on 16 Apr 2008 12:32
Jim Cochrane wrote:
> On 2008-04-16, Gordon Etly <get(a)bentsys.com> wrote:
>> 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?
>
> IMO, it's fine to use PERL as an acronym for "Practical Extraction
> and Report Language", but that (PERL) is not the name of a programming
> language; rather, it is simply an acronym for
> "Practical Extraction and Report Language", which is a description of
> the perl executable that shows up via the perl man pages.

For the record, I never said it was the name of the language, but,
rather, just as you said about the acronym part :)

Thank you for your understanding.

--
G.Etly


From: Stephan Bour on 16 Apr 2008 13:07
Uri Guttman wrote:
} Stephan Bour <sbour(a)niaid.nih.gov> writes:
} >
} > Uri Guttman wrote:
} >
} > } why don't you just shut up about this already like you said you
} >
} > If you bothered to read the thread, he replied to someone who
} > replied before he did, so why focus this one single individual,
} > and waste a perfectly good post displaying you are incapable of
} > opening your mind to other possibilities instead of acting as if
} > all the FAQs, et al, are carved in granite.
}
} he was continuing when he said he wouldn't. he singled himself out.


So what? He was answering someone else, what concern is it of yours? Is
someone forcing you to read everything that comes down the pipe? Are you
unable to killfile a thread?

} > } all the people who want to use PERL are those who never help
} > } others here.
} >
} > That's a rather broad statement, don'cha think? There is a certain
} > logic in rewriting `Practical Extraction and Report Language` as
} > `PERL` which is a common form of writing a term whose characters
} > each have a documented meaning, which would appear to be the case.
}
} and did you address my point?

I didn't know you had one.

} do you help people here? i don't recall your name on many posts.

That's not what is or was of question, and is utterly irrelevant. Stop
invoking the straw-man.

} it is simple. you help with real perl questions, you have a
} right to say stuff about this group.

And who decides who say what? You? I think not. Everyone has a right to post
in a public news group, and you have no right what so ever to dictate
otherwise.


Stephan.


From: Stephan Bour on 16 Apr 2008 13:20
Peter Wyzl wrote:
} "Gordon Etly" <get(a)bentsys.com> wrote in message
} > 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?
}
} Because by convention among those in the community, 'perl' refers to
} the binary and 'Perl' refers to the language and PERL is a joke and
} refers to neither.

It maybe a joke to *you* but your opinion doesn't change what it says in the
applicable doc. `PERL` very well could correspond with `Practical Extraction
and Report Language`, whether it's a true acronym or as some say, a
backronym [1], it's a shorted form for that description. Everyone who keeps
using the excuse you are is refusing to open their mind to other ideas than
the already established ones.

} If you want to engage with those knowlegeable in a subject, you
} should adopt their conventions. If not....your call...

So, `my way or the hiway`? Are you saying no one may question rules,
conventions, and ideals? Is this really the way you feel a community should
function?


[1]
http://dictionary.reference.com/browse/backronym
" backronym jargon
" (Backward acronym) A word which has been turned into an acronym
" by inventing an expansion, rather than the other way around.

" n. [portmanteau of back + acronym] A word interpreted as an
" acronym that was not originally so intended.


Stephan.


From: J�rgen Exner on 16 Apr 2008 13:38
"Stephan Bour" <sbour(a)niaid.nih.gov> wrote:
>`PERL` very well could correspond with `Practical Extraction
>and Report Language`

It very well could and probably does. But what does that have to do with
the programming language named 'Perl'?

jue
First  |  Prev  |  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