User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
References: <49A453A1.9040000@morningstar2.co.uk>           
            <FB18C832-EA5E-42F0-9BF7-6853DB79B805@gmail.com>           
            <49A4F031.50405@morningstar2.co.uk>           
            <49A4FE4F.6040304@morningstar2.co.uk>           
            <27990a880902250600v21963220v319195a504107625@mail.gmail.com>
            <18853.41758.364009.703166@morse.mittelbach-online.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <49A5A982.9050508@morningstar2.co.uk>
Date:         Wed, 25 Feb 2009 20:26:42 +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: Re: Missing expl3 primitives
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <18853.41758.364009.703166@morse.mittelbach-online.de>
Precedence: list
Status: R

Frank Mittelbach wrote:
> I really expect all (or nearly all) of them to used in higher-level
> interfaces, each in one specific module and that the low-level functionality
> outside these interfaces should not be accessed at all.
> This is precisely the issue that exists in LaTeX2e right now which has a very
> specific use for \everypar (but only a poorly developed inferface to access it
> by others. As a result packages mistakenly use \everpar directly only to find
> out that they die in certain situation or produce unexpected results.
> 
> So yes, we do want a functionality like \everypar available, but if LaTeX3
> implements a galley module (whether it be variant of galley2 or something
> leaner like xfmgalley or ...) then this functionality will not be provided
> through the primitive \everpar but through something else that fits that
> model.
> 
> Same essentially for every other \every... command: "every end of file" might
> be useful and should be provided, but probably not through the primitive as
> the l3file might as well have something to do at the end of every file first
> (hijacking that lowlevel and instead providing something else for other
> packages).
> 
> as i expect kernel (or near kernel) modules for all areas that offer
> \every... I would leave this alone as \tex_every_...:D for now
> 
> if it turns out that one or the other is not going to be hijacked by the
> kernel we can in the end still offer it as programmer available, but not
> before

One "philosophical" question: are the xpackages allowed to use :D
functions?  My (possibly faulty) understanding was that expl3 is the
language definition, and only the functions defined there are allowed
anywhere else in LaTeX3.  This implies to me that the xpackages can't
use :D functions, but that something in expl3 has to make the
functionality available.
--
Joseph Wright