Re: allowing L<text|href>
[email protected] (David E . Wheeler)
| Newsgroups | perl.pod-people |
|---|---|
| Message-ID | <[email protected]> |
Anyone else got any opinions on this? I'd love to see a new version of Test::Pod with this update… Thanks, David On Dec 11, 2009, at 3:23 PM, David E. Wheeler wrote: > While I was at it, and now that the change is in blead and released in Pod::Simple 3.11 (which includes perlpod.pod and perlpodspec.pod, FBOFW), I've taken the time to send a pull request for Test::Pod to allow this new syntax. > > http://github.com/theory/test-pod/commit/ae6a44894eda4fd09fb412d837efe543628cd7d6 > > I've sent a pull request to Andy and sent the patch to [RT](http://rt.cpan.org/Ticket/Display.html?id=52688). > > My motivation here is to match the current spec, at least as implemented by Pod::Simple, which Test::Pod uses to do the actual parsing and validation. I also want to start using this syntax, since search.cpan.org uses Pod::Simple and will therefore get the sane links ASAP. The only stopping point from my POV is that my Pod tests will fail, and since this is now legal, I'd rather they didn't. > > It turns out that the Test::Pod's ability to detect L<text|scheme:...> links was added only this past July. Before that, it had completely relied on Pod::Simple, which has supported such links for a long time. So it's not that long that Test::Pod has forbidden them. Furthermore, this isn't taking any syntax away from users, so those who don't want to use L<text|scheme:...> links don't have to. It's possible to add some sort of flag to let Test::Pod so that such users can enforce the rule, but doing so seems like a slippery slope that would eventually end up requiring that Test::Pod track different versions of the pod spec (and it's not versioned!). > > Anyway, my $0.02. > > Best, > > David >