Re: Re: cvs: php4 /pear DB.php /pear/DB common.phperror.phpmysql.php result.php warning.php

Quoting Sebastian Bergmann <sb@sebastian-bergmann.de>: > Namely the splitting of DB.php (there where other classes than DB defined > in that file) into one file per class. Why? Given that you then simply require_once() each of those files at the top of DB.php, all you're doing is requiring an additional 4 filesystem accesses every time you load DB.php. All of those classes are used together and tightly conceptually related; is there any particular reason to split them out, given that we have no _requirement_ of sticking to one class per file? Also, why are all of the DB files now indented 2 spaces from the margin? -chuck -- Charles Hagenbuch, <chuck@horde.org> "If you can't stand the heat, get out of the chicken!" - Baby Blues