Marcus Boerger wrote:
Hello Jochem,
hi Marcus,
thanks for your response (It remains a bit of a honour when
someone from the dev ranks takes time to give feedback -
new insight often follows as secondary benefit).
Tuesday, April 25, 2006, 3:15:52 PM, you wrote:
Petar Nedyalkov wrote:
On Tuesday 25 April 2006 14:30, Edin Kadribasic wrote:
...
Do not mix class based OO like PHP and prototype based OO like JavaScript.
agreed - my point was more that to speak of 'the OO paradigm' might be
considered
rather useless considering the disparity of paradigms that exist in the myriad
of 'OO' languages out there (I named scripting languages because thats all I
really know :-)
(anyone with the argument that PHP!=Ruby or PHP!=Javascript might consider that
PHP!="the OO paradigm")
PHP simply supports its own set and view of OO.
indeed, which is more than fair, but I doubt you would deny that the 'set/view'
you speak of is set in stone - then goals post do move now and again because of
new developer wishes and/or insights into usage in the real world.
...
Was this not possible because of the engine implementation of the static
properties?
It is just some decision that was taken that the newer OO stuff should be a
bit more strict.
'a bit'? ;-) that said your answer is honest and to the point and makes the
position of the devs clear - which is a good thing - knowing exactly what kind
of
dogfood is on offer allows for informed decision by the user.
I realise that it must be difficult to strike a balance between those that
strive to drive the language to ever greater heights of
<buzzword>enterprise-readiness</buzzword>
and the lower echalons that protest/struggle against/with the increasing
strictness of the language. (personally I find myself in between ... and
sometimes
finding it hard to keep my existing code compliant :-)
Best regards,
Marcus
many thanks for your clarification.
rgds,
Jochem
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
