Commit | Line | Data |
68dc0745 |
1 | =head1 NAME |
2 | |
b68463f7 |
3 | perlfaq7 - General Perl Language Issues ($Revision: 1.25 $, $Date: 2005/08/08 02:38:25 $) |
68dc0745 |
4 | |
5 | =head1 DESCRIPTION |
6 | |
7 | This section deals with general Perl language issues that don't |
8 | clearly fit into any of the other sections. |
9 | |
10 | =head2 Can I get a BNF/yacc/RE for the Perl language? |
11 | |
c8db1d39 |
12 | There is no BNF, but you can paw your way through the yacc grammar in |
13 | perly.y in the source distribution if you're particularly brave. The |
14 | grammar relies on very smart tokenizing code, so be prepared to |
15 | venture into toke.c as well. |
16 | |
17 | In the words of Chaim Frenkel: "Perl's grammar can not be reduced to BNF. |
18 | The work of parsing perl is distributed between yacc, the lexer, smoke |
19 | and mirrors." |
68dc0745 |
20 | |
d92eb7b0 |
21 | =head2 What are all these $@%&* punctuation signs, and how do I know when to use them? |
68dc0745 |
22 | |
23 | They are type specifiers, as detailed in L<perldata>: |
24 | |
25 | $ for scalar values (number, string or reference) |
26 | @ for arrays |
27 | % for hashes (associative arrays) |
d92eb7b0 |
28 | & for subroutines (aka functions, procedures, methods) |
68dc0745 |
29 | * for all types of that symbol name. In version 4 you used them like |
30 | pointers, but in modern perls you can just use references. |
31 | |
a6dd486b |
32 | There are couple of other symbols that you're likely to encounter that aren't |
33 | really type specifiers: |
68dc0745 |
34 | |
35 | <> are used for inputting a record from a filehandle. |
36 | \ takes a reference to something. |
37 | |
c47ff5f1 |
38 | Note that <FILE> is I<neither> the type specifier for files |
39 | nor the name of the handle. It is the C<< <> >> operator applied |
a6dd486b |
40 | to the handle FILE. It reads one line (well, record--see |
197aec24 |
41 | L<perlvar/$E<sol>>) from the handle FILE in scalar context, or I<all> lines |
68dc0745 |
42 | in list context. When performing open, close, or any other operation |
a6dd486b |
43 | besides C<< <> >> on files, or even when talking about the handle, do |
68dc0745 |
44 | I<not> use the brackets. These are correct: C<eof(FH)>, C<seek(FH, 0, |
45 | 2)> and "copying from STDIN to FILE". |
46 | |
47 | =head2 Do I always/never have to quote my strings or use semicolons and commas? |
48 | |
49 | Normally, a bareword doesn't need to be quoted, but in most cases |
50 | probably should be (and must be under C<use strict>). But a hash key |
51 | consisting of a simple word (that isn't the name of a defined |
c47ff5f1 |
52 | subroutine) and the left-hand operand to the C<< => >> operator both |
68dc0745 |
53 | count as though they were quoted: |
54 | |
55 | This is like this |
56 | ------------ --------------- |
571e049f |
57 | $foo{line} $foo{'line'} |
58 | bar => stuff 'bar' => stuff |
68dc0745 |
59 | |
60 | The final semicolon in a block is optional, as is the final comma in a |
61 | list. Good style (see L<perlstyle>) says to put them in except for |
62 | one-liners: |
63 | |
64 | if ($whoops) { exit 1 } |
65 | @nums = (1, 2, 3); |
66 | |
67 | if ($whoops) { |
68 | exit 1; |
69 | } |
70 | @lines = ( |
71 | "There Beren came from mountains cold", |
72 | "And lost he wandered under leaves", |
73 | ); |
74 | |
75 | =head2 How do I skip some return values? |
76 | |
77 | One way is to treat the return values as a list and index into it: |
78 | |
79 | $dir = (getpwnam($user))[7]; |
80 | |
81 | Another way is to use undef as an element on the left-hand-side: |
82 | |
83 | ($dev, $ino, undef, undef, $uid, $gid) = stat($file); |
197aec24 |
84 | |
49d635f9 |
85 | You can also use a list slice to select only the elements that |
86 | you need: |
87 | |
88 | ($dev, $ino, $uid, $gid) = ( stat($file) )[0,1,4,5]; |
68dc0745 |
89 | |
90 | =head2 How do I temporarily block warnings? |
91 | |
9f1b1f2d |
92 | If you are running Perl 5.6.0 or better, the C<use warnings> pragma |
93 | allows fine control of what warning are produced. |
94 | See L<perllexwarn> for more details. |
95 | |
96 | { |
97 | no warnings; # temporarily turn off warnings |
98 | $a = $b + $c; # I know these might be undef |
99 | } |
6670e5e7 |
100 | |
28b41a80 |
101 | Additionally, you can enable and disable categories of warnings. |
102 | You turn off the categories you want to ignore and you can still |
103 | get other categories of warnings. See L<perllexwarn> for the |
104 | complete details, including the category names and hierarchy. |
105 | |
106 | { |
107 | no warnings 'uninitialized'; |
108 | $a = $b + $c; |
109 | } |
9f1b1f2d |
110 | |
111 | If you have an older version of Perl, the C<$^W> variable (documented |
112 | in L<perlvar>) controls runtime warnings for a block: |
68dc0745 |
113 | |
114 | { |
115 | local $^W = 0; # temporarily turn off warnings |
116 | $a = $b + $c; # I know these might be undef |
117 | } |
118 | |
119 | Note that like all the punctuation variables, you cannot currently |
120 | use my() on C<$^W>, only local(). |
121 | |
68dc0745 |
122 | =head2 What's an extension? |
123 | |
a6dd486b |
124 | An extension is a way of calling compiled C code from Perl. Reading |
125 | L<perlxstut> is a good place to learn more about extensions. |
68dc0745 |
126 | |
127 | =head2 Why do Perl operators have different precedence than C operators? |
128 | |
129 | Actually, they don't. All C operators that Perl copies have the same |
130 | precedence in Perl as they do in C. The problem is with operators that C |
131 | doesn't have, especially functions that give a list context to everything |
a6dd486b |
132 | on their right, eg. print, chmod, exec, and so on. Such functions are |
68dc0745 |
133 | called "list operators" and appear as such in the precedence table in |
134 | L<perlop>. |
135 | |
136 | A common mistake is to write: |
137 | |
138 | unlink $file || die "snafu"; |
139 | |
140 | This gets interpreted as: |
141 | |
142 | unlink ($file || die "snafu"); |
143 | |
144 | To avoid this problem, either put in extra parentheses or use the |
145 | super low precedence C<or> operator: |
146 | |
147 | (unlink $file) || die "snafu"; |
148 | unlink $file or die "snafu"; |
149 | |
150 | The "English" operators (C<and>, C<or>, C<xor>, and C<not>) |
151 | deliberately have precedence lower than that of list operators for |
152 | just such situations as the one above. |
153 | |
154 | Another operator with surprising precedence is exponentiation. It |
155 | binds more tightly even than unary minus, making C<-2**2> product a |
156 | negative not a positive four. It is also right-associating, meaning |
157 | that C<2**3**2> is two raised to the ninth power, not eight squared. |
158 | |
c8db1d39 |
159 | Although it has the same precedence as in C, Perl's C<?:> operator |
160 | produces an lvalue. This assigns $x to either $a or $b, depending |
161 | on the trueness of $maybe: |
162 | |
163 | ($maybe ? $a : $b) = $x; |
164 | |
68dc0745 |
165 | =head2 How do I declare/create a structure? |
166 | |
167 | In general, you don't "declare" a structure. Just use a (probably |
168 | anonymous) hash reference. See L<perlref> and L<perldsc> for details. |
169 | Here's an example: |
170 | |
171 | $person = {}; # new anonymous hash |
172 | $person->{AGE} = 24; # set field AGE to 24 |
173 | $person->{NAME} = "Nat"; # set field NAME to "Nat" |
174 | |
175 | If you're looking for something a bit more rigorous, try L<perltoot>. |
176 | |
177 | =head2 How do I create a module? |
178 | |
7678cced |
179 | (contributed by brian d foy) |
68dc0745 |
180 | |
7678cced |
181 | L<perlmod>, L<perlmodlib>, L<perlmodstyle> explain modules |
cf525c36 |
182 | in all the gory details. L<perlnewmod> gives a brief |
7678cced |
183 | overview of the process along with a couple of suggestions |
184 | about style. |
65acb1b1 |
185 | |
7678cced |
186 | If you need to include C code or C library interfaces in |
187 | your module, you'll need h2xs. h2xs will create the module |
188 | distribution structure and the initial interface files |
189 | you'll need. L<perlxs> and L<perlxstut> explain the details. |
7207e29d |
190 | |
7678cced |
191 | If you don't need to use C code, other tools such as |
192 | ExtUtils::ModuleMaker and Module::Starter, can help you |
193 | create a skeleton module distribution. |
194 | |
195 | You may also want to see Sam Tregar's "Writing Perl Modules |
196 | for CPAN" ( http://apress.com/book/bookDisplay.html?bID=14 ) |
197 | which is the best hands-on guide to creating module |
198 | distributions. |
65acb1b1 |
199 | |
68dc0745 |
200 | =head2 How do I create a class? |
201 | |
202 | See L<perltoot> for an introduction to classes and objects, as well as |
203 | L<perlobj> and L<perlbot>. |
204 | |
205 | =head2 How can I tell if a variable is tainted? |
206 | |
213329dd |
207 | You can use the tainted() function of the Scalar::Util module, available |
208 | from CPAN (or included with Perl since release 5.8.0). |
209 | See also L<perlsec/"Laundering and Detecting Tainted Data">. |
68dc0745 |
210 | |
211 | =head2 What's a closure? |
212 | |
213 | Closures are documented in L<perlref>. |
214 | |
215 | I<Closure> is a computer science term with a precise but |
216 | hard-to-explain meaning. Closures are implemented in Perl as anonymous |
217 | subroutines with lasting references to lexical variables outside their |
218 | own scopes. These lexicals magically refer to the variables that were |
219 | around when the subroutine was defined (deep binding). |
220 | |
221 | Closures make sense in any programming language where you can have the |
222 | return value of a function be itself a function, as you can in Perl. |
223 | Note that some languages provide anonymous functions but are not |
a6dd486b |
224 | capable of providing proper closures: the Python language, for |
68dc0745 |
225 | example. For more information on closures, check out any textbook on |
226 | functional programming. Scheme is a language that not only supports |
227 | but encourages closures. |
228 | |
229 | Here's a classic function-generating function: |
230 | |
231 | sub add_function_generator { |
c98c5709 |
232 | return sub { shift() + shift() }; |
68dc0745 |
233 | } |
234 | |
235 | $add_sub = add_function_generator(); |
c8db1d39 |
236 | $sum = $add_sub->(4,5); # $sum is 9 now. |
68dc0745 |
237 | |
238 | The closure works as a I<function template> with some customization |
239 | slots left out to be filled later. The anonymous subroutine returned |
240 | by add_function_generator() isn't technically a closure because it |
241 | refers to no lexicals outside its own scope. |
242 | |
243 | Contrast this with the following make_adder() function, in which the |
244 | returned anonymous function contains a reference to a lexical variable |
245 | outside the scope of that function itself. Such a reference requires |
246 | that Perl return a proper closure, thus locking in for all time the |
247 | value that the lexical had when the function was created. |
248 | |
249 | sub make_adder { |
250 | my $addpiece = shift; |
c98c5709 |
251 | return sub { shift() + $addpiece }; |
68dc0745 |
252 | } |
253 | |
254 | $f1 = make_adder(20); |
255 | $f2 = make_adder(555); |
256 | |
257 | Now C<&$f1($n)> is always 20 plus whatever $n you pass in, whereas |
258 | C<&$f2($n)> is always 555 plus whatever $n you pass in. The $addpiece |
259 | in the closure sticks around. |
260 | |
261 | Closures are often used for less esoteric purposes. For example, when |
262 | you want to pass in a bit of code into a function: |
263 | |
264 | my $line; |
265 | timeout( 30, sub { $line = <STDIN> } ); |
266 | |
c47ff5f1 |
267 | If the code to execute had been passed in as a string, |
268 | C<< '$line = <STDIN>' >>, there would have been no way for the |
269 | hypothetical timeout() function to access the lexical variable |
270 | $line back in its caller's scope. |
68dc0745 |
271 | |
46fc3d4c |
272 | =head2 What is variable suicide and how can I prevent it? |
273 | |
274 | Variable suicide is when you (temporarily or permanently) lose the |
275 | value of a variable. It is caused by scoping through my() and local() |
368c9434 |
276 | interacting with either closures or aliased foreach() iterator |
46fc3d4c |
277 | variables and subroutine arguments. It used to be easy to |
278 | inadvertently lose a variable's value this way, but now it's much |
279 | harder. Take this code: |
280 | |
281 | my $f = "foo"; |
282 | sub T { |
283 | while ($i++ < 3) { my $f = $f; $f .= "bar"; print $f, "\n" } |
284 | } |
285 | T; |
286 | print "Finally $f\n"; |
287 | |
288 | The $f that has "bar" added to it three times should be a new C<$f> |
d92eb7b0 |
289 | (C<my $f> should create a new local variable each time through the loop). |
290 | It isn't, however. This was a bug, now fixed in the latest releases |
291 | (tested against 5.004_05, 5.005_03, and 5.005_56). |
46fc3d4c |
292 | |
d92eb7b0 |
293 | =head2 How can I pass/return a {Function, FileHandle, Array, Hash, Method, Regex}? |
68dc0745 |
294 | |
d92eb7b0 |
295 | With the exception of regexes, you need to pass references to these |
68dc0745 |
296 | objects. See L<perlsub/"Pass by Reference"> for this particular |
297 | question, and L<perlref> for information on references. |
298 | |
b432a672 |
299 | See "Passing Regexes", below, for information on passing regular |
a6dd486b |
300 | expressions. |
301 | |
68dc0745 |
302 | =over 4 |
303 | |
304 | =item Passing Variables and Functions |
305 | |
a6dd486b |
306 | Regular variables and functions are quite easy to pass: just pass in a |
68dc0745 |
307 | reference to an existing or anonymous variable or function: |
308 | |
309 | func( \$some_scalar ); |
310 | |
65acb1b1 |
311 | func( \@some_array ); |
68dc0745 |
312 | func( [ 1 .. 10 ] ); |
313 | |
314 | func( \%some_hash ); |
315 | func( { this => 10, that => 20 } ); |
316 | |
317 | func( \&some_func ); |
318 | func( sub { $_[0] ** $_[1] } ); |
319 | |
320 | =item Passing Filehandles |
321 | |
49d635f9 |
322 | As of Perl 5.6, you can represent filehandles with scalar variables |
323 | which you treat as any other scalar. |
324 | |
325 | open my $fh, $filename or die "Cannot open $filename! $!"; |
326 | func( $fh ); |
197aec24 |
327 | |
49d635f9 |
328 | sub func { |
329 | my $passed_fh = shift; |
197aec24 |
330 | |
49d635f9 |
331 | my $line = <$fh>; |
332 | } |
197aec24 |
333 | |
49d635f9 |
334 | Before Perl 5.6, you had to use the C<*FH> or C<\*FH> notations. |
a6dd486b |
335 | These are "typeglobs"--see L<perldata/"Typeglobs and Filehandles"> |
c8db1d39 |
336 | and especially L<perlsub/"Pass by Reference"> for more information. |
337 | |
d92eb7b0 |
338 | =item Passing Regexes |
339 | |
340 | To pass regexes around, you'll need to be using a release of Perl |
341 | sufficiently recent as to support the C<qr//> construct, pass around |
342 | strings and use an exception-trapping eval, or else be very, very clever. |
68dc0745 |
343 | |
d92eb7b0 |
344 | Here's an example of how to pass in a string to be regex compared |
345 | using C<qr//>: |
68dc0745 |
346 | |
347 | sub compare($$) { |
d92eb7b0 |
348 | my ($val1, $regex) = @_; |
349 | my $retval = $val1 =~ /$regex/; |
350 | return $retval; |
351 | } |
352 | $match = compare("old McDonald", qr/d.*D/i); |
353 | |
354 | Notice how C<qr//> allows flags at the end. That pattern was compiled |
355 | at compile time, although it was executed later. The nifty C<qr//> |
356 | notation wasn't introduced until the 5.005 release. Before that, you |
357 | had to approach this problem much less intuitively. For example, here |
358 | it is again if you don't have C<qr//>: |
359 | |
360 | sub compare($$) { |
361 | my ($val1, $regex) = @_; |
362 | my $retval = eval { $val1 =~ /$regex/ }; |
68dc0745 |
363 | die if $@; |
364 | return $retval; |
365 | } |
366 | |
d92eb7b0 |
367 | $match = compare("old McDonald", q/($?i)d.*D/); |
68dc0745 |
368 | |
369 | Make sure you never say something like this: |
370 | |
d92eb7b0 |
371 | return eval "\$val =~ /$regex/"; # WRONG |
68dc0745 |
372 | |
d92eb7b0 |
373 | or someone can sneak shell escapes into the regex due to the double |
68dc0745 |
374 | interpolation of the eval and the double-quoted string. For example: |
375 | |
376 | $pattern_of_evil = 'danger ${ system("rm -rf * &") } danger'; |
377 | |
378 | eval "\$string =~ /$pattern_of_evil/"; |
379 | |
380 | Those preferring to be very, very clever might see the O'Reilly book, |
381 | I<Mastering Regular Expressions>, by Jeffrey Friedl. Page 273's |
382 | Build_MatchMany_Function() is particularly interesting. A complete |
383 | citation of this book is given in L<perlfaq2>. |
384 | |
385 | =item Passing Methods |
386 | |
387 | To pass an object method into a subroutine, you can do this: |
388 | |
389 | call_a_lot(10, $some_obj, "methname") |
390 | sub call_a_lot { |
391 | my ($count, $widget, $trick) = @_; |
392 | for (my $i = 0; $i < $count; $i++) { |
393 | $widget->$trick(); |
394 | } |
395 | } |
396 | |
a6dd486b |
397 | Or, you can use a closure to bundle up the object, its |
398 | method call, and arguments: |
68dc0745 |
399 | |
400 | my $whatnot = sub { $some_obj->obfuscate(@args) }; |
401 | func($whatnot); |
402 | sub func { |
403 | my $code = shift; |
404 | &$code(); |
405 | } |
406 | |
407 | You could also investigate the can() method in the UNIVERSAL class |
408 | (part of the standard perl distribution). |
409 | |
410 | =back |
411 | |
412 | =head2 How do I create a static variable? |
413 | |
6670e5e7 |
414 | (contributed by brian d foy) |
68dc0745 |
415 | |
6670e5e7 |
416 | Perl doesn't have "static" variables, which can only be accessed from |
417 | the function in which they are declared. You can get the same effect |
418 | with lexical variables, though. |
419 | |
420 | You can fake a static variable by using a lexical variable which goes |
421 | of scope. In this example, you define the subroutine C<counter>, and |
422 | it uses the lexical variable C<$count>. Since you wrap this in a BEGIN |
423 | block, C<$count> is defined at compile-time, but also goes out of |
424 | scope at the end of the BEGIN block. The BEGIN block also ensures that |
425 | the subroutine and the value it uses is defined at compile-time so the |
426 | subroutine is ready to use just like any other subroutine, and you can |
427 | put this code in the same place as other subroutines in the program |
428 | text (i.e. at the end of the code, typically). The subroutine |
429 | C<counter> still has a reference to the data, and is the only way you |
430 | can access the value (and each time you do, you increment the value). |
431 | The data in chunk of memory defined by C<$count> is private to |
432 | C<counter>. |
433 | |
3a205795 |
434 | BEGIN { |
435 | my $count = 1; |
436 | sub counter { $count++ } |
437 | } |
68dc0745 |
438 | |
3a205795 |
439 | my $start = count(); |
68dc0745 |
440 | |
3a205795 |
441 | .... # code that calls count(); |
68dc0745 |
442 | |
3a205795 |
443 | my $end = count(); |
68dc0745 |
444 | |
6670e5e7 |
445 | In the previous example, you created a function-private variable |
446 | because only one function remembered its reference. You could define |
447 | multiple functions while the variable is in scope, and each function |
448 | can share the "private" variable. It's not really "static" because you |
449 | can access it outside the function while the lexical variable is in |
450 | scope, and even create references to it. In this example, |
451 | C<increment_count> and C<return_count> share the variable. One |
452 | function adds to the value and the other simply returns the value. |
453 | They can both access C<$count>, and since it has gone out of scope, |
454 | there is no other way to access it. |
68dc0745 |
455 | |
6670e5e7 |
456 | BEGIN { |
457 | my $count = 1; |
458 | sub increment_count { $count++ } |
459 | sub return_count { $count } |
3a205795 |
460 | } |
68dc0745 |
461 | |
6670e5e7 |
462 | To declare a file-private variable, you still use a lexical variable. |
463 | A file is also a scope, so a lexical variable defined in the file |
464 | cannot be seen from any other file. |
68dc0745 |
465 | |
6670e5e7 |
466 | See L<perlsub/"Persistent Private Variables"> for more information. |
467 | The discussion of closures in L<perlref> may help you even though we |
468 | did not use anonymous subroutines in this answer. See |
469 | L<perlsub/"Persistent Private Variables"> for details. |
c8db1d39 |
470 | |
68dc0745 |
471 | =head2 What's the difference between dynamic and lexical (static) scoping? Between local() and my()? |
472 | |
a6dd486b |
473 | C<local($x)> saves away the old value of the global variable C<$x> |
474 | and assigns a new value for the duration of the subroutine I<which is |
68dc0745 |
475 | visible in other functions called from that subroutine>. This is done |
476 | at run-time, so is called dynamic scoping. local() always affects global |
477 | variables, also called package variables or dynamic variables. |
478 | |
479 | C<my($x)> creates a new variable that is only visible in the current |
a6dd486b |
480 | subroutine. This is done at compile-time, so it is called lexical or |
68dc0745 |
481 | static scoping. my() always affects private variables, also called |
482 | lexical variables or (improperly) static(ly scoped) variables. |
483 | |
484 | For instance: |
485 | |
486 | sub visible { |
487 | print "var has value $var\n"; |
488 | } |
489 | |
490 | sub dynamic { |
491 | local $var = 'local'; # new temporary value for the still-global |
492 | visible(); # variable called $var |
493 | } |
494 | |
495 | sub lexical { |
496 | my $var = 'private'; # new private variable, $var |
497 | visible(); # (invisible outside of sub scope) |
498 | } |
499 | |
500 | $var = 'global'; |
501 | |
502 | visible(); # prints global |
503 | dynamic(); # prints local |
504 | lexical(); # prints global |
505 | |
506 | Notice how at no point does the value "private" get printed. That's |
507 | because $var only has that value within the block of the lexical() |
508 | function, and it is hidden from called subroutine. |
509 | |
510 | In summary, local() doesn't make what you think of as private, local |
511 | variables. It gives a global variable a temporary value. my() is |
512 | what you're looking for if you want private variables. |
513 | |
197aec24 |
514 | See L<perlsub/"Private Variables via my()"> and |
13a2d996 |
515 | L<perlsub/"Temporary Values via local()"> for excruciating details. |
68dc0745 |
516 | |
517 | =head2 How can I access a dynamic variable while a similarly named lexical is in scope? |
518 | |
49d635f9 |
519 | If you know your package, you can just mention it explicitly, as in |
520 | $Some_Pack::var. Note that the notation $::var is B<not> the dynamic $var |
521 | in the current package, but rather the one in the "main" package, as |
522 | though you had written $main::var. |
523 | |
524 | use vars '$var'; |
525 | local $var = "global"; |
526 | my $var = "lexical"; |
68dc0745 |
527 | |
49d635f9 |
528 | print "lexical is $var\n"; |
529 | print "global is $main::var\n"; |
68dc0745 |
530 | |
49d635f9 |
531 | Alternatively you can use the compiler directive our() to bring a |
532 | dynamic variable into the current lexical scope. |
68dc0745 |
533 | |
49d635f9 |
534 | require 5.006; # our() did not exist before 5.6 |
535 | use vars '$var'; |
68dc0745 |
536 | |
49d635f9 |
537 | local $var = "global"; |
538 | my $var = "lexical"; |
539 | |
540 | print "lexical is $var\n"; |
541 | |
542 | { |
543 | our $var; |
544 | print "global is $var\n"; |
545 | } |
68dc0745 |
546 | |
547 | =head2 What's the difference between deep and shallow binding? |
548 | |
549 | In deep binding, lexical variables mentioned in anonymous subroutines |
550 | are the same ones that were in scope when the subroutine was created. |
551 | In shallow binding, they are whichever variables with the same names |
552 | happen to be in scope when the subroutine is called. Perl always uses |
553 | deep binding of lexical variables (i.e., those created with my()). |
554 | However, dynamic variables (aka global, local, or package variables) |
555 | are effectively shallowly bound. Consider this just one more reason |
556 | not to use them. See the answer to L<"What's a closure?">. |
557 | |
04d666b1 |
558 | =head2 Why doesn't "my($foo) = E<lt>FILEE<gt>;" work right? |
68dc0745 |
559 | |
c8db1d39 |
560 | C<my()> and C<local()> give list context to the right hand side |
c47ff5f1 |
561 | of C<=>. The <FH> read operation, like so many of Perl's |
c8db1d39 |
562 | functions and operators, can tell which context it was called in and |
563 | behaves appropriately. In general, the scalar() function can help. |
564 | This function does nothing to the data itself (contrary to popular myth) |
565 | but rather tells its argument to behave in whatever its scalar fashion is. |
566 | If that function doesn't have a defined scalar behavior, this of course |
567 | doesn't help you (such as with sort()). |
68dc0745 |
568 | |
569 | To enforce scalar context in this particular case, however, you need |
570 | merely omit the parentheses: |
571 | |
572 | local($foo) = <FILE>; # WRONG |
573 | local($foo) = scalar(<FILE>); # ok |
574 | local $foo = <FILE>; # right |
575 | |
576 | You should probably be using lexical variables anyway, although the |
577 | issue is the same here: |
578 | |
579 | my($foo) = <FILE>; # WRONG |
580 | my $foo = <FILE>; # right |
581 | |
54310121 |
582 | =head2 How do I redefine a builtin function, operator, or method? |
68dc0745 |
583 | |
584 | Why do you want to do that? :-) |
585 | |
586 | If you want to override a predefined function, such as open(), |
587 | then you'll have to import the new definition from a different |
4a4eefd0 |
588 | module. See L<perlsub/"Overriding Built-in Functions">. There's |
65acb1b1 |
589 | also an example in L<perltoot/"Class::Template">. |
68dc0745 |
590 | |
591 | If you want to overload a Perl operator, such as C<+> or C<**>, |
592 | then you'll want to use the C<use overload> pragma, documented |
593 | in L<overload>. |
594 | |
595 | If you're talking about obscuring method calls in parent classes, |
596 | see L<perltoot/"Overridden Methods">. |
597 | |
598 | =head2 What's the difference between calling a function as &foo and foo()? |
599 | |
600 | When you call a function as C<&foo>, you allow that function access to |
a6dd486b |
601 | your current @_ values, and you bypass prototypes. |
602 | The function doesn't get an empty @_--it gets yours! While not |
68dc0745 |
603 | strictly speaking a bug (it's documented that way in L<perlsub>), it |
604 | would be hard to consider this a feature in most cases. |
605 | |
c8db1d39 |
606 | When you call your function as C<&foo()>, then you I<do> get a new @_, |
68dc0745 |
607 | but prototyping is still circumvented. |
608 | |
609 | Normally, you want to call a function using C<foo()>. You may only |
610 | omit the parentheses if the function is already known to the compiler |
611 | because it already saw the definition (C<use> but not C<require>), |
612 | or via a forward reference or C<use subs> declaration. Even in this |
613 | case, you get a clean @_ without any of the old values leaking through |
614 | where they don't belong. |
615 | |
616 | =head2 How do I create a switch or case statement? |
617 | |
618 | This is explained in more depth in the L<perlsyn>. Briefly, there's |
619 | no official case statement, because of the variety of tests possible |
620 | in Perl (numeric comparison, string comparison, glob comparison, |
83df6a1d |
621 | regex matching, overloaded comparisons, ...). |
622 | Larry couldn't decide how best to do this, so he left it out, even |
623 | though it's been on the wish list since perl1. |
68dc0745 |
624 | |
83df6a1d |
625 | Starting from Perl 5.8 to get switch and case one can use the |
626 | Switch extension and say: |
627 | |
628 | use Switch; |
629 | |
630 | after which one has switch and case. It is not as fast as it could be |
631 | because it's not really part of the language (it's done using source |
632 | filters) but it is available, and it's very flexible. |
633 | |
634 | But if one wants to use pure Perl, the general answer is to write a |
635 | construct like this: |
c8db1d39 |
636 | |
637 | for ($variable_to_test) { |
638 | if (/pat1/) { } # do something |
639 | elsif (/pat2/) { } # do something else |
640 | elsif (/pat3/) { } # do something else |
641 | else { } # default |
197aec24 |
642 | } |
68dc0745 |
643 | |
c8db1d39 |
644 | Here's a simple example of a switch based on pattern matching, this |
645 | time lined up in a way to make it look more like a switch statement. |
8305e449 |
646 | We'll do a multiway conditional based on the type of reference stored |
c8db1d39 |
647 | in $whatchamacallit: |
648 | |
649 | SWITCH: for (ref $whatchamacallit) { |
68dc0745 |
650 | |
651 | /^$/ && die "not a reference"; |
652 | |
653 | /SCALAR/ && do { |
654 | print_scalar($$ref); |
655 | last SWITCH; |
656 | }; |
657 | |
658 | /ARRAY/ && do { |
659 | print_array(@$ref); |
660 | last SWITCH; |
661 | }; |
662 | |
663 | /HASH/ && do { |
664 | print_hash(%$ref); |
665 | last SWITCH; |
666 | }; |
667 | |
668 | /CODE/ && do { |
669 | warn "can't print function ref"; |
670 | last SWITCH; |
671 | }; |
672 | |
673 | # DEFAULT |
674 | |
675 | warn "User defined type skipped"; |
676 | |
677 | } |
678 | |
197aec24 |
679 | See C<perlsyn/"Basic BLOCKs and Switch Statements"> for many other |
c8db1d39 |
680 | examples in this style. |
681 | |
682 | Sometimes you should change the positions of the constant and the variable. |
683 | For example, let's say you wanted to test which of many answers you were |
684 | given, but in a case-insensitive way that also allows abbreviations. |
685 | You can use the following technique if the strings all start with |
a6dd486b |
686 | different characters or if you want to arrange the matches so that |
c8db1d39 |
687 | one takes precedence over another, as C<"SEND"> has precedence over |
688 | C<"STOP"> here: |
689 | |
690 | chomp($answer = <>); |
691 | if ("SEND" =~ /^\Q$answer/i) { print "Action is send\n" } |
692 | elsif ("STOP" =~ /^\Q$answer/i) { print "Action is stop\n" } |
693 | elsif ("ABORT" =~ /^\Q$answer/i) { print "Action is abort\n" } |
694 | elsif ("LIST" =~ /^\Q$answer/i) { print "Action is list\n" } |
695 | elsif ("EDIT" =~ /^\Q$answer/i) { print "Action is edit\n" } |
696 | |
197aec24 |
697 | A totally different approach is to create a hash of function references. |
c8db1d39 |
698 | |
699 | my %commands = ( |
700 | "happy" => \&joy, |
701 | "sad", => \&sullen, |
702 | "done" => sub { die "See ya!" }, |
703 | "mad" => \&angry, |
704 | ); |
705 | |
706 | print "How are you? "; |
707 | chomp($string = <STDIN>); |
708 | if ($commands{$string}) { |
709 | $commands{$string}->(); |
710 | } else { |
711 | print "No such command: $string\n"; |
197aec24 |
712 | } |
c8db1d39 |
713 | |
49d635f9 |
714 | =head2 How can I catch accesses to undefined variables, functions, or methods? |
68dc0745 |
715 | |
716 | The AUTOLOAD method, discussed in L<perlsub/"Autoloading"> and |
717 | L<perltoot/"AUTOLOAD: Proxy Methods">, lets you capture calls to |
718 | undefined functions and methods. |
719 | |
720 | When it comes to undefined variables that would trigger a warning |
49d635f9 |
721 | under C<use warnings>, you can promote the warning to an error. |
68dc0745 |
722 | |
49d635f9 |
723 | use warnings FATAL => qw(uninitialized); |
68dc0745 |
724 | |
725 | =head2 Why can't a method included in this same file be found? |
726 | |
727 | Some possible reasons: your inheritance is getting confused, you've |
728 | misspelled the method name, or the object is of the wrong type. Check |
a6dd486b |
729 | out L<perltoot> for details about any of the above cases. You may |
730 | also use C<print ref($object)> to find out the class C<$object> was |
731 | blessed into. |
68dc0745 |
732 | |
733 | Another possible reason for problems is because you've used the |
734 | indirect object syntax (eg, C<find Guru "Samy">) on a class name |
735 | before Perl has seen that such a package exists. It's wisest to make |
736 | sure your packages are all defined before you start using them, which |
737 | will be taken care of if you use the C<use> statement instead of |
a6dd486b |
738 | C<require>. If not, make sure to use arrow notation (eg., |
c47ff5f1 |
739 | C<< Guru->find("Samy") >>) instead. Object notation is explained in |
68dc0745 |
740 | L<perlobj>. |
741 | |
c8db1d39 |
742 | Make sure to read about creating modules in L<perlmod> and |
ae93639c |
743 | the perils of indirect objects in L<perlobj/"Method Invocation">. |
c8db1d39 |
744 | |
68dc0745 |
745 | =head2 How can I find out my current package? |
746 | |
747 | If you're just a random program, you can do this to find |
748 | out what the currently compiled package is: |
749 | |
c8db1d39 |
750 | my $packname = __PACKAGE__; |
68dc0745 |
751 | |
a6dd486b |
752 | But, if you're a method and you want to print an error message |
68dc0745 |
753 | that includes the kind of object you were called on (which is |
754 | not necessarily the same as the one in which you were compiled): |
755 | |
756 | sub amethod { |
92c2ed05 |
757 | my $self = shift; |
68dc0745 |
758 | my $class = ref($self) || $self; |
759 | warn "called me from a $class object"; |
760 | } |
761 | |
46fc3d4c |
762 | =head2 How can I comment out a large block of perl code? |
763 | |
659cfd94 |
764 | You can use embedded POD to discard it. Enclose the blocks you want |
7678cced |
765 | to comment out in POD markers. The <=begin> directive marks a section |
766 | for a specific formatter. Use the C<comment> format, which no formatter |
767 | should claim to understand (by policy). Mark the end of the block |
768 | with <=end>. |
46fc3d4c |
769 | |
770 | # program is here |
771 | |
7678cced |
772 | =begin comment |
46fc3d4c |
773 | |
774 | all of this stuff |
775 | |
776 | here will be ignored |
777 | by everyone |
778 | |
7678cced |
779 | =end comment |
6670e5e7 |
780 | |
659cfd94 |
781 | =cut |
782 | |
783 | # program continues |
46fc3d4c |
784 | |
f05bbc40 |
785 | The pod directives cannot go just anywhere. You must put a |
786 | pod directive where the parser is expecting a new statement, |
787 | not just in the middle of an expression or some other |
659cfd94 |
788 | arbitrary grammar production. |
fc36a67e |
789 | |
f05bbc40 |
790 | See L<perlpod> for more details. |
c8db1d39 |
791 | |
65acb1b1 |
792 | =head2 How do I clear a package? |
793 | |
794 | Use this code, provided by Mark-Jason Dominus: |
795 | |
796 | sub scrub_package { |
797 | no strict 'refs'; |
798 | my $pack = shift; |
197aec24 |
799 | die "Shouldn't delete main package" |
65acb1b1 |
800 | if $pack eq "" || $pack eq "main"; |
801 | my $stash = *{$pack . '::'}{HASH}; |
802 | my $name; |
803 | foreach $name (keys %$stash) { |
804 | my $fullname = $pack . '::' . $name; |
805 | # Get rid of everything with that name. |
806 | undef $$fullname; |
807 | undef @$fullname; |
808 | undef %$fullname; |
809 | undef &$fullname; |
810 | undef *$fullname; |
811 | } |
812 | } |
813 | |
197aec24 |
814 | Or, if you're using a recent release of Perl, you can |
65acb1b1 |
815 | just use the Symbol::delete_package() function instead. |
816 | |
d92eb7b0 |
817 | =head2 How can I use a variable as a variable name? |
818 | |
819 | Beginners often think they want to have a variable contain the name |
820 | of a variable. |
821 | |
822 | $fred = 23; |
823 | $varname = "fred"; |
824 | ++$$varname; # $fred now 24 |
825 | |
826 | This works I<sometimes>, but it is a very bad idea for two reasons. |
827 | |
a6dd486b |
828 | The first reason is that this technique I<only works on global |
829 | variables>. That means that if $fred is a lexical variable created |
830 | with my() in the above example, the code wouldn't work at all: you'd |
831 | accidentally access the global and skip right over the private lexical |
832 | altogether. Global variables are bad because they can easily collide |
833 | accidentally and in general make for non-scalable and confusing code. |
d92eb7b0 |
834 | |
835 | Symbolic references are forbidden under the C<use strict> pragma. |
836 | They are not true references and consequently are not reference counted |
837 | or garbage collected. |
838 | |
839 | The other reason why using a variable to hold the name of another |
a6dd486b |
840 | variable is a bad idea is that the question often stems from a lack of |
d92eb7b0 |
841 | understanding of Perl data structures, particularly hashes. By using |
842 | symbolic references, you are just using the package's symbol-table hash |
843 | (like C<%main::>) instead of a user-defined hash. The solution is to |
844 | use your own hash or a real reference instead. |
845 | |
369b44b4 |
846 | $USER_VARS{"fred"} = 23; |
d92eb7b0 |
847 | $varname = "fred"; |
848 | $USER_VARS{$varname}++; # not $$varname++ |
849 | |
850 | There we're using the %USER_VARS hash instead of symbolic references. |
851 | Sometimes this comes up in reading strings from the user with variable |
852 | references and wanting to expand them to the values of your perl |
853 | program's variables. This is also a bad idea because it conflates the |
854 | program-addressable namespace and the user-addressable one. Instead of |
855 | reading a string and expanding it to the actual contents of your program's |
856 | own variables: |
857 | |
858 | $str = 'this has a $fred and $barney in it'; |
859 | $str =~ s/(\$\w+)/$1/eeg; # need double eval |
860 | |
a6dd486b |
861 | it would be better to keep a hash around like %USER_VARS and have |
d92eb7b0 |
862 | variable references actually refer to entries in that hash: |
863 | |
864 | $str =~ s/\$(\w+)/$USER_VARS{$1}/g; # no /e here at all |
865 | |
866 | That's faster, cleaner, and safer than the previous approach. Of course, |
867 | you don't need to use a dollar sign. You could use your own scheme to |
868 | make it less confusing, like bracketed percent symbols, etc. |
869 | |
870 | $str = 'this has a %fred% and %barney% in it'; |
871 | $str =~ s/%(\w+)%/$USER_VARS{$1}/g; # no /e here at all |
872 | |
a6dd486b |
873 | Another reason that folks sometimes think they want a variable to |
874 | contain the name of a variable is because they don't know how to build |
875 | proper data structures using hashes. For example, let's say they |
876 | wanted two hashes in their program: %fred and %barney, and that they |
877 | wanted to use another scalar variable to refer to those by name. |
d92eb7b0 |
878 | |
879 | $name = "fred"; |
880 | $$name{WIFE} = "wilma"; # set %fred |
881 | |
197aec24 |
882 | $name = "barney"; |
d92eb7b0 |
883 | $$name{WIFE} = "betty"; # set %barney |
884 | |
885 | This is still a symbolic reference, and is still saddled with the |
886 | problems enumerated above. It would be far better to write: |
887 | |
888 | $folks{"fred"}{WIFE} = "wilma"; |
889 | $folks{"barney"}{WIFE} = "betty"; |
890 | |
891 | And just use a multilevel hash to start with. |
892 | |
893 | The only times that you absolutely I<must> use symbolic references are |
894 | when you really must refer to the symbol table. This may be because it's |
895 | something that can't take a real reference to, such as a format name. |
896 | Doing so may also be important for method calls, since these always go |
897 | through the symbol table for resolution. |
898 | |
899 | In those cases, you would turn off C<strict 'refs'> temporarily so you |
900 | can play around with the symbol table. For example: |
901 | |
902 | @colors = qw(red blue green yellow orange purple violet); |
903 | for my $name (@colors) { |
904 | no strict 'refs'; # renege for the block |
905 | *$name = sub { "<FONT COLOR='$name'>@_</FONT>" }; |
197aec24 |
906 | } |
d92eb7b0 |
907 | |
908 | All those functions (red(), blue(), green(), etc.) appear to be separate, |
909 | but the real code in the closure actually was compiled only once. |
910 | |
911 | So, sometimes you might want to use symbolic references to directly |
912 | manipulate the symbol table. This doesn't matter for formats, handles, and |
a6dd486b |
913 | subroutines, because they are always global--you can't use my() on them. |
914 | For scalars, arrays, and hashes, though--and usually for subroutines-- |
915 | you probably only want to use hard references. |
d92eb7b0 |
916 | |
5cd0b561 |
917 | =head2 What does "bad interpreter" mean? |
918 | |
571e049f |
919 | (contributed by brian d foy) |
920 | |
5cd0b561 |
921 | The "bad interpreter" message comes from the shell, not perl. The |
922 | actual message may vary depending on your platform, shell, and locale |
923 | settings. |
924 | |
925 | If you see "bad interpreter - no such file or directory", the first |
926 | line in your perl script (the "shebang" line) does not contain the |
6670e5e7 |
927 | right path to perl (or any other program capable of running scripts). |
5cd0b561 |
928 | Sometimes this happens when you move the script from one machine to |
929 | another and each machine has a different path to perl---/usr/bin/perl |
571e049f |
930 | versus /usr/local/bin/perl for instance. It may also indicate |
6670e5e7 |
931 | that the source machine has CRLF line terminators and the |
932 | destination machine has LF only: the shell tries to find |
571e049f |
933 | /usr/bin/perl<CR>, but can't. |
5cd0b561 |
934 | |
935 | If you see "bad interpreter: Permission denied", you need to make your |
936 | script executable. |
937 | |
938 | In either case, you should still be able to run the scripts with perl |
939 | explicitly: |
940 | |
941 | % perl script.pl |
942 | |
943 | If you get a message like "perl: command not found", perl is not in |
944 | your PATH, which might also mean that the location of perl is not |
945 | where you expect it so you need to adjust your shebang line. |
946 | |
68dc0745 |
947 | =head1 AUTHOR AND COPYRIGHT |
948 | |
7678cced |
949 | Copyright (c) 1997-2005 Tom Christiansen, Nathan Torkington, and |
950 | other authors as noted. All rights reserved. |
5a964f20 |
951 | |
5a7beb56 |
952 | This documentation is free; you can redistribute it and/or modify it |
953 | under the same terms as Perl itself. |
5a964f20 |
954 | |
955 | Irrespective of its distribution, all code examples in this file |
956 | are hereby placed into the public domain. You are permitted and |
957 | encouraged to use this code in your own programs for fun |
958 | or for profit as you see fit. A simple comment in the code giving |
959 | credit would be courteous but is not required. |
a6dd486b |
960 | |