Re: Pod::Simple issues

[Russ Allbery]

Karl Williamson  writes:

> Rather than aborting parsing at the point where this occurs, I think it
> should continue on, but generate an errors section, like it does for most
> other errors.

This will cause a hard failure in pod2man and pod2text by default, since
they do not generate ERRORS sections by default (you have to request that
behavior with a flag).  They used to generate ERRORS sections, which made
people very unhappy because they didn't want their documents published
with sections saying the documents were bad, and after a lot of previous
discussion I changed the default to fail on generation.  (I'd really
rather not reverse that decision at this point.)

-- 
#!/usr/bin/perl -- Russ Allbery, Just Another Perl Hacker
$^=q;@!>~|{>krw>yn{u<$$<[~|| 0gFzD gD,
 00Fz, 0,,( 0hF 0g)F/=, 0> "L$/GEIFewe{,$/ 0C$~> "@=,m,|,(e 0.), 01,pnn,y{
rw} >;,$0=q,$,,($_=$^)=~y,$/ C-~><@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print

Re: Pod::Simple issues

[Karl Williamson]

On 04/29/2016 01:58 PM, Shawn H Corey wrote:

On Fri, 29 Apr 2016 13:34:21 -0600
Karl Williamson  wrote:


Nested L<> are illegal.  Pretending inner one is X<> so can
continue looking for other errors.


That would be Z<>




That would generate an additional warning that it wasn't empty.  The 
mechanism is to divert the incoming text into the X<> so it doesn't do 
anything bad.  I suppose we could set a flag for the Z<> to suppress the 
warning.