summaryrefslogtreecommitdiff
path: root/pod/perlpodspec.pod
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2010-04-17 14:34:28 -0400
committerRicardo Signes <rjbs@cpan.org>2010-04-19 12:26:33 -0400
commita3d78747dc6076a86b29e59f911247652002f29b (patch)
tree800177d5aaf6579c854c5aee426551514a307dfe /pod/perlpodspec.pod
parente05a0d7494b04196ac0b6dbeb026a51df2a2a73d (diff)
downloadperl-a3d78747dc6076a86b29e59f911247652002f29b.tar.gz
clarification of multi-bracket format
Diffstat (limited to 'pod/perlpodspec.pod')
-rw-r--r--pod/perlpodspec.pod12
1 files changed, 12 insertions, 0 deletions
diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index b7c3122f02..0bf84e0910 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -429,6 +429,18 @@ themselves. That is, these are all synonymous:
and so on.
+Finally, the multiple-angle-bracket form does I<not> alter the interpretation
+of nested formatting codes, meaning that the following four example lines are
+identical in meaning:
+
+ B<example: C<$a E<lt>=E<gt> $b>>
+
+ B<example: C<< $a <=> $b >>>
+
+ B<example: C<< $a E<lt>=E<gt> $b >>>
+
+ B<<< example: C<< $a E<lt>=E<gt> $b >> >>>
+
=back
In parsing Pod, a notably tricky part is the correct parsing of