diff options
author | Gurusamy Sarathy <gsar@cpan.org> | 1999-03-26 01:30:25 +0000 |
---|---|---|
committer | Gurusamy Sarathy <gsar@cpan.org> | 1999-03-26 01:30:25 +0000 |
commit | d98d5fffa337682ca6cac752b32ff55e863a53a0 (patch) | |
tree | 5646cc0346e5300e94342be857a116e70c22528d /pod/perlstyle.pod | |
parent | a7ae9550f26a080556f67048e2697d3c5a20f9f4 (diff) | |
download | perl-d98d5fffa337682ca6cac752b32ff55e863a53a0.tar.gz |
specify type of bracket in "Unmatched bracket" diagnostic;
prefer 'brace' or 'curly bracket' over 'curly brace'
p4raw-id: //depot/perl@3170
Diffstat (limited to 'pod/perlstyle.pod')
-rw-r--r-- | pod/perlstyle.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlstyle.pod b/pod/perlstyle.pod index cf280ce1da..04aab9854a 100644 --- a/pod/perlstyle.pod +++ b/pod/perlstyle.pod @@ -16,7 +16,7 @@ The C<use sigtrap> and even C<use diagnostics> pragmas may also prove useful. Regarding aesthetics of code lay out, about the only thing Larry -cares strongly about is that the closing curly brace of +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: |