> -- Big License block - useless for maint. What on earth does that mean? The license doesn't change (unless you add a new contributor.)
> -- No file description block - What does this object do? Where is the > reference to the Object Behavior Description? Surprisingly enough, not everyone in the world uses those. > -- No Change log (CVS or RSC or whatever, the change log should be in > the source as well) Why? Surely this is a project management decision, not a decree-from-on-high absolute. There are arguments on both sides. If you want the change log, ask CVS or Bonsai (for the cvs-challenged.) > Now, there are probably processes in place that are understood by the > full-time developers; tools; perl scripts; some sort of design docs > squirled away. You'd think, wouldn't you? ;-) > But these are no help to someone you feel could be > constructive working on a piece of code. A person can't just pick a file > and start coding. That would be a silly way to work on any project. Why do you want to change this file anyway? > What are the naming > conventions? They are on the website. > How are the error catchers handling destructors in the > multi-threaded environment? You expect this to be described in the comments of every source code file? I'm not claiming our code is nice - a lot of it isn't. But you are going about this the wrong way. Gerv
