User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
References: <4A7921CF.5020803@morningstar2.co.uk>                              
            <4A86949D.3090500@morningstar2.co.uk>                              
            <4A886BA8.2000209@morningstar2.co.uk>                              
            <0417DF73-EC19-4262-B9DF-5C870D47BFCE@gmail.com>                   
            <4A893816.2090807@residenset.net>                                 
            <4A89610D.8060108@morningstar2.co.uk>                      
            <4A8C71CC.7000006@residenset.net>           
            <4A8D0048.4070101@morningstar2.co.uk>
            <4A946AD7.4020506@residenset.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <4A9EC61D.5000502@morningstar2.co.uk>
Date:         Wed, 2 Sep 2009 20:23:09 +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:  <4A946AD7.4020506@residenset.net>
Precedence: list
Status: R

Lars Hellström wrote:
> Finally, there is the issue that a processor has to put the argument in
> a toks register. I understand this is for generality (only sane way to
> pass along # tokens), but my experience with this type of API is that
> one should make it easy to use commands that happen to already exist. In
> this case, it would mean to also support a processor that would store
> its result in a macro rather than a toks register, since I'm quite sure
> this is what people tend to do unless they definitely need a toks register.

Maybe I'm missing something here, but if we need the processed value
returned in a named variable it should not matter whether it is a toks
or a tl (or indeed anything else). All that needs to happen is

\toks_set:NV \l_xparse_arg_toks <variable-used-in-processor>

which is the same action if <variable-used-in-processor> is a tl or a
toks. As there are add left/right functions for toks, there should also
be no problem "building up" \l_xparse_arg_toks piecewise:

\toks_out_right:Nn \l_xparse_arg_toks { <whatever> }

and so on.
-- 
Joseph Wright