Re: Some more plane hacking...

Nicolas Hoizey wrote: Please don't cut the other reasons :-) - The work needed to build a valid C extension in the terms of bug haunting, cross platform, PHP/Zend internals knowledge, speed of coding, etc is too big. - The number of contributors will be reduced draticaly. Don't know what's the general C knowledge here, but I know that mines for example is not valid for a seriuos work. - Moving PHP PEAR classes from one server to another is a trivial work, C classes shouldn't. - Most of PHP users haven't enought tools and knowledge to compile a external C extensions. > > > The only reason I see where a C extension makes sense is the speed, > > but the speed in the most of the php develpments isn't a real worry > > compared to maintainability or speed of development. If you want to > > write a C extension for a class put it in the class package space as > > another nice choice, but don't cut its usability to others. > > Speed is often a real issue for professional use of PHP, so having > some of the core components of PEAR available as extensions would be > great ! Let's define "professional". I have one server with 1,5 millon _hits_ a day with php, templates, postgres, and it's running fast and smooth. The amount of speed you can gain optimizing classes is nothing compared to optimizing queries, databse, SO, web server. If we are talking of > 50.000 visitors a day you're not talking in "general purpose" terms (isn't PEAR a "general purpose repository"?). > I think it could be possible to have both the C and the PHP versions > running together, the right choice being made "automagicaly", don't > you think ? :) > If so, yeah no problem and no more discuss :-). But I (and I'm sure many others) don't want to spend > 4 hours propagating changes of a C extension thru servers with differents operating systems/c libs, when I can do it in two minutes with .php's. This without think in the time lost doing the always needed small and quick changes to fit it in a yet built app. Just ask a question if you let me: the guys who are promoting C extension will join to pear and work in the this C extensions? will maintain them? will ensure cross-platform/cross-compiler ability? will attend bug reports? Tomas V.V.Cox