Re: Why does Pod::Checker deprecate section numbers in links to man pages?

2010-06-01 Thread Nicholas Clark
On Fri, May 28, 2010 at 10:33:13PM -0600, karl williamson wrote:
 And in fact, recommends not using L to anything other than another pod.
 
 This seems like a useful feature, which is supported at least in html.
 
 I've searched the archives but not found anything.

git blame on the lines in question in blead from
cpan/Pod-Parser/lib/Pod/Checker.pm
points to commit 92e3d63aacb66085fea74c3f951f09e136337b97

Update to Pod::Parser 1.17, from Brad Appleton.


Some grovelling in CPAN reveals that the code was added in release 1.091 of
Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.09to=PodParser-1.091w=1

commented out in release 1.093 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.092to=PodParser-1.093w=1

uncommented in release 1.14 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.13to=PodParser-1.14w=1

and documented in release 1.15 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.14to=PodParser-1.15w=1


No idea whether Brad Appleton, Marek Rouchal, or someone else initiated
these changes

On Sat, May 29, 2010 at 01:01:35PM -0700, Russ Allbery wrote:
 karl williamson pub...@khwilliamson.com writes:
 
  And in fact, recommends not using L to anything other than another pod.
 
  This seems like a useful feature, which is supported at least in html.
 
 Yes, I disagree with this as well and have POD conversion software that
 relies on being able to use L for man pages, URLs, and several other
 things that aren't POD.
 
 If you have tools available to create real links for man pages, you want
 to allow specifying man pages in L, since otherwise you have to make
 guesses at whether something(1) is a man page reference or something else.
 So this is a bad thing to deprecate.

Agree. As I loathe heuristics, because they mean that you can't predict
how your document will be parsed, and effectively mean that you can't
write some totally legitimate code examples without it mistakenly being
treated as a link.

Nicholas Clark


Re: Why does Pod::Checker deprecate section numbers in links to man pages?

2010-06-01 Thread karl williamson

Nicholas Clark wrote:

On Fri, May 28, 2010 at 10:33:13PM -0600, karl williamson wrote:

And in fact, recommends not using L to anything other than another pod.

This seems like a useful feature, which is supported at least in html.

I've searched the archives but not found anything.


git blame on the lines in question in blead from
cpan/Pod-Parser/lib/Pod/Checker.pm
points to commit 92e3d63aacb66085fea74c3f951f09e136337b97

Update to Pod::Parser 1.17, from Brad Appleton.


Some grovelling in CPAN reveals that the code was added in release 1.091 of
Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.09to=PodParser-1.091w=1

commented out in release 1.093 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.092to=PodParser-1.093w=1

uncommented in release 1.14 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.13to=PodParser-1.14w=1

and documented in release 1.15 of Pod-Parser:

http://search.cpan.org/diff?from=PodParser-1.14to=PodParser-1.15w=1


No idea whether Brad Appleton, Marek Rouchal, or someone else initiated
these changes

On Sat, May 29, 2010 at 01:01:35PM -0700, Russ Allbery wrote:

karl williamson pub...@khwilliamson.com writes:


And in fact, recommends not using L to anything other than another pod.
This seems like a useful feature, which is supported at least in html.

Yes, I disagree with this as well and have POD conversion software that
relies on being able to use L for man pages, URLs, and several other
things that aren't POD.

If you have tools available to create real links for man pages, you want
to allow specifying man pages in L, since otherwise you have to make
guesses at whether something(1) is a man page reference or something else.
So this is a bad thing to deprecate.


Agree. As I loathe heuristics, because they mean that you can't predict
how your document will be parsed, and effectively mean that you can't
write some totally legitimate code examples without it mistakenly being
treated as a link.

Nicholas Clark



FWIW, I submitted a bug report for this module on an unrelated issue a 
month ago, and about the same time sent an email directly to Marek about 
a p5p discussion, and have gotten no responses.