Vít Starý Novotný submitted an update to the

              expltools

package.

Version: 2026-03-30
License: lppl1.3c gpl2+

Summary description: Development tools for expl3 programmers

Announcement text:
----------------------------------------------------------------------

## expltools 2026-03-30

### explcheck v0.19.0

#### New features

This version of explcheck has implemented the following new features:

- Add more support for flow analysis. (#188)

This adds support for the following issues from Section 5.1 of the document
titled [_Warnings and errors for the expl3 analysis tool_][warnings-and-errors]:

 1. E500 (Multiply defined function)
 2. W501 (Multiply defined function variant)
 3. E504 (Function variant for an undefined function)
 4. E506 (Indirect function definition from an undefined function)
 5. W507 (Setting a function before definition)

[warnings-and-errors]: 
https://github.com/witiko/expltools/releases/download/latest/warnings-and-errors.pdf

#### Continuous integration

This version of explcheck has made the following changes to our continuous
integration:

- Update regression baselines from TeX Live 2024 to 2025. (f57c0080..e0ce50c4)
- Test TeX Live 2026. (c578802e)
- Disable caching in the `zauguin/install-texlive` action.
(added by @zauguin in zauguin/install-texlive#128 and 611fde4)

----------------------------------------------------------------------

The package’s Catalogue entry can be viewed at
  https://ctan.org/pkg/expltools

The package’s files themselves can be inspected at
  https://mirrors.ctan.org/support/expltools/

----------------------------------------------------------------------

Thanks for the upload.

For the CTAN Team
Vincent Goulet

----------------------------------------------------------------------

CTAN is run entirely by volunteers and supported by TeX user groups.
Please join a user group or donate to one, see https://ctan.org/lugs
_______________________________________________
ctan-ann mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to