Re: Subject/Observer design pattern in PEAR

On Wed, Jul 21, 2004 at 06:50:11PM -0400, Hans Lellelid wrote: > I'm not really trying to convince anyone, as I think probably everyone > agrees at some level with this idea :) I guess the question is just how > to best propose or negotiate these interfaces. I imagine someone from > PEAR Group may have a suggestion ... Instead of enforcing this kind of thing at a coding standard -level, I'd suggest creating a new "Interfaces" category which includes a set of packages that do nothing other than define an interface for a specific pattern or use case. That way, the developer is free to use an existing "standard" interface or roll their own if they feel it's necessary. This also makes it easy to track dependencies and interface adoption. Granted, this really only makes sense for PHP5, but maybe this "standard" should only apply to PHP5 where interface actually make sense. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)