Dear all, I tend to agree that dahes '-' should be allowed in POD links, e.g. L<Inline::C-Cookbook>, which refers to .../Inline/C-Cookbook.pod
I extended the character class in Pod::ParseUtils for the "page" regexp, which makes the example below work nicely, and the conversion of all Pod in the Inline package gives nice hyperlinked results e.g. with Marek::Pod::HTML. On the other hand I am a little bit afraid that some "lax" Pod documents may then cease to work, consider this: =head2 Cross-Compiling .... See L<Cross-Compiling> above. __EOF__ ....which should of course read L<"Cross-Compiling">! What do you think is less evil? Cheers, Marek PS. Mark, you had a similar problem, IIRC? > -----Original Message----- > From: Slaven Rezic [mailto:slaven.rezic@;berlin.de] > Sent: Sunday, October 27, 2002 9:42 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Pod::ParseUtils > > > Try this with Pod::ParseUtils which comes with perl 5.8.0: > > perl -MPod::ParseUtils -e 'warn > Pod::Hyperlink->new("Inline::C-Cookbook")->page' > > returns nothing, but expected was "Inline::C-Cookbook". The problem is > obvious: Pod::ParseUtils only recognizes valid perl module names > (without a dash), but "Inline::C-Cookbook" is just a pure > documentation pod. How to solve this problem: rename > Inline::C-Cookbook? Allow Pod::Hyperlink to recognize also links which > are non-valid perl module names?
