Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Pod-Simple CPAN distribution.

Report information
The Basics
Id: 55602
Status: resolved
Priority: 0/
Queue: Pod-Simple

People
Owner: Nobody in particular
Requestors: cjm [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 3.09
Fixed in: 3.14



Subject: Bug #12239 was a mistake (nested formatting codes)
In bug #12239, Schwern expected "C<<< C<<foo>> >>>" to render as a literal "C<<foo>>", and you changed Pod-Simple to make that happen. But I disagree with this interpretation of the spec, and consider it a serious loss of functionality. Where exactly in perlpod or perlpodspec does it suggest that characters inside C<> are treated differently than those inside C<< >>? As I read the spec, the only difference is in how the end of the code is located. Once you've located the end of the content (and stripped the mandatory whitespace from the C<< >> version), it's rendered the same. That is, I claim that "C<<< C<<foo>> >>>" is a C<> nested inside a C<>, and Schwern should have written ""C<<< CZ<><<foo>> >>>" or "C<<< CE<lt><foo>> >>>". perlpod clearly states that "C<$a E<lt>=E<gt> $b>" is rendered as "$a <=> $b". You're saying that C<$a E<lt>=E<gt> $b> C<< $a E<lt>=E<gt> $b >> mean two completely different things, and I don't see where the spec supports that. Otherwise, how am I supposed to write: S<< C<< name => value >> >> or S<< C<< <bug-PostScript-Calendar AT rt.cpan.org> >> >>
Thanks, RJBS, for pointing me at this thread: http://www.nntp.perl.org/group/perl.pod-people/2010/03/msg1476.html On the assumption that the updated spec will simply restore the pre-3.09 behavior, I've reverted the change made in 3.09 (but kept the tests and added a couple new ones). The patch is available here: http://github.com/madsen/pod-simple/commit/e02b2ab78c87b6b4b81d92c91b4743bc1242265d