LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced 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
Mime-Version:
1.0 (Apple Message framework v1081)
Content-Type:
text/plain; charset=us-ascii
Date:
Wed, 9 Mar 2011 11:24:11 +1030
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
Will Robertson <[log in to unmask]>
Message-ID:
In-Reply-To:
Content-Transfer-Encoding:
8bit
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (24 lines)
On 08/03/2011, at 11:47 PM, Bruno Le Floch wrote:

> Thank you Joseph for the quick bug fix. Let me propose the following
> code for inclusion. The idea is similar to `\prg_new_map_functions`,
> which defines a set of maps, some of which are expandable. Namely,
> 
> \tl_gset_replacer:nnn {<name>} {<item1>} {<item2>}

As an aside, based on the name of \prg_new_map_functions:Nn I think \prg_new_replace_functions:Nn would be better.

> defines expandable replacement functions:
> 
> \<name>_replace_aux:nwwn
> \<name>_replace_some:nn
> \<name>_replace_one:n
> \<name>_replace_all:n
> 
> which are all `f`-expandable.

This sounds pretty good to me. How useful is the _some function? I'd be happy without it.
Anyway, I'd vote for adding this to expl3.

-- Will

ATOM RSS1 RSS2