1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>perlstyle - perldoc.perl.org</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta http-equiv="Content-Language" content="en-gb">
<link rel="search" type="application/opensearchdescription+xml" title="Search perldoc.perl.org" href="/static/search.xml"/>
<link href="static/css-20100830.css" rel="stylesheet" rev="stylesheet" type="text/css" media="screen">
<link href="static/exploreperl.css" rel="stylesheet" rev="stylesheet" type="text/css">
</head>
<body onLoad="perldoc.startup();" onPageShow="if (event.persisted) perldoc.startup();">
<div id="page">
<div id="header">
<div id="homepage_link">
<a href="index.html"></a>
</div>
<div id="strapline">
Perl Programming Documentation
</div>
<div id="download_link" class="download">
<a href="http://www.perl.org/get.html">Download Perl</a>
</div>
<div id="explore_link" class="download">
<a id="explore_anchor" href="#">Explore</a>
</div>
</div>
<div id="body">
<div id="left_column">
<div class="side_group">
<div class="side_panel doc_panel">
<p>Manual</p>
<ul>
<li><a href="index-overview.html">Overview</a>
<li><a href="index-tutorials.html">Tutorials</a>
<li><a href="index-faq.html">FAQs</a>
<li><a href="index-history.html">History / Changes</a>
<li><a href="index-licence.html">License</a>
</ul>
</div>
<div class="side_panel doc_panel">
<p>Reference</p>
<ul>
<li><a href="index-language.html">Language</a>
<li><a href="index-functions.html">Functions</a>
<li><a href="perlop.html">Operators</a>
<li><a href="perlvar.html">Special Variables</a>
<li><a href="index-pragmas.html">Pragmas</a>
<li><a href="index-utilities.html">Utilities</a>
<li><a href="index-internals.html">Internals</a>
<li><a href="index-platforms.html">Platform Specific</a>
</ul>
</div>
<div class="side_panel doc_panel">
<p>Modules</p>
<ul>
<li>
<a href="index-modules-A.html">A</a>
•
<a href="index-modules-B.html">B</a>
•
<a href="index-modules-C.html">C</a>
•
<a href="index-modules-D.html">D</a>
•
<a href="index-modules-E.html">E</a>
<li>
<a href="index-modules-F.html">F</a>
•
<a href="index-modules-G.html">G</a>
•
<a href="index-modules-H.html">H</a>
•
<a href="index-modules-I.html">I</a>
•
<a href="index-modules-L.html">L</a>
<li>
<a href="index-modules-M.html">M</a>
•
<a href="index-modules-N.html">N</a>
•
<a href="index-modules-O.html">O</a>
•
<a href="index-modules-P.html">P</a>
•
<a href="index-modules-S.html">S</a>
<li>
<a href="index-modules-T.html">T</a>
•
<a href="index-modules-U.html">U</a>
•
<a href="index-modules-X.html">X</a>
</ul>
</div>
<div class="side_panel doc_panel">
<p>Tools</p>
<ul>
<li><a href="preferences.html">Preferences</a>
</ul>
</div>
</div>
</div>
<div id="centre_column">
<div id="content_header">
<div id="title_bar">
<div id="page_name">
<h1>perlstyle</h1>
</div>
<div id="perl_version">
Perl 5 version 14.0 documentation
</div>
<div class="page_links" id="page_links_top">
<a href="#" onClick="toolbar.goToTop();return false;">Go to top</a>
</div>
<div class="page_links" id="page_links_bottom">
<a href="#" id="page_index_toggle">Show page index</a> •
<a href="#" id="recent_pages_toggle">Show recent pages</a>
</div>
<div id="search_form">
<form action="search.html" method="GET" id="search">
<input type="text" name="q" id="search_box" alt="Search">
</form>
</div>
</div>
<div id="breadcrumbs">
<a href="index.html">Home</a> >
<a href="index-tutorials.html">Tutorials</a> >
perlstyle
</div>
</div>
<div id="content_body">
<!--[if lt IE 7]>
<div class="noscript">
<p>
<strong>It looks like you're using Internet Explorer 6. This is a very old
browser which does not offer full support for modern websites.</strong>
</p>
<p>
Unfortunately this means that this website will not work on
your computer.
</p>
<p>
Don't miss out though! To view the site (and get a better experience from
many other websites), simply upgrade to
<a href="http://www.microsoft.com/windows/Internet-explorer/default.aspx">Internet
Explorer 8</a>
or download an alternative browser such as
<a href="http://www.mozilla.com/en-US/firefox/firefox.html">Firefox</a>,
<a href="http://www.apple.com/safari/download/">Safari</a>, or
<a href="http://www.google.co.uk/chrome">Google Chrome</a>.
</p>
<p>
All of these browsers are free. If you're using a PC at work, you may
need to contact your IT administrator.
</p>
</div>
<![endif]-->
<noscript>
<div class="noscript">
<p>
<strong>Please note: Many features of this site require JavaScript. You appear to have JavaScript disabled,
or are running a non-JavaScript capable web browser.</strong>
</p>
<p>
To get the best experience, please enable JavaScript or download a modern web browser such as <a href="http://www.microsoft.com/windows/Internet-explorer/default.aspx">Internet Explorer 8</a>, <a href="http://www.mozilla.com/en-US/firefox/firefox.html">Firefox</a>, <a href="http://www.apple.com/safari/download/">Safari</a>, or <a href="http://www.google.co.uk/chrome">Google Chrome</a>.
</p>
</div>
</noscript>
<div id="recent_pages" class="hud_container">
<div id="recent_pages_header" class="hud_header">
<div id="recent_pages_close" class="hud_close"><a href="#" onClick="recentPages.hide();return false;"></a></div>
<div id="recent_pages_title" class="hud_title"><span class="hud_span_top">Recently read</span></div>
<div id="recent_pages_topright" class="hud_topright"></div>
</div>
<div id="recent_pages_content" class="hud_content">
</div>
<div id="recent_pages_footer" class="hud_footer">
<div id="recent_pages_bottomleft" class="hud_bottomleft"></div>
<div id="recent_pages_bottom" class="hud_bottom"><span class="hud_span_bottom"></span></div>
<div id="recent_pages_resize" class="hud_resize"></div>
</div>
</div>
<div id="from_search"></div>
<h1>perlstyle</h1>
<!-- -->
<ul><li><a href="#NAME">NAME</a><li><a href="#DESCRIPTION">DESCRIPTION</a></ul><a name="NAME"></a><h1>NAME</h1>
<p>perlstyle - Perl style guide</p>
<a name="DESCRIPTION"></a><h1>DESCRIPTION</h1>
<p>Each programmer will, of course, have his or her own preferences in
regards to formatting, but there are some general guidelines that will
make your programs easier to read, understand, and maintain.</p>
<p>The most important thing is to run your programs under the <b>-w</b>
flag at all times. You may turn it off explicitly for particular
portions of code via the <code class="inline"><a class="l_k" href="functions/no.html">no</a> <span class="w">warnings</span></code>
pragma or the <code class="inline"><span class="i">$^W</span></code>
variable
if you must. You should also always run under <code class="inline"><a class="l_k" href="functions/use.html">use</a> <span class="w">strict</span></code>
or know the
reason why not. The <code class="inline"><a class="l_k" href="functions/use.html">use</a> <span class="w">sigtrap</span></code>
and even <code class="inline"><a class="l_k" href="functions/use.html">use</a> <span class="w">diagnostics</span></code>
pragmas
may also prove useful.</p>
<p>Regarding aesthetics of code lay out, about the only thing Larry
cares strongly about is that the closing curly bracket of
a multi-line BLOCK should line up with the keyword that started the construct.
Beyond that, he has other preferences that aren't so strong:</p>
<ul>
<li>
<p>4-column indent.</p>
</li>
<li>
<p>Opening curly on same line as keyword, if possible, otherwise line up.</p>
</li>
<li>
<p>Space before the opening curly of a multi-line BLOCK.</p>
</li>
<li>
<p>One-line BLOCK may be put on one line, including curlies.</p>
</li>
<li>
<p>No space before the semicolon.</p>
</li>
<li>
<p>Semicolon omitted in "short" one-line BLOCK.</p>
</li>
<li>
<p>Space around most operators.</p>
</li>
<li>
<p>Space around a "complex" subscript (inside brackets).</p>
</li>
<li>
<p>Blank lines between chunks that do different things.</p>
</li>
<li>
<p>Uncuddled elses.</p>
</li>
<li>
<p>No space between function name and its opening parenthesis.</p>
</li>
<li>
<p>Space after each comma.</p>
</li>
<li>
<p>Long lines broken after an operator (except <code class="inline">and</code>
and <code class="inline">or</code>
).</p>
</li>
<li>
<p>Space after last parenthesis matching on current line.</p>
</li>
<li>
<p>Line up corresponding items vertically.</p>
</li>
<li>
<p>Omit redundant punctuation as long as clarity doesn't suffer.</p>
</li>
</ul>
<p>Larry has his reasons for each of these things, but he doesn't claim that
everyone else's mind works the same as his does.</p>
<p>Here are some other more substantive style issues to think about:</p>
<ul>
<li>
<p>Just because you <i>CAN</i> do something a particular way doesn't mean that
you <i>SHOULD</i> do it that way. Perl is designed to give you several
ways to do anything, so consider picking the most readable one. For
instance</p>
<pre class="verbatim"><ol><li> <a class="l_k" href="functions/open.html">open</a><span class="s">(</span><span class="w">FOO</span><span class="cm">,</span><span class="i">$foo</span><span class="s">)</span> || <a class="l_k" href="functions/die.html">die</a> <span class="q">"Can't open $foo: $!"</span><span class="sc">;</span></li></ol></pre><p>is better than</p>
<pre class="verbatim"><ol><li> <a class="l_k" href="functions/die.html">die</a> <span class="q">"Can't open $foo: $!"</span> unless <a class="l_k" href="functions/open.html">open</a><span class="s">(</span><span class="w">FOO</span><span class="cm">,</span><span class="i">$foo</span><span class="s">)</span><span class="sc">;</span></li></ol></pre><p>because the second way hides the main point of the statement in a
modifier. On the other hand</p>
<pre class="verbatim"><ol><li> <a class="l_k" href="functions/print.html">print</a> <span class="q">"Starting analysis\n"</span> if <span class="i">$verbose</span><span class="sc">;</span></li></ol></pre><p>is better than</p>
<pre class="verbatim"><ol><li> <span class="i">$verbose</span> && <a class="l_k" href="functions/print.html">print</a> <span class="q">"Starting analysis\n"</span><span class="sc">;</span></li></ol></pre><p>because the main point isn't whether the user typed <b>-v</b> or not.</p>
<p>Similarly, just because an operator lets you assume default arguments
doesn't mean that you have to make use of the defaults. The defaults
are there for lazy systems programmers writing one-shot programs. If
you want your program to be readable, consider supplying the argument.</p>
<p>Along the same lines, just because you <i>CAN</i> omit parentheses in many
places doesn't mean that you ought to:</p>
<pre class="verbatim"><ol><li> <a class="l_k" href="functions/return.html">return</a> <a class="l_k" href="functions/print.html">print</a> <a class="l_k" href="functions/reverse.html">reverse</a> <a class="l_k" href="functions/sort.html">sort</a> <span class="i">num</span> <a class="l_k" href="functions/values.html">values</a> <span class="i">%array</span><span class="sc">;</span></li><li> <a class="l_k" href="functions/return.html">return</a> <a class="l_k" href="functions/print.html">print</a><span class="s">(</span><a class="l_k" href="functions/reverse.html">reverse</a><span class="s">(</span><a class="l_k" href="functions/sort.html">sort</a> <span class="i">num</span> <span class="s">(</span><a class="l_k" href="functions/values.html">values</a><span class="s">(</span><span class="i">%array</span><span class="s">)</span><span class="s">)</span><span class="s">)</span><span class="s">)</span><span class="sc">;</span></li></ol></pre><p>When in doubt, parenthesize. At the very least it will let some poor
schmuck bounce on the % key in <b>vi</b>.</p>
<p>Even if you aren't in doubt, consider the mental welfare of the person
who has to maintain the code after you, and who will probably put
parentheses in the wrong place.</p>
</li>
<li>
<p>Don't go through silly contortions to exit a loop at the top or the
bottom, when Perl provides the <code class="inline"><a class="l_k" href="functions/last.html">last</a></code> operator so you can exit in
the middle. Just "outdent" it a little to make it more visible:</p>
<pre class="verbatim"><ol><li> <span class="j">LINE:</span></li><li> for <span class="s">(</span><span class="sc">;</span><span class="sc">;</span><span class="s">)</span> <span class="s">{</span></li><li> <span class="w">statements</span><span class="sc">;</span></li><li> <a class="l_k" href="functions/last.html">last</a> <span class="j">LINE</span> if <span class="i">$foo</span><span class="sc">;</span></li><li> <a class="l_k" href="functions/next.html">next</a> <span class="j">LINE</span> if <span class="q">/^#/</span><span class="sc">;</span></li><li> <span class="w">statements</span><span class="sc">;</span></li><li> <span class="s">}</span></li></ol></pre></li>
<li>
<p>Don't be afraid to use loop labels--they're there to enhance
readability as well as to allow multilevel loop breaks. See the
previous example.</p>
</li>
<li>
<p>Avoid using <code class="inline"><a class="l_k" href="functions/grep.html">grep()</a></code> (or <code class="inline"><a class="l_k" href="functions/map.html">map()</a></code>) or `backticks` in a void context, that is,
when you just throw away their return values. Those functions all
have return values, so use them. Otherwise use a <code class="inline">foreach<span class="s">(</span><span class="s">)</span></code>
loop or
the <code class="inline"><a class="l_k" href="functions/system.html">system()</a></code> function instead.</p>
</li>
<li>
<p>For portability, when using features that may not be implemented on
every machine, test the construct in an eval to see if it fails. If
you know what version or patchlevel a particular feature was
implemented, you can test <code class="inline"><span class="i">$]</span></code>
(<code class="inline"><span class="i">$PERL_VERSION</span></code>
in <code class="inline"><span class="w">English</span></code>
) to see if it
will be there. The <code class="inline"><span class="w">Config</span></code>
module will also let you interrogate values
determined by the <b>Configure</b> program when Perl was installed.</p>
</li>
<li>
<p>Choose mnemonic identifiers. If you can't remember what mnemonic means,
you've got a problem.</p>
</li>
<li>
<p>While short identifiers like <code class="inline"><span class="i">$gotit</span></code>
are probably ok, use underscores to
separate words in longer identifiers. It is generally easier to read
<code class="inline"><span class="i">$var_names_like_this</span></code>
than <code class="inline"><span class="i">$VarNamesLikeThis</span></code>
, especially for
non-native speakers of English. It's also a simple rule that works
consistently with <code class="inline"><span class="w">VAR_NAMES_LIKE_THIS</span></code>
.</p>
<p>Package names are sometimes an exception to this rule. Perl informally
reserves lowercase module names for "pragma" modules like <code class="inline"><span class="w">integer</span></code>
and
<code class="inline"><span class="w">strict</span></code>
. Other modules should begin with a capital letter and use mixed
case, but probably without underscores due to limitations in primitive
file systems' representations of module names as files that must fit into a
few sparse bytes.</p>
</li>
<li>
<p>You may find it helpful to use letter case to indicate the scope
or nature of a variable. For example:</p>
<pre class="verbatim"><ol><li> $ALL_CAPS_HERE constants only (beware clashes with perl vars!)</li><li> $Some_Caps_Here package-wide global/static</li><li> $no_caps_here function scope my() or local() variables</li></ol></pre><p>Function and method names seem to work best as all lowercase.
E.g., <code class="inline"><span class="i">$obj</span><span class="i">->as_string</span><span class="s">(</span><span class="s">)</span></code>
.</p>
<p>You can use a leading underscore to indicate that a variable or
function should not be used outside the package that defined it.</p>
</li>
<li>
<p>If you have a really hairy regular expression, use the <code class="inline">/x</code> modifier and
put in some whitespace to make it look a little less like line noise.
Don't use slash as a delimiter when your regexp has slashes or backslashes.</p>
</li>
<li>
<p>Use the new <code class="inline">and</code>
and <code class="inline">or</code>
operators to avoid having to parenthesize
list operators so much, and to reduce the incidence of punctuation
operators like <code class="inline">&&</code> and <code class="inline">||</code>. Call your subroutines as if they were
functions or list operators to avoid excessive ampersands and parentheses.</p>
</li>
<li>
<p>Use here documents instead of repeated <code class="inline"><a class="l_k" href="functions/print.html">print()</a></code> statements.</p>
</li>
<li>
<p>Line up corresponding things vertically, especially if it'd be too long
to fit on one line anyway.</p>
<pre class="verbatim"><ol><li> <span class="i">$IDX</span> = <span class="i">$ST_MTIME</span><span class="sc">;</span></li><li> <span class="i">$IDX</span> = <span class="i">$ST_ATIME</span> if <span class="i">$opt_u</span><span class="sc">;</span></li><li> <span class="i">$IDX</span> = <span class="i">$ST_CTIME</span> if <span class="i">$opt_c</span><span class="sc">;</span></li><li> <span class="i">$IDX</span> = <span class="i">$ST_SIZE</span> if <span class="i">$opt_s</span><span class="sc">;</span></li><li></li><li> <a class="l_k" href="functions/mkdir.html">mkdir</a> <span class="i">$tmpdir</span><span class="cm">,</span> <span class="n">0700</span> or <a class="l_k" href="functions/die.html">die</a> <span class="q">"can't mkdir $tmpdir: $!"</span><span class="sc">;</span></li><li> <a class="l_k" href="functions/chdir.html">chdir</a><span class="s">(</span><span class="i">$tmpdir</span><span class="s">)</span> or <a class="l_k" href="functions/die.html">die</a> <span class="q">"can't chdir $tmpdir: $!"</span><span class="sc">;</span></li><li> <a class="l_k" href="functions/mkdir.html">mkdir</a> <span class="q">'tmp'</span><span class="cm">,</span> <span class="n">0777</span> or <a class="l_k" href="functions/die.html">die</a> <span class="q">"can't mkdir $tmpdir/tmp: $!"</span><span class="sc">;</span></li></ol></pre></li>
<li>
<p>Always check the return codes of system calls. Good error messages should
go to <code class="inline"><span class="w">STDERR</span></code>
, include which program caused the problem, what the failed
system call and arguments were, and (VERY IMPORTANT) should contain the
standard system error message for what went wrong. Here's a simple but
sufficient example:</p>
<pre class="verbatim"><ol><li> <a class="l_k" href="functions/opendir.html">opendir</a><span class="s">(</span><span class="w">D</span><span class="cm">,</span> <span class="i">$dir</span><span class="s">)</span> or <a class="l_k" href="functions/die.html">die</a> <span class="q">"can't opendir $dir: $!"</span><span class="sc">;</span></li></ol></pre></li>
<li>
<p>Line up your transliterations when it makes sense:</p>
<pre class="verbatim"><ol><li> <span class="q">tr [abc]</span></li><li> <span class="q"> [xyz]</span><span class="sc">;</span></li></ol></pre></li>
<li>
<p>Think about reusability. Why waste brainpower on a one-shot when you
might want to do something like it again? Consider generalizing your
code. Consider writing a module or object class. Consider making your
code run cleanly with <code class="inline"><a class="l_k" href="functions/use.html">use</a> <span class="w">strict</span></code>
and <code class="inline"><a class="l_k" href="functions/use.html">use</a> <span class="w">warnings</span></code>
(or <b>-w</b>) in
effect. Consider giving away your code. Consider changing your whole
world view. Consider... oh, never mind.</p>
</li>
<li>
<p>Try to document your code and use Pod formatting in a consistent way. Here
are commonly expected conventions:</p>
<ul>
<li>
<p>use <code class="inline"><span class="w">C</span><></code>
for function, variable and module names (and more
generally anything that can be considered part of code, like filehandles
or specific values). Note that function names are considered more readable
with parentheses after their name, that is <code class="inline"><span class="i">function</span><span class="s">(</span><span class="s">)</span></code>
.</p>
</li>
<li>
<p>use <code class="inline"><span class="w">B</span><></code>
for commands names like <b>cat</b> or <b>grep</b>.</p>
</li>
<li>
<p>use <code class="inline"><span class="w">F</span><></code>
or <code class="inline"><span class="w">C</span><></code>
for file names. <code class="inline"><span class="w">F</span><></code>
should
be the only Pod code for file names, but as most Pod formatters render it
as italic, Unix and Windows paths with their slashes and backslashes may
be less readable, and better rendered with <code class="inline"><span class="w">C</span><></code>
.</p>
</li>
</ul>
</li>
<li>
<p>Be consistent.</p>
</li>
<li>
<p>Be nice.</p>
</li>
</ul>
<div id="page_index" class="hud_container">
<div id="page_index_header" class="hud_header">
<div id="page_index_close" class="hud_close"><a href="#" onClick="pageIndex.hide();return false;"></a></div>
<div id="page_index_title" class="hud_title"><span class="hud_span_top">Page index</span></div>
<div id="page_index_topright" class="hud_topright"></div>
</div>
<div id="page_index_content" class="hud_content">
<ul><li><a href="#NAME">NAME</a><li><a href="#DESCRIPTION">DESCRIPTION</a></ul>
</div>
<div id="page_index_footer" class="hud_footer">
<div id="page_index_bottomleft" class="hud_bottomleft"></div>
<div id="page_index_bottom" class="hud_bottom"><span class="hud_span_bottom"></span></div>
<div id="page_index_resize" class="hud_resize"></div>
</div>
</div>
</div>
<div id="content_footer">
</div>
</div>
<div class="clear"></div>
</div>
<div id="footer">
<div id="footer_content">
<div id="footer_strapline">
perldoc.perl.org - Official documentation for the Perl programming language
</div>
<div id="footer_links">
<div id="address">
<p class="name">Contact details</p>
<p class="address">
Site maintained by <a href="http://perl.jonallen.info">Jon Allen (JJ)</a><br>
See the <a href="http://perl.jonallen.info/projects/perldoc">project page</a> for more details
</p>
<p class="contact">
Documentation maintained by the <a href="http://lists.cpan.org/showlist.cgi?name=perl5-porters">Perl 5 Porters</a>
</p>
</div>
<ul class="f1">
<li>Manual
<ul class="f2">
<li><a href="index-overview.html">Overview</a>
<li><a href="index-tutorials.html">Tutorials</a>
<li><a href="index-faq.html">FAQs</a>
<li><a href="index-history.html">Changes</a>
</ul>
<li>Reference
<ul class="f2">
<li><a href="index-language.html">Language</a>
<li><a href="index-functions.html">Functions</a>
<li><a href="perlop.html">Operators</a>
<li><a href="perlvar.html">Variables</a>
</ul>
<li>Modules
<ul class="f2">
<li><a href="index-modules-A.html">Modules</a>
<li><a href="index-pragmas.html">Pragmas</a>
<li><a href="index-utilities.html">Utilities</a>
</ul>
<li>Misc
<ul class="f2">
<li><a href="index-licence.html">License</a>
<li><a href="index-internals.html">Internals</a>
<li><a href="index-platforms.html">Platforms</a>
</ul> </ul>
<div class="clear"></div>
</div>
</div>
<div id="footer_end">
</div>
</div>
</div>
<script language="JavaScript" type="text/javascript" src="static/exploreperl.js"></script>
<script language="JavaScript" src="static/combined-20100403.js" type="text/javascript"></script>
<script language="JavaScript" type="text/javascript">
perldoc.setPath(0);
perldoc.pageName = 'perlstyle';
perldoc.pageAddress = 'perlstyle.html';
perldoc.contentPage = 1;
explorePerl.render();
explorePerl.addEvents('explore_anchor');
</script>
</body>
</html>
|
