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:
Fri, 12 Feb 2010 09:26:03 +0100
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID:
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=us-ascii
From:
Frank Mittelbach <[log in to unmask]>
Parts/Attachments:
text/plain (19 lines)
Joseph Wright writes:
 > >> A quick search shows they are used in the tl module. I'd stick to defining "private" scratch variables.
 > >
 > > Should we change this?
 > > I.e., use \l_kernel_tmpa_tl or \l_reserveda_tl instead for us and let package writers use \l_tmpa_tl ?
 > >
 > > -- Will
 > >
 > I think we probably should: the documentation seems to imply that they 
 > are available, and it would be best if there was clear demarcation.

yes, keep private kernel scratch registers only used in controlled situations
and documented as not being available for programming - just like we did with
\reserved@a etc in 2e

\l_kernel_tmpa_tl sounds  fine enough for those

frank

ATOM RSS1 RSS2