From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: safe_call1 considered harmful Date: Mon, 24 Jul 2006 10:44:10 +0900 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1153705520 4062 80.91.229.2 (24 Jul 2006 01:45:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Jul 2006 01:45:20 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 24 03:45:19 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 1G4pVR-0000L6-70 for ged-emacs-devel@m.gmane.org; Mon, 24 Jul 2006 03:45:14 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4pVQ-0002I5-Py for ged-emacs-devel@m.gmane.org; Sun, 23 Jul 2006 21:45:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G4pVD-0002HY-Cu for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:44:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G4pVC-0002HM-28 for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:44:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4pVB-0002HJ-SE for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:44:57 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G4pW7-0000d3-Tf; Sun, 23 Jul 2006 21:45:56 -0400 Original-Received: from smtp2.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k6O1iqxM024745; Mon, 24 Jul 2006 10:44:52 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp2.aist.go.jp with ESMTP id k6O1iqbM018584; Mon, 24 Jul 2006 10:44:52 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1G4pUQ-00062s-00; Mon, 24 Jul 2006 10:44:10 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Fri, 21 Jul 2006 15:37:04 -0400) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:57515 Archived-At: In article , Richard Stallman writes: > But, by considering this problem again, I found another > solution than calling find-operation-coding-system with > (FILENAME . BUFFER). That is to provide an extra argument > BUFFER. > Would you please be more concrete? Passing an extra argument to a set > of functions is very incompatible. find-operation-coding-system calls a registered function with a single argument; a list of arguments given to find-operation-coding-system. So, appending an extra argument at the tail of the list is fairly safe. --- Kenichi Handa handa@m17n.org