On Sun, Jan 29, 2012 at 9:31 AM, Ricardo Signes <[email protected]>wrote:
> * Patrice Dumas <[email protected]> [2012-01-27T18:15:17] > > 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 > > podchecker is in the process of being replaced with Pod::Simple-based code. > Hopefully that will help. > > Maybe Marc Green can comment... > > If I am understanding the situation correctly, the problem is that Pod::Checker does not issue an "unresolved internal link" warning when the target of an L<> formatting code does not exist in the document *if* the target is the prefix of another node in the document (i.e., is a prefix of a =head or =item directive). This functionality still exists in the Pod::Simple-based code, so the issue won't be taken care of when Pod::Checker is replaced. Thus, we need to decide whether or not the "L<> target shortcut" behavior should stay (and perhaps be documented better) or go. I think Marek suggested that X<> can serve as a way to create an anchor that can be linked to as a fix for the problem, because if that functionality is implemented, then the "L<> target shortcut" behavior can be removed. As Shawn said, there aren't many (if any) POD parsers that create indexes, so X<> is not being used as much as the designer of the formatting code thought it would be. (Note that I may be mistaken here. I am talking from limited personal experience, so let me know if this is not the case.) Thus, letting L<> targets link to X<>s sounds appealing to me.
