2015-02-10 14:56 GMT+03:00 Patrick Schaaf <b...@bof.de>: > Ahem. Any open ended API-for-frameworks will A) force me to pick a > framework and bend to the way it wants these things to look, and B) result > in fragmentation and incompatibilities for any two pieces of code/library > developed with different such frameworks in mind. That will be a total mess.
It's another task for another people, typically for standartization group, like PSR, JSR, PEP, etc. Framework developers should rely on interfaces and should provide interfaces. For Java world this works (some ideas here http://java.dzone.com/articles/jsr-305-and-design-contract) If put all the things into the PHP core, it will become much bigger, more slower and hard to maintain. Later posts describes EOL for some extensions and SAPIs, but this place will not be clean, because another custom feature XXX is landed on free space. I would like to see a language with good extension API. For now, it's almost impossible to extend a parser, even from extension level (however, PHP7 will have a hook for that, thanks God).
