Re: Removal of "php_fopen_wrapper" in HEAD will break binary modules between 4.2 and HEAD (4.3)

Hi Thies, I did raise this issue a while back, but got no response (happens quite a lot on php-dev). I think bumping the API number would be the best course of action; a lot of things have changed (binary wise) as a result of streams, and I don't think it is possible to emulate the old things without a lot of mess - the whole point of streams was to eliminate the issock mess we had in the first place. --Wez. On 27/04/02, "Thies C. Arntzen" <thies@thiesos.org> wrote: > 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