I am trying to follow all the latest threads on various decorators, casting, contracts, iterators, interfaces and the rest but I have to be honest ... I simply don't understand the majority of what is being discussed. All right I don't have to use it, but on the whole I have no problem with any of the existing code. Except perhaps for zend, but that is mainly because I just don't work the way it is trying to force me. I can quite happily work on existing third party libraries, debug and fix problems, and move forward. But the examples being given simply don't fit with my view of how PHP works.

How much of this taint/reflection/... is actually going to be used by the majority of users? I keep seeing references to 'compile time' and thinking when on earth does compiling come into the equation? When I process a page request I load just the components needed to do the job, and if something is wrong I give an error page. A hell of a lot of the comments being made relate to the IDE and THAT is where the bulk of this checking should be provided, not loading down the runtime engine with checks that should have been done when writing the code?

I know I keep harping on about it, but it still seems to me that there is no cohesive basic framework defined for the core functionality needed to run simple php scripts? SOmething on to of which all the esoteric bits can be added and explained without having to dig through numerous RFC's and release notes to see what the current state of play is :(

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to