On Wed, Jan 26, 2000 at 05:01:17PM -0800, Larry Wall wrote:
> But strippable spaces might generalize better if you pick some other
> character that is unlikely to follow <. We could have
>
> C<: $ref->[0] :>
> C<: <=> :>
> B<: -w :>
> I<: not :>
>
> etc. There are no occurrences of /\b[a-z]<: / in the standard docs
> as far as I can tell.
So is this saying that any whitespace after /[A-Z]<:/ and before the
corresponding /:>/ are not only stripped (by the parser) but are
required? Or is the whitespace optional here? Is C<: <=> :> the
same as C<:<=>:>?
> And now we come full circle back to C<< $ref->[0] >> because there are
> no occurrences of /\b[A-Z]<< / in the docs either. So we just make
> a rule that if you double the angle brackets, you have to add whitespace
> around it too.
>
> C<< $ref->[0] >>
> C<< <=> >>
> B<< -w >>
> I<< not >>
This is in addition to the above? (and here the whitespace is
definitely required.)
> This is POD. This is your brain on POD. Any questions?
I definitely like both of these *LOTS* better then the existing
setup that special cases '->' and '=>' inside C<...>. So instead
of looking for /\b[A-Z]</ to start a sequence I instead look for:
/\b[A-Z]<([<:]\s+)?/
I think I can do that. And it looks SO MUCH NICER than the other
stuff thats been both implemented and tossed about. Why - it almost
looks as plain as POD is supposed to look ;-)
If someone makes the appropriate changes to perlpod.pod, I will
do my best to modify Pod::Parser to accommodate the new spec
just as soon as possible.
--
Brad Appleton <[EMAIL PROTECTED]> http://www.enteract.com/~bradapp/
"And miles to go before I sleep." -- Robert Frost
