From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: zack@rabi.columbia.edu
Cc: eggert@twinsun.com, rms@gnu.org, bothner@cygnus.com, amylaar@cygnus.co.uk, gcc2@gnu.org, egcs@cygnus.com
Subject: Re: revised proposal for GCC and non-Ascii source files
Date: Sun, 31 Jan 1999 23:58:00 -0000
Message-id: <199901042305.AAA00716@mira.isdn.cs.tu-berlin.de>
References: <199901042115.QAA13627@rabi.phys.columbia.edu>
X-SW-Source: 1999-01n/msg00095.html

> This raises the issue of how we tell native extended character X from native
> ASCII character %.  I'm beginning to suspect we need the more general locale
> information, not just the charset.

Paul suggested that you can test whether you are in the initial state
when using the multibyte functions. If that is true, and if we assume
that the initial state is ASCII (as mandated by the C and C++
standards), we have a test whether a single byte we just saw really is
from the base character set.

Furthermore, the standards require that we are in the initial state
after each identifier. So we have good reason to reject

<escape>printf<funny characters>("Hello world");<escape to ASCII>

The escape back to ASCII must occur right after <funny characters>,
and should probably count as part of the identifier.

Regards,
Martin