unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Michał Nazarewicz" <mina86@mina86.com>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
Subject: Re: Regexp for c-or-c++-mode
Date: Thu, 11 Jun 2020 09:40:53 +0000	[thread overview]
Message-ID: <20200611094053.GA5703@ACM> (raw)
In-Reply-To: <CA+pa1O1-i+Ea2pgjyhL5VkpzTVrETwcrZ-=-EivmNURq7pAwRA@mail.gmail.com>

Hello, Micha�.

On Thu, Jun 11, 2020 at 00:42:25 +0100, Michał Nazarewicz wrote:
> On Wed, 10 Jun 2020 at 15:15, Robert Pluim <rpluim@gmail.com> wrote:

> > >>>>> On Wed, 10 Jun 2020 14:58:18 +0100, Michał Nazarewicz <mina86@mina86.com> said:

> >     Michał> On Wed, 10 Jun 2020 at 12:40, Robert Pluim <rpluim@gmail.com> wrote:
> >     Michał> I suppose you’re right. It should be [ \t\v\f] instead to catch
> >     Michał> all non-new-line white-space characters. Or [ \t\v\f\r\n] to catch
> >     Michał> all white-space characters.

> >     >> [[:blank:]] ?

> >     Michał> [[:blank:]] is defined in terms of Unicode properties so that would
> >     Michał> catch things which C does not consider white-space.

> > [[:space:]] then, which uses the buffer's syntax table.

> The regex under discussion needs to adhere to C syntax but is (may be)
> used outside of cc-mode and thus should not rely on syntax table being
> set up for C.

How about using simply [ \t]?  The \r doesn't really add any utility,
just confusion, and there seem not to have been any problems with
c-or-c++-mode so far.  Like you said, including the "bigger" whitespace
characters might lead to false positives.

> -- 
> Best regards
> ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
> «If at first you don’t succeed, give up skydiving»

-- 
Alan Mackenzie (Nuremberg, Germany).



      reply	other threads:[~2020-06-11  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 16:41 Regexp for c-or-c++-mode Alan Mackenzie
2020-06-07 18:07 ` Michał Nazarewicz
2020-06-09 20:12   ` Alan Mackenzie
2020-06-10 11:35     ` Michał Nazarewicz
2020-06-10 11:40       ` Robert Pluim
2020-06-10 13:58         ` Michał Nazarewicz
2020-06-10 14:15           ` Robert Pluim
2020-06-10 23:42             ` Michał Nazarewicz
2020-06-11  9:40               ` Alan Mackenzie [this message]

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=20200611094053.GA5703@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=mina86@mina86.com \
    --cc=rpluim@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).