One bit. Oh, you weren't talking ASCII? :-) Larry now uses ``Perl'' to signify the language proper and ``perl'' the implementation of it, i.e. the current interpreter. Hence Tom's quip that ``Nothing but perl can parse Perl.'' You may or may not choose to follow this usage. For example, parallelism means ``awk and perl'' and ``Python and Perl'' look ok, while ``awk and Perl'' and ``Python and perl'' do not.I guess it would be better to link to a more current version of said question. For instance, current blead answers the question as:
"Perl" is the name of the language. Only the "P" is capitalized. The name of the interpreter (the program which runs the Perl script) is "perl" with a lowercase "p".Now, I grant you, that says perl isn't an acronym. But if there's contradicting documentation, on the one hand we have have the Perl manual page, claiming something since perl-1.0, and maintained by p5p, and on the other hand we have a contradicting opinion from a document that's moderated by a single person, and is imported from CPAN, guess which one I consider should carry more weight?You may or may not choose to follow this usage. But never write "PERL", because perl is not an acronym.
Now, I don't care jack shit whether Perl is written as perl, PERL, PeRl or someway else, or whether it's an acronym or not, but I do get pissed off at people who think they should belittle others when they assume Perl is an acronym.
Fix your bloody documentation first, then tell others off .
In reply to Re^4: Web-designing using PERL
by JavaFan
in thread Web-designing using PERL
by Arthes
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |