On 02/20/2012 06:58 PM, Florent Angly wrote:
Hi Sean,
You are right that Pod::Simple has problems with multiline POD strings
contained into a variable or heredoc section:
https://rt.cpan.org/Ticket/Display.html?id=36404
https://rt.cpan.org/Ticket/Display.html?id=69390
Oh now I remember... yes,
"Sean M. Burke" writes:
> 3) Point 3 is a problem in theory, and possibly in practice, but for which
> the *solution* is "SO DON'T DO SCREW IT UP!".
> I had this in mind: supporting linktext could mean:
> "You can just Lmailto:sbu...@cpan.org> Now!"
> which, outside of hypertext, *could* be ren
On 02/20/2012 06:58 PM, Florent Angly wrote:
In that second link, David Wheeler wrote that the simplest workaround
is to escape POD directives in the string, as in:
> my $var =<
> \=head1 FAKE_POD_ENTRY_HERE
>
Now, you'd THINK that that would have occurred to me!
I kinda passed off perlpodspec to... whoever...
I'm pretty sure I did, to somebody
But I'll chip in about L in perlpodspec.
Long story short, about Lhttp://stuff.com/hditfn> and modding
perlpodspec to say it's okay: DOIT!
There *were* three things that I thought were stumbling blocks with
On 02/09/2012 04:34 AM, David Cantrell wrote:
I doubt you'll ever see a distribution which has POD in both Foo/Bar.pm
and Foo/Bar.pod, because the perldoc tool will only see one or the other
when a user types 'perldoc Foo::Bar'.
+1 !
...by which I mean that I took this as a given: when Perl it
On 02/19/2012 02:19 PM, Marc Green wrote:
Hello Pod People,
When given the following input, Pod::Simple does not warn that the
[text] portion of the 2nd and 3rd =item is invalid.
In passing, I'll note that the =over ... =item ... =back code was some
of the hardest notions/code in perlpodspec/
As I look in Pod::Simple's ./t/ dir...
Gawd those tests I made with \n\n's in them, with like ten lines
squooshed into one blob with \n\n\n etc, like this:
print "#\n# Tests for simple =item *'s\n";
ok( $x->_out("\n=over\n\n=item *\n\nStuff\n\n=item *\n\nBar
I!\n\n=back\n\n"),
'indent="4">
As I stumble past this list, which I don't follow much anymore, I'll
give a few responses to, but not definitive answers to, some issues
that are either because of things in perlpodspec, or because of things
not in Perlpodspec.
Here goes...
