Re: Re[4]: [PHP-PEAR] Re: [phplib] Re: [PHP-PEAR] PHPLib and Pear merge

--- Stig Sæther Bakken <[email protected]> wrote:
[...snip...]
> A C rewrite would at least do
> away with the
> compilation overhead, and add some execution speed. 
> There are other
> goodies that are only available in C too, such as
> object overloading.
> I've started converting the PEAR base class to C
> while figuring out
> the ins and outs of the Zend class API.

That sounds very interesting. One thing that would be
also good to have is method overloading, but not
critical because we can always fake it in PHP.

And while we are at it, do you know what would be
needed to implement desctructors in objects? If we are
going to have objects with a life longer than the ones
we have now, I think we will need destructors, as well
as some type of object garbage collection or memory
leak protection.

BTW, I had not had much experience w/ the Zend API, so
some of this might already be there.

> But I agree that an application server is needed. 
> All that is really
> necessary to make it happen is a SAPI implementation
> (similar to
> sapi/servlet).  With a few tweaks in the PHP build
> system we could
> even put SAPI implementations in PEAR.

We could already use the servlet extension, and make
servlet server based PEAR app server. If not for final
deployment, for testing of code and/or the app server
mechanisms that will need to be implemented in/by
PEAR.

Just played w/ the servlet bit some time ago, when it
was still not too stable, but the idea of having a
script running as a servlet is appealing. The JVM
takes care of gc, and you could use some remote
debugging if needed.

Just my 2 cents



=====
--- Jesus M. Castagnetto ([email protected])

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/