From: Ted Zlatanov <tzz@lifelogs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: (cperl-mode) Problems with syntax highlighting after __DATA__ !
Date: Fri, 22 Oct 2010 10:57:54 -0500 [thread overview]
Message-ID: <87aam6nrst.fsf@lifelogs.com> (raw)
In-Reply-To: 496a9e4f-414a-44c2-8f3e-a83071743a5c@a36g2000yqc.googlegroups.com
On Thu, 21 Oct 2010 04:43:43 -0700 (PDT) LanX <rolf.langsdorf@googlemail.com> wrote:
>> I think it's not that bad. __DATA__ is the same content (semantically)
>> as a here-file,
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.
__DATA__ begins a section that can be used through the DATA filehandle.
It's a true here-file without interpolation and has no syntax.
__END__ ends the Perl program and any __DATA__ effects. Usually POD
will follow but the Perl parser doesn't care (unlike =cut markers, which
do matter to the Perl parser). The POD extractor, usually `perldoc',
will care. So it's nice to the user to highlight it as POD.
On Wed, 20 Oct 2010 19:40:30 +0000 (UTC) Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
IZ> On 2010-10-19, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> I think it's not that bad. __DATA__ is the same content (semantically)
>> as a here-file, which perl-mode and cperl-mode can handle.
IZ> Are you sure? I think if one would put the same breaks-CPerl content
IZ> inside a here-doc, CPerl would slow down as well. AFAIK, here-docs
IZ> are still facified; the result is just ignored.
Well, you could try it... I will not presume to know the cperl-mode
internals, I was just talking about parsing the sections when I said
"it's not that bad."
IZ> Hmm, on the other hand, if it is syntaxification which is slowed down,
IZ> then yes - it should not be a lot of problem to skip stuff after
IZ> __DATA__, since CPerl does syntaxification in one pass.
Right. Perl won't parse after __DATA__ or __END__ no matter what.
>> It always ends with EOF or with another __X__ marker on a new line.
IZ> Eh??? AFAIK, it ends with EOF period.
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).
Ted
next prev parent reply other threads:[~2010-10-22 15:57 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 [this message]
2010-10-24 5:59 ` Ilya Zakharevich
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=87aam6nrst.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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.