From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: help-gnu-emacs@gnu.org
Subject: Re: (cperl-mode) Problems with syntax highlighting after __DATA__ !
Date: Sun, 24 Oct 2010 05:59:07 +0000 (UTC) [thread overview]
Message-ID: <slrnic7ipb.5t9.nospam-abuse@powdermilk.math.berkeley.edu> (raw)
In-Reply-To: 87aam6nrst.fsf@lifelogs.com
On 2010-10-22, Ted Zlatanov <tzz@lifelogs.com> wrote:
> L> or a POD-section , i.e. natural solution would be comment-face.
> L> (like most other editors I tested do, just check vim)
>
> L> __END__ is practically the same as __DATA__ and Ilya is right those
> L> sections are terminated only by EOF.
>
> Theoretically they are practically the same, but in practice they are not.
[Ignoring that, formally, this is content-free,] I believe you are mistaken.
> __END__ ends the Perl program and any __DATA__ effects.
No.
> Right. Perl won't parse after __DATA__ or __END__ no matter what.
Nevertheless, most of the time, it will.
> IZ> (The code to parse <DATA> may have some special logic to find your
> IZ> __X__; but it may look for whatever it wants as well...)
>
> There are at least a few CPAN modules that care, e.g. Inline::Files and
> company. So I think it's nice to highlight every __X__ marker instead
> of special-casing __DATA__ (__END__ has to be special because it means
> POD will start, usually).
I'm very wary about handling "quirks of Perl modules" - having handled
quirks of Perl itself. ;-)
Yours,
Ilya
next prev parent reply other threads:[~2010-10-24 5:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 12:22 (cperl-mode) Problems with syntax highlighting after __DATA__ ! LanX
2010-10-15 6:57 ` Ilya Zakharevich
2010-10-15 10:40 ` LanX
2010-10-15 13:14 ` LanX
2010-10-15 13:35 ` LanX
2010-10-15 13:35 ` LanX
2010-10-15 22:40 ` Ilya Zakharevich
2010-10-16 14:20 ` LanX
2010-10-17 2:56 ` Stefan Monnier
2010-10-19 15:38 ` Ted Zlatanov
2010-10-20 19:40 ` Ilya Zakharevich
2010-10-20 19:42 ` Ilya Zakharevich
2010-10-21 11:43 ` LanX
2010-10-22 15:57 ` Ted Zlatanov
2010-10-24 5:59 ` Ilya Zakharevich [this message]
2010-10-17 11:03 ` Ilya Zakharevich
2010-10-15 14:25 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnic7ipb.5t9.nospam-abuse@powdermilk.math.berkeley.edu \
--to=nospam-abuse@ilyaz.org \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.