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>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:  <4B7C044A.50006@morningstar2.co.uk>
Date:         Wed, 17 Feb 2010 14:59:22 +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:  <2D995100-34EE-4B91-BDFE-9BDCCF3A6BEC@yahoo.de>
Precedence: list
Status: R

On 17/02/2010 14:38, Philipp Stephani wrote:
>   through the input processor, things like spaces and comments are inevitably lost. I thought of something like this:

We had quite a bit of discussion before about verbatim input and xparse. 
At the time the general agreement seemed to be that you can't reliably 
tackle all verbatim items with a generic function. So we decided that it 
was best to stick to code that will work reliably and accept that some 
items (a small percentage of all functions) will need handling "by hand".
-- 
Joseph Wright