User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0)
            Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
References: <4FCE2B42.2090006@morningstar2.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4FCF90E2.8090607@morningstar2.co.uk>
Date:         Wed, 6 Jun 2012 18:18:26 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Separating out 'public' and 'internal' functions/variables in LaTeX3 modules
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <4FCE2B42.2090006@morningstar2.co.uk>
Precedence: list
Status: R

Hello all,

A few points to be clarified came up via the TeX StackExchange chat
system [http://chat.stackexchange.com/transcript/message/4850082#4850082]

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