Re: Template Proposal

Quoting Martin Jansen <mail@martin-jansen.de>: > I'm not willing to break backwards compatibility. My proposal is > to make the coding standards less strict (e.g. allow different > function names or other bracket conventions). > > But I think you will be even against this, right? (I can really > understand your opinion.) I want a core library of classes that are standard, follow strict coding standards, and have tested, peer-reviewed code. I think there should also be a repository for people to distribute whatever they want using the same installation/propogation mechanisms. On the latter, enforcing coding standards is counter productive. It'd be nice if someone would security audit stuff now and then, but whatever. What's good will get noticed, hopefully. But on a core library, I want consistently spaced, commented, and named code, I want consistent APIs, etc. Right now, we have a mix between the two. It doesn't work. -chuck -- Charles Hagenbuch, <chuck@horde.org> "What was and what may be, lie, like children whose faces we cannot see, in the arms of silence. All we ever have is here, now." - Ursula K. Le Guin