From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Aidan Kehoe Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Fri, 5 May 2006 21:20:57 +0200 Message-ID: <17499.42393.597479.46003@parhasard.net> References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> <17498.11949.75640.41779@parhasard.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1146856906 5511 80.91.229.2 (5 May 2006 19:21:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 5 May 2006 19:21:46 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 05 21:21:21 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Fc5ra-0003Sp-FD for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 21:21:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc5rZ-0008D8-Um for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 15:21:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fc5rL-0008Bq-HL for emacs-devel@gnu.org; Fri, 05 May 2006 15:21:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fc5rK-0008BA-24 for emacs-devel@gnu.org; Fri, 05 May 2006 15:21:03 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc5rJ-0008Au-JI for emacs-devel@gnu.org; Fri, 05 May 2006 15:21:01 -0400 Original-Received: from [66.111.49.30] (helo=icarus.asclepian.ie) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fc5rV-0006PQ-Ey; Fri, 05 May 2006 15:21:13 -0400 Original-Received: by icarus.asclepian.ie (Postfix, from userid 1003) id 305C38008D; Fri, 5 May 2006 20:20:59 +0100 (IST) Original-To: rms@gnu.org In-Reply-To: X-Mailer: VM 7.17 under 21.5 (beta25) "eggplant" (+CVS-20060325) XEmacs Lucid X-Echelon-distraction: RECCEX SADRS Military Intelligence DEADBEEF Spetznaz MDA X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:53970 Archived-At: Ar an c=C3=BAigi=C3=BA l=C3=A1 de m=C3=AD Bealtaine, scr=C3=ADobh Richar= d Stallman:=20 > [...] The thing with the Emacs \x escape is that anyone using it f= or > characters outside of ASCII is asking for pain, and always has bee= n.=20 > It has only ever been clearly defined for that character set; any > existing code in the repository for other characters, for example, > _will definitely_ break with the merging of the Unicode branch. >=20 > We are miscommunicating. Whether it is wise to use \x is not the > question. The issue I am talking about is that of _coherence_ > (parallelism of syntax) between \x and \u. Indeed. And one of the paragraphs you snipped indicated my doubts as to whether it is wise to be coherent with something that is either bad style= or broken. > [...] Thank you, but my question here is not about \u. Rather, it is > about whether there are OTHER incompatibilities between Emacs Lisp and= C > string syntax. > > I want to see that information before deciding what to do here. There aren=E2=80=99t, to my knowledge, C is a pretty conservative languag= e. GCC and its conscientious approach to the standards is a big part of why that is = so, as I understand it.=20 --=20 Aidan Kehoe, http://www.parhasard.net/