Re: Release-status of dependent packages (special: with PEAR_ErrorStack)

Stefan Neufeind wrote:

Hi, Greg recently mentioned several times that he rates PEAR_ErrorStack still alpha-quality, until it has run through more extensive testing. And it's also been mentioned that there should not be any stable packages that depend on non-stable packages. So am I right that it should be noted on pear-dev that devs must not release stable packages that use PEAR_ErrorStack, for the moment? How about beta-packages that rely on alpha-code? Stefan

Any package that simply *uses* PEAR_ErrorStack can be released as beta. Any package the *extends* PEAR_ErrorStack (exposes the API directly) must remain alpha quality. No stable package may be released yet that depends on PEAR_ErrorStack - sorry folks :). Don't worry, PEAR_ErrorStack will reach stability pretty quickly. I've been trying to use it myself, and discovered that it is often desirable to emulate the error_reporting() constant of PHP, and so implemented a way to retrieve all errors of a certain severity, or a range of severities. $stack->getErrors(false, 'error') will return all errors of severity "error" and leave them untouched on the stack. $stack->getErrors(true, array('error', 'warning', 'exception')) will return all errors of the listed severities, and remove them from the stack, but will not touch, for instance, any notices. More importantly, $stack->hasErrors('error') or $stack->hasErrors(array('error', 'exception')) is now possible. There is one open bug regarding default callbacks, that I need to fix, and then it will be ready for use. I imagine we can release PEAR 1.3.2 (Pierre is in charge of this) with bugfixes and the updated PEAR_ErrorStack around the time of PHP 4.3.7 Greg