Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28429
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender)
Message-ID: <45FEBD70.2090000@zend.com>
Date: Mon, 19 Mar 2007 09:42:24 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: =?UTF-8?B?QmFua8OzIMOBZMOhbQ==?= <thefirstofall@gmail.com>
CC:  internals@lists.php.net, Lukas Kahwe Smith <mls@pooteeweet.org>
References: <1174134488.8667.33.camel@lena>	 <45FC74A5.6080307@pooteeweet.org> <1174231834.12274.110.camel@lena>
In-Reply-To: <1174231834.12274.110.camel@lena>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] google SoC - dbobj
From: stas@zend.com (Stanislav Malyshev)

> Pure C code has access to PHP5's low level object API, so it can produce
> a really intuitive interface (object persistence), that you can't do
> from PHP code. C code uses a bit less memory and a lot less CPU time

Just curious - which access do you need that PHP API doesn't give?

> And one more point. In C you can implement complex object oriented
> structures (lot of classes with fancy virtual functions) with small

What do you mean by virtual functions? If you mean C++ meaning, all 
class methods in PHP are "virtual".

> overhead, while in PHP this structure could mean a lot of overhead. For
> example separate class for every column type, and separate object for
> every persistent value is unimaginable in PHP, but sounds OK in C. This

Why would it be that different in C - you'd still have to define the 
same classes and same objects and play by the engine rules?
-- 
Stanislav Malyshev, Zend Products Engineer
stas@zend.com  http://www.zend.com/