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: Tue, 2 May 2006 12:59:43 +0200 Message-ID: <17495.15263.333311.84802@parhasard.net> References: <17491.34779.959316.484740@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 1146567615 9837 80.91.229.2 (2 May 2006 11:00:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 2 May 2006 11:00:15 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 02 13:00:08 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 1Fasbr-0004ks-3B for ged-emacs-devel@m.gmane.org; Tue, 02 May 2006 13:00:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fasbq-0007tM-NE for ged-emacs-devel@m.gmane.org; Tue, 02 May 2006 07:00:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fasbf-0007so-I9 for emacs-devel@gnu.org; Tue, 02 May 2006 06:59:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fasbb-0007og-Sy for emacs-devel@gnu.org; Tue, 02 May 2006 06:59:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fasbb-0007oQ-JL for emacs-devel@gnu.org; Tue, 02 May 2006 06:59:47 -0400 Original-Received: from [66.111.49.30] (helo=icarus.asclepian.ie) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fasbg-00034r-Vt; Tue, 02 May 2006 06:59:53 -0400 Original-Received: by icarus.asclepian.ie (Postfix, from userid 1003) id 6C39C8008C; Tue, 2 May 2006 11:59:43 +0100 (IST) Original-To: Eli Zaretskii In-Reply-To: X-Mailer: VM 7.17 under 21.5 (beta25) "eggplant" (+CVS-20060325) XEmacs Lucid X-Echelon-distraction: Fox burhop zipgun Menwith SRI Golf 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:53782 Archived-At: Ar an dara l=C3=A1 de m=C3=AD Bealtaine, scr=C3=ADobh Eli Zaretskii:=20 > Whether it is safe or not, I think it's certainly better to implement > the guts of decode-char in C, if it's gonna be called from > read_escape.=20 If it=E2=80=99s only going to be called rarely (twice a file for non-byte= -compiled files, at a liberal guess, never for byte-compiled files), and after decode-char is already loaded--both of which are the case--I don=E2=80=99= t see the argument for that. > All those guts do is simple arithmetics, which will be much faster in = C. > > Moreover, I think the fact that decode-char uses translation tables to > support unify-8859-on-*coding-mode (and thus might produce characters > other than mule-unicode-*) could even be a misfeature: do we really > want read_escape to produce Unicode or non-Unicode characters when it > sees \uNNNN, depending on the current user settings? This is not significantly different from the question =E2=80=9Cdo we real= ly want (decode-char 'ucs #xABCD) to produce Unicode or non-Unicode characters depending on the current user settings?=E2=80=9D, since making string esc= apes inconsistent with the Unicode coding systems does not make any sense. And that question has already been answered. Cf.=20 http://article.gmane.org/gmane.emacs.bugs/3422 .=20 --=20 Aidan Kehoe, http://www.parhasard.net/