Christoph M. Becker
Christoph M. Becker
Is that still an issue?
This is a somewhat philosophical question: if `exit` does not stop program execution, is the `never` return type actually appropriate?
I understand what this ticket is about, but I'm still not sure if we should try to "fix" the issue, for the following reasons: * disabling `ZEND_EXIT` might not be...
Do you have configured `uopz.exit=1`? Also note that as of uopz 7.0.0, PHP 7 is no longer supported.
> 1. Found [[a post](https://github.com/krakjoe/uopz/issues/63)]([opcache do not update class constant after uopz_redefine #63](https://github.com/krakjoe/uopz/issues/63)) about “loading uopz before opcache per docs” but don’t see direction on how that should be done...
Is this still an issue with uopz 7.1.1? Note that at this point it wouldn't make sense to even attempt to fix uopz 6 (i.e. for support for PHP prior...
Closing and re-opening to (hopefully) trigger the CI workflow.
@remicollet, is this still unresolved, or maybe was it just an optimization glitch that had been fixed in the meantime?
> Other functions such as `uopz_unset_return()` appear to be affected by this issue, too. No, this function is not affected by this issue, and apparently no other function.
Is this still unresolved? Maybe there have been new builds done in the meantime.