Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
References: <4AE0BFB3.7080905@morningstar2.co.uk>
Message-ID:  <8A015AE0-022B-4462-B8D5-CC1010E49205@gmail.com>
Date:         Fri, 23 Oct 2009 13:47:41 +1030
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: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: xparse processors
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4AE0BFB3.7080905@morningstar2.co.uk>
Precedence: list
Status: R

On 23/10/2009, at 6:55 AM, Joseph Wright wrote:

> This would allow things like:
>
> > \ReturnVariable { \MakeHarmless\ReturnVariable }
>  % Will absorb one more argument, as required
>
> (using \MakeHarmless from xdoc). That doesn't work at present as the  
> return has to be in a toks.
>
> As Lars points out, that is quite a bit more flexible at the cost of  
> a little complexity in the syntax.


I'm not sure that I see how this is any more flexible?
Oh, simply that your argument processor doesn't have to be hard-coded  
to use \l_xparse_arg_toks.
But hang on, can't you do the same thing at present by just writing

     > { \MakeHarmless\l_xparse_arg_toks }

?

-- Will