User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
References: <4A7921CF.5020803@morningstar2.co.uk>                              
            <4A7A1505.4040604@residenset.net>                                  
            <DB76B425-0A88-43B4-9CF0-B92FAF159E37@gmail.com>                   
            <4A7AD930.2090106@residenset.net>                                  
            <8516B615-51AA-4D90-BB7D-A9E122AA0335@gmail.com>                   
            <4A804317.6050909@morningstar2.co.uk> <4A80508F.3030904@elzevir.fr>
            <0C83E480-14E3-4CD8-924E-3B9EA602E004@gmail.com>           
            <4A810D6E.5050207@morningstar2.co.uk> <4A815596.6090308@elzevir.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <4A815ACD.1040706@morningstar2.co.uk>
Date:         Tue, 11 Aug 2009 12:49:33 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: xparse
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4A815596.6090308@elzevir.fr>
Precedence: list
Status: R

Manuel Pégourié-Gonnard wrote:
> Maybe I confused pre/post in my previous message. I always meant post-grabbing
> and pre-actual-function-call processing :-)

I guessed that was the case: just wanted to be 100 % clear.

>> (2) + for \long, upper-case for defaults on optional arguments:
>>
>> \DeclareDocumentCommand \foo { o           >\MakeHarmless +m }
>> \DeclareDocumentCommand \foo { O{default}  >\MakeHarmless +m }
>> \DeclareDocumentCommand \foo { +o          >\MakeHarmless +m }
>> \DeclareDocumentCommand \foo { +O{default} >\MakeHarmless +m }

[snip]

> I'm in favour of option 2. It looks more "extensible", if extensions are ever
> needed in the future.

I think this is the consensus view: I'm going to look at doing this
(really pretty close to what xparse has anyway).

> OTOH, as you mentioned in another message, it would be very interesting to
> detect trivial cases like only 'm' arguments and use the trivial (hence purely
> expandable) parser in this case with DeclareDocumentCommand.

I'm viewing "only m" as a rather special case, as there is clearly no
need for extra processing.  The only place this shows up, I think, is as
you point out when TeX is looking for an \omit.
-- 
Joseph Wright