Re: kick-off

> Welcome to the PEAR mailing list! > > I'd like to start off by throwing out the first unresolved issue I can > think of: > > Should PEAR contain classes and extensions only, or functions too? By > using the Class::method() syntax, functions can be made part of a class > but still be available directly, so I lean towards using only classes. > If we do decide on having functions too, we should consider namespace > issues: should functions then have a prefix based on the name of the > package they are from (for example "db_mysql_query"), or should they > have simpler names? > I am completely for only using classes, for all the reasons stated in the list. Perhaps we might however have a different area of PEAR for functions, sort of like CPAN has a different area for pre-built Perl scripts and the like. Sterling Hughes sterling@designmultimedia.com