Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id p4G802uC015463 for ; Mon, 16 May 2011 10:00:03 +0200 Received: (qmail 21028 invoked by alias); 16 May 2011 07:59:57 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 16 May 2011 07:59:56 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx111) with SMTP; 16 May 2011 09:59:56 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p4G7vtUl020617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 May 2011 09:57:56 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p4G7HTZm004064; Mon, 16 May 2011 09:57:55 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1217053 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 16 May 2011 09:57:55 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p4G7vtQn031942 for ; Mon, 16 May 2011 09:57:55 +0200 Received: from ueamailgate02.uea.ac.uk (ueamailgate02.uea.ac.uk [139.222.131.185]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p4G7vgLH020485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 16 May 2011 09:57:49 +0200 Received: from ueams01.uea.ac.uk (ueams01.uea.ac.uk [139.222.131.78]) by ueamailgate02.uea.ac.uk (8.13.8/8.13.8) with ESMTP id p4G7ve7S023193; Mon, 16 May 2011 08:57:40 +0100 Received: from [139.222.114.131] by ueams01.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1QLsgL-0000cA-LS; Mon, 16 May 2011 08:57:37 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 References: <4DCA93CC.5020605@morningstar2.co.uk> <19920.15087.714131.100464@morse.mittelbach-online.de> <447088.31292.qm@web24704.mail.ird.yahoo.com> <4DD0BFB3.7070007@morningstar2.co.uk> <27DAD3FD-9C28-4707-9454-FBB65B66A56D@gmail.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, outgoing) X-CanIt-Geo: ip=139.222.131.78; country=GB; region=I9; city=Norwich; latitude=52.6333; longitude=1.3000; http://maps.google.com/maps?q=52.6333,1.3000&z=6 X-CanItPRO-Stream: UEA:outgoing (inherits from UEA:default,base:default) X-Canit-Stats-ID: 06EI7VEMR - 31d0c833d594 - 20110516 X-Scanned-By: CanIt (www . roaringpenguin . com) on 139.222.131.185 Message-ID: <4DD0D8F4.7030101@morningstar2.co.uk> Date: Mon, 16 May 2011 08:57:40 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: xparse and space skipping To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <27DAD3FD-9C28-4707-9454-FBB65B66A56D@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p5Xglyw75EiO2RwPv/SB5M6b62N/A3QeAkGfLbAlElHVyQXIvxgvk5mcUY5w h3QTTm+LGMZnILQ83KkyYwBWPBsuh7V0Dr+RHAuDR7ExBlErtEqIvwZ5xWUjvRaOpr/0SgfWPqWx HFutPE3u95uJbaZaFCW0fNoAHULQQqcUlOxg5NnFbrXplG03evoWjKck04Ec1IgdVOpzA==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6755 On 16/05/2011 08:51, Will Robertson wrote: > Dropping trailing optional arguments just doesn't feel right to me; in the interests of disclosure, however, at least two of the packages I've written (pstool and mlist) use them, so I'm clearly biased :) Their interfaces could certainly be revised but I don't think (yet) in hindsight that the way the commands work therein is necessary a bad idea. As I said in my other mail, at the moment xparse is about LaTeX2e conventions using LaTeX3 ideas. So there is no danger of dropping trailing optional arguments at the moment! I'd also note that there is an outstanding question on the coffin code about whether optional arguments, a keyval approach or something in between is best. So I certainly don't regard this question as resolved one way or the other at present: at the moment, I'm just worried about spaces :-) -- Joseph Wright