This is the mail archive of the
mailing list for the GCC project.
Re: __HAVE_BUILTIN_SETJMP__: why?
- From: Andreas Schwab <schwab at suse dot de>
- To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 15 May 2002 10:27:41 +0200
- Subject: Re: __HAVE_BUILTIN_SETJMP__: why?
- References: <20020515133952.A12223@hg.cs.mu.oz.au>
Fergus Henderson <email@example.com.OZ.AU> writes:
|> You could use something like
|> #if (__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 8))
|> instead of
|> #ifdef __HAVE_BUILTIN_SETJMP__
|> so it is not strictly necessary, but the definition of __HAVE_BUILTIN_SETJMP__
|> is pretty harmless, so personally I would leave it in to avoid breaking any
|> existing code which relies on it.
Any code that relies on an undocumented identifier that is in the
implementation's name space is broken by design.
Andreas Schwab, SuSE Labs, firstname.lastname@example.org
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."