LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version: 1.0 (Apple Message framework v928.1)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Date: Wed, 10 Sep 2008 00:35:41 +0930
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Will Robertson <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments: text/plain (34 lines)
On 10/09/2008, at 12:06 AM, Joseph Wright wrote:

> Hello,
>
> A "philosophy" question.  For storing values that will be used "as  
> is",
> normally one would do \def\storesomething{Something}.  In the LaTeX3
> model, I can choose either
>
> \def:NNn \store_something: 0 {Something}

or

\def:Npn \store_something: {Something}

(I prefer it without the "0" argument spec.)

> or
>
> \tlp_new:N \l_store_something_tlp
> \tlp_set:Nn \l_store_something_tlp {Something}
>
> and get the same result, function-wise.  Is the later closer to the
> model proposed, or should I stick with the former?

I think the philosophy is that \def:NNn and friends are designed to  
create "functions", whereas tlps and the like are designed to store  
"data".

So I'd choose the latter, but I'd be interested to hear the others'  
opinions.

Will

ATOM RSS1 RSS2