User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7)
            Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
References: <4B727378.8060704@morningstar2.co.uk>                              
            <20100210100943.GA3759@oberdiek.my-fqdn.de>                        
            <4B7298D6.7080206@morningstar2.co.uk>                              
            <20100210145258.GA18188@oberdiek.my-fqdn.de>                       
            <4B72D339.5080104@morningstar2.co.uk> <4B7AA5D7.8010104@elzevir.fr>
            <D1A7BA35-0312-4658-BD04-28AC330FD41A@yahoo.de>                    
            <4B7BEB3D.8020105@residenset.net>                      
            <2D995100-34EE-4B91-BDFE-9BDCCF3A6BEC@yahoo.de>           
            <4B7C044A.50006@morningstar2.co.uk>
            <4B7C05BB.8030403@morningstar2.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:  <4B7C071E.2080407@morningstar2.co.uk>
Date:         Wed, 17 Feb 2010 15:11:26 +0000
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: String module
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4B7C05BB.8030403@morningstar2.co.uk>
Precedence: list
Status: R

On 17/02/2010 15:05, Joseph Wright wrote:
> I should add that the issue was *if* you could include verbatim input
> using \NewDocumentCommand (as the last argument). The problem is not so
> much getting things right for one argument but dealing with the various
> cases:
> - Several arguments with only the last optional
> - Verbatim w.r.t. only some characters (some can be handled with
> \scantokens, some cannot)
> - Dealing entirely properly with nested functions (and making sure that
> the limitations are clear).

I should also add that perhaps having something like 
\DeclareVerbatimCommand is at least as sensible as 
\DeclareExpandableDocumentCommand.  If others agree I'm sure we can look 
at it (starting with the suggested code and then trying to break it!).
-- 
Joseph Wright