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: externs and thread local storage



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
to me.)

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 them
in the correct context and even then it becomes confusing.
Anyways __* keywords the correct way to have an extension anything else is
wrong.




-- Pinski


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