Mime-Version:
1.0 (Apple Message framework v1077)
Content-Type:
text/plain; charset=iso-8859-1
Date:
Wed, 17 Feb 2010 08:47:52 +1030
Content-Transfer-Encoding:
8bit
|
On 17/02/2010, at 12:34 AM, Manuel Pégourié-Gonnard wrote:
> By the way, I find is rather weird, that \tl_if_eq doesn't really compare token
> lists, but only their conversions as TeX strings. IMO it would be clearer to
> have a \str_if_eq::nn(TF) function in the string module, and then conversion
> functions from the tl to the str data type.
>
> Such conversion function could also be the place to implement "string input
> methods" if they are needed. Eg, the most basic conversion function would be
> something like \edef + \detokenize, but one could imagine a conversion function
> that locally redefines \% as expanding into a catcode 12 %, etc. before
> performing the \edef, so that a user can easily input arbitrary strings.
FWIW, I'm in favour of these ideas.
Clearly up some of the edge cases with tl_replace_in (for example), which doesn't accept braces, would be helpful, I think.
-- Will
|
|
|