On Tue, Jan 25, 2000 at 12:11:33PM -0500, Ronald J Kimball wrote: > The code may become less complicated, but the parsing rules may become > more complicated No more so than they are already. > The POD author would have to remember when -> and => end the block > and when they don't, No they wouldn't. They'd simply expect it to work intuitively and that things that saw '=>' or '->' in context that didn't look like a Perl expression would simple "do the write thing" much as pod2man has tried to do all this time. Whenever it didn't, they'd submit a bug report. > How would you allow both C<@-> and C<$@->[0]> while decreasing the > number of special cases? Because the result would probably still be no more special cases than are currently required to do it the current way (there are about two dozen at present). > I think I'm starting the favor the original proposal of C<@-Z<>>. :D I prefer the even earlier original proposal of not having C<...> do any special handling for '->' and '=>' :-). Either that, or make it possible for Pod::Parser to reuse the perl-parser since it would basically have to know most of perl to get it completely right ;-) -- Brad Appleton <[EMAIL PROTECTED]> http://www.enteract.com/~bradapp/ "And miles to go before I sleep." -- Robert Frost
