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
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Thu, 20 Nov 2008 12:28:13 +1030
Content-Disposition:
inline
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
Re: \exp_after:NN
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
<[log in to unmask]>
Content-Type:
text/plain; charset=UTF-8
From:
Will Robertson <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines) 
On Thu, Nov 20, 2008 at 8:00 AM, Joseph Wright
<[log in to unmask]> wrote:
> Hello all,
>
> I've been writing a talk about LaTeX3, and something struck me.  Why is it
> \exp_after:NN and no \exp_after:NO?

Or even \exp_args:NO, which saves us a char. (In fact, we could drop
the "s" in all of the \exp_args functions and save us another...)

I guess \exp_after:NN is an edge-case of the naming scheme. In fact,
it should probably be called \exp_after:ww because in a case like
this:
  \foo\expandafter{\bar}
the opening brace doesn't really qualify as a "N" type argument.

Morten and Frank (and others), is this something that we need to address?

Will

ATOM RSS1 RSS2