Re: Lancaster Consensus, deal with PUREPERL_ONLY=0
[email protected] (David Golden)
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <CAOeq1c_GufRPRP-ZZYHoZwn_=sdcd8s=NNc=5XcJx-y=A1nHdA@mail.gmail.com> |
On Mon, Jun 2, 2014 at 7:28 PM, Aristotle Pagaltzis <[email protected]> wrote: > If I have my system set up to support XS then I want it to use XS, and > if for some reason it can’t, then there is a bug somewhere that needs to > be fixed, so I do *not* want it to silently give me the PP version and > carry on, but to fall down and die screaming so I’ll find out. I've been trying to think of how that could happen and so far all I can come up with is this scenario: * XS bits compile successfully, but the shared object croaks during bootstrap, and the calling module traps the bootstrap error and falls back to PP David