* Christopher H. Laco <[EMAIL PROTECTED]> [2007-07-29 17:05]: > A failing pod test is the first sign pod2* generation is > broken. It's rare, but I've been in the situation where for > some reason (mistmatching dist requirements, failed upgrades, > bad dist packages, broken troff, etc) the creation of man > pages/html from the dist pod fails outright. Pod tests assure > the user that they will be able to perldoc/man the thing they > are installing. That's doubly true if you're using pod2usage to > expose help in scripts.
Is that actually true? Test::Pod uses Pod::Simple, but that’s far from the only game in POD town. Even the perldoc utility included with versions of perl that ship with Pod::Simple uses its own formatter by default. And Pod::Simple has not always shipped with perl. So if Pod::Test says you’re fine, that doesn’t necessarily mean things will work for the user (though if it says you’re broken then things are likely to break for the user as well, since Pod::Simple is very solid). Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
