Hi! > I explained that in another mail and will put it (amongst a lot of other > things that came up during this thread) into the RFC:
This is not enough. Saying "ZE APIs suck, so I implemented a bunch of my own and want to merge it in core because I like them" is not enough to make an informed decision - why ZE APIs suck? Can we fix them without introducing a bunch of new APIs? Are new APIs good for common case beyond this particular extension? It is not really feasible for each extension to use it's own API to deal with resources or objects. So if we introduce a new one, we should have clear understanding that a) existing ones are not enough and b) new one would serve more than narrow need of one case. > I'm a bad sales person, but I'll try better. The community needs to take an informed decision. For that, we need the information. You are the one who has the information, so please share it! It is obvious you think that what you did is good - otherwise you wouldn't propose it, and you probably know why exactly it is good - so please tell us so we'd know too. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
