yagyala <[EMAIL PROTECTED]> writes: > I recently started working for a company that has just implemented its > first set of software standards. So far, so good. Here's the problem: > one of those standards is that the comments for each routine must > indicate every other routine that it calls. As I try to keep my
Oh dear. > I'm sure some will wonder about the reasoning of this standard. The > company primarily has experience writing scientific alogorythms which > can get rather long. It makes a bit more sense to document all > routines called for a very long routine, but for short routines that > primarily call other routines, as most mine do, well.... Perhaps you can reason with them. Perhaps suggest the possibility that parts of the standard be waived or modified for the area of work you're involved with (rather than asking them for special personal dispensation, or asking them to throw away or rewrite their standards). John -- http://mail.python.org/mailman/listinfo/python-list
