References: <559AE0A8.3080907@morningstar2.co.uk> <55A3E1DD.8050707@posteo.net>
            <55A3E5E6.2060405@morningstar2.co.uk> <55A4137A.7030807@posteo.net>
            <55A415FF.8030305@nag.co.uk> <55A801A8.5090702@posteo.net>
            <55A809C4.70009@nag.co.uk> <55AA1554.3050509@posteo.net>
            <55AA24D9.1050904@latex-project.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <55AA29B9.9050104@posteo.net>
Date:         Sat, 18 Jul 2015 12:26:01 +0200
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: Stephan Hennig <sh-list@POSTEO.NET>
Subject: Re: LuaTeX support in the LaTeX kernel
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <55AA24D9.1050904@latex-project.org>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Am 18.07.2015 um 12:05 schrieb Frank Mittelbach:
> Am 18.07.2015 um 10:59 schrieb Stephan Hennig:
> 
>> and b) means that new features related to resource allocation will be
>> released in sync with new LaTeX versions only (as resource allocation is
>> completely implemented as part of the format).
> 
> 
> right (at least for the broader mass) which is  imho a good thing. 
> Perhaps so much if LaTeX releases are only happening only every couple 
> of years, but then we are currently in the process of setting things up 
> so that this can (and will) happen more often again.
> 
> on the other hand once the base allocations are all provided that is not 
> likely to be an area of much mods - and cutting edge/experimental stuff 
> you can still do on a package level if really necessary

I think you're not taking into account the needs of Lua package authors.
 While a Lua package depends on the LuaTeX engine, it is otherwise
naturally format independent.  Say I write a pure Lua package replacing
all A glyphs by Z in whatever callback.  How do I hook into that
callback in a format independent way?  A luatexbase package that
abstracts from minimal format implementations (as far as such are needed
in a format) would solve that issue.

Best regards,
Stephan Hennig