Thanks, will fix.
- put every exception in it's own file
Sure, I could do this. Is this the general consensus? I thought
exceptions were the exception to the rule of class <-> file, but I
certainly see the pros and cons here.
Yes, I thought the exception RFC had talked about that. Making a one line definition in one file is getting really silly..
class MyPackage_Exception_xxxxxx extends PEAR_Exception {}
The rules are there to make code readable / document-able.
At present, a few of them are getting in the way of it by the look of things.
BTW - yes, I think the @licences/@.... docs infront of each Exception definition is applying rules for rules sake, rather than considering if there is a reason for it..
This is always the Catch-22 with our rules - People treat them like law's rather than guidelines, to be applied with some common sense.. (hint - phc!?!?)
Regards
Alan
-Philippe