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

Scott Mattocks wrote:

I know it is late but I didn't put things together until just now. Anyway, there needs to be an exception clause for Gtk2 packages and other C library wrapper extension packages. Gtk+2 has classes that extend one another and overwrite methods with different signatures. This causes PHP 5 to throw an E_STRICT warning when the class is used. There is nothing that a developer can do about this and it should not prevent a package from being accepted. Of course the PHP-GTK team is working on a solution to this problem, but this is not a PHP-GTK only issue. Any PHP warapper around a C library could potentially have the same problem.

Isnt this even fatal in PHP 5.2? Anyways why do C wrappers need to rewrite signatures? regards, Lukas