Re: Subject/Observer design pattern in PEAR

Jon Parise wrote: >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. This looks like a good idea. +1 Bertrand Mansion Mamasam