hello, you should create an account at http://framework.zend.com/issues and file issues against Zend_Db, put their alert level up based on what you think is necessary. Also make sure not to put all the things into one issue, but split them up so that they are unique items to be worked at.
greetings On Wed, 11 Feb 2009 08:58:56 -0800 (PST), william0275 <[email protected]> wrote: > > The more I look at the source code of some Zend Framework elements, the > more > I see bad OOP practices and worse... > > For example, Zend_Db_Statement and Zend_Db_Statement_Pdo are a > frankenstein > of OOP. There are methods accessed by the abstract, parent class that *are > not* defined in the parent and are expected to exist in the inherited > class. > These methods should be declared in the parent class as abstract methods > at > least... > > A second example, the use of a variable that has *the same* name as a > method > defined in the inherited class... some ugly 'overloading' right there > between an array and a method... > > I would like to alert the Zend Framework team about this but have > absolutely > no clue how. > -- > View this message in context: > http://www.nabble.com/How-to-contact-the-Zend-Framework-team-about-OOP-bad-practices-suggestions--tp21958265p21958265.html > Sent from the Zend Framework mailing list archive at Nabble.com.
