On Fri, Jul 28, 2023 at 03:14:31PM +0100, David Carlisle wrote:
> On 28/07/2023 15:03, LARONDE Thierry wrote:
> > On Fri, Jul 28, 2023 at 12:57:44PM +0100, Joseph Wright wrote:
> > > On 28/07/2023 12:28, LARONDE Thierry wrote:
> > > > Hello,
> > > > 
> > > > Apparently, somewhere between 2022 and 2023, you have changed the way
> > > > the LaTeX \input macro, replacing the primitive, is behaving regarding
> > > > the extension when brackets are used.
> > > > 
> > To be more specific, somewhere between 2022-11-01 and today (CTAN
> > 2023-06-30).
> > 
> > As a remainder: I'm the developer of kerTeX (a distribution) and of
> > Prote (a change file to add LaTeX needed primitives to TeX + e-TeX). So
> > the glue code is the kerTeX one; and the engine is the Prote one.
> > 
> > So there is a stack of things:
> > 
> > 1) Glue added by the distribution (TeXLive doesn't implement the same
> > thing as kerTeX);
> > 
> > 2) The engine: here it is Prote;
> > 
> > 3) LaTeX (and different behavior with different versions).
> > 
> > 
> > When dumping the LaTeX macro package (today's version on CTAN), LaTeX
> > running on the Prote engine, the \input is not the primitive but a
> > wrapper.
> 
> \input in latex has always been such a wrapper even back as far as the 1980s
> 
> 
> 
> > Now:
> > 
> > ---8<---
> > $ echo '\input{docstrip}' | latex
> > 
> > This is Prote, Version kerTeX C 3.141592653-2.6-1.0.0
> > entering extended mode
> > entering prote mode
> > LaTeX2e <2023-06-01> patch level 1
> > L3 programming layer <2023-06-30>
> > 
> > *
> > ! LaTeX Error: File `docstrip.tex' not found.
> 
> 
> That would seem to be an engine feature, not a latex issue. The expected
> behaviour is

Yes. But the same engine does things differently between LaTeX
2022-11-01 and LaTeX 2023-06-01.

So could someone give me the diff of the input related things in
LaTeX between these two versions so that I can have a clue about
what LaTeX is expecting and what it is eventually calling (because it
could be calling, low level, the open routine, and there is no
acrobatics made in the open routine in kerTeX: the handling is made
before calling the routine; so if LaTeX is calling low level like
this, the result is not a surprise).
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C