Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Thu, 6 Aug 2009 10:20:29 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n768KSxH025743 for ; Thu, 6 Aug 2009 10:20:29 +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 n768CiiV004881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Aug 2009 10:12:45 +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 n7687nEx001169; Thu, 6 Aug 2009 10:12:44 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 286907 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 6 Aug 2009 10:12:44 +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 n768CiQM018092 for ; Thu, 6 Aug 2009 10:12:44 +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 n768CPRq004566 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Aug 2009 10:12:29 +0200 Received: from ueams01.uea.ac.uk (ueams01.uea.ac.uk [139.222.131.78]) by ueamailgate02.uea.ac.uk (8.13.1/8.13.1) with ESMTP id n768CPUH011105 for ; Thu, 6 Aug 2009 09:12:25 +0100 Received: from [139.222.203.158] by ueams01.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MYy5E-0000FP-6I for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 06 Aug 2009 09:12:20 +0100 User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 References: <4A7921CF.5020803@morningstar2.co.uk> <4A7A1505.4040604@residenset.net> <4A7A726F.3080006@morningstar2.co.uk> <4A7A857F.4010400@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Canit-CHI2: 0.00 X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, outgoing) X-CanItPRO-Stream: UEA:outgoing (inherits from UEA:default,base:default) X-Canit-Stats-ID: 27605544 - 70cac5e84899 X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 X-Scanned-By: CanIt (www . roaringpenguin . com) on 139.222.131.185 Message-ID: <4A7A906B.6080709@morningstar2.co.uk> Date: Thu, 6 Aug 2009 09:12:27 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: xparse To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 06 Aug 2009 08:20:29.0944 (UTC) FILETIME=[C288CF80:01CA166E] Status: R X-Status: X-Keywords: X-UID: 5829 Will Robertson wrote: > I'm more in favour of having the single letter with a possible optional > default. > I still think that { o } and { o{default} } make the most sense. Well, in a way so do I (it was my suggestion :-)) > I like this way of doing coordinates. Could 'd{}{-default-}' be > shoe-horned into this syntax as well? I suppose that would mean > completely re-writing the parser. But then we wouldn't need another > letter for my feature of limited value. I thought about this. There is an issue, though. For a standard delimited argument, the two "ends" are arbitrary: [) will work as well as []. You can easily pick up: d{ ... for the opening-group token, but in this case you have to have a closing group token as the closing token (both for d{} and for gathering the argument). So d[]{default} and d{}{default} are subtly but importantly different. I'm not opposed, though: "d{}{} can be used to include an optional argument surrounded by braces. Note that in this case the closing token *must* be a close-group token (usually `}')." -- Joseph Wright