all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: A possible way for CC Mode to resolve its sluggishness
Date: Fri, 26 Apr 2019 22:53:09 +0300	[thread overview]
Message-ID: <83k1fgwnkq.fsf@gnu.org> (raw)
In-Reply-To: <20190426193056.GC4720@ACM> (message from Alan Mackenzie on Fri,  26 Apr 2019 19:30:56 +0000)

> Date: Fri, 26 Apr 2019 19:30:56 +0000
> From: Alan Mackenzie <acm@muc.de>
> 
> (i) A CC Mode buffer will be partitioned into @dfn{syntactic cells}.
> These will be things like a section of code, a comment, a string, a raw
> string, a CPP construct ....  Possibly even comment delimiters would
> have their own cells.
> 
> (ii) Syntactic cells will be implemented by a text property, c-syntax,
> whose value will indicate the type of the cell, and possibly an
> identifier for it.  Neighbouring cells will always have distinct
> c-syntax values.

Can a syntactic cell have other syntactic cells embedded in it?
Because if it can, you cannot use text properties for that, since text
properties cannot overlap.

> Thoughts?

Why do you think this proposal will make CC Mode faster?  Wouldn't
computing and updating the cells in itself be expensive?



  reply	other threads:[~2019-04-26 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 19:30 A possible way for CC Mode to resolve its sluggishness Alan Mackenzie
2019-04-26 19:53 ` Eli Zaretskii [this message]
2019-04-26 20:11   ` Alan Mackenzie
2019-04-27  2:10 ` Stefan Monnier
2019-04-27  3:34   ` Óscar Fuentes
2019-04-27 13:57   ` Alan Mackenzie
2019-04-28 17:32     ` Stephen Leake
2019-04-29  1:46     ` Stefan Monnier
2019-04-29  9:23       ` Alan Mackenzie
2019-04-29 12:19         ` 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=83k1fgwnkq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@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.