From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: User-reserved element in byte code vectors Date: 18 May 2004 00:33:37 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <85ekpz5twj.fsf@junk.nocrew.org> <874qqiao9o.fsf@tc-1-100.kawasaki.gol.ne.jp> <20040515231012.GA20052@fencepost> <20040517220612.GA6421@fencepost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084833681 28278 80.91.224.253 (17 May 2004 22:41:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 May 2004 22:41:21 +0000 (UTC) Cc: lars@nocrew.org, Stefan Monnier , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 18 00:41:14 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 1BPqnJ-0004Qe-00 for ; Tue, 18 May 2004 00:41:13 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BPqnJ-0007gG-00 for ; Tue, 18 May 2004 00:41:13 +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 1BPqlX-0005PK-4k for emacs-devel@quimby.gnus.org; Mon, 17 May 2004 18:39:23 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BPqiD-0004N2-QI for emacs-devel@gnu.org; Mon, 17 May 2004 18:35:58 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BPqg6-0003D8-DM for emacs-devel@gnu.org; Mon, 17 May 2004 18:34:17 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BPqg6-0003Cg-0q for emacs-devel@gnu.org; Mon, 17 May 2004 18:33:46 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1BPqfz-0006JO-3E; Mon, 17 May 2004 18:33:39 -0400 Original-To: Miles Bader In-Reply-To: <20040517220612.GA6421@fencepost> Original-Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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:23601 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23601 Miles Bader writes: > On Mon, May 17, 2004 at 12:30:05PM -0400, Stefan Monnier wrote: > > > 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: > > I think the case where using `lambda' becomes annoying is when you have a > variable-length arglist, which with lambda would require using &rest or > something, and so do lots of run-time consing. Without lexical binding, currying a curried function would probably not work when using the lambda approach (haven't thought this through in detail, though). -- David Kastrup, Kriemhildstr. 15, 44793 Bochum