Jay Rossiter / Signe wrote:
>> So again I say: let's do OO, but let's avoid using PHP classes. I
>> present Drupal's document as a good argument in favor of this. Please
>> present a factual counter-argument in real world terms.
>>
>
> Never do anything in PHP that you can do in C (i.e. internals code,
> not user-land code). The Drupal method is re-implementing language
> concepts at the application layer. It's slow. It requires constant
> validation of whether functions exist, and then calling them from
> user-space with things like call_user_func, or variable-functions.
> Neither of which are pretty to debug or design.
I pretty much debate all of that. Drupal's approach is eminently
practical, and while it's imperfect, you may have noticed that I am not
aiming at the paramount ideal of beautiful CS code. I'm looking to make
something small, practical and really really fast. Last time I profiled
Drupal's approach it was 2x faster than the OO version (this was on
PHP4). I found it very easy to write and debug the Drupal modules I've
written. I'll re-run my benchmarks with PHP 5.x.
-Bharat
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive -->
http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download -->
http://gallery.sf.net ]
