From: Daniel Pfeiffer <occitan@esperanto.org>
Subject: Re: Is this a bug in cperl mode
Date: Mon, 17 Feb 2003 09:04:55 +0100 [thread overview]
Message-ID: <20030217090455.2ec904d2.occitan@esperanto.org> (raw)
In-Reply-To: b2mukm$23ne$1@agate.berkeley.edu
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? Of course if by hasard the matching end
of construct is near, that corrects the situation. But usually they
won't be near, unless it's a script written with your mode, where the
friendly programmer set things up that way. (E.g. end of line comment
with whatever CPerl mode is expecting)
> > $opt_s!asd!bsd!
>
> This is OK with cperl-under-as-char TRUE.
Which is otherwise undesirable, as it breaks conventions Emacs users expect.
But your other post yesterday suggests you have a solution-idea for that.
> > $opt::s!asd!bsd!
>
> $opt::s = $foo = $bar =exe; # Warnings, but no error
As above.
> > $opt{s}asd}bsd}
>
> $opt{s} = ({asd => 1}, {bsd => 1});
As above again.
> > (s => ...)=bsd=
>
> @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, "> ...); $b" in
light brown, "$bsd" in black and "exe" in green. So again same as my first
remark.
> In my experience, the others
> appear much much rarer.
$opt{s} would be fairly common, and for giving it a default value @opt = (s => ...)
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
-- GPL 3: take the wind out of Palladium's sails! --
------
-- My other stuff here too, sawfish, make.pl...: --
------
-- http://dapfy.bei.t-online.de/ --
next prev parent reply other threads:[~2003-02-17 8:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 3:20 Is this a bug in cperl mode Harry Putnam
2003-02-10 9:29 ` Kai Großjohann
2003-02-10 10:14 ` Daniel Pfeiffer
2003-02-11 1:23 ` Unknown
2003-02-11 2:04 ` Unknown
2003-02-10 15:50 ` Harry Putnam
2003-02-10 16:11 ` Harry Putnam
2003-02-10 21:07 ` Daniel Pfeiffer
2003-02-16 1:30 ` Ilya Zakharevich
2003-02-16 1:28 ` Ilya Zakharevich
2003-02-10 21:26 ` Daniel Pfeiffer
2003-02-11 21:21 ` Daniel Pfeiffer
2003-02-16 2:56 ` Ilya Zakharevich
2003-02-17 8:04 ` Daniel Pfeiffer [this message]
2003-02-17 19:33 ` Ilya Zakharevich
2003-02-17 7:56 ` CPerl mode v5.0 Ilya Zakharevich
2003-02-17 19:50 ` Ilya Zakharevich
2003-02-20 0:00 ` Daniel Pfeiffer
2003-02-20 20:26 ` Ilya Zakharevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030217090455.2ec904d2.occitan@esperanto.org \
--to=occitan@esperanto.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).