Date: Tue, 13 Jul 1999 09:41:44 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Anton Helm <tony AT dictator DOT nt DOT tuwien DOT ac DOT at>
cc: djgpp AT delorie DOT com, Martin Str|mberg <ams AT ludd DOT luth DOT se>
Subject: Re: Hiding globals when using flex/bison in a library
In-Reply-To: <4.2.0.58.19990712151434.00a497e0@hal.nt.tuwien.ac.at>
Message-ID: <Pine.SUN.3.91.990713094126.25972C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 12 Jul 1999, Anton Helm wrote:

> >The easiest solution is not to hide them at all, but use the feature
> >you mentioned and name them __anton_helm_yy_something_or_other.
> 
> That's the way it currently works (__LIBGEO__xxx). I was just looking 
> for something more elegant.

While `__anton_helm...' would probably never hit this problem, you
should be aware that ANSI C says that external names which begin with
two underscores are reserved for the standard libraries (libc.a and
such likes), as are those which begin with a single underscore and a
capital letter.