TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: To case or not to Case From:tomb -at- ssllc -dot- com To:techwr-l Date:Wed, 21 Jun 2000 08:32:18 -0700
Find a copy of the follow book; it's the Strunk and White of programming.
Kernighan, Brian W. & P.J. Plauger. The Elements of Programming Style. ISBN
The examples used are FOTRAN and PL/I but, as with Strunk and White, the
information is valuable. This may be a useful resource for programmers and
TD Beau, Project Manager
Signet Systems, LLC
Milwaukee, WI USA
> While proofreading code, I came across a command written two ways in two
> bits of code only a paragraph apart:
> <disarmname> <fullghostname>
> <disarmname> <FullGhostName> / <ArmedGhostName>
> OTOH, if the programmer
> (rather inconsistently) prefers <fullghostname>...
> I know the programmer: he's likely not noticed that he had inconsistencies
> right next to each other if they made no difference to his code.
> Jane Carnall
> Technical Writer, Compaq, UK
> Unless stated otherwise, these opinions are mine, and mine alone.