From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: decode-coding-string gone awry? Date: Fri, 18 Feb 2005 09:12:41 -0500 Message-ID: References: <200502140150.KAA29610@etlken.m17n.org> <200502171208.VAA09592@etlken.m17n.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1108736462 24317 80.91.229.2 (18 Feb 2005 14:21:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 18 Feb 2005 14:21:02 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 18 15:21:01 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D28zs-0003kJ-Ct for ged-emacs-devel@m.gmane.org; Fri, 18 Feb 2005 15:20:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D29GE-0006gs-En for ged-emacs-devel@m.gmane.org; Fri, 18 Feb 2005 09:37:38 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D29Fu-0006ct-Dr for emacs-devel@gnu.org; Fri, 18 Feb 2005 09:37:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D29Fq-0006Yr-7U for emacs-devel@gnu.org; Fri, 18 Feb 2005 09:37:14 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D29Fq-0006X7-09 for emacs-devel@gnu.org; Fri, 18 Feb 2005 09:37:14 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D28wY-0004mK-5f for emacs-devel@gnu.org; Fri, 18 Feb 2005 09:17:18 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D28s5-0008Sg-7S; Fri, 18 Feb 2005 09:12:43 -0500 Original-To: Kenichi Handa In-reply-to: <200502171208.VAA09592@etlken.m17n.org> (message from Kenichi Handa on Thu, 17 Feb 2005 21:08:02 +0900 (JST)) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33605 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33605 It's not a trivial work to change the current code (in coding.c) to signal an error safely while doing a code conversion. So, to check if decoding is valid or not, we have to check all characters in a string in advance, which, I think, slows down the operation considerably. Does the speed of decoding for strings really matter? Maybe not. We could try checking the characters in advance, but only for strings. We could also add an arg to decode-coding-string saying "don't check", which people could use in cases where the speed really matters.