Skip Menu |

This queue is for tickets about the PodParser CPAN distribution.

Report information
The Basics
Id: 4640
Status: resolved
Priority: 0/
Queue: PodParser
People
Owner: Nobody in particular
Requestors:
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Dec 11 11:56:06 2003 kane [...] cpan.org - Ticket created
Subject: bad warnings from podchecker
=head1 flub =head2 blah =over 4 =item foo bar =item zot bar =back =cut #### =head2 flubber =over 4 =item foo bar =item zot bar =back =cut 1; ############################## gives these warnings: [kane@nsa-dev /tmp]$ podchecker x.pod *** WARNING: multiple occurrence of link target 'foo' at line - in file x.pod *** WARNING: multiple occurrence of link target 'zot' at line - in file x.pod note how it also doesn't show the line number...
  Fri Jan 09 23:34:30 2004 andy [...] petdance.com - Queue changed from Test-Pod to PodParser
  Fri Jan 09 23:34:31 2004 andy [...] petdance.com - Correspondence added
This is from the PodParser distro, not Test-Pod. I'm sending it to the appropriate queue.
  Tue May 31 15:53:07 2005 Marek.Rouchal [...] gmx.net - Status changed from 'new' to 'resolved'
  Tue May 31 15:53:07 2005 Marek.Rouchal [...] gmx.net - Correspondence added
This warning was downgraded to a "verbose warning" (podchecker -warn -warn). Reason for the warning: if you have two identical =head2 foo =head2 foo or =item bar =item bar in your POD, and someone has a L<.../"foo"> or L<.../bar> to your POD, then - strictly speaking - POD does not allow to distinguish which of the two to take, since there is no criteria to distinguish them. And because the Pod::Checker is lazy, it just count the number of destination, not their line, therefore there is no line printed. -Marek