public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/9449] UCNs not recognized in identifiers (c++/c99)
Date: Fri, 07 Jan 2005 15:02:00 -0000	[thread overview]
Message-ID: <20050107150158.4232.qmail@sourceware.org> (raw)
In-Reply-To: <20030127145600.9449.rearnsha@arm.com>


------- Additional Comments From joseph at codesourcery dot com  2005-01-07 15:01 -------
Subject: Re:  UCNs not recognized in identifiers
 (c++/c99)

On Fri, 7 Jan 2005, gdr at integrable-solutions dot net wrote:

> 
> ------- Additional Comments From gdr at integrable-solutions dot net  2005-01-07 14:27 -------
> Subject: Re:  UCNs not recognized in identifiers (c++/c99)
> 
> "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> writes:
> 
> | I've had no on-list response yet to the query about this I sent to the 
> | WG14 reflector on Tuesday (reflector message 10698), with the HEBREW 
> | LETTER SHIN WITH DAGESH AND SHIN DOT examples.
> 
> Since this issue contains a compatibility fragment and affects both C
> and C++, it occurs to me that you should resend a copy of your message
> to the C/C++ compatibility reflector (reaching both WG14 and WG21).  I
> highly encourage you to do that.  The address is c++std-compat at accu
> dot org.  It would be wrong to let the issue debated by WG14 only
> without WG21 knowing. 

I've now sent it to c++std-compat (having checked that the C++ list of 
characters also includes combining characters in more than one combining 
class so the same issues can arise there at least in principle, whether or 
not they can arise with realistic natural language identifiers).



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9449


  parent reply	other threads:[~2005-01-07 15:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030127145600.9449.rearnsha@arm.com>
2003-11-05  6:51 ` pinskia at gcc dot gnu dot org
2004-12-16  2:16 ` zack at codesourcery dot com
2004-12-16  2:37 ` gdr at integrable-solutions dot net
2004-12-16  2:54 ` joseph at codesourcery dot com
2004-12-16  3:04 ` zack at codesourcery dot com
2004-12-16 12:33 ` joseph at codesourcery dot com
2004-12-16 14:23 ` joseph at codesourcery dot com
2004-12-16 23:05 ` joseph at codesourcery dot com
2005-01-07  7:10 ` zack at gcc dot gnu dot org
2005-01-07 10:28 ` joseph at codesourcery dot com
2005-01-07 14:27 ` gdr at integrable-solutions dot net
2005-01-07 15:02 ` joseph at codesourcery dot com [this message]
2005-01-07 15:39   ` Gabriel Dos Reis
2005-01-07 15:39 ` gdr at integrable-solutions dot net
2005-01-08  2:20 ` geoffk at gcc dot gnu dot org
2005-01-08  4:11 ` joseph at codesourcery dot com
2005-01-08  4:45 ` gdr at integrable-solutions dot net
2005-01-08  5:32 ` joseph at codesourcery dot com
2005-01-09  3:20 ` gdr at integrable-solutions dot net
2005-02-21 21:34 ` jsm28 at gcc dot gnu dot org
2005-02-21 23:39 ` joseph at codesourcery dot com
2005-02-21 23:50 ` zack at codesourcery dot com
2005-02-21 23:51 ` zack at codesourcery dot com
2005-02-22  0:10 ` zack at codesourcery dot com
2005-02-22  3:14 ` neil at daikokuya dot co dot uk
2005-02-22 10:50 ` joseph at codesourcery dot com
2005-02-22 11:24 ` joseph at codesourcery dot com
2005-02-22 12:00 ` joseph at codesourcery dot com
2005-03-12 11:15 ` jsm28 at gcc dot gnu dot org
2005-07-05  2:14 ` pinskia at gcc dot gnu dot org
2005-09-15 22:34 ` geoffk at gcc dot gnu dot org
2005-09-15 22:53   ` Neil Booth
2005-09-15 22:54 ` neil at daikokuya dot co dot uk
2005-09-15 22:54 ` joseph at codesourcery dot com
2005-09-15 22:59 ` neil at daikokuya dot co dot uk
2005-09-15 23:38 ` joseph at codesourcery dot com
2005-09-16  0:02 ` geoffk at geoffk dot org
     [not found] <bug-9449-4@http.gcc.gnu.org/bugzilla/>
2014-11-05 16:20 ` jsm28 at gcc dot gnu.org
2014-11-05 16:23 ` jsm28 at gcc dot gnu.org
2014-11-06 21:09 ` jsm28 at gcc dot gnu.org

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=20050107150158.4232.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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.
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).