PEAR should be this "standard format", but whatever high-quality code
people want to contribute to the cause.
I think we are all saying the same thing. My 2.5 cents.
If you're right and this is what everyone is thinking, then I'll feel much
my euros here too :)
high-quality code seems *very* reasonable, although we should not force people to merge new classes provided into existing ones if parts of functionatily are duplicated, although we should keep the number of dupplicated functionality very small, db layers should be at not more than 1 or 2, maybe 3 regarding very special aspects
perhaps we should apply case by case decsision with problematic classes
but I do not mind having 4 or more template classes to choose from (ok. 15 or way to much in general (not in special))
andré
--
· André Langhorst · t: +49 571 3201801 ·
· waldschrott@php.net · m: +49 173 9558736 ·
· PHP Quality Assurance · http://qa.php.net ·