At 10:37 AM 1/4/2002 +0100, Markus Fischer wrote:
>On Fri, Jan 04, 2002 at 09:24:33AM +0000, Phil Driscoll wrote :
> > On Thursday 03 January 2002 11:08 pm, Zak Greant wrote:
> > > > > Why?
> > > >
> > > > Because not everyone wants to use *(#$&ing objects in a simple script!
> > >
> > >   No one will be forced to use the wrapper! :)
> >
> > Whilst this is true, and I know that you are thoughtful and conciencious
> > enough to make sure that any new stuff available via OO would also be
> > available via a procedural interface, I fear that this might be the 
> start of
> > a trend which would spoil PHP.
> >
> > If you are a web applications developer, there are plenty of mainstream
> > options if you like OO. There are fewer if you prefer procedural code, and
> > PHP is certainly the natural home for those of us in the latter camp. The
> > further PHP moves into the OO camp, the less appealing it becomes for the
> > procedural people. Once we have an OO interface to such a mainstream
> > extension as mysql (probably *the* most important php extension?), it 
> sends
> > an important message to users and developers alike.
>
>     Maybe you missed that ZE2 new major strength will better OOP
>     support. So its a good idea to start getting users used to it
>     because that is were ZE2 (namespaces, etc) will lead us to.

I don't quite agree. I see PHP's future as a hybrid language which allows 
most developers to feel comfortable and allows them to use the programming 
paradigm of their choice. The ease of use which often is very much linked 
to the functional interfaces is one of the reasons for PHP's success.
Although I think it is important to improve the OOP support I am still very 
much for keeping our functional support as strong as it has been up to 
today. We are still keeping the OOP support in the Zend Engine 2 at a level 
which is good for decent OOP developers but aren't going bezerq like OOP 
fanatics would like us to go :)

Andi


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to