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
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.