LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Classic View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Mon, 18 Oct 2021 14:04:20 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=utf-8; format=flowed
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (26 lines)
Hello Thierry

>  From an engineering point of view, couldn't the code set everything with
> some:
> 
> \ifx\engineversion\undefined
> \else
>    \input engine.tex
> \fi
> 
> ? So that it's easier to see what depends on the engine and in order
> for modifications to the engine to be severed from the rest of the code?

Very little of the code is engine-specific, and the parts that are are 
largely in separate files as you suggest. Broadly

- l3names needs to save primitives in a predictable way, so checks for
   example for pdfTeX and LuaTeX names for the same concepts
- l3sys sets up engine-specific paths
- l3backend is split by backend: you likely are using dvips so
   l3backend-dvips.def needs to be loaded

I see Phelype has addressed the other parts.

Joseph

ATOM RSS1 RSS2