Re: [PEPr] Call for votes on RFC::Requiring E_STRICT Compatibilityfor New PEAR Packages

From: Date: Wed, 06 Sep 2006 16:41:27 +0000
Subject: Re: [PEPr] Call for votes on RFC::Requiring E_STRICT Compatibilityfor New PEAR Packages
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-43897@lists.php.net to get a copy of this message
Lukas Kahwe Smith wrote:
Well in theory the base classes should be properly designed to preclude this. Also there is the option of simply using new method names. But I do agree that this can require a lot of planning and if the original class you are extending is in C, it becomes a lot harder to fix the issue at the source.
I agree, if base code is PHP there is no excuse. My concern is that as the RFC is written, it basically means that there can be no more new PHP-GTK 2 packages until Gtk+2.0 is changed, which is not likely. I think the RFC should apply only to E_STRICT errors generated because of PHP code and not some underlying library. Anyway, I know the time for debate has passed. I just wanted to bring this issue to light. Thanks, Scott

« previous php.pear.dev (#43897) next »