On Sun, May 24, 2009 at 2:31 AM, Ricardo SIGNES <[email protected]>wrote:
> > perlpodspec gives "two syntaxes" for formatting codes. There's X<content> > and > X<< content >>. In the "two or more angle brackets" form, the whitespace > immediately following << and preceding >> are not renderable. That's fine, > but > I'm confused as to why that isn't just the universal case. Is it just a > backcompat issue that someone might have been relying on B< foo > having > spaces > at either end? Hi, In areas of uncertainty you can probably take Pod::Simple as the reference implementation of perlpodspec since since Sean Burke wrote them both concurrently/consecutively. In this particular case the intention was to preserve whitespace within single bracket formatting codes since there are several tests in Pod::Simple that address that exact case, for example: http://cpansearch.perl.org/src/ARANDAL/Pod-Simple-3.07/t/fcodes.t > I realize these are edge cases. I'm only asking because I'm interested in > opinions, not because I think it will come up frequently. > There are only edge cases when you writing a parser. :-) John. --
