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:
Tue, 11 Aug 2009 23:34:02 +0200
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
8bit
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
From:
Lars Hellström <[log in to unmask]>
Parts/Attachments:
text/plain (36 lines)
Joseph Wright skrev:
> Lars Hellström wrote:
>>>     }
>>>     \cs_generate_variant:Nn \foo_internal:n {V}
>> I thought O was the appropriate variant for expanding a token list
>> control sequence?
> 
> The re-factor saw us drop "O", and sort-of downgrade "o" (we use it
> less). The V specifier lets you write both
> 
> \foo_internal:V \l_my_tl  % A macro at the TeX level
> 
> and
> 
> \foo_internal:V \l_my_toks % A toks at the TeX level

(o.0)

Does it inspect the argument at runtime to figure out which of the two 
cases is at hand? Looks rather fragile & syntactic sugar to me.

> whereas \foo_internal:o would need
> 
> \foo_internal:o {\l_my_tl}
> \foo_internal:o { \toks_use:N \l_my_toks }

I think I would rather prefer that, myself!

> So V is preferred for accessing variables (as the internal structure is
> not important), 

Wouldn't you still need to know the variable's "internal structure" 
when setting it?

Lars Hellström

ATOM RSS1 RSS2