From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Tue, 02 May 2006 22:26:51 +0300 Message-ID: References: <17491.34779.959316.484740@parhasard.net> <17495.15263.333311.84802@parhasard.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1146598047 26920 80.91.229.2 (2 May 2006 19:27:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 2 May 2006 19:27:27 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 02 21:27:25 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 1Fb0Wf-0003rS-AC for ged-emacs-devel@m.gmane.org; Tue, 02 May 2006 21:27:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fb0We-000055-Nn for ged-emacs-devel@m.gmane.org; Tue, 02 May 2006 15:27:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fb0WK-0008Va-1L for emacs-devel@gnu.org; Tue, 02 May 2006 15:26:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fb0WH-0008Uk-GV for emacs-devel@gnu.org; Tue, 02 May 2006 15:26:50 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fb0WH-0008UE-5B for emacs-devel@gnu.org; Tue, 02 May 2006 15:26:49 -0400 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fb0WU-0005Ht-FJ for emacs-devel@gnu.org; Tue, 02 May 2006 15:27:02 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-31-178.inter.net.il [80.230.31.178]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id ECG76464 (AUTH halo1); Tue, 2 May 2006 22:26:47 +0300 (IDT) Original-To: Aidan Kehoe In-reply-to: <17495.15263.333311.84802@parhasard.net> (message from Aidan Kehoe on Tue, 2 May 2006 12:59:43 +0200) 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:53807 Archived-At: > From: Aidan Kehoe > Date: Tue, 2 May 2006 12:59:43 +0200 > Cc: emacs-devel@gnu.org > > > 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. > > If it's 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't see the > argument for that. And I don't see why we should assume anything for something as basic as a subroutine of readevalloop. It could be used to read anything, not just .el files. > > 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 "do we really want > (decode-char 'ucs #xABCD) to produce Unicode or non-Unicode characters > depending on the current user settings?" Maybe it's the same question, but since you are proposing to have decode-char become part of routine reading of Lisp, this feature's impact becomes much more important to discuss. > since making string escapes inconsistent with the Unicode coding > systems does not make any sense. I'm not sure you are right; it should be discussed. > And that question has already been answered. Cf. > http://article.gmane.org/gmane.emacs.bugs/3422 Don't see any answers there about this, perhaps I'm too dumb.