bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: vinschen@redhat.com, eggert@cs.ucla.edu, bug-gnulib@gnu.org,
	bruno@clisp.org
Cc: eblake@redhat.com, grep-devel@gnu.org
Subject: Re: [Grep-devel] handling of non-BMP characters
Date: Wed, 19 Dec 2018 23:49:39 -0700	[thread overview]
Message-ID: <201812200649.wBK6nd6c031463@freefriends.org> (raw)
In-Reply-To: <c3b9cb7b-150d-d2b3-c699-8842ec1643b1@cs.ucla.edu>

Paul Eggert <eggert@cs.ucla.edu> wrote:

> On 12/18/18 11:51 PM, Bruno Haible wrote:
> >    2) change those gnulib modules that don't behave well with beyond-BMP
> >       characters on Windows and AIX to use char32_t instead of wchar_t.
>
> This sounds good to me. I assume the regexp code will need to be changed 
> accordingly, and if so I can volunteer to coordinate that with glibc 
> (we're close to a freeze in Glibc, but we can install into Gnulib first).
>

I assume you'll make parallel changes in dfa.c at the same time?

Thanks,

Arnold


  reply	other threads:[~2018-12-20  6:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lubpf3h8feabk5.fsf@meyering.net>
     [not found] ` <57223855.0cMppWhKHm@omega>
     [not found]   ` <CA+8g5KGumQSMO82BKDsYUAuTzzkAAAZ+H1qqzy1-HiU0AOxbaA@mail.gmail.com>
2018-12-15 22:08     ` new snapshot available: grep-3.1.46-504af Bruno Haible
2018-12-15 23:32       ` Jim Meyering
2018-12-16 22:52 ` grep-3.1.46-504af on Minix Bruno Haible
     [not found] ` <20181216204837.GM28727@calimero.vinschen.de>
     [not found]   ` <20181216205140.GN28727@calimero.vinschen.de>
2018-12-19  7:51     ` [Grep-devel] handling of non-BMP characters Bruno Haible
2018-12-19 14:41       ` Corinna Vinschen
2018-12-19 14:44         ` Corinna Vinschen
2018-12-19 17:21       ` Jim Meyering
2018-12-19 22:54       ` Paul Eggert
2018-12-20  6:49         ` arnold [this message]
2018-12-20 11:30           ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201812200649.wBK6nd6c031463@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eblake@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=grep-devel@gnu.org \
    --cc=vinschen@redhat.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. 
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).