This is the mail archive of the gcc-patches@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: [PATCH] document -Winvalid-memory-model


On 01/04/2016 05:15 PM, Martin Sebor wrote:

s/built-ins/builtins/ (like in the @refs you used previously)

I thought the @refs were an inconsistency and built-in was
the preferred spelling.  That's what someone else pointed
out to me sometime ago and what I see documented in the GCC
Coding Conventions (and what I also noticed used elsewhere
in this section of the manual).

But looking more closely, there are quite a few uses of both
builtins and built-ins, on this manual page as well as on
others.  Which makes me wonder which of the two is prevalent.

I count 68 occurrences of the words builtin and builtins in
the manual (separated by space and ignoring capitalization)
and 481 occurrences of the words built-in and built-ins.

I also count 50 occurrences of built-in in the gcc.pot file
and 33 occurrences of builtin.

This seems to confirm my understanding of the recommended
convention (though it also shows how inconsistently it is
being followed).  Please let me know if I missed something.

Sorry, my bad. "Built-in", hyphenated, is correct as an adjective, as in "built-in function". It's not clear what we're supposed to use as a noun, but it seems "builtin" isn't it, either. :-S I think that a couple years ago I changed a bunch of other instances to "built-in function" to avoid this trouble, but I won't insist on that here.

I will go ahead and commit this version of the patch tomorrow
unless you have objections.

Looks OK to me now.

-Sandra


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