podchecker _does_ detect wrong internal links. If you put any of the following links in the POD you quoted below, podchecker (as of Pod-Parser-1.38 and higher) will flag it as an error:
L</"open FILEHANDLE,MODE,EXPRESSION"> L<"open FILEHANDLE,MODE,EXPRESSION"> L</open FILEHANDLE,MODE,EXPRESSION> It is true that L</open> will work OK, because perlfunc (at least at the time when I wrote podchecker) contained many L</function> although the actual item was =item function ARGUMENTS and I did not want to flag dozens of errors for those. In other words: if the =item text matches /(\S+)\s+\S/ Then $1 is also regarded as a valid reference for L<...> If you think that there should be something changed in podchecker, then please provide a complete POD example, the podchecker output and a statement on what should be changed and why. -Marek -----Ursprüngliche Nachricht----- Von: Patrice Dumas [mailto:[email protected]] Gesendet: Samstag, 28. Januar 2012 00:15 An: [email protected] Betreff: pod checker that finds missing internal links? Hello, I have searched for a pod checker that finds missing internal links, but I haven't found one. More precisely, podchecker coming with perl 5.10 gets it wrong, it finds multiple defined labels because it takes only into account the beginning of an =item, for example =item open FILEHANDLE,EXPR =item open FILEHANDLE,MODE,EXPR is the same for this podchecker (and I guess it is 'open'). The pod simple checker do not check for multiple labels. podlint do not find these either. Maybe podlinkcheck does it, but it also do much more. Did I miss something? Maybe this would be an interesting addition to Pod::Simple? The perl-5.14.2 documentation, maybe because there is no warning emitted by any of the pod formatters used to process it, has missing labels, in perlfunc.pod, perlapi.pod and perltoc.pod. -- Pat
