LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 24 Dec 2018 11:45:10 +0100
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID:
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=utf-8; format=flowed
From:
Frank Mittelbach <[log in to unmask]>
Parts/Attachments:
text/plain (21 lines)
Am 24.12.2018 um 10:22 schrieb Joseph Wright:
> 
> Bear in mind that the code here is often optimised or is set up for 
> bootstrapping, particularly if you look at the early stuff.

which is really another way of saying that the core kernel code is 
something that is not meant to (and in fact in many cases to able to) 
show expl3 coding conventions.
For example, \exp_after:wN is something that in package code should be 
rarely if ever needed (and if you are using it then it usually means 
that you are thinking too much in the TeX model of expansion). However, 
while providing the core expl3 functionality it is obviously needed and 
so you will see that a lot in kernel code.

Better places for understanding expl3 convention would therefore be 
packages such as siunitx etc or many of the answers given by @egreg on 
Stack Exchange.

Seasonal greetings
frank

ATOM RSS1 RSS2