add Mike Frysinger's GCC builtins regex to the "c-file" regexes

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2772 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

ChangeLog

@@ -368,6 +368,7 @@ CVS code -
 	  this to other regex strings whenever possible.
 	- Move some overly long split-up regex strings that cover
 	  similar areas onto the same line. (DLR)
+	- Add GCC builtins to the "c-file" regexes. (Mike Frysinger)
 - nanorc.5:
 	- Update the description of how the "color" regex works. (DLR)
 	- Clarify descriptions of the characters that aren't allowed

doc/nanorc.sample

@@ -165,6 +165,10 @@
 # color brightcyan "^[[:space:]]*#[[:space:]]*(define|undef|include|ifn?def|endif|elif|else|if|warning|error)"
 # color brightmagenta "'([^\]|(\\['abfnrtv\\]))'" "'\\(([0-7][0-7]?)|([0-3][0-7][0-7]))'" "'\\x[0-9A-Fa-f][0-9A-Fa-f]?'"
 ##
+## GCC builtins
+##
+# color cyan "__attribute__[[:space:]]*\(\([^)]*\)\)" "__(asm|builtin|inline|restrict|typeof)__"
+##
 ## You will in general want your comments and strings to come last,
 ## because syntax highlighting rules will be applied in the order they
 ## are read in.