This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: correct place for code.

From: Andreas Schwab <schwab at suse dot de>
To: IainS <developer at sandoe-acoustics dot co dot uk>
Cc: Ian Lance Taylor <iant at google dot com>, GCC Development <gcc at gcc dot gnu dot org>
Date: Thu, 15 Jan 2009 10:26:06 +0100
Subject: Re: correct place for code.
References: <341CF03E-15DD-4BD1-9059-FA1AFCE29211@sandoe-acoustics.co.uk> <m37i4x8hs3.fsf@google.com> <3A4B5411-E049-489B-871C-F457A6884FDF@sandoe-acoustics.co.uk>

IainS <developer@sandoe-acoustics.co.uk> writes:

> 2/ assume that no sensible user will make an intention external symbol
> named ZLnnnn_OBJC_xxxxxx
>    perhaps that's not too unreasonable... OBJC_xxxxx are effectively
> reserved identifiers - so perhaps mangled file scope variants of  those
> could be too.

Symbols starting with _[A-Z] are reserved for the implementation in any
context.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- correct place for code.
  - From: IainS
- Re: correct place for code.
  - From: Ian Lance Taylor
- Re: correct place for code.
  - From: IainS

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]