LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Wed, 6 Jun 2012 18:18:26 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (19 lines)
Hello all,

A few points to be clarified came up via the TeX StackExchange chat
system []

Taking the example of the l3prop module \prop_put:nn is a function of
the prop module that can be used by other modules. In other words it is
a public interface. On the other hand \prop_put_aux:NNnn, called by
\prop_put:nn and others, is an internal function, and so would be
renamed as \__prop_put_aux:NNnn or possibly \__prop_put:NNnn (as the
_aux is not directly needed here).

As such, 'well behaved' LaTeX3 module will still have access to exactly
the same functions from the kernel as they do now, and via the same
names. It is only functions which are 'private' to a single module which
would be changed.
Joseph Wright