On 20/10/06, Edin Kadribasic <[EMAIL PROTECTED]> wrote:
Lukas Kahwe Smith wrote:
> Ilia Alshanetsky wrote:
>
>> It is working code, its far from perfect given that it makes little
>> programatic sense and does break all known OO conventions.
>
> Being allowed to break these "known OO conventions" is a major
> feature, which has established PHP as a rapid prototyping language.
> Having some tool to tell users that they are breaking these
> conventions is a good idea however.
>
Let me translate it to you Lukas:
"Known OO conventions" -> how Java people do it
"Its supposed to work that way" -> it works like that in Java
Those coming to PHP from say Java / Delphi / C++ (I only know about
Delphi), would expect PHP to operate in similar ways in terms of the
structure and definition of objects. Sure the syntax is different but
it can do it in Java/Delphi/C++, why not in PHP. And if not in JDC
then why in PHP?
With respect to abstract static method, it DOESN'T make sense as I
know that an abstract method cannot be called directly as it has to be
defined in a subclass. So the static keyword and the function itself
are redundant. I think being reported as E_STRICT is fine. It helps
you fix your code!
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
