Compiled pear classes.

Its obvious to anyone that pear is a compromise between speed /
performance and ease / usability / scalability. This is to make our
lives easier we're willing to take some performance hit on our product.
Some scripting languages use byte compiled code, which is again I
believe a compromise while gives the better performance than the
original it's still not fast enough as the compiled code. I even think I
sow something like that available from zend somewhere, I could be wrong
though.

Now if pear could be converted into a php extension that would be a
great performance boost right. Of course I'm not suggesting that people
would sit back and just rewrite each class as an extension. that would
be clearly unacceptable but how about making a parser which would create
the c source for a php extension. this might seem a bit hard to do, with
source code being as messy as it is but pear already has some coding
guidelines set which would make things much easier. Another great
advantage is that pear already uses a parsing engine of some sort for
it's documentation, phpDoc. If this idea becomes accepted it would be as
easy as extending phpDoc to out put c code instead of html/xml. 

good idea why don't do it then? well unfortunately my c coding skills
are not nearly as good as I would like them to be. phpDoc is written in
php but in order for the proper code to be outputted you would have to
know what the c syntax would be, plus you would need some good knowledge
of the gnu build tools (make flex bison etc) and the scope of this is
clearly out of my reach I however willing to participate in this project
all the way.

so what do you think is this idea feasible or I'm I just day dreaming


The difference between a good man and a bad one is the choice of cause -
William James