Re: =head1 inside =over

2003-09-07 Thread Sean M. Burke
At 11:40 AM 2003-09-07 +0100, Mark Thornber wrote: At 00:31 06/09/03, Mike Guy wrote: But the pickier checkers should point out the error of the author's ways. Any chance that the error message could display _line_ number (as well as Using the new Pod::Simple now entering CPAN: use Pod::Simple::Du

Re: =head1 inside =over

2003-09-07 Thread Mark Thornber
At 00:31 06/09/03, Mike Guy wrote: But the pickier checkers should point out the error of the author's ways. Any chance that the error message could display _line_ number (as well as paragraph number) ? -- MarkT = E M Thornber CEng MIEE Enchanted Systems Limited Software T

Re: =head1 inside =over

2003-09-06 Thread Sean M. Burke
At 03:34 PM 2003-09-06 +0100, Graham Barr wrote: I have not announced anywhere yet but http://search.cpan.org/pod2html allows people to check how thier PODs render. But I guess I just have. Yay! This is the best! (I keep meaning to nag someone at ORA to set up something similar for their Doc

Re: =head1 inside =over

2003-09-06 Thread Graham Barr
On Sat, 2003-09-06 at 03:21, Iain Truskett wrote: > That said, I spent some time a couple of days ago inserting missing > "=back"s into about 10 of the DateTime modules (so they're render nicely > in my personal Pod::Simple based viewer and also in search.cpan.org). > And I've asked the author in

=head1 inside =over

2003-09-06 Thread Mike Guy
"Sean M. Burke" <[EMAIL PROTECTED]> wrote > Now, I'm thinking of saying that =headN's can't be inside =over's, so that > if such is found, it will DWIMically close the open =over. > But going the other way, I'm thinking "no way, there's nothing wrong with > having a =headN inside an =over! Don't

Re: =head1 inside =over

2003-09-06 Thread Sean M. Burke
At 01:00 PM 2003-09-05 -0700, Russ Allbery wrote: This has in my experience always been an error. I'd automatically close and additional issue a warning when run through a checker/lint tool. Okay, I've now implemented this. It'll be in the next Pod-Simple release. -- Sean M. Burkehttp://sear

Re: =head1 inside =over

2003-09-05 Thread Iain Truskett
* Sean 'TorgoX' Burke ([EMAIL PROTECTED]) [06 Sep 2003 05:35]: [...] > Anyone have any preferences either way? I think I might be leaning > toward the former approach (where =headN closes =over) just because I > think most cases of people apparently having a =head1 inside an =over > are actually

RE: =head1 inside =over

2003-09-05 Thread Hugh S. Myers
Err on the side of DWIM-ness. --hsm > -Original Message- > From: Sean M. Burke [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2003 4:25 AM > To: [EMAIL PROTECTED] > Subject: =head1 inside =over > > > So I was running Pod::Simple on some test docume

Re: =head1 inside =over

2003-09-05 Thread Russ Allbery
Sean M Burke <[EMAIL PROTECTED]> writes: > Now, I'm thinking of saying that =headN's can't be inside =over's, so > that if such is found, it will DWIMically close the open =over. But > going the other way, I'm thinking "no way, there's nothing wrong with > having a =headN inside an =over! Don't

=head1 inside =over

2003-09-05 Thread Sean M. Burke
So I was running Pod::Simple on some test documents and noted a document where the author forgot to close an =over, and so it contains the whole rest of the document, including several =head1's. Here's a test case: =head2 BLOOP Hoopbehwo! =over =item Stuff. Um. Brop. =head1 SVUP Myup. =