Re: [PEPr] Call for votes on RFC::Requiring E_STRICT Compatibilityfor New PEAR Packages
| From: | Alexey Borzov | Date: | Wed, 06 Sep 2006 16:49:39 +0000 |
| Subject: | Re: [PEPr] Call for votes on RFC::Requiring E_STRICT Compatibilityfor New PEAR Packages | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43898@lists.php.net to get a copy of this message | ||
Hi,
Scott Mattocks wrote:
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.Well, after this RFC is accepted (and it looks like it *is* going to be accepted) you have time until January 1, 2007 to write another RFC which will prevent problems with new GTK packages.