Commit | Line | Data |
---|---|---|
0453d815 | 1 | =head1 NAME |
d74e8afc | 2 | X<warning, lexical> X<warnings> X<warning> |
0453d815 PM |
3 | |
4 | perllexwarn - Perl Lexical Warnings | |
5 | ||
6 | =head1 DESCRIPTION | |
5a3e7812 | 7 | |
4438c4b7 | 8 | The C<use warnings> pragma is a replacement for both the command line |
0453d815 PM |
9 | flag B<-w> and the equivalent Perl variable, C<$^W>. |
10 | ||
11 | The pragma works just like the existing "strict" pragma. | |
12 | This means that the scope of the warning pragma is limited to the | |
106325ad | 13 | enclosing block. It also means that the pragma setting will not |
0453d815 PM |
14 | leak across files (via C<use>, C<require> or C<do>). This allows |
15 | authors to independently define the degree of warning checks that will | |
16 | be applied to their module. | |
17 | ||
18 | By default, optional warnings are disabled, so any legacy code that | |
19 | doesn't attempt to control the warnings will work unchanged. | |
20 | ||
21 | All warnings are enabled in a block by either of these: | |
c47ff5f1 | 22 | |
4358a253 SS |
23 | use warnings; |
24 | use warnings 'all'; | |
c47ff5f1 | 25 | |
0453d815 PM |
26 | Similarly all warnings are disabled in a block by either of these: |
27 | ||
4358a253 SS |
28 | no warnings; |
29 | no warnings 'all'; | |
0453d815 PM |
30 | |
31 | For example, consider the code below: | |
32 | ||
4358a253 SS |
33 | use warnings; |
34 | my @a; | |
0453d815 | 35 | { |
4358a253 SS |
36 | no warnings; |
37 | my $b = @a[0]; | |
0453d815 | 38 | } |
f1f33818 | 39 | my $c = @a[0]; |
0453d815 PM |
40 | |
41 | The code in the enclosing block has warnings enabled, but the inner | |
f1f33818 PM |
42 | block has them disabled. In this case that means the assignment to the |
43 | scalar C<$c> will trip the C<"Scalar value @a[0] better written as $a[0]"> | |
44 | warning, but the assignment to the scalar C<$b> will not. | |
0453d815 PM |
45 | |
46 | =head2 Default Warnings and Optional Warnings | |
47 | ||
48 | Before the introduction of lexical warnings, Perl had two classes of | |
49 | warnings: mandatory and optional. | |
50 | ||
51 | As its name suggests, if your code tripped a mandatory warning, you | |
52 | would get a warning whether you wanted it or not. | |
252aa082 JH |
53 | For example, the code below would always produce an C<"isn't numeric"> |
54 | warning about the "2:". | |
0453d815 | 55 | |
252aa082 | 56 | my $a = "2:" + 3; |
0453d815 | 57 | |
0453d815 PM |
58 | With the introduction of lexical warnings, mandatory warnings now become |
59 | I<default> warnings. The difference is that although the previously | |
60 | mandatory warnings are still enabled by default, they can then be | |
61 | subsequently enabled or disabled with the lexical warning pragma. For | |
e476b1b5 | 62 | example, in the code below, an C<"isn't numeric"> warning will only |
0453d815 PM |
63 | be reported for the C<$a> variable. |
64 | ||
252aa082 | 65 | my $a = "2:" + 3; |
4358a253 | 66 | no warnings; |
252aa082 | 67 | my $b = "2:" + 3; |
0453d815 PM |
68 | |
69 | Note that neither the B<-w> flag or the C<$^W> can be used to | |
70 | disable/enable default warnings. They are still mandatory in this case. | |
71 | ||
72 | =head2 What's wrong with B<-w> and C<$^W> | |
73 | ||
74 | Although very useful, the big problem with using B<-w> on the command | |
75 | line to enable warnings is that it is all or nothing. Take the typical | |
76 | scenario when you are writing a Perl program. Parts of the code you | |
77 | will write yourself, but it's very likely that you will make use of | |
78 | pre-written Perl modules. If you use the B<-w> flag in this case, you | |
79 | end up enabling warnings in pieces of code that you haven't written. | |
80 | ||
81 | Similarly, using C<$^W> to either disable or enable blocks of code is | |
82 | fundamentally flawed. For a start, say you want to disable warnings in | |
83 | a block of code. You might expect this to be enough to do the trick: | |
84 | ||
85 | { | |
4358a253 SS |
86 | local ($^W) = 0; |
87 | my $a =+ 2; | |
88 | my $b; chop $b; | |
0453d815 PM |
89 | } |
90 | ||
91 | When this code is run with the B<-w> flag, a warning will be produced | |
92 | for the C<$a> line -- C<"Reversed += operator">. | |
93 | ||
94 | The problem is that Perl has both compile-time and run-time warnings. To | |
95 | disable compile-time warnings you need to rewrite the code like this: | |
96 | ||
97 | { | |
98 | BEGIN { $^W = 0 } | |
4358a253 SS |
99 | my $a =+ 2; |
100 | my $b; chop $b; | |
0453d815 PM |
101 | } |
102 | ||
f1f33818 | 103 | The other big problem with C<$^W> is the way you can inadvertently |
0453d815 PM |
104 | change the warning setting in unexpected places in your code. For example, |
105 | when the code below is run (without the B<-w> flag), the second call | |
106 | to C<doit> will trip a C<"Use of uninitialized value"> warning, whereas | |
107 | the first will not. | |
108 | ||
109 | sub doit | |
110 | { | |
4358a253 | 111 | my $b; chop $b; |
0453d815 PM |
112 | } |
113 | ||
4358a253 | 114 | doit(); |
0453d815 PM |
115 | |
116 | { | |
4358a253 | 117 | local ($^W) = 1; |
0453d815 PM |
118 | doit() |
119 | } | |
120 | ||
121 | This is a side-effect of C<$^W> being dynamically scoped. | |
122 | ||
123 | Lexical warnings get around these limitations by allowing finer control | |
124 | over where warnings can or can't be tripped. | |
125 | ||
126 | =head2 Controlling Warnings from the Command Line | |
127 | ||
128 | There are three Command Line flags that can be used to control when | |
129 | warnings are (or aren't) produced: | |
130 | ||
131 | =over 5 | |
132 | ||
133 | =item B<-w> | |
d74e8afc | 134 | X<-w> |
0453d815 PM |
135 | |
136 | This is the existing flag. If the lexical warnings pragma is B<not> | |
137 | used in any of you code, or any of the modules that you use, this flag | |
138 | will enable warnings everywhere. See L<Backward Compatibility> for | |
139 | details of how this flag interacts with lexical warnings. | |
140 | ||
141 | =item B<-W> | |
d74e8afc | 142 | X<-W> |
c47ff5f1 | 143 | |
0453d815 PM |
144 | If the B<-W> flag is used on the command line, it will enable all warnings |
145 | throughout the program regardless of whether warnings were disabled | |
4438c4b7 | 146 | locally using C<no warnings> or C<$^W =0>. This includes all files that get |
0453d815 PM |
147 | included via C<use>, C<require> or C<do>. |
148 | Think of it as the Perl equivalent of the "lint" command. | |
149 | ||
150 | =item B<-X> | |
d74e8afc | 151 | X<-X> |
0453d815 PM |
152 | |
153 | Does the exact opposite to the B<-W> flag, i.e. it disables all warnings. | |
154 | ||
155 | =back | |
156 | ||
157 | =head2 Backward Compatibility | |
158 | ||
159 | If you are used with working with a version of Perl prior to the | |
160 | introduction of lexically scoped warnings, or have code that uses both | |
161 | lexical warnings and C<$^W>, this section will describe how they interact. | |
162 | ||
163 | How Lexical Warnings interact with B<-w>/C<$^W>: | |
5a3e7812 | 164 | |
0453d815 PM |
165 | =over 5 |
166 | ||
167 | =item 1. | |
168 | ||
169 | If none of the three command line flags (B<-w>, B<-W> or B<-X>) that | |
e476b1b5 GS |
170 | control warnings is used and neither C<$^W> or the C<warnings> pragma |
171 | are used, then default warnings will be enabled and optional warnings | |
172 | disabled. | |
0453d815 PM |
173 | This means that legacy code that doesn't attempt to control the warnings |
174 | will work unchanged. | |
175 | ||
176 | =item 2. | |
177 | ||
178 | The B<-w> flag just sets the global C<$^W> variable as in 5.005 -- this | |
179 | means that any legacy code that currently relies on manipulating C<$^W> | |
180 | to control warning behavior will still work as is. | |
181 | ||
182 | =item 3. | |
c47ff5f1 | 183 | |
0453d815 PM |
184 | Apart from now being a boolean, the C<$^W> variable operates in exactly |
185 | the same horrible uncontrolled global way, except that it cannot | |
186 | disable/enable default warnings. | |
187 | ||
188 | =item 4. | |
c47ff5f1 | 189 | |
e476b1b5 | 190 | If a piece of code is under the control of the C<warnings> pragma, |
0453d815 PM |
191 | both the C<$^W> variable and the B<-w> flag will be ignored for the |
192 | scope of the lexical warning. | |
193 | ||
194 | =item 5. | |
c47ff5f1 | 195 | |
0453d815 PM |
196 | The only way to override a lexical warnings setting is with the B<-W> |
197 | or B<-X> command line flags. | |
198 | ||
199 | =back | |
200 | ||
106325ad | 201 | The combined effect of 3 & 4 is that it will allow code which uses |
e476b1b5 | 202 | the C<warnings> pragma to control the warning behavior of $^W-type |
0453d815 PM |
203 | code (using a C<local $^W=0>) if it really wants to, but not vice-versa. |
204 | ||
0453d815 | 205 | =head2 Category Hierarchy |
d74e8afc | 206 | X<warning, categories> |
c47ff5f1 | 207 | |
e476b1b5 GS |
208 | A hierarchy of "categories" have been defined to allow groups of warnings |
209 | to be enabled/disabled in isolation. | |
210 | ||
211 | The current hierarchy is: | |
212 | ||
213 | all -+ | |
214 | | | |
702815ca RGS |
215 | +- assertions |
216 | | | |
e476b1b5 GS |
217 | +- closure |
218 | | | |
12bcd1a6 PM |
219 | +- deprecated |
220 | | | |
e476b1b5 GS |
221 | +- exiting |
222 | | | |
223 | +- glob | |
224 | | | |
225 | +- io -----------+ | |
226 | | | | |
227 | | +- closed | |
228 | | | | |
229 | | +- exec | |
230 | | | | |
99ef548b PM |
231 | | +- layer |
232 | | | | |
e476b1b5 GS |
233 | | +- newline |
234 | | | | |
235 | | +- pipe | |
236 | | | | |
237 | | +- unopened | |
238 | | | |
239 | +- misc | |
240 | | | |
241 | +- numeric | |
242 | | | |
243 | +- once | |
244 | | | |
245 | +- overflow | |
246 | | | |
247 | +- pack | |
248 | | | |
249 | +- portable | |
250 | | | |
251 | +- recursion | |
252 | | | |
253 | +- redefine | |
254 | | | |
255 | +- regexp | |
256 | | | |
257 | +- severe -------+ | |
258 | | | | |
259 | | +- debugging | |
260 | | | | |
261 | | +- inplace | |
262 | | | | |
263 | | +- internal | |
264 | | | | |
265 | | +- malloc | |
266 | | | |
267 | +- signal | |
268 | | | |
269 | +- substr | |
270 | | | |
271 | +- syntax -------+ | |
272 | | | | |
273 | | +- ambiguous | |
274 | | | | |
275 | | +- bareword | |
276 | | | | |
e476b1b5 GS |
277 | | +- digit |
278 | | | | |
279 | | +- parenthesis | |
280 | | | | |
281 | | +- precedence | |
282 | | | | |
283 | | +- printf | |
284 | | | | |
285 | | +- prototype | |
286 | | | | |
287 | | +- qw | |
288 | | | | |
289 | | +- reserved | |
290 | | | | |
291 | | +- semicolon | |
292 | | | |
293 | +- taint | |
294 | | | |
38875929 DM |
295 | +- threads |
296 | | | |
e476b1b5 GS |
297 | +- uninitialized |
298 | | | |
299 | +- unpack | |
300 | | | |
301 | +- untie | |
302 | | | |
303 | +- utf8 | |
304 | | | |
305 | +- void | |
0453d815 | 306 | |
4438c4b7 JH |
307 | Just like the "strict" pragma any of these categories can be combined |
308 | ||
4358a253 SS |
309 | use warnings qw(void redefine); |
310 | no warnings qw(io syntax untie); | |
4438c4b7 JH |
311 | |
312 | Also like the "strict" pragma, if there is more than one instance of the | |
e476b1b5 | 313 | C<warnings> pragma in a given scope the cumulative effect is additive. |
4438c4b7 | 314 | |
4358a253 | 315 | use warnings qw(void); # only "void" warnings enabled |
4438c4b7 | 316 | ... |
4358a253 | 317 | use warnings qw(io); # only "void" & "io" warnings enabled |
4438c4b7 | 318 | ... |
4358a253 | 319 | no warnings qw(void); # only "io" warnings enabled |
4438c4b7 | 320 | |
e476b1b5 GS |
321 | To determine which category a specific warning has been assigned to see |
322 | L<perldiag>. | |
0453d815 | 323 | |
12bcd1a6 PM |
324 | Note: In Perl 5.6.1, the lexical warnings category "deprecated" was a |
325 | sub-category of the "syntax" category. It is now a top-level category | |
326 | in its own right. | |
327 | ||
328 | ||
0453d815 | 329 | =head2 Fatal Warnings |
d74e8afc | 330 | X<warning, fatal> |
c47ff5f1 | 331 | |
0453d815 | 332 | The presence of the word "FATAL" in the category list will escalate any |
e476b1b5 | 333 | warnings detected from the categories specified in the lexical scope |
f1f33818 PM |
334 | into fatal errors. In the code below, the use of C<time>, C<length> |
335 | and C<join> can all produce a C<"Useless use of xxx in void context"> | |
336 | warning. | |
4438c4b7 | 337 | |
4358a253 | 338 | use warnings; |
cea6626f | 339 | |
4358a253 | 340 | time; |
cea6626f | 341 | |
0453d815 | 342 | { |
4358a253 SS |
343 | use warnings FATAL => qw(void); |
344 | length "abc"; | |
0453d815 | 345 | } |
cea6626f | 346 | |
4358a253 | 347 | join "", 1,2,3; |
cea6626f | 348 | |
4358a253 | 349 | print "done\n"; |
f1f33818 PM |
350 | |
351 | When run it produces this output | |
352 | ||
353 | Useless use of time in void context at fatal line 3. | |
354 | Useless use of length in void context at fatal line 7. | |
355 | ||
356 | The scope where C<length> is used has escalated the C<void> warnings | |
357 | category into a fatal error, so the program terminates immediately it | |
358 | encounters the warning. | |
c47ff5f1 | 359 | |
6e9af7e4 PM |
360 | To explicitly turn off a "FATAL" warning you just disable the warning |
361 | it is associated with. So, for example, to disable the "void" warning | |
362 | in the example above, either of these will do the trick: | |
08540116 PM |
363 | |
364 | no warnings qw(void); | |
365 | no warnings FATAL => qw(void); | |
0453d815 | 366 | |
6e9af7e4 PM |
367 | If you want to downgrade a warning that has been escalated into a fatal |
368 | error back to a normal warning, you can use the "NONFATAL" keyword. For | |
369 | example, the code below will promote all warnings into fatal errors, | |
370 | except for those in the "syntax" category. | |
371 | ||
372 | use warnings FATAL => 'all', NONFATAL => 'syntax'; | |
373 | ||
e476b1b5 | 374 | =head2 Reporting Warnings from a Module |
d74e8afc | 375 | X<warning, reporting> X<warning, registering> |
e476b1b5 | 376 | |
d3a7d8c7 GS |
377 | The C<warnings> pragma provides a number of functions that are useful for |
378 | module authors. These are used when you want to report a module-specific | |
7e6d00f8 | 379 | warning to a calling module has enabled warnings via the C<warnings> |
d3a7d8c7 | 380 | pragma. |
e476b1b5 | 381 | |
d3a7d8c7 | 382 | Consider the module C<MyMod::Abc> below. |
e476b1b5 | 383 | |
d3a7d8c7 | 384 | package MyMod::Abc; |
e476b1b5 | 385 | |
d3a7d8c7 GS |
386 | use warnings::register; |
387 | ||
388 | sub open { | |
4358a253 | 389 | my $path = shift; |
7ddf7bb5 | 390 | if ($path !~ m#^/#) { |
2359510d | 391 | warnings::warn("changing relative path to /var/abc") |
7ddf7bb5 | 392 | if warnings::enabled(); |
2359510d | 393 | $path = "/var/abc/$path"; |
d3a7d8c7 GS |
394 | } |
395 | } | |
396 | ||
4358a253 | 397 | 1; |
d3a7d8c7 GS |
398 | |
399 | The call to C<warnings::register> will create a new warnings category | |
7e6d00f8 PM |
400 | called "MyMod::abc", i.e. the new category name matches the current |
401 | package name. The C<open> function in the module will display a warning | |
402 | message if it gets given a relative path as a parameter. This warnings | |
403 | will only be displayed if the code that uses C<MyMod::Abc> has actually | |
404 | enabled them with the C<warnings> pragma like below. | |
d3a7d8c7 GS |
405 | |
406 | use MyMod::Abc; | |
407 | use warnings 'MyMod::Abc'; | |
408 | ... | |
409 | abc::open("../fred.txt"); | |
410 | ||
411 | It is also possible to test whether the pre-defined warnings categories are | |
412 | set in the calling module with the C<warnings::enabled> function. Consider | |
413 | this snippet of code: | |
414 | ||
415 | package MyMod::Abc; | |
416 | ||
417 | sub open { | |
7e6d00f8 | 418 | warnings::warnif("deprecated", |
4358a253 SS |
419 | "open is deprecated, use new instead"); |
420 | new(@_); | |
e476b1b5 | 421 | } |
6bc102ca | 422 | |
e476b1b5 GS |
423 | sub new |
424 | ... | |
4358a253 | 425 | 1; |
e476b1b5 GS |
426 | |
427 | The function C<open> has been deprecated, so code has been included to | |
428 | display a warning message whenever the calling module has (at least) the | |
429 | "deprecated" warnings category enabled. Something like this, say. | |
430 | ||
431 | use warnings 'deprecated'; | |
d3a7d8c7 | 432 | use MyMod::Abc; |
e476b1b5 | 433 | ... |
4358a253 | 434 | MyMod::Abc::open($filename); |
e476b1b5 | 435 | |
7e6d00f8 PM |
436 | Either the C<warnings::warn> or C<warnings::warnif> function should be |
437 | used to actually display the warnings message. This is because they can | |
438 | make use of the feature that allows warnings to be escalated into fatal | |
439 | errors. So in this case | |
e476b1b5 | 440 | |
d3a7d8c7 GS |
441 | use MyMod::Abc; |
442 | use warnings FATAL => 'MyMod::Abc'; | |
e476b1b5 | 443 | ... |
d3a7d8c7 | 444 | MyMod::Abc::open('../fred.txt'); |
e476b1b5 | 445 | |
7e6d00f8 | 446 | the C<warnings::warnif> function will detect this and die after |
d3a7d8c7 | 447 | displaying the warning message. |
e476b1b5 | 448 | |
7e6d00f8 PM |
449 | The three warnings functions, C<warnings::warn>, C<warnings::warnif> |
450 | and C<warnings::enabled> can optionally take an object reference in place | |
451 | of a category name. In this case the functions will use the class name | |
452 | of the object as the warnings category. | |
453 | ||
454 | Consider this example: | |
455 | ||
4358a253 | 456 | package Original; |
7e6d00f8 | 457 | |
4358a253 SS |
458 | no warnings; |
459 | use warnings::register; | |
7e6d00f8 PM |
460 | |
461 | sub new | |
462 | { | |
4358a253 SS |
463 | my $class = shift; |
464 | bless [], $class; | |
7e6d00f8 PM |
465 | } |
466 | ||
467 | sub check | |
468 | { | |
4358a253 SS |
469 | my $self = shift; |
470 | my $value = shift; | |
7e6d00f8 PM |
471 | |
472 | if ($value % 2 && warnings::enabled($self)) | |
473 | { warnings::warn($self, "Odd numbers are unsafe") } | |
474 | } | |
475 | ||
476 | sub doit | |
477 | { | |
4358a253 SS |
478 | my $self = shift; |
479 | my $value = shift; | |
480 | $self->check($value); | |
7e6d00f8 PM |
481 | # ... |
482 | } | |
483 | ||
4358a253 | 484 | 1; |
7e6d00f8 | 485 | |
4358a253 | 486 | package Derived; |
7e6d00f8 | 487 | |
4358a253 SS |
488 | use warnings::register; |
489 | use Original; | |
490 | our @ISA = qw( Original ); | |
7e6d00f8 PM |
491 | sub new |
492 | { | |
4358a253 SS |
493 | my $class = shift; |
494 | bless [], $class; | |
7e6d00f8 PM |
495 | } |
496 | ||
13a2d996 | 497 | |
4358a253 | 498 | 1; |
7e6d00f8 PM |
499 | |
500 | The code below makes use of both modules, but it only enables warnings from | |
501 | C<Derived>. | |
502 | ||
4358a253 SS |
503 | use Original; |
504 | use Derived; | |
7e6d00f8 | 505 | use warnings 'Derived'; |
4358a253 SS |
506 | my $a = new Original; |
507 | $a->doit(1); | |
508 | my $b = new Derived; | |
509 | $a->doit(1); | |
7e6d00f8 PM |
510 | |
511 | When this code is run only the C<Derived> object, C<$b>, will generate | |
512 | a warning. | |
513 | ||
514 | Odd numbers are unsafe at main.pl line 7 | |
515 | ||
516 | Notice also that the warning is reported at the line where the object is first | |
517 | used. | |
518 | ||
e476b1b5 | 519 | =head1 TODO |
c47ff5f1 | 520 | |
0453d815 PM |
521 | perl5db.pl |
522 | The debugger saves and restores C<$^W> at runtime. I haven't checked | |
523 | whether the debugger will still work with the lexical warnings | |
524 | patch applied. | |
525 | ||
526 | diagnostics.pm | |
527 | I *think* I've got diagnostics to work with the lexical warnings | |
528 | patch, but there were design decisions made in diagnostics to work | |
529 | around the limitations of C<$^W>. Now that those limitations are gone, | |
530 | the module should be revisited. | |
531 | ||
7e6d00f8 PM |
532 | document calling the warnings::* functions from XS |
533 | ||
0453d815 PM |
534 | =head1 SEE ALSO |
535 | ||
e476b1b5 | 536 | L<warnings>, L<perldiag>. |
c47ff5f1 | 537 | |
0453d815 | 538 | =head1 AUTHOR |
c47ff5f1 | 539 | |
0453d815 | 540 | Paul Marquess |