References: <559AE0A8.3080907@morningstar2.co.uk>
            <559B6B5C.4080603@telecom-bretagne.eu> <559B969E.4020202@nag.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.0.1
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Message-ID:  <559B9E6B.8080109@morningstar2.co.uk>
Date:         Tue, 7 Jul 2015 10:39:55 +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: LuaTeX support in the LaTeX kernel
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <559B969E.4020202@nag.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 07/07/2015 10:06, David Carlisle wrote:
>>> We are looking for feedback in two areas. Firstly, does the
>>> functionality provided cover the needs of package authors using LuaTeX?
>>
>> The whatsit allocation is still missing, maybe it could be added to
>> lualatexsupport?
> 
> One thing to discuss: it could be added to lualatexsupport (a package)
> or ltluatex (planned to be in the format) and could be handled
> as a normal tex register allocation (with \count26x holding the unique
> id) or handled purely in lua.  Does anyone have any examples of these
> things in use??? Some real use cases would be good to check any design
> decisions here.

Indeed, this bit is missing mainly as I've yet to read the existing code
in detail and work out what exactly we should provide. For example,
David suggested to me that the allocation number might need to be
accessible from TeX (or that at least this was desirable), so using a
\count26x value rather than Lua variable would be best. But without any
use cases I'm not at all sure.
--
Joseph Wright