Yeah.. we already ran into it when writing tests, because FilterChain is defined by both phing and Agavi ;) Definitely a big +1 for renaming our base objects... I guess someone should compile a list on the wiki? ;) --Bob
On 7/1/05, David Zülke <[EMAIL PROTECTED]> wrote: > > I'll rename it AgaviMessage (avoid stepping on toes) > > Hmm right; however, that would break with the existing naming "conventions" > we have right now. Except of AgaviObject, all classes don't carry "Agavi" in > their names. Maybe we should change that; it would lead to way less naming > conflicts anyway (think of class "User" for example). > > - David > > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
