Re: [PEPr] +1 for PHP::PHP_ArrayOf

On Sat, Apr 26, 2008 at 12:04 PM, Alan Knowles <alan@akbkhome.com> wrote: > > > > > > On Sat, Apr 26, 2008 at 2:04 AM, Alan Knowles <alan@akbkhome.com> wrote: > > > > > > > Yes, I thought the exception RFC had talked about that. Making a one > line > > > definition in one file is getting really silly.. > > > > > > > > > > Do you refer to > > http://pear.php.net/pepr/pepr-proposal-show.php?id=132 ? > > I don't see it making clear whether it should be in one or multiple files. > > > > IMHO making one exception per file is not silly, it gives you a fast > > overview of what exceptions the package will throw. > > > > > So you want me to either > a) Open every single file to read the description about what the exception > is for. > b) Locate the Documentation file for the project, and go through it looking > for the details on Excpetions > c) Look at the manual pages for the exceptions.. which may not exist? > > or > d) Just look at the source code file with the list of exceptions in it. > Maybe someone with advanced PEAR-website-i-know-where-the-RFC-is-fu can answer this - is there a one class per file rule, or not? ;-) That would be the most simple thing to solve this dilemma. I don't mind the extra bytes of a new file, let alone the microseconds it takes to load. But that's just me, if it's not a rule (but a recommendation), then it's up to the people if they do it, or not. Till