Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Why I use gcc Date: Fri, 07 Oct 2016 12:20:23 -0700 Organization: None to speak of Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="16484"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+V3Sln774a3cAuH7C9Tjjo" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:NLVx797EZzXN6XlSN/LVktyS1SU= sha1:UpGhiH2/iHL+FNrzeMGvEApXQRw= Xref: csiph.com comp.lang.c:94566 BartC writes: [...] > It standard doesn't need to do anything other than acknowledge that > implementation-defined attributes might exist. > > Then it can help by stipulating where those attributes can go. It > doesn't need to know what they are, what they do, or which keywords are > chosen. [...] C++ (starting with C++11, I think) defines a syntax for attributes: [[ attribute_name ]] There are only a handful of language-defined attributes, but implementation-defined attributes are permitted (perhaps even encouraged). I wouldn't mind seeing C adopt something similar or perhaps identical. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"