From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Unicode Lisp reader escapes Date: Fri, 05 May 2006 09:05:15 -0400 Message-ID: <87bquctz7t.fsf-monnier+emacs@gnu.org> References: <17491.34779.959316.484740@parhasard.net> <87odyfnqcj.fsf-monnier+emacs@gnu.org> <87psiuj8at.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1146834377 19466 80.91.229.2 (5 May 2006 13:06:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 5 May 2006 13:06:17 +0000 (UTC) Cc: alkibiades@gmx.de, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 05 15:06:14 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 1Fc00R-0003H4-Kj for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 15:06:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc00R-0001ri-6m for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 09:06:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fbzzo-0001Wf-36 for emacs-devel@gnu.org; Fri, 05 May 2006 09:05:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fbzzl-0001V3-J8 for emacs-devel@gnu.org; Fri, 05 May 2006 09:05:23 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fbzzl-0001Uz-FH for emacs-devel@gnu.org; Fri, 05 May 2006 09:05:21 -0400 Original-Received: from [209.226.175.93] (helo=tomts36-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fbzzu-0003Fs-Dz; Fri, 05 May 2006 09:05:30 -0400 Original-Received: from alfajor ([70.55.147.184]) by tomts36-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060505130519.EDWS13653.tomts36-srv.bellnexxia.net@alfajor>; Fri, 5 May 2006 09:05:19 -0400 Original-Received: by alfajor (Postfix, from userid 1000) id 3C7C52FE7B; Fri, 5 May 2006 09:05:15 -0400 (EDT) Original-To: Eli Zaretskii In-Reply-To: (Eli Zaretskii's message of "Fri, 05 May 2006 13:25:23 +0300") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:53948 Archived-At: >> > ??? inside the Lisp reader, everything needs to be fast, IMO. >> Why? > Because the Lisp reader is the backbone of the Lisp interpreter. >> IMO the only things that need to be fast are those things whose >> performance has a visible impact. I see no evidence that there'll ever be >> a case where the speed with which we can read \u escapes will matter. > You don't need to see an evidence of a collapsing bridge to know that > it must be several times stronger than any imaginable load that could > ever be put on it. We're talking performance here, not correctness. > In other words, not everything is empirical; there's a thing called > ``good engineering practice.'' And we're talking about a micro-optimization, not an algorithmic optimization, so the only good engineering principle I know in this domain is: don't micro-optimize before you know it's necessary. > Sorry for being overly didactic, I'm sure you know all that. I'm just > amazed that such a fundamental issue needs evidence. I don't need evidence to accept the C code version, but I need such evidence before I can accept "performance" as the motivation for the use of C code rather than elisp. Stefan