Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!aplcen!haven!uvaarpa!randall
From: randall@uvaarpa.virginia.edu (Randall Atkinson)
Newsgroups: comp.lang.c
Subject: Re: Variable Name Conventions
Message-ID: <2151@uvaarpa.virginia.edu>
Date: 21 Jan 90 18:47:55 GMT
References: <36190@cornell.UUCP> <1990Jan19.183036.24440@utzoo.uucp> <983@excelan.COM> <26160@cup.portal.com>
Reply-To: randall@uvaarpa.Virginia.EDU (Randall Atkinson)
Followup-To: comp.lang.misc
Distribution: usa
Organization: University of Virginia, Charlottesville
Lines: 13

There is still the matter of subsystems composed of several modules.
In such cases, the practice of prefixing all identifiers external to
a module with an abbreviated module identifier really pays off.

More than just avoiding namespace collisions, it aids developers
in finding out where the procedure lives and what its parameters are
and what service it provides.  This is especially helpful in environments
where the external header file for a module contains meaningful comments
about public identifiers.  

All of these comments (and for that matter those in the articles I'm
following up to) really aren't C specific so I've redirected followups
elsewhere...