Despite a lot of anecdote to the contrary, "PERL" was never really an acronym -- it's a "backronym". The name Perl was chosen first, then some people jokingly applied expansions to it, which caught on.
The PerlMonks community (highly recommended!) taught me the convention, and it's similar to Java's:
It's never PERL (or JAVA)
When you're talking about the language, it's Perl (or Java)
When you're talking about the interpreter itself, it's perl (or java).
That said, it doesn't make a whole hill of beans if you do it "wrong".
While, as has been said, it doesn't make THAT much difference if you get it wrong, some folks do use correct capitalization (or at least, NOT referring to 'PERL' or any of the more sensible backcronyms) as a shibboleth for clue in job ads. :)
"The name is normally capitalized (Perl) when referring to the language and uncapitalized (perl) when referring to the interpreter program itself since Unix-like file systems are case-sensitive." From wikipedia at time of posting.
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. But never write "PERL", because perl is not an acronym, apocryphal folklore and post-facto expansions notwithstanding.
The name is normally capitalized (Perl) when referring to the language and uncapitalized (perl) when referring to the interpreter program itself since Unix-like file systems are case-sensitive. Before the release of the first edition of Programming Perl, it was common to refer to the language as perl; Randal L. Schwartz, however, capitalised the language's name in the book to make it stand out better when typeset. The case distinction was subsequently adopted by the community.
The correct casing is "Perl" for the language and "perl" for the executable. Using "PERL" flags you as someone who isn't particularly familiar with the language or community.
发布评论
评论（8）
perl 或 Perl 都可以。
perl or Perl is fine.
Perl
Perl
尽管有很多相反的轶事，“PERL”从来都不是一个真正的缩写词——它是一个“反缩写词”。 Perl 这个名字首先被选定，然后一些人开玩笑地对它进行了扩展，从而流行起来。
PerlMonks 社区（强烈推荐！）教会了我这个约定，它与 Java 的类似：
也就是说，如果你做得“错误”，它也不会产生一整堆豆子。
Despite a lot of anecdote to the contrary, "PERL" was never really an acronym -- it's a "backronym". The name Perl was chosen first, then some people jokingly applied expansions to it, which caught on.
The PerlMonks community (highly recommended!) taught me the convention, and it's similar to Java's:
That said, it doesn't make a whole hill of beans if you do it "wrong".
虽然，正如已经说过的，如果你写错了，也没有多大区别，但有些人确实使用正确的大写字母（或者至少，不指“PERL”或任何更明智的缩写词）作为招聘广告中的线索。 :)
While, as has been said, it doesn't make THAT much difference if you get it wrong, some folks do use correct capitalization (or at least, NOT referring to 'PERL' or any of the more sensible backcronyms) as a shibboleth for clue in job ads. :)
“当指代语言时，名称通常是大写的 (Perl)，而当指代解释程序本身时，名称通常是大写的 (perl)，因为类 Unix 文件系统区分大小写。” 来自发布时的维基百科。
"The name is normally capitalized (Perl) when referring to the language and uncapitalized (perl) when referring to the interpreter program itself since Unix-like file systems are case-sensitive." From wikipedia at time of posting.
这是 perlfaq1 的答案：
Here's the answer from perlfaq1:
引用 Wikipedia 上的 Perl 文章。
另请检查 perlfaq 关于这个问题。
Quoting the Perl article on Wikipedia.
Also check the perlfaq about this question.
语言的正确大小写是“Perl”，可执行文件的正确大小写是“perl”。 使用“PERL”会将您标记为不太熟悉该语言或社区的人。
另请参阅perlfaq1< 中的“perl”和“Perl”有什么区别？ /a>.
The correct casing is "Perl" for the language and "perl" for the executable. Using "PERL" flags you as someone who isn't particularly familiar with the language or community.
See also What's the difference between "perl" and "Perl"? in perlfaq1.