From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: User-reserved element in byte code vectors Date: 17 May 2004 12:30:05 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <85fzaiakb9.fsf@junk.nocrew.org> <20040503195701.GD21891@fencepost> <85ekpz5twj.fsf@junk.nocrew.org> <874qqiao9o.fsf@tc-1-100.kawasaki.gol.ne.jp> <20040515231012.GA20052@fencepost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084813824 15202 80.91.224.253 (17 May 2004 17:10:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 May 2004 17:10:24 +0000 (UTC) Cc: lars@nocrew.org, emacs-devel@gnu.org, Miles Bader Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon May 17 19:10:03 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BPlcp-0003ZU-00 for ; Mon, 17 May 2004 19:10:03 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BPlcp-0008QE-00 for ; Mon, 17 May 2004 19:10:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BPlbZ-0005Dx-Aj for emacs-devel@quimby.gnus.org; Mon, 17 May 2004 13:08:45 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BPlTq-00041E-Jm for emacs-devel@gnu.org; Mon, 17 May 2004 13:00:46 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BPl0D-0007Ge-2N for emacs-devel@gnu.org; Mon, 17 May 2004 12:30:45 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BPl0C-0007GF-Go; Mon, 17 May 2004 12:30:08 -0400 Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 5E65E20D18; Mon, 17 May 2004 12:30:06 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 1249E8CA23; Mon, 17 May 2004 12:30:06 -0400 (EDT) Original-To: rms@gnu.org In-Reply-To: Original-Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.9, requis 5, BAYES_00 -4.90) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23588 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23588 > My idea is that it would say where to fit the new args around the old > args. For instance, you might want to curry args 2 and 3. This would > be easy if the first slot has a list saying where the curried args go. > For instance, a list of integers saying which positions to use > the curried args in. We already have a very simple way to express such things: (curry (lambda (x2 x3 x1 x4) (f x1 x2 x3 x4) arg2 arg3) this also has the advangtage that it is naturally extends to (curry (lambda (x23 x1 x4) (f x1 x23 x23 x4) arg23) and many other cases we can't even think of yet. And it requires ZERO extra C code. Stefan