/
usr
/
share
/
perl5
/
pod
/
/usr/share/perl5/pod
mkdir
upload
Name
Size
Mode
Actions
perl.pod
16667
0644
edit
dl
rm
perl56delta.pod
107201
0644
edit
dl
rm
perl58delta.pod
115165
0644
edit
dl
rm
perl561delta.pod
124713
0644
edit
dl
rm
perl581delta.pod
38060
0644
edit
dl
rm
perl582delta.pod
4470
0644
edit
dl
rm
perl583delta.pod
6335
0644
edit
dl
rm
perl584delta.pod
7363
0644
edit
dl
rm
perl585delta.pod
5889
0644
edit
dl
rm
perl586delta.pod
4651
0644
edit
dl
rm
perl587delta.pod
8357
0644
edit
dl
rm
perl588delta.pod
25281
0644
edit
dl
rm
perl589delta.pod
53904
0644
edit
dl
rm
perl5004delta.pod
56240
0644
edit
dl
rm
perl5005delta.pod
34283
0644
edit
dl
rm
perl5100delta.pod
55533
0644
edit
dl
rm
perl5101delta.pod
43888
0644
edit
dl
rm
perl5120delta.pod
89271
0644
edit
dl
rm
perl5121delta.pod
10141
0644
edit
dl
rm
perl5122delta.pod
9603
0644
edit
dl
rm
perl5123delta.pod
4100
0644
edit
dl
rm
perl5124delta.pod
3672
0644
edit
dl
rm
perl5125delta.pod
7683
0644
edit
dl
rm
perl5140delta.pod
144325
0644
edit
dl
rm
perl5141delta.pod
7966
0644
edit
dl
rm
perl5142delta.pod
6892
0644
edit
dl
rm
perl5143delta.pod
7760
0644
edit
dl
rm
perl5144delta.pod
6327
0644
edit
dl
rm
perl5160delta.pod
133651
0644
edit
dl
rm
perl5161delta.pod
6142
0644
edit
dl
rm
perl5162delta.pod
3594
0644
edit
dl
rm
perl5163delta.pod
4085
0644
edit
dl
rm
perl5180delta.pod
119429
0644
edit
dl
rm
perl5181delta.pod
6597
0644
edit
dl
rm
perl5182delta.pod
5335
0644
edit
dl
rm
perl5184delta.pod
4642
0644
edit
dl
rm
perl5200delta.pod
115698
0644
edit
dl
rm
perl5201delta.pod
10899
0644
edit
dl
rm
perl5202delta.pod
12509
0644
edit
dl
rm
perl5203delta.pod
9392
0644
edit
dl
rm
perl5220delta.pod
130963
0644
edit
dl
rm
perl5221delta.pod
10767
0644
edit
dl
rm
perl5222delta.pod
12629
0644
edit
dl
rm
perl5223delta.pod
8456
0644
edit
dl
rm
perl5224delta.pod
4460
0644
edit
dl
rm
perl5240delta.pod
64923
0644
edit
dl
rm
perl5241delta.pod
8215
0644
edit
dl
rm
perl5242delta.pod
4113
0644
edit
dl
rm
perl5243delta.pod
11428
0644
edit
dl
rm
perl5244delta.pod
4510
0644
edit
dl
rm
perl5260delta.pod
101835
0644
edit
dl
rm
perl5261delta.pod
7927
0644
edit
dl
rm
perl5262delta.pod
7880
0644
edit
dl
rm
perl5263delta.pod
7067
0644
edit
dl
rm
perl5280delta.pod
72113
0644
edit
dl
rm
perl5281delta.pod
4639
0644
edit
dl
rm
perl5282delta.pod
6200
0644
edit
dl
rm
perl5283delta.pod
5111
0644
edit
dl
rm
perl5300delta.pod
41281
0644
edit
dl
rm
perl5301delta.pod
5730
0644
edit
dl
rm
perl5302delta.pod
4682
0644
edit
dl
rm
perl5303delta.pod
4980
0644
edit
dl
rm
perl5320delta.pod
54601
0644
edit
dl
rm
perl5321delta.pod
7003
0644
edit
dl
rm
perlaix.pod
20438
0644
edit
dl
rm
perlamiga.pod
5749
0644
edit
dl
rm
perlandroid.pod
8222
0644
edit
dl
rm
perlapi.pod
493106
0644
edit
dl
rm
perlapio.pod
21336
0644
edit
dl
rm
perlartistic.pod
7010
0644
edit
dl
rm
perlbook.pod
8386
0644
edit
dl
rm
perlboot.pod
294
0644
edit
dl
rm
perlbot.pod
304
0644
edit
dl
rm
perlbs2000.pod
7994
0644
edit
dl
rm
perlcall.pod
56738
0644
edit
dl
rm
perlcheat.pod
4480
0644
edit
dl
rm
perlclib.pod
9607
0644
edit
dl
rm
perlcn.pod
4763
0644
edit
dl
rm
perlcommunity.pod
6983
0644
edit
dl
rm
perlcygwin.pod
27202
0644
edit
dl
rm
perldata.pod
49782
0644
edit
dl
rm
perldbmfilter.pod
4981
0644
edit
dl
rm
perldebguts.pod
42331
0644
edit
dl
rm
perldebtut.pod
22152
0644
edit
dl
rm
perldebug.pod
39383
0644
edit
dl
rm
perldelta.pod
7003
0644
edit
dl
rm
perldeprecation.pod
20825
0644
edit
dl
rm
perldiag.pod
296986
0644
edit
dl
rm
perldos.pod
10522
0644
edit
dl
rm
perldsc.pod
25614
0644
edit
dl
rm
perldtrace.pod
7959
0644
edit
dl
rm
perlebcdic.pod
84345
0644
edit
dl
rm
perlembed.pod
37569
0644
edit
dl
rm
perlexperiment.pod
7234
0644
edit
dl
rm
perlfork.pod
13355
0644
edit
dl
rm
perlform.pod
16608
0644
edit
dl
rm
perlfreebsd.pod
1623
0644
edit
dl
rm
perlfunc.pod
403777
0644
edit
dl
rm
perlgit.pod
29591
0644
edit
dl
rm
perlgov.pod
14481
0644
edit
dl
rm
perlgpl.pod
13815
0644
edit
dl
rm
perlguts.pod
162103
0644
edit
dl
rm
perlhack.pod
43157
0644
edit
dl
rm
perlhacktips.pod
57692
0644
edit
dl
rm
perlhacktut.pod
6153
0644
edit
dl
rm
perlhaiku.pod
1508
0644
edit
dl
rm
perlhist.pod
56164
0644
edit
dl
rm
perlhpux.pod
30609
0644
edit
dl
rm
perlhurd.pod
1994
0644
edit
dl
rm
perlintern.pod
83565
0644
edit
dl
rm
perlinterp.pod
33715
0644
edit
dl
rm
perlintro.pod
22135
0644
edit
dl
rm
perliol.pod
34804
0644
edit
dl
rm
perlipc.pod
71529
0644
edit
dl
rm
perlirix.pod
4415
0644
edit
dl
rm
perljp.pod
8431
0644
edit
dl
rm
perlko.pod
12208
0644
edit
dl
rm
perllexwarn.pod
355
0644
edit
dl
rm
perllinux.pod
2007
0644
edit
dl
rm
perllocale.pod
74112
0644
edit
dl
rm
perllol.pod
9580
0644
edit
dl
rm
perlmacos.pod
998
0644
edit
dl
rm
perlmacosx.pod
12124
0644
edit
dl
rm
perlmod.pod
26197
0644
edit
dl
rm
perlmodinstall.pod
10261
0644
edit
dl
rm
perlmodlib.pod
76348
0644
edit
dl
rm
perlmodstyle.pod
22588
0644
edit
dl
rm
perlmroapi.pod
3280
0644
edit
dl
rm
perlnetware.pod
6648
0644
edit
dl
rm
perlnewmod.pod
11037
0644
edit
dl
rm
perlnumber.pod
8353
0644
edit
dl
rm
perlobj.pod
35717
0644
edit
dl
rm
perlootut.pod
26757
0644
edit
dl
rm
perlop.pod
148888
0644
edit
dl
rm
perlopenbsd.pod
1224
0644
edit
dl
rm
perlopentut.pod
15223
0644
edit
dl
rm
perlos2.pod
93348
0644
edit
dl
rm
perlos390.pod
16527
0644
edit
dl
rm
perlos400.pod
4765
0644
edit
dl
rm
perlpacktut.pod
51370
0644
edit
dl
rm
perlperf.pod
49881
0644
edit
dl
rm
perlplan9.pod
5125
0644
edit
dl
rm
perlpod.pod
23076
0644
edit
dl
rm
perlpodspec.pod
68628
0644
edit
dl
rm
perlpolicy.pod
26562
0644
edit
dl
rm
perlport.pod
88693
0644
edit
dl
rm
perlpragma.pod
5176
0644
edit
dl
rm
perlqnx.pod
6673
0644
edit
dl
rm
perlre.pod
130817
0644
edit
dl
rm
perlreapi.pod
30245
0644
edit
dl
rm
perlrebackslash.pod
32285
0644
edit
dl
rm
perlrecharclass.pod
49707
0644
edit
dl
rm
perlref.pod
35432
0644
edit
dl
rm
perlreftut.pod
18826
0644
edit
dl
rm
perlreguts.pod
39301
0644
edit
dl
rm
perlrepository.pod
509
0644
edit
dl
rm
perlrequick.pod
19141
0644
edit
dl
rm
perlreref.pod
15590
0644
edit
dl
rm
perlretut.pod
122527
0644
edit
dl
rm
perlriscos.pod
1529
0644
edit
dl
rm
perlrun.pod
55980
0644
edit
dl
rm
perlsec.pod
27601
0644
edit
dl
rm
perlsecpolicy.pod
19450
0644
edit
dl
rm
perlsolaris.pod
29843
0644
edit
dl
rm
perlsource.pod
7132
0644
edit
dl
rm
perlstyle.pod
8734
0644
edit
dl
rm
perlsub.pod
74405
0644
edit
dl
rm
perlsymbian.pod
15344
0644
edit
dl
rm
perlsyn.pod
45138
0644
edit
dl
rm
perlsynology.pod
7960
0644
edit
dl
rm
perlthrtut.pod
46522
0644
edit
dl
rm
perltie.pod
39314
0644
edit
dl
rm
perltoc.pod
701800
0644
edit
dl
rm
perltodo.pod
372
0644
edit
dl
rm
perltooc.pod
294
0644
edit
dl
rm
perltoot.pod
294
0644
edit
dl
rm
perltrap.pod
10623
0644
edit
dl
rm
perltru64.pod
8492
0644
edit
dl
rm
perltw.pod
4463
0644
edit
dl
rm
perlunicode.pod
91353
0644
edit
dl
rm
perlunicook.pod
25658
0644
edit
dl
rm
perlunifaq.pod
13644
0644
edit
dl
rm
perluniintro.pod
38647
0644
edit
dl
rm
perluniprops.pod
441614
0644
edit
dl
rm
perlunitut.pod
7951
0644
edit
dl
rm
perlutil.pod
7291
0644
edit
dl
rm
perlvar.pod
82577
0644
edit
dl
rm
perlvms.pod
50823
0644
edit
dl
rm
perlvos.pod
3843
0644
edit
dl
rm
perlwin32.pod
40317
0644
edit
dl
rm
Edit:
/usr/share/perl5/pod/perlstyle.pod
(8734B)
=head1 NAME perlstyle - Perl style guide =head1 DESCRIPTION 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. The most important thing is to use L<strict> and L<warnings> in all your code or know the reason why not to. You may turn them off explicitly for particular portions of code via C<no warnings> or C<no strict>, and this can be limited to the specific warnings or strict features you wish to disable. The B<-w> flag and C<$^W> variable should not be used for this purpose since they can affect code you use but did not write, such as modules from core or CPAN. 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: =over 4 =item * 4-column indent. =item * Opening curly on same line as keyword, if possible, otherwise line up. =item * Space before the opening curly of a multi-line BLOCK. =item * One-line BLOCK may be put on one line, including curlies. =item * No space before the semicolon. =item * Semicolon omitted in "short" one-line BLOCK. =item * Space around most operators. =item * Space around a "complex" subscript (inside brackets). =item * Blank lines between chunks that do different things. =item * Uncuddled elses. =item * No space between function name and its opening parenthesis. =item * Space after each comma. =item * Long lines broken after an operator (except C<and> and C<or>). =item * Space after last parenthesis matching on current line. =item * Line up corresponding items vertically. =item * Omit redundant punctuation as long as clarity doesn't suffer. =back 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. Here are some other more substantive style issues to think about: =over 4 =item * Just because you I<CAN> do something a particular way doesn't mean that you I<SHOULD> do it that way. Perl is designed to give you several ways to do anything, so consider picking the most readable one. For instance open(my $fh, '<', $foo) || die "Can't open $foo: $!"; is better than die "Can't open $foo: $!" unless open(my $fh, '<', $foo); because the second way hides the main point of the statement in a modifier. On the other hand print "Starting analysis\n" if $verbose; is better than $verbose && print "Starting analysis\n"; because the main point isn't whether the user typed B<-v> or not. 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. Along the same lines, just because you I<CAN> omit parentheses in many places doesn't mean that you ought to: return print reverse sort num values %array; return print(reverse(sort num (values(%array)))); When in doubt, parenthesize. At the very least it will let some poor schmuck bounce on the % key in B<vi>. 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. =item * Don't go through silly contortions to exit a loop at the top or the bottom, when Perl provides the C<last> operator so you can exit in the middle. Just "outdent" it a little to make it more visible: LINE: for (;;) { statements; last LINE if $foo; next LINE if /^#/; statements; } =item * 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. =item * Avoid using C<grep()> (or C<map()>) 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 C<foreach()> loop or the C<system()> function instead. =item * 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 C<$]> (C<$PERL_VERSION> in C<English>) to see if it will be there. The C<Config> module will also let you interrogate values determined by the B<Configure> program when Perl was installed. =item * Choose mnemonic identifiers. If you can't remember what mnemonic means, you've got a problem. =item * While short identifiers like C<$gotit> are probably ok, use underscores to separate words in longer identifiers. It is generally easier to read C<$var_names_like_this> than C<$VarNamesLikeThis>, especially for non-native speakers of English. It's also a simple rule that works consistently with C<VAR_NAMES_LIKE_THIS>. Package names are sometimes an exception to this rule. Perl informally reserves lowercase module names for "pragma" modules like C<integer> and C<strict>. 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. =item * You may find it helpful to use letter case to indicate the scope or nature of a variable. For example: $ALL_CAPS_HERE constants only (beware clashes with perl vars!) $Some_Caps_Here package-wide global/static $no_caps_here function scope my() or local() variables Function and method names seem to work best as all lowercase. E.g., C<$obj-E<gt>as_string()>. You can use a leading underscore to indicate that a variable or function should not be used outside the package that defined it. =item * If you have a really hairy regular expression, use the C</x> or C</xx> modifiers 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. =item * Use the new C<and> and C<or> operators to avoid having to parenthesize list operators so much, and to reduce the incidence of punctuation operators like C<&&> and C<||>. Call your subroutines as if they were functions or list operators to avoid excessive ampersands and parentheses. =item * Use here documents instead of repeated C<print()> statements. =item * Line up corresponding things vertically, especially if it'd be too long to fit on one line anyway. $IDX = $ST_MTIME; $IDX = $ST_ATIME if $opt_u; $IDX = $ST_CTIME if $opt_c; $IDX = $ST_SIZE if $opt_s; mkdir $tmpdir, 0700 or die "can't mkdir $tmpdir: $!"; chdir($tmpdir) or die "can't chdir $tmpdir: $!"; mkdir 'tmp', 0777 or die "can't mkdir $tmpdir/tmp: $!"; =item * Always check the return codes of system calls. Good error messages should go to C<STDERR>, 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: opendir(my $dh, $dir) or die "can't opendir $dir: $!"; =item * Line up your transliterations when it makes sense: tr [abc] [xyz]; =item * 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 C<use strict> and C<use warnings> in effect. Consider giving away your code. Consider changing your whole world view. Consider... oh, never mind. =item * Try to document your code and use Pod formatting in a consistent way. Here are commonly expected conventions: =over 4 =item * use C<CE<lt>E<gt>> 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 C<function()>. =item * use C<BE<lt>E<gt>> for commands names like B<cat> or B<grep>. =item * use C<FE<lt>E<gt>> or C<CE<lt>E<gt>> for file names. C<FE<lt>E<gt>> 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 C<CE<lt>E<gt>>. =back =item * Be consistent. =item * Be nice. =back
Save
cmd:
run