From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: Keyword args Date: Mon, 13 Dec 2010 09:30:35 +0100 Message-ID: References: <87mxojwu15.fsf@uwakimon.sk.tsukuba.ac.jp> <87k4jnweng.fsf@uwakimon.sk.tsukuba.ac.jp> <87d3pdwt1x.fsf@uwakimon.sk.tsukuba.ac.jp> <87bp4x37ey.fsf@lola.goethe.zz> <874oapwnon.fsf@uwakimon.sk.tsukuba.ac.jp> <4D01D9D8.5040400@gmail.com> <4D0580A6.7090307@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1292229065 25196 80.91.229.12 (13 Dec 2010 08:31:05 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 13 Dec 2010 08:31:05 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 13 09:30:59 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PS3oB-0001Cm-4h for ged-emacs-devel@m.gmane.org; Mon, 13 Dec 2010 09:30:59 +0100 Original-Received: from localhost ([127.0.0.1]:41686 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PS3oA-0002rq-IN for ged-emacs-devel@m.gmane.org; Mon, 13 Dec 2010 03:30:58 -0500 Original-Received: from [140.186.70.92] (port=45629 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PS3o2-0002r1-9b for emacs-devel@gnu.org; Mon, 13 Dec 2010 03:30:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PS3o1-0006o1-2v for emacs-devel@gnu.org; Mon, 13 Dec 2010 03:30:50 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:48684) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PS3o0-0006nJ-Pk for emacs-devel@gnu.org; Mon, 13 Dec 2010 03:30:49 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PS3ny-00018u-NR for emacs-devel@gnu.org; Mon, 13 Dec 2010 09:30:46 +0100 Original-Received: from 212.46.169.137 ([212.46.169.137]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Dec 2010 09:30:46 +0100 Original-Received: from eller.helmut by 212.46.169.137 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Dec 2010 09:30:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 33 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 212.46.169.137 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:qvnTeBkk24D6LpyhiwVvP3ux8f8= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:133642 Archived-At: * Daniel Colascione [2010-12-13 02:10] writes: > On 12/10/10 12:53 AM, Helmut Eller wrote: >> * Daniel Colascione [2010-12-10 07:42] writes: >> >>> On 12/7/10 8:30 AM, Stephen J. Turnbull wrote: >>>> David Kastrup writes: >>>> >>>> > I don't think anybody minds the features. >>>> >>>> IIRC rms has recently declared his dislike for CL-style keyword >>>> arguments. I suppose that's part of the "syntactic complexity" you >>>> mention, but MON KEY OTOH points out cases where he'd like to use >>>> them. So there are some fundamental disagreements here. >>> >>> I'd just like to add my support for keyword arguments. Functions like >>> write-region are both horrible and brittle because their parameters are >>> both numerous and overloaded; specific functionality can be more simply >>> expressed with using keyword arguments. >> >> You always have the option to make a macro with keyword arguments which >> expands to a call to the "raw" function. > > How many forwarder macros do you need to sufficiently cover the problem > space? Combinatorial explosion is a problem when the set of possible > inputs is large. Exactly as many macros as you would be need keyword argument parsing functions. Whether keywords are used for functions or macros makes no difference to cover the "problem space" (which I presume is a better interface to write-region). Helmut