Re: XS module not loaded and erroring out in the default case

On Fri, Mar 06, 2026 at 10:00:44PM +0000, Gavin Smith wrote:
> Would it be right to describe your recommendation as splitting the
> XS modules into two groups, "core" modules which would be loaded with
> with requiredifenabled, and other modules where fall-back to pure Perl
> doesn't cause any other modules to fail?

An additional change I propose is that in the default case, even for the
modules where fall-back to pure Perl doesn't cause failures, the default
case should be the same as setting requiredifenabled, ie texi2any
would die.  Another possibility should be available, maybe
TEXINFO_XS=permissive, TEXINFO_XS=fallback or something like that, and
if set, the modules where fall-back to pure Perl doesn't cause failures
would fall-back silently.

-- 
Pat