all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: help-gnu-emacs@gnu.org
Subject: Re: (cperl-mode) Problems with syntax highlighting after __DATA__ !
Date: Wed, 20 Oct 2010 19:40:30 +0000 (UTC)	[thread overview]
Message-ID: <slrnibuhde.f5f.nospam-abuse@powdermilk.math.berkeley.edu> (raw)
In-Reply-To: 87wrpeqjkb.fsf@lifelogs.com

On 2010-10-19, Ted Zlatanov <tzz@lifelogs.com> wrote:
> SM> Yes, of course: short of using multiple major modes (which is something
> SM> Emacs doesn't support very well for now), there's not much highlighting
> SM> we can do other than assuming Perl syntax.
>
> 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.

Are you sure?  I think if one would put the same breaks-CPerl content
inside a here-doc, CPerl would slow down as well.  AFAIK, here-docs
are still facified; the result is just ignored.

Hmm, on the other hand, if it is syntaxification which is slowed down,
then yes - it should not be a lot of problem to skip stuff after
__DATA__, since CPerl does syntaxification in one pass.

> It always ends with EOF or with another __X__ marker on a new line.

Eh???  AFAIK, it ends with EOF period.

  (The code to parse <DATA> may have some special logic to find your
   __X__; but it may look for whatever it wants as well...)

Yours,
Ilya


  reply	other threads:[~2010-10-20 19:40 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 [this message]
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
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=slrnibuhde.f5f.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.