Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Re: Token pasting in #include directive
Message-ID: <11731@smoke.BRL.MIL>
Date: 2 Dec 89 04:47:21 GMT
References: <11160@riks.csl.sony.co.jp> <1989Nov22.222413.3874@utzoo.uucp> <MCGRATH.89Dec1135522@paris.Berkeley.EDU> <5522@ncar.ucar.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <5522@ncar.ucar.edu> steve@groucho.ucar.edu (Steve Emmerson) writes:
>True.  But what about the rest of us (i.e. non-implementors).  Should
>we begin to "comment out" argument names in prototypes, or use
>single leading underscores, or just hope for the best (with or without
>documentation)?

C application developers have to deal with name space conflicts SOMEhow.
You should NOT start using _names, because those are reserved for C
implementions.  You can use any names that you're sure will not be
#defined before your header is included.  What those names are depends
on the name space partitioning rules you have adopted.  If you use the
"package prefix" notion I've described in previous postings, then names
incorporating the header's package prefix would be wise.