RE: [PEAR-DEV] design of forum applications

From: Date: Thu, 15 May 2003 22:18:25 +0000
Subject: RE: [PEAR-DEV] design of forum applications
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-16331@lists.php.net to get a copy of this message
> From: Ilia A. [mailto:ilia@prohost.org] > Sent: Thursday, May 15, 2003 7:22 PM > Bytecode compilers do help, because PEAR classes for the most part tend to > be > rather big monsters (100k Common.php in MDB). However, the code itself > still > needs to be executed and if it is inefficient all the opcode caches & > bytecode compilers in the world won't help you. Just as an FYI: I will try to clean up the API of MDB. There are several reasons why its so large (however its not considerably slower than PEAR DB .. but I guess that is a matter of benchmarking tricks). 1. MDB has almost the entire PEAR DB and Metabase API because nobody was interested in helping me make these choices and I was too worried that cutting out methods would result in people not bothering with a port. So there is a lot of redundant methods in MDB and methods that simply don't make sense to use (for example cell based fetching). 2. All of the rarely used management methods (like createDatabase, alterTable etc.) are in MDB. Actually the implementation is in another class but you call them through the MDB object. 3. Since I didn't have (and still don't have complete) documentation the PHPDoc comments are rather elaborate compared to most other packages. So anyways the good news is that soon I will cut down the API. The bad news is that this will obviously break BC. I hope to also find the time to update the wrappers.

« previous php.pear.dev (#16331) next »