From: Michal Nazarewicz <mina86@mina86.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lists@dima.secretsauce.net, 24071@debbugs.gnu.org
Subject: bug#24071: [PATCH] Refactor regex character class parsing in [:name:]
Date: Wed, 27 Jul 2016 20:30:28 +0200 [thread overview]
Message-ID: <xa1th9bb2at7.fsf@mina86.com> (raw)
In-Reply-To: <83fuqvrqom.fsf@gnu.org>
On Wed, Jul 27 2016, Eli Zaretskii wrote:
> But this later patch looks like a beginning of a series of refactoring
> (is it?), hopefully followed by more features,
Well… I had bunch of patches prepared but then I discovered that
‘#ifndef emacs’ is used by etags and ‘#ifdef _LIBC’ cannot go away
either so all of them are now gone… :(
But I am wondering about a way to turn all of the ‘syntax & RE_FOO’
checks into compile-time expressions when compiling regex.c for Emacs.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
next prev parent reply other threads:[~2016-07-27 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 22:54 bug#24071: [PATCH] Refactor regex character class parsing in [:name:] Michal Nazarewicz
2016-07-26 14:46 ` Eli Zaretskii
2016-07-27 15:29 ` Michal Nazarewicz
2016-07-27 16:28 ` Eli Zaretskii
2016-07-27 18:30 ` Michal Nazarewicz [this message]
2016-07-27 16:50 ` bug#24071: [PATCH 1/7] New regex tests imported from glibc 2.21 Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 2/7] Added driver for the regex tests Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 3/7] Fix reading of regex-resources in regex-tests Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 4/7] Don’t (require 'cl) Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 5/7] Split regex glibc test cases into separet tests Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 6/7] Remove dead opcodes in regex bytecode Michal Nazarewicz
2016-07-27 16:50 ` bug#24071: [PATCH 7/7] Refactor regex character class parsing in [:name:] Michal Nazarewicz
2016-07-29 5:31 ` bug#24071: [PATCH] " Dima Kogan
2016-07-29 5:53 ` Eli Zaretskii
2016-07-29 13:07 ` Michal Nazarewicz
2016-08-02 16:06 ` Michal Nazarewicz
2016-08-02 16:46 ` Eli Zaretskii
2016-08-02 17:54 ` Michal Nazarewicz
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=xa1th9bb2at7.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=24071@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lists@dima.secretsauce.net \
/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.