>[and a discussion of "=for foo bar" ensued] > >Anything to do with Pod, perldoc, or the pod formatters belongs on the >pod-people list, not p5p. > Oops :-]
>But anyway, you happen to have caught me at a great time for >this. I'm :-) >about to cook up the perldoc <-> Pod::Simple interface, and I >think I could >try adding stuff to accodomate something so that you could say >"I want to >format the '=for foo ...' sections too", without requiring that the >formatter even know that such sections weren't just normal paragraphs. > That sounds interesing. I mean, I like Slaven's solution, but it requires everybody (who wants it), to do something particular - although it'll work for me in the meantime :-) >MUST be an =item (if there's going to be any =item's in that over >block). So this is bad: > >=over > >=begin private > >=item > >=end private > Ouch, I can see that being wanted, this would, I suspect, be typical: =head =over =item public =item private =item private =item public =back =cut Is it possible to (horrors), stick a new tag in, like 'internal'? =internal ... Everything treats it as an item, in the current context. I'm sure that's more complicated to implement. >A more pragmatic consideration is that you have to tell people, pretty >visibly, something like "If you want to see the private >methods, format >this with C<perldoc -whatever=private>", etc. > Correct, that's why I suggested -_ or something or --internal, would also be practical, for example. I don't think the usual user will want to use this, but only people who are digging around a bit, or even the original author. Richard Foley Ciao - shorter than Aufwiedersehen -- ps. sorry about the sig. (below) - can't get rid of it, for the moment :-\ Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
