RE: [PEAR] I can't believe it...

I as well joined this list to keep up-to-date with the latest info on the PEAR classes, but I think that there's a few key points that need to be made. First off, there are many different meanings to the phrase "coding style". There is the way taht you lay out your code, and the way taht you write the code. An example of the difference in how you write your code is the difference between using a foreach() statement or a while(list()=each()) statement to go through an array. An example of the difference in how you lay out your code is the difference between using spaces and using tabs. Another thing that I would like to point out is that with PEAR, speed is an important thing. Just by using PEAR::DB, you end up include()-ing ~70 kb of files. Using more classes means more include()-ing. That can become hefty, if your site or application that uses PEAR classes has a lot of traffic. I myself am a proponent of tabs, for this reason -- it is less code to parse. If you use 8 spaces instead of one tab, it is seven more characters to include(), and also seven more characters for the PHP parser to parse. Hence, slower code. Besides the fact that editing code written with tabs is also easier and a faster development process. --Jason