This is the mail archive of the
mailing list for the GCC project.
Re: externs and thread local storage
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: "Gary Funck" <gary at intrepid dot com>
- Cc: "'Gcc Mailing List'" <gcc at gcc dot gnu dot org>
- Date: Sun, 2 Jul 2006 12:44:15 -0700
- Subject: Re: externs and thread local storage
- References: <JCEPIPKHCJGDMPOHDOIGOEIIDFAA.email@example.com>
On Jul 2, 2006, at 12:23 PM, Gary Funck wrote:
(Btw, personally, I'd prefer that a propoasl to extend the "C"
language use something other than a keyword beginning
with __ as a way of doing that. For example, a compound keyword
such as "thread local" would read better and is unlikely to clobber
many existing programs. If the idea of a compound keyword
is too offensive, then thread_local seems a lot better than __thread
Well keywords starting with two underscore are reserved by the standard
for extensions like this :).
So having the keyword thread_local would be bad as it means it has to be
a context sensitive keyword. Context sensitive keywords are much harder
to parse and you have to check to make sure the person actually used
in the correct context and even then it becomes confusing.
Anyways __* keywords the correct way to have an extension anything