Commit | Line | Data |
---|---|---|
68dc0745 | 1 | =head1 NAME |
2 | ||
f05bbc40 | 3 | perlfaq1 - General Questions About Perl ($Revision: 1.8 $, $Date: 2002/04/07 18:46:13 $) |
68dc0745 | 4 | |
5 | =head1 DESCRIPTION | |
6 | ||
7 | This section of the FAQ answers very general, high-level questions | |
8 | about Perl. | |
9 | ||
10 | =head2 What is Perl? | |
11 | ||
12 | Perl is a high-level programming language with an eclectic heritage | |
13 | written by Larry Wall and a cast of thousands. It derives from the | |
14 | ubiquitous C programming language and to a lesser extent from sed, | |
15 | awk, the Unix shell, and at least a dozen other tools and languages. | |
16 | Perl's process, file, and text manipulation facilities make it | |
17 | particularly well-suited for tasks involving quick prototyping, system | |
18 | utilities, software tools, system management tasks, database access, | |
19 | graphical programming, networking, and world wide web programming. | |
20 | These strengths make it especially popular with system administrators | |
21 | and CGI script authors, but mathematicians, geneticists, journalists, | |
22 | and even managers also use Perl. Maybe you should, too. | |
23 | ||
24 | =head2 Who supports Perl? Who develops it? Why is it free? | |
25 | ||
26 | The original culture of the pre-populist Internet and the deeply-held | |
27 | beliefs of Perl's author, Larry Wall, gave rise to the free and open | |
28 | distribution policy of perl. Perl is supported by its users. The | |
29 | core, the standard Perl library, the optional modules, and the | |
30 | documentation you're reading now were all written by volunteers. See | |
31 | the personal note at the end of the README file in the perl source | |
5e3006a4 GS |
32 | distribution for more details. See L<perlhist> (new as of 5.005) |
33 | for Perl's milestone releases. | |
68dc0745 | 34 | |
65acb1b1 | 35 | In particular, the core development team (known as the Perl Porters) |
006d0b46 JH |
36 | are a rag-tag band of highly altruistic individuals committed to |
37 | producing better software for free than you could hope to purchase for | |
06a5f41f | 38 | money. You may snoop on pending developments via the archives at |
1577cd80 | 39 | http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/ |
f05bbc40 | 40 | and http://archive.develooper.com/perl5-porters@perl.org/ |
cf682770 | 41 | or the news gateway nntp://nntp.perl.org/perl.perl5.porters or |
4915ea75 | 42 | its web interface at http://nntp.perl.org/group/perl.perl5.porters , |
1577cd80 | 43 | or read the faq at http://perlhacker.org/p5p-faq , |
006d0b46 JH |
44 | or you can subscribe to the mailing list by sending |
45 | perl5-porters-request@perl.org a subscription request | |
46 | (an empty message with no subject is fine). | |
68dc0745 | 47 | |
48 | While the GNU project includes Perl in its distributions, there's no | |
49 | such thing as "GNU Perl". Perl is not produced nor maintained by the | |
50 | Free Software Foundation. Perl's licensing terms are also more open | |
51 | than GNU software's tend to be. | |
52 | ||
53 | You can get commercial support of Perl if you wish, although for most | |
54 | users the informal support will more than suffice. See the answer to | |
55 | "Where can I buy a commercial version of perl?" for more information. | |
56 | ||
57 | =head2 Which version of Perl should I use? | |
58 | ||
59 | You should definitely use version 5. Version 4 is old, limited, and | |
65acb1b1 TC |
60 | no longer maintained; its last patch (4.036) was in 1992, long ago and |
61 | far away. Sure, it's stable, but so is anything that's dead; in fact, | |
62 | perl4 had been called a dead, flea-bitten camel carcass. The most recent | |
a6dd486b JB |
63 | production release is 5.6 (although 5.005_03 is still supported). |
64 | The most cutting-edge development release is 5.7. Further references | |
65acb1b1 | 65 | to the Perl language in this document refer to the production release |
d92eb7b0 GS |
66 | unless otherwise specified. There may be one or more official bug fixes |
67 | by the time you read this, and also perhaps some experimental versions | |
68 | on the way to the next release. All releases prior to 5.004 were subject | |
69 | to buffer overruns, a grave security issue. | |
68dc0745 | 70 | |
71 | =head2 What are perl4 and perl5? | |
72 | ||
73 | Perl4 and perl5 are informal names for different versions of the Perl | |
74 | programming language. It's easier to say "perl5" than it is to say | |
75 | "the 5(.004) release of Perl", but some people have interpreted this | |
76 | to mean there's a language called "perl5", which isn't the case. | |
77 | Perl5 is merely the popular name for the fifth major release (October 1994), | |
78 | while perl4 was the fourth major release (March 1991). There was also a | |
79 | perl1 (in January 1988), a perl2 (June 1988), and a perl3 (October 1989). | |
80 | ||
65acb1b1 TC |
81 | The 5.0 release is, essentially, a ground-up rewrite of the original |
82 | perl source code from releases 1 through 4. It has been modularized, | |
83 | object-oriented, tweaked, trimmed, and optimized until it almost doesn't | |
84 | look like the old code. However, the interface is mostly the same, and | |
13a2d996 SP |
85 | compatibility with previous releases is very high. |
86 | See L<perltrap/"Perl4 to Perl5 Traps">. | |
68dc0745 | 87 | |
88 | To avoid the "what language is perl5?" confusion, some people prefer to | |
89 | simply use "perl" to refer to the latest version of perl and avoid using | |
90 | "perl5" altogether. It's not really that big a deal, though. | |
91 | ||
5a964f20 TC |
92 | See L<perlhist> for a history of Perl revisions. |
93 | ||
65acb1b1 TC |
94 | =head2 What is perl6? |
95 | ||
4b29649f JH |
96 | At The Second O'Reilly Open Source Software Convention, Larry Wall |
97 | announced Perl6 development would begin in earnest. Perl6 was an oft | |
98 | used term for Chip Salzenberg's project to rewrite Perl in C++ named | |
0bc0ad85 JH |
99 | Topaz. However, Topaz provided valuable insights to the next version |
100 | of Perl and its implementation, but was ultimately abandoned. | |
7e14cdc9 | 101 | |
0bc0ad85 JH |
102 | If you want to learn more about Perl6, or have a desire to help in |
103 | the crusade to make Perl a better place then peruse the Perl6 developers | |
104 | page at http://dev.perl.org/perl6/ and get involved. | |
7e14cdc9 | 105 | |
0bc0ad85 JH |
106 | Perl6 is not scheduled for release yet, and Perl5 will still be supported |
107 | for quite awhile after its release. Do not wait for Perl6 to do whatever | |
108 | you need to do. | |
7e14cdc9 EHA |
109 | |
110 | "We're really serious about reinventing everything that needs reinventing." | |
111 | --Larry Wall | |
65acb1b1 | 112 | |
68dc0745 | 113 | =head2 How stable is Perl? |
114 | ||
115 | Production releases, which incorporate bug fixes and new functionality, | |
116 | are widely tested before release. Since the 5.000 release, we have | |
117 | averaged only about one production release per year. | |
118 | ||
119 | Larry and the Perl development team occasionally make changes to the | |
120 | internal core of the language, but all possible efforts are made toward | |
121 | backward compatibility. While not quite all perl4 scripts run flawlessly | |
122 | under perl5, an update to perl should nearly never invalidate a program | |
123 | written for an earlier version of perl (barring accidental bug fixes | |
124 | and the rare new keyword). | |
125 | ||
126 | =head2 Is Perl difficult to learn? | |
127 | ||
a6dd486b | 128 | No, Perl is easy to start learning--and easy to keep learning. It looks |
5a964f20 | 129 | like most programming languages you're likely to have experience |
87275199 | 130 | with, so if you've ever written a C program, an awk script, a shell |
a6dd486b | 131 | script, or even a BASIC program, you're already partway there. |
68dc0745 | 132 | |
133 | Most tasks only require a small subset of the Perl language. One of | |
134 | the guiding mottos for Perl development is "there's more than one way | |
135 | to do it" (TMTOWTDI, sometimes pronounced "tim toady"). Perl's | |
136 | learning curve is therefore shallow (easy to learn) and long (there's | |
137 | a whole lot you can do if you really want). | |
138 | ||
65acb1b1 TC |
139 | Finally, because Perl is frequently (but not always, and certainly not by |
140 | definition) an interpreted language, you can write your programs and test | |
141 | them without an intermediate compilation step, allowing you to experiment | |
142 | and test/debug quickly and easily. This ease of experimentation flattens | |
143 | the learning curve even more. | |
68dc0745 | 144 | |
145 | Things that make Perl easier to learn: Unix experience, almost any kind | |
146 | of programming experience, an understanding of regular expressions, and | |
147 | the ability to understand other people's code. If there's something you | |
148 | need to do, then it's probably already been done, and a working example is | |
149 | usually available for free. Don't forget the new perl modules, either. | |
65acb1b1 | 150 | They're discussed in Part 3 of this FAQ, along with CPAN, which is |
68dc0745 | 151 | discussed in Part 2. |
152 | ||
153 | =head2 How does Perl compare with other languages like Java, Python, REXX, Scheme, or Tcl? | |
154 | ||
155 | Favorably in some areas, unfavorably in others. Precisely which areas | |
156 | are good and bad is often a personal choice, so asking this question | |
157 | on Usenet runs a strong risk of starting an unproductive Holy War. | |
158 | ||
159 | Probably the best thing to do is try to write equivalent code to do a | |
160 | set of tasks. These languages have their own newsgroups in which you | |
161 | can learn about (but hopefully not argue about) them. | |
162 | ||
65acb1b1 TC |
163 | Some comparison documents can be found at http://language.perl.com/versus/ |
164 | if you really can't stop yourself. | |
165 | ||
68dc0745 | 166 | =head2 Can I do [task] in Perl? |
167 | ||
65acb1b1 TC |
168 | Perl is flexible and extensible enough for you to use on virtually any |
169 | task, from one-line file-processing tasks to large, elaborate systems. | |
170 | For many people, Perl serves as a great replacement for shell scripting. | |
171 | For others, it serves as a convenient, high-level replacement for most of | |
172 | what they'd program in low-level languages like C or C++. It's ultimately | |
173 | up to you (and possibly your management) which tasks you'll use Perl | |
174 | for and which you won't. | |
68dc0745 | 175 | |
176 | If you have a library that provides an API, you can make any component | |
177 | of it available as just another Perl function or variable using a Perl | |
178 | extension written in C or C++ and dynamically linked into your main | |
179 | perl interpreter. You can also go the other direction, and write your | |
180 | main program in C or C++, and then link in some Perl code on the fly, | |
65acb1b1 | 181 | to create a powerful application. See L<perlembed>. |
68dc0745 | 182 | |
183 | That said, there will always be small, focused, special-purpose | |
184 | languages dedicated to a specific problem domain that are simply more | |
185 | convenient for certain kinds of problems. Perl tries to be all things | |
186 | to all people, but nothing special to anyone. Examples of specialized | |
187 | languages that come to mind include prolog and matlab. | |
188 | ||
189 | =head2 When shouldn't I program in Perl? | |
190 | ||
a6dd486b | 191 | When your manager forbids it--but do consider replacing them :-). |
68dc0745 | 192 | |
193 | Actually, one good reason is when you already have an existing | |
194 | application written in another language that's all done (and done | |
195 | well), or you have an application language specifically designed for a | |
196 | certain task (e.g. prolog, make). | |
197 | ||
198 | For various reasons, Perl is probably not well-suited for real-time | |
199 | embedded systems, low-level operating systems development work like | |
65acb1b1 | 200 | device drivers or context-switching code, complex multi-threaded |
68dc0745 | 201 | shared-memory applications, or extremely large applications. You'll |
202 | notice that perl is not itself written in Perl. | |
203 | ||
65acb1b1 TC |
204 | The new, native-code compiler for Perl may eventually reduce the |
205 | limitations given in the previous statement to some degree, but understand | |
206 | that Perl remains fundamentally a dynamically typed language, not | |
207 | a statically typed one. You certainly won't be chastised if you don't | |
208 | trust nuclear-plant or brain-surgery monitoring code to it. And Larry | |
a6dd486b | 209 | will sleep easier, too--Wall Street programs not withstanding. :-) |
68dc0745 | 210 | |
211 | =head2 What's the difference between "perl" and "Perl"? | |
212 | ||
213 | One bit. Oh, you weren't talking ASCII? :-) Larry now uses "Perl" to | |
214 | signify the language proper and "perl" the implementation of it, | |
215 | i.e. the current interpreter. Hence Tom's quip that "Nothing but perl | |
216 | can parse Perl." You may or may not choose to follow this usage. For | |
217 | example, parallelism means "awk and perl" and "Python and Perl" look | |
87275199 | 218 | OK, while "awk and Perl" and "Python and perl" do not. But never |
881bdbd4 | 219 | write "PERL", because perl is not an acronym, apocryphal |
65acb1b1 | 220 | folklore and post-facto expansions notwithstanding. |
68dc0745 | 221 | |
222 | =head2 Is it a Perl program or a Perl script? | |
223 | ||
65acb1b1 TC |
224 | Larry doesn't really care. He says (half in jest) that "a script is |
225 | what you give the actors. A program is what you give the audience." | |
226 | ||
227 | Originally, a script was a canned sequence of normally interactive | |
a6dd486b | 228 | commands--that is, a chat script. Something like a UUCP or PPP chat |
65acb1b1 TC |
229 | script or an expect script fits the bill nicely, as do configuration |
230 | scripts run by a program at its start up, such F<.cshrc> or F<.ircrc>, | |
231 | for example. Chat scripts were just drivers for existing programs, | |
232 | not stand-alone programs in their own right. | |
233 | ||
234 | A computer scientist will correctly explain that all programs are | |
a6dd486b | 235 | interpreted and that the only question is at what level. But if you |
65acb1b1 TC |
236 | ask this question of someone who isn't a computer scientist, they might |
237 | tell you that a I<program> has been compiled to physical machine code | |
a6dd486b | 238 | once and can then be run multiple times, whereas a I<script> must be |
65acb1b1 TC |
239 | translated by a program each time it's used. |
240 | ||
241 | Perl programs are (usually) neither strictly compiled nor strictly | |
242 | interpreted. They can be compiled to a byte-code form (something of a | |
fc36a67e | 243 | Perl virtual machine) or to completely different languages, like C or |
65acb1b1 TC |
244 | assembly language. You can't tell just by looking at it whether the |
245 | source is destined for a pure interpreter, a parse-tree interpreter, | |
246 | a byte-code interpreter, or a native-code compiler, so it's hard to give | |
247 | a definitive answer here. | |
248 | ||
249 | Now that "script" and "scripting" are terms that have been seized by | |
250 | unscrupulous or unknowing marketeers for their own nefarious purposes, | |
251 | they have begun to take on strange and often pejorative meanings, | |
87275199 | 252 | like "non serious" or "not real programming". Consequently, some Perl |
65acb1b1 | 253 | programmers prefer to avoid them altogether. |
68dc0745 | 254 | |
255 | =head2 What is a JAPH? | |
256 | ||
257 | These are the "just another perl hacker" signatures that some people | |
65acb1b1 TC |
258 | sign their postings with. Randal Schwartz made these famous. About |
259 | 100 of the earlier ones are available from | |
a93751fa | 260 | http://www.cpan.org/misc/japh . |
68dc0745 | 261 | |
262 | =head2 Where can I get a list of Larry Wall witticisms? | |
263 | ||
264 | Over a hundred quips by Larry, from postings of his or source code, | |
a93751fa | 265 | can be found at http://www.cpan.org/misc/lwall-quotes.txt.gz . |
65acb1b1 | 266 | |
ae3d0b9f | 267 | =head2 How can I convince my sysadmin/supervisor/employees to use version 5/5.6.1/Perl instead of some other language? |
68dc0745 | 268 | |
269 | If your manager or employees are wary of unsupported software, or | |
87275199 | 270 | software which doesn't officially ship with your operating system, you |
68dc0745 | 271 | might try to appeal to their self-interest. If programmers can be |
272 | more productive using and utilizing Perl constructs, functionality, | |
273 | simplicity, and power, then the typical manager/supervisor/employee | |
274 | may be persuaded. Regarding using Perl in general, it's also | |
275 | sometimes helpful to point out that delivery times may be reduced | |
a6dd486b | 276 | using Perl compared to other languages. |
68dc0745 | 277 | |
278 | If you have a project which has a bottleneck, especially in terms of | |
5a964f20 | 279 | translation or testing, Perl almost certainly will provide a viable, |
a6dd486b | 280 | quick solution. In conjunction with any persuasion effort, you |
68dc0745 | 281 | should not fail to point out that Perl is used, quite extensively, and |
282 | with extremely reliable and valuable results, at many large computer | |
a6dd486b JB |
283 | software and hardware companies throughout the world. In fact, |
284 | many Unix vendors now ship Perl by default. Support is usually | |
68dc0745 | 285 | just a news-posting away, if you can't find the answer in the |
286 | I<comprehensive> documentation, including this FAQ. | |
287 | ||
65acb1b1 TC |
288 | See http://www.perl.org/advocacy/ for more information. |
289 | ||
68dc0745 | 290 | If you face reluctance to upgrading from an older version of perl, |
291 | then point out that version 4 is utterly unmaintained and unsupported | |
292 | by the Perl Development Team. Another big sell for Perl5 is the large | |
293 | number of modules and extensions which greatly reduce development time | |
294 | for any given task. Also mention that the difference between version | |
295 | 4 and version 5 of Perl is like the difference between awk and C++. | |
f4c2dd42 JA |
296 | (Well, OK, maybe it's not quite that distinct, but you get the idea.) |
297 | If you want support and a reasonable guarantee that what you're | |
298 | developing will continue to work in the future, then you have to run | |
ae3d0b9f | 299 | the supported version. As of January 2002 that probably means |
bd15af9d | 300 | running either of the releases 5.6.1 (released in April 2001) or |
f4c2dd42 JA |
301 | 5.005_03 (released in March 1999), although 5.004_05 isn't that bad |
302 | if you B<absolutely> need such an old version (released in April 1999) | |
303 | for stability reasons. Anything older than 5.004_05 shouldn't be used. | |
5e3006a4 | 304 | |
87275199 | 305 | Of particular note is the massive bug hunt for buffer overflow |
5e3006a4 GS |
306 | problems that went into the 5.004 release. All releases prior to |
307 | that, including perl4, are considered insecure and should be upgraded | |
65acb1b1 | 308 | as soon as possible. |
68dc0745 | 309 | |
cb4d4ad7 | 310 | In August 2000 in all Linux distributions a new security problem was |
f4c2dd42 JA |
311 | found in the optional 'suidperl' (not built or installed by default) |
312 | in all the Perl branches 5.6, 5.005, and 5.004, see | |
313 | http://www.cpan.org/src/5.0/sperl-2000-08-05/ | |
03739d21 JH |
314 | Perl maintenance releases 5.6.1 and 5.8.0 have this security hole closed. |
315 | Most, if not all, Linux distribution have patches for this | |
316 | vulnerability available, see http://www.linuxsecurity.com/advisories/ , | |
317 | but the most recommendable way is to upgrade to at least Perl 5.6.1. | |
f4c2dd42 | 318 | |
68dc0745 | 319 | =head1 AUTHOR AND COPYRIGHT |
320 | ||
0bc0ad85 JH |
321 | Copyright (c) 1997, 1998, 1999, 2000, 2001 Tom Christiansen and Nathan |
322 | Torkington. All rights reserved. | |
5a964f20 | 323 | |
5a7beb56 JH |
324 | This documentation is free; you can redistribute it and/or modify it |
325 | under the same terms as Perl itself. | |
c8db1d39 | 326 | |
87275199 | 327 | Irrespective of its distribution, all code examples here are in the public |
c8db1d39 TC |
328 | domain. You are permitted and encouraged to use this code and any |
329 | derivatives thereof in your own programs for fun or for profit as you | |
330 | see fit. A simple comment in the code giving credit to the FAQ would | |
331 | be courteous but is not required. |