User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0)
            Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <53248902.4050200@morningstar2.co.uk>
Date:         Sat, 15 Mar 2014 17:08:18 +0000
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: Documenting 'locally added' expl3 variants
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Hello all,

I'm currently making a start on v3 of siunitx, and am trying to tighten
up the 'expl3 purity' of the code. One area I'm keen to sort out is a
proper set of documented commands at the code level so people can
exploit parts of siunitx without being tied to the interface layer I
provide.

Working systematically, I notice that I use a few variants of core expl3
commands that have to be created. Based on the 'document everything
public' principle, these should be mentioned (they have 'public'
function names). On the other hand, they are 'nothing to do with me' as
all I'm doing is something like

  \cs_generate_variant:Nn \some_team_function:n { V }

(OK, as I'm on the team they are actually something to do with me, but
hopefully my point is clear!)

How do other people see this?
__
Joseph Wright