hi,
is there any way we could avoid this?
i think we should aim for keeping binary compatiblity as long
as it makes sense. so, question is, would it make sense to
have a function called php_fopen_wrapper in HEAD that behaves
_exactly_ like it did in 4.2. elsewise we need to bump the
API number - whereby that wouldn't buy us anything real as
a 4.2 (binary) module woundn't even load up to that point
where PHP could give a decent error-message as the
shared-linker refuses to load it (atleast if the module uses
php_fopen_wrapper).
thoughts?
tc
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
