Re: Is this a bug in cperl mode

[Ilya Zakharevich <nospam-abuse@ilyaz.org>]

[A complimentary Cc of this posting was sent to
Daniel Pfeiffer 
<occitan@esperanto.org>], who wrote in article <20030217090455.2ec904d2.occitan@esperanto.org>:
> Ilya Zakharevich <nospam-abuse@ilyaz.org> skribis:
> > [A complimentary Cc of this posting was sent to
> > Daniel Pfeiffer 
> > <occitan@esperanto.org>], who wrote in article <20030211222108.11234512.occitan@esperanto.org>:
> > > Here is a little snippet of (wrong!) Perl code, which shows what is needed
> > > to catch each of the font-lock errors:
> > 
> > > \$"asd"
> > > \$'asd'
> > > \$`asd`
> > 
> > $a = \$"->asd(\$");		# syntaxically correct
> 
> What are you trying to show? 

I remove your "(wrong!)", showing how the things may appear in
real-world Perl code.

> > > $opt_s!asd!bsd!
> > 
> > This is OK with cperl-under-as-char TRUE.

> Which is otherwise undesirable, as it breaks conventions Emacs users expect.

Emacs being such a mess, there is nothing "Emacs users expect".  Perl
users expect that _ is a word char.

> >   @a = (s => ...); $b = $bsd =exe;
> > 
> > > The fourth case is the one originally posted here.  Both Ilya's and Emacs'
> > > modes fall into precisely the same traps.
> > 
> > Nope, the 4th one is OK with my version.
> 
> Not with SuSE 8.1's emacs -q --no-site-file (version 21.2) and M-x load-file
> your cperl version.  I get the three "=" in light blue

4th case (IIRC originally posted here) was with $opt_s.

Ilya