Re: [ID 20000124.002] Unterminated C<...> at perlvar.pod line 188

[Steve Fink <sfink@digital-integrity.com>]

Ilya Zakharevich wrote:
> 
> Ronald J Kimball writes:
> > >     ** Unterminated C<...> at .../pod/perlvar.pod line 188
> > >     ** Unterminated C<...> at .../pod/perlvar.pod line 188
> > >     ** Unterminated C<...> at .../pod/perlvar.pod line 424
> > >
> > > This is due to C<@-> and the like.
> > >
> > > Patch below
> >
> > Why can't the POD parser be fixed, rather than hacking the POD?  POD is
> > supposed to be readable; C<@-Z<>> and C<$#-Z<>> are not readable.
> 
> This is another indication that the idea of allowing -> and => inside
> a group is a broken idea.

Could pod learn a little from perl? Make C<...> work like m<...> by
accepting any delimiters? C[@-] and C[->] don't look so bad. And it's
gotta be easier than handling C<->> properly.

Hm. On second thought:

% fgrep 'C|' *.pod | less 
perlfaq5.pod:    sysopen(FH, $path, O_WRONLY|O_TRUNC|O_CREAT)        ||
die $!;
perlfaq5.pod:    sysopen(FH, $path, O_WRONLY|O_TRUNC|O_CREAT, 0666)  ||
die $!;

Ok, how about just C(...) in addition? Or something. Or use Q<C[...]>,
where [] are arbitrary (Quoted C<>).

Um. Q<C[->]>. Looks like I may have won the battle and lost the war.
Hey, it still looks better than C<$#-Z<>>!

---

References to:

Ilya Zakharevich <ilya@math.ohio-state.edu>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---