LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 21 Feb 2011 12:45:36 +0000
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID:
<[log in to unmask]>
Subject:
Re: Fully expandable "x" argument (was "expandable \uppercase...")
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
<[log in to unmask]>
Content-Type:
text/plain; charset=ISO-8859-1
From:
Joseph Wright <[log in to unmask]>
Parts/Attachments:
text/plain (17 lines) 
On 21/02/2011 12:07, Bruno Le Floch wrote:
>> I suspect condition (2) is  killer. While assuming "{" is catcode 1 is
>> fine for LaTeX-like input, what happens if you're using LaTeX3 with some
>> other input syntax (for example XML)?
> 
> Ok, the code can be changed so that the condition becomes
> 
> (2') There is only one character with catcode 1, and it is known when
> the package is loaded.

I'll give it some thought: as I'm most interested in a new kernel, 'load
time' is not 100% reliable. On the other hand, for internal processing
you can imagine that you might have to rescan material in any case, so
it might not be such an issue.
-- 
Joseph Wright

ATOM RSS1 RSS2