Re: Function caching...

I think we've been through this before - what you describe is simply not PHP. It's changing the whole approach PHP is based on. In your opinion it is wrong, in mine it isn't, and I believe that most people will disagree with you once they understood what you're talking about. A long lasting, multithreaded server running a set of precompiled scripts is a great idea, but it has nothing to do with PHP. Worse, it doesn't cut it for most people, because you have to start worrying much more about all sorts of things you don't have to worry about when you program in PHP. In my opinion, what you want is exactly what made mod_perl fail in comparison with PHP's success. The kind of ideas that are interesting for me to implement are those that will transparently improve performance - not by changing the rules of the game. The Zend Cache does this very nicely, as it allows you to go on using PHP just as you did before, and speeds things up. I completely disagree that the current implementation is a result of bad design. If I were to rethink about the way to implement PHP today, I'd do it in a very similar way to the way it's implemented today. Sure, there are things I would have changed (most notably, either nuking the OO subsystem completely, or creating a more robust one). As a concept, though, PHP has proved that it's done the right thing beyond a reasonable doubt. I'm not saying that your ideas are bad. They just have very little to do with PHP, and most of the advantages PHP has will be lost in such a setup (ease of use, mainly). Remember, the primary concern for PHP is usability and ease of use, and performance does come in second. It's very easy and much cheaper to add more hardware, than to hire&train more people, and have longer development times. In my opinion, the day performance becomes more important than ease of use, would be the starting day of PHP's downfall. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/