Re: QuickForm or HTML_QuickForm?

On Fri, 2002-05-24 at 14:36, Michael Haertl wrote: > Just a thought on class nomenclature: > > I just saw that e.g. the QuickForm package's class name is declared as > > class HTML_QuickForm extends HTML_Common { ... > > So the user would have to write something like > > require_once("HTML/QuickForm.php"); > $myform = new HTML_QuickForm(...); > > Wouldn't it be more convenient to strip all the 'HTML_', 'HTTP_' etc. > prefixes from the class names like e.g. in the Auth package? It's really > confusing for the end user that there's no common scheme for class names. > > Maybe it would make sense to extend the coding standards that whenever > possible the name of the class should be the same as the package name. > Well, just a thought. Since PEAR is still beta it could still be time to > trim all packages to this scheme. But this _is_ the common scheme for class names. If a package has a parser, what do you think would happen if everyone named their parsing class "Parser"? - Stig