From owner-freebsd-questions@FreeBSD.ORG Mon Jun 7 20:10:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A2316A4CE for ; Mon, 7 Jun 2004 20:10:19 +0000 (GMT) Received: from mail2.ctiseattle.com (mail2.ctiseattle.com [65.112.26.67]) by mx1.FreeBSD.org (Postfix) with SMTP id 4BB1543D1D for ; Mon, 7 Jun 2004 20:10:19 +0000 (GMT) (envelope-from JGoodleaf@ctiseattle.com) Received: from cti-501exchange.celltherapeutics.local(172.21.0.165) by mail2.ctiseattle.com via csmap id 6d6a18ea_b8bf_11d8_911e_00304811ff59_23877; Mon, 07 Jun 2004 13:15:32 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message Content-Transfer-Encoding: 7bit Date: Mon, 7 Jun 2004 13:10:06 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: OT: group coding standards Thread-Index: AcRMy28jh2l2Vgy3S9Wyg9N4EpDB3w== From: "Goodleaf, John" To: X-NAIMIME-Modified: 1 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: OT: group coding standards X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 20:10:19 -0000 Hello, I'm abusing the mailing list because many of you are sickeningly clever and have long experience in IT. I'm working to establish a document (yep) providing guidance for our company's small-but-growing IT group with regard to coding standards and practices. It seems rife with potential problems and there is already the potential for one of those variable-naming holy wars (e.g. intVariableName, varname, VarName, varName). So my question: is there a good document out there on the net somewhere, maybe hiding at a University site from which I can draw for general consideration? Any experiences? Recommendations? It's a hard problem. How do you provide conventions that don't annoy the hell out of programmers, but which ensure that legibile, maintainable code is left? Any suggestions welcome. Please cc me directly, as I'm not currently on this list. John _________________________________________________________________ This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.