| blob | 2b6dc7a9df74b4fa663fc9f7880de17194a39203 |
1 ;;; cc-langs.el --- language specific settings for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2011 Free Software Foundation, Inc.
5 ;; Authors: 2002- Alan Mackenzie
6 ;; 1998- Martin Stjernholm
7 ;; 1992-1999 Barry A. Warsaw
8 ;; 1987 Dave Detlefs
9 ;; 1987 Stewart Clamen
10 ;; 1985 Richard M. Stallman
11 ;; Maintainer: bug-cc-mode@gnu.org
12 ;; Created: 22-Apr-1997 (split from cc-mode.el)
13 ;; Keywords: c languages
14 ;; Package: cc-mode
16 ;; This file is part of GNU Emacs.
18 ;; GNU Emacs is free software: you can redistribute it and/or modify
19 ;; it under the terms of the GNU General Public License as published by
20 ;; the Free Software Foundation, either version 3 of the License, or
21 ;; (at your option) any later version.
23 ;; GNU Emacs is distributed in the hope that it will be useful,
24 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
25 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
26 ;; GNU General Public License for more details.
28 ;; You should have received a copy of the GNU General Public License
29 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
31 ;;; Commentary:
33 ;; HACKERS NOTE: There's heavy macro magic here. If you need to make
34 ;; changes in this or other files containing `c-lang-defconst' but
35 ;; don't want to read through the longer discussion below then read
36 ;; this:
37 ;;
38 ;; o A change in a `c-lang-defconst' or `c-lang-defvar' will not take
39 ;; effect if the file containing the mode init function (typically
40 ;; cc-mode.el) is byte compiled.
41 ;; o To make changes show in font locking you need to reevaluate the
42 ;; `*-font-lock-keywords-*' constants, which normally is easiest to
43 ;; do with M-x eval-buffer in cc-fonts.el.
44 ;; o In either case it's necessary to reinitialize the mode to make
45 ;; the changes show in an existing buffer.
47 ;;; Introduction to the language dependent variable system:
48 ;;
49 ;; This file contains all the language dependent variables, except
50 ;; those specific for font locking which reside in cc-fonts.el. As
51 ;; far as possible, all the differences between the languages that CC
52 ;; Mode supports are described with these variables only, so that the
53 ;; code can be shared.
54 ;;
55 ;; The language constant system (see cc-defs.el) is used to specify
56 ;; various language dependent info at a high level, such as lists of
57 ;; keywords, and then from them generate - at compile time - the
58 ;; various regexps and other low-level structures actually employed in
59 ;; the code at runtime.
60 ;;
61 ;; This system is also designed to make it easy for developers of
62 ;; derived modes to customize the source constants for new language
63 ;; variants, without having to keep up with the exact regexps etc that
64 ;; are used in each CC Mode version. It's possible from an external
65 ;; package to add a new language by inheriting an existing one, and
66 ;; then change specific constants as necessary for the new language.
67 ;; The old values for those constants (and the values of all the other
68 ;; high-level constants) may be used to build the new ones, and those
69 ;; new values will in turn be used by the low-level definitions here
70 ;; to build the runtime constants appropriately for the new language
71 ;; in the current version of CC Mode.
72 ;;
73 ;; Like elsewhere in CC Mode, the existence of a doc string signifies
74 ;; that a language constant is part of the external API, and that it
75 ;; therefore can be used with a high confidence that it will continue
76 ;; to work with future versions of CC Mode. Even so, it's not
77 ;; unlikely that such constants will change meaning slightly as this
78 ;; system is refined further; a certain degree of dependence on the CC
79 ;; Mode version is unavoidable when hooking in at this level. Also
80 ;; note that there's still work to be done to actually use these
81 ;; constants everywhere inside CC Mode; there are still hardcoded
82 ;; values in many places in the code.
83 ;;
84 ;; Separate packages will also benefit from the compile time
85 ;; evaluation; the byte compiled file(s) for them will contain the
86 ;; compiled runtime constants ready for use by (the byte compiled) CC
87 ;; Mode, and the source definitions in this file don't have to be
88 ;; loaded then. However, if a byte compiled package is loaded that
89 ;; has been compiled with a different version of CC Mode than the one
90 ;; currently loaded, then the compiled-in values will be discarded and
91 ;; new ones will be built when the mode is initialized. That will
92 ;; automatically trig a load of the file(s) containing the source
93 ;; definitions (i.e. this file and/or cc-fonts.el) if necessary.
94 ;;
95 ;; A small example of a derived mode is available at
96 ;; <http://cc-mode.sourceforge.net/derived-mode-ex.el>. It also
97 ;; contains some useful hints for derived mode developers.
99 ;;; Using language variables:
100 ;;
101 ;; The `c-lang-defvar' forms in this file comprise the language
102 ;; variables that CC Mode uses. It does not work to use
103 ;; `c-lang-defvar' anywhere else (which isn't much of a limitation
104 ;; since these variables sole purpose is to interface with the CC Mode
105 ;; core functions). The values in these `c-lang-defvar's are not
106 ;; evaluated right away but instead collected to a single large `setq'
107 ;; that can be inserted for a particular language with the
108 ;; `c-init-language-vars' macro.
110 ;; This file is only required at compile time, or when not running
111 ;; from byte compiled files, or when the source definitions for the
112 ;; language constants are requested.
114 ;;; Code:
116 ;; For Emacs < 22.2.
125 load-path)))
132 ;; This file is not always loaded. See note above.
135 \f
136 ;;; Setup for the `c-lang-defvar' system.
139 ;; These are used to collect the init forms from the subsequent
140 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
141 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
142 ;; and `make-variable-buffer-local's in cc-engine and
143 ;; `make-local-variable's in `c-init-language-vars-for'.
147 c-lang-variable-inits-tail c-lang-variable-inits)
151 c-emacs-variable-inits-tail c-emacs-variable-inits))
154 "Declares the buffer local variable VAR to get the value VAL. VAL is
155 evaluated and assigned at mode initialization. More precisely, VAL is
156 evaluated and bound to VAR when the result from the macro
157 `c-init-language-vars' is evaluated.
159 `c-lang-const' is typically used in VAL to get the right value for the
160 language being initialized, and such calls will be macro expanded to
161 the evaluated constant value at compile time."
167 ;; Special case: If there's no docstring and the value is a
168 ;; simple (c-lang-const foo) where foo is the same name as VAR
169 ;; then take the docstring from the language constant foo.
181 ;; Return the symbol, like the other def* forms.
185 "Causes the variable VAR to be made buffer local and to get set to the
186 value VAL. VAL is evaluated and assigned at mode initialization. More
187 precisely, VAL is evaluated and bound to VAR when the result from the
188 macro `c-init-language-vars' is evaluated. VAR is typically a standard
189 Emacs variable like `comment-start'.
191 `c-lang-const' is typically used in VAL to get the right value for the
192 language being initialized, and such calls will be macro expanded to
193 the evaluated constant value at compile time."
200 ;; Return the symbol, like the other def* forms.
204 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
205 ; '
209 ;; Suppress "might not be defined at runtime" warning.
210 ;; This file is only used when compiling other cc files.
216 ;; Some helper functions used when building the language constants.
219 ;; Extract a subset of the operators in the list OPS in a DWIM:ey
220 ;; way. The return value is a plain list of operators:
221 ;;
222 ;; OPS either has the structure of `c-operators', is a single
223 ;; group in `c-operators', or is a plain list of operators.
224 ;;
225 ;; OPGROUP-FILTER specifies how to select the operator groups. It
226 ;; can be t to choose all groups, a list of group type symbols
227 ;; (such as 'prefix) to accept, or a function which will be called
228 ;; with the group symbol for each group and should return non-nil
229 ;; if that group is to be included.
230 ;;
231 ;; If XLATE is given, it's a function which is called for each
232 ;; matching operator and its return value is collected instead.
233 ;; If it returns a list, the elements are spliced directly into
234 ;; the final result, which is returned as a list with duplicates
235 ;; removed using `equal'.
236 ;;
237 ;; `c-mode-syntax-table' for the current mode is in effect during
238 ;; the whole procedure.
259 t)
260 t)
265 opgroup)))
266 ops)
269 \f
270 ;;; Various mode specific values that aren't language related.
273 ;; The definition for the mode menu. The menu title is prepended to
274 ;; this before it's fed to `easy-menu-define'.
284 "----"
288 ;; Only applicable if there's a cpp preprocessor.
292 "----"
297 "----"
301 "Style Name: %s"
306 c-guess-guessed-basic-offset) ]
309 c-guess-guessed-basic-offset) ])
310 "----"
322 subword-mode)])))
324 \f
325 ;;; Syntax tables.
328 "Populate the given syntax table as necessary for a C-like language.
346 ;; Set up block and line oriented comments. The new C
347 ;; standard mandates both comment styles even in C, so since
348 ;; all languages now require dual comments, we make this the
349 ;; default.
351 ;; XEmacs
355 ;; Emacs
359 ;; incompatible
363 ;; Give CR the same syntax as newline, for selective-display
367 "Functions that generates the mode specific syntax tables.
368 The syntax tables aren't stored directly since they're quite large."
372 ;; Mode specific syntaxes.
374 ;; Let '@' be part of symbols in ObjC to cope with
375 ;; its compiler directives as single keyword tokens.
376 ;; This is then necessary since it's assumed that
377 ;; every keyword is a single symbol.
381 table)))
384 ;; The syntax tables in evaluated form. Only used temporarily when
385 ;; the constants in this file are evaluated.
389 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
390 ;; parenthesis characters. Used temporarily when template argument
391 ;; lists are parsed. Note that this encourages incorrect parsing of
392 ;; templates since they might contain normal operators that uses the
393 ;; '<' and '>' characters. Therefore this syntax table might go
394 ;; away when CC Mode handles templates correctly everywhere.
395 t nil
400 table)))
406 ;; A variant of the standard syntax table which is used to find matching
407 ;; "<"s and ">"s which have been marked as parens using syntax table
408 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
409 ;; non-paren syntax here. so that the list commands will work on "< ... >"
410 ;; even when there's unbalanced other parens inside them.
411 ;;
412 ;; This variable is nil for languages which don't have template stuff.
422 table))))
427 "A list that describes the modifications that should be done to the
428 mode syntax table to get a syntax table that matches all identifiers
429 and keywords as words.
431 The list is just like the one used in `font-lock-defaults': Each
432 element is a cons where the car is the character to modify and the cdr
433 the new syntax, as accepted by `modify-syntax-entry'."
434 ;; The $ character is not allowed in most languages (one exception
435 ;; is Java which allows it for legacy reasons) but we still classify
436 ;; it as an identifier character since it's often used in various
437 ;; machine generated identifiers.
448 mod)
453 table)
454 "Syntax table built on the mode syntax table but additionally
455 classifies symbol constituents like '_' and '$' as word constituents,
459 ;; For documentation see the following c-lang-defvar of the same name.
460 ;; The value here may be a list of functions or a single function.
461 t nil
464 ;; java 'c-before-change-check-<>-operators
469 fs
471 "If non-nil, a list of functions called from c-before-change-hook.
472 Typically these will record enough state to allow
473 `c-before-font-lock-function' to extend the region to fontify,
474 and may do such things as removing text-properties which must be
475 recalculated.
477 These functions will be run in the order given. Each of them
478 takes 2 parameters, the BEG and END supplied to every
479 before-change function; on entry, the buffer will have been
480 widened and match-data will have been saved; point is undefined
481 on both entry and exit; the return value is ignored.
483 The functions are called even when font locking isn't enabled.
485 When the mode is initialized, the functions are called with
489 ;; For documentation see the following c-lang-defvar of the same name.
490 ;; The value here may be a list of functions or a single function.
491 t 'c-set-fl-decl-start
497 fs
499 "If non-nil, a list of functions called just before font locking.
500 Typically they will extend the region about to be fontified \(see
501 below) and will set `syntax-table' text properties on the region.
503 These functions will be run in the order given. Each of them
504 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
505 after-change function; point is undefined on both entry and exit;
506 on entry, the buffer will have been widened and match-data will
507 have been saved; the return value is ignored.
509 The functions may extend the region to be fontified by setting the
510 buffer local variables c-new-BEG and c-new-END.
512 The functions are called even when font locking is disabled.
514 When the mode is initialized, these functions are called with
517 \f
518 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
521 Such a function takes one optional parameter, a buffer position (defaults to
522 point), and returns nil or t. This variable contains nil for languages which
523 don't have EOL terminated statements. "
524 t nil
531 The (admittedly kludgy) purpose of such a function is to prevent an infinite
532 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
533 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
534 even indirectly. This variable contains nil for languages which don't have
535 EOL terminated statements."
536 t nil
542 \f
543 ;;; Lexer-level syntax (identifiers, tokens etc).
546 "Whether the language has bitfield declarations."
547 t nil
552 "Regexp that matches the start of a symbol, i.e. any identifier or
554 operator at the top level."
562 "Set of characters that can be part of a symbol.
563 This is of the form that fits inside [ ] in a regexp."
564 ;; Pike note: With the backquote identifiers this would include most
565 ;; operator chars too, but they are handled with other means instead.
571 "Regexp matching identifiers and keywords (with submatch 0). Assumed
572 to match if `c-symbol-start' matches on the same position."
576 ;; Use the value from C here since the operator backquote is
577 ;; covered by the other alternative.
585 ;; Number of regexp grouping parens in `c-symbol-key'.
589 "This is the set of chars that can't be part of a symbol, i.e. the
590 negation of `c-symbol-chars'."
595 "Regexp that matches any character that can't be part of a symbol.
596 It's usually appended to other regexps to avoid matching a prefix.
597 It's assumed to not contain any submatchers."
598 ;; The same thing regarding Unicode identifiers applies here as to
599 ;; `c-symbol-key'.
603 "The operators that make up fully qualified identifiers. nil in
604 languages that don't have such things. See `c-operators' for a
605 description of the format. Binary operators can concatenate symbols,
609 This value is by default merged into `c-operators'."
610 t nil
614 ;; Java has "." to concatenate identifiers but it's also used for
615 ;; normal indexing. There's special code in the Java font lock
616 ;; rules to fontify qualified identifiers based on the standard
617 ;; naming conventions. We still define "." here to make
618 ;; `c-forward-name' move over as long names as possible which is
619 ;; necessary to e.g. handle throws clauses correctly.
628 ;; Appendable adorned regexp matching the operators that join
629 ;; symbols to fully qualified identifiers, or nil in languages that
630 ;; don't have such things.
631 ;;
632 ;; This was a docstring constant in 5.30. It still works but is now
633 ;; considered internal - change `c-identifier-ops' instead.
636 t)))
644 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
648 ;; Appendable adorned regexp matching operators that might precede
649 ;; an identifier and that are part of the identifier in that case.
650 ;; nil in languages without such things.
653 t)))
658 "Operators that can occur after a binary operator on `c-identifier-ops'
659 in identifiers. nil in languages that don't have such things.
661 Operators here should also have appropriate entries in `c-operators' -
662 it's not taken care of by default."
663 t nil
664 ;; '~' for destructors in C++, '*' for member pointers.
666 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
667 ;; in import declarations. (This will also match bogus things like
668 ;; "foo.*bar" but we don't bother.)
672 ;; Regexp that must match the token after
673 ;; `c-opt-identifier-concat-key' for it to be considered an
674 ;; identifier concatenation operator (which e.g. causes the
675 ;; preceding identifier to be fontified as a reference). Assumed to
676 ;; be a string if `c-opt-identifier-concat-key' is.
677 ;;
678 ;; This was a docstring constant in 5.30. It still works but is now
679 ;; considered internal - change `c-after-id-concat-ops' instead.
687 "Regexp that matches the start of an (optionally qualified) identifier.
688 It should also match all keywords. It's unspecified how far it
689 matches."
699 C++. It does not recognize the full range of syntactic whitespace
700 between the tokens; `c-forward-name' has to be used for that. It
701 should also not match identifiers containing parenthesis groupings,
703 ;; This regexp is more complex than strictly necessary to ensure
704 ;; that it can be matched with a minimum of backtracking.
725 ;; For flexibility, consider the symbol match
726 ;; optional if we've hit a
727 ;; `c-after-id-concat-ops' operator. This is
728 ;; also necessary to handle the "*" that can
729 ;; end import declaration identifiers in Java.
743 ;; This was a docstring constant in 5.30 but it's no longer used.
744 ;; It's only kept to avoid breaking third party code.
745 ;;
746 ;; Used to identify the submatch in `c-identifier-key' that
747 ;; surrounds the last symbol in the qualified identifier. It's a
748 ;; list of submatch numbers, of which the first that has a match is
749 ;; taken. It's assumed that at least one does when the regexp has
750 ;; matched.
751 t nil)
754 "Set if the language support backslash escaped newlines inside string
755 literals."
756 t nil
762 "Set if the language supports multiline string literals without escaped
763 newlines. If t, all string literals are multiline. If a character,
764 only literals where the open quote is immediately preceded by that
765 literal are multiline."
766 t nil
767 pike ?#)
772 "The symbol which starts preprocessor constructs when in the margin."
773 t "#"
778 "Regexp matching the prefix of a cpp directive in the languages that
779 normally use that macro preprocessor. Tested at bol or at boi.
781 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
782 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
788 "Regexp matching the prefix of a cpp directive anchored to BOL,
789 in the languages that have a macro preprocessor."
795 "Regexp matching the prefix of a cpp directive including the directive
796 name, or nil in languages without preprocessor support. The first
797 submatch surrounds the directive name."
801 ;; Pike, being a scripting language, recognizes hash-bangs too.
807 "List of cpp directives (without the prefix) that are followed by a
808 string message."
814 "List of cpp directives (without the prefix) that are followed by a
815 file name in angle brackets or quotes."
821 "Cpp directive (without the prefix) that is followed by a macro
822 definition, or nil if the language doesn't have any."
829 ;; Regexp matching everything up to the macro body of a cpp define, or the
830 ;; end of the logical line if there is none. Submatch 1 is the name of the
831 ;; macro. Set if c-opt-cpp-macro-define is.
836 ;; ^ ^ #defined name
842 ;; Regexp matching everything up to the end of the identifier defined
843 ;; by a cpp define.
852 "List of cpp directives (without the prefix) that are followed by an
853 expression."
858 "Regexp which matches the start of a CPP directive which contains an
859 expression, or nil if there aren't any in the language."
868 "List of functions in cpp expressions."
874 "List of all assignment operators."
880 idl nil)
883 "List describing all operators, along with their precedence and
884 associativity. The order in the list corresponds to the precedence of
885 the operators: The operators in each element are a group with the same
886 precedence, and the group has higher precedence than the groups in all
887 following elements. The car of each element describes the type of the
888 operator group, and the cdr is a list of the operator tokens in it.
889 The operator group types are:
891 'prefix Unary prefix operators.
892 'postfix Unary postfix operators.
893 'postfix-if-paren
894 Unary postfix operators if and only if the chars have
895 parenthesis syntax.
896 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
897 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
898 'right-assoc-sequence
899 Right associative operator that constitutes of a
900 sequence of tokens that separate expressions. All the
901 tokens in the group are in this case taken as
902 describing the sequence in one such operator, and the
903 order between them is therefore significant.
905 Operators containing a character with paren syntax are taken to match
906 with a corresponding open/close paren somewhere else. A postfix
907 operator with close paren syntax is taken to end a postfix expression
908 started somewhere earlier, rather than start a new one at point. Vice
909 versa for prefix operators with open paren syntax.
912 often are described as postfix operators are considered binary here,
913 since CC Mode treats every identifier as an expression."
915 ;; There's currently no code in CC Mode that exploit all the info
916 ;; in this variable; precedence, associativity etc are present as a
917 ;; preparation for future work.
928 ;; Primary.
937 ;; Postfix.
939 ;; The following need special treatment.
949 ;; Unary.
956 ;; The following need special treatment.
967 ;; Member selection.
971 ;; Multiplicative.
974 ;; Additive.
977 ;; Shift.
982 ;; Relational.
987 ;; Equality.
991 ;; Bitwise and.
995 ;; Bitwise exclusive or.
1001 ;; Bitwise or.
1007 ;; Logical and.
1011 ;; Logical or.
1017 ;; Conditional.
1020 ;; Assignment.
1023 ;; Exception.
1027 ;; Sequence.
1030 ;; IDL got its own definition since it has a much smaller operator
1031 ;; set than the other languages.
1035 ;; Primary.
1037 ;; Unary.
1039 ;; Multiplicative.
1041 ;; Additive.
1043 ;; Shift.
1045 ;; And.
1047 ;; Xor.
1049 ;; Or.
1053 ;; The operators as a flat list (without duplicates).
1059 t nil
1068 ;; These work like identifiers in Pike.
1075 ;; Regexp tested after an "operator" token in C++.
1076 t nil
1082 "Regexp matching the token before the ones in
1083 `c-overloadable-operators' when operators are specified in their
1086 languages without operator functions or where the complete operator
1087 identifier is listed in `c-overloadable-operators'.
1089 This regexp is assumed to not match any non-operator identifier."
1090 t nil
1095 ;; Note: the following alias is an old name which was a mis-spelling. It has
1096 ;; been corrected above and throughout cc-engine.el. It will be removed at
1097 ;; some release very shortly in the future. ACM, 2006-04-14.
1103 "List of the tokens made up of characters in the punctuation or
1104 parenthesis syntax classes that have uses other than as expression
1105 operators."
1123 ;; List of all tokens in the punctuation and parenthesis syntax
1124 ;; classes.
1130 ;; List containing all chars not in the word, symbol or
1131 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1132 ;; parenthesis and string delimiter chars.
1134 ;; Only go through the chars in the printable ASCII range. No
1135 ;; language so far has 8-bit or widestring operators.
1141 list)))
1144 ;; Regexp matching all tokens in the punctuation and parenthesis
1145 ;; syntax classes. Note that this also matches ".", which can start
1146 ;; a float.
1149 t
1155 ;; Regexp matching all assignment operators and only them. The
1156 ;; beginning of the first submatch is used to detect the end of the
1157 ;; token, along with the end of the whole match.
1160 ;; Need special case for "=" since it's a prefix of "==".
1172 ;; Regexp matching all tokens containing "<" or ">" which are longer
1173 ;; than one char.
1176 t
1182 ;; Regexp matching the second and subsequent characters of all
1183 ;; multicharacter tokens that begin with "<".
1186 t
1193 ;; Regexp matching the second and subsequent characters of all
1194 ;; multicharacter tokens that begin with ">".
1197 t
1202 t
1209 ;; The characters that should be considered to bound statements. To
1210 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1211 ;; begin with "^" to negate the set. If ? : operators should be
1212 ;; detected then the string must end with "?:".
1217 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1222 \f
1223 ;;; Syntactic whitespace.
1226 "Regexp matching an ordinary whitespace character.
1228 ;; "\\s " is not enough since it doesn't match line breaks.
1232 ;; Number of regexp grouping parens in `c-simple-ws'.
1236 "String that starts line comments, or nil if such don't exist.
1237 Line comments are always terminated by newlines. At least one of
1238 `c-block-comment-starter' and this one is assumed to be set.
1240 Note that it's currently not enough to set this to support a new
1241 comment style. Other stuff like the syntax table must also be set up
1242 properly."
1243 t "//"
1248 "String that starts block comments, or nil if such don't exist.
1249 Block comments are ended by `c-block-comment-ender', which is assumed
1250 to be set if this is. At least one of `c-line-comment-starter' and
1251 this one is assumed to be set.
1253 Note that it's currently not enough to set this to support a new
1254 comment style. Other stuff like the syntax table must also be set up
1255 properly."
1256 t "/*"
1257 awk nil)
1260 "String that ends block comments, or nil if such don't exist.
1262 Note that it's currently not enough to set this to support a new
1263 comment style. Other stuff like the syntax table must also be set up
1264 properly."
1265 t "*/"
1266 awk nil)
1269 ;; Regexp to match the start of any type of comment.
1275 re)))
1279 ;; Regexp which matches the start of a block comment (if such exists in the
1280 ;; language)
1288 ;; Regexp which matches the start of a line comment (if such exists in the
1289 ;; language; it does in all 7 CC Mode languages).
1297 ;; Regexp to match the start of comments and string literals.
1306 "Regexp to match the start of documentation comments."
1308 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1316 "String that starts comments inserted with M-; etc.
1317 `comment-start' is initialized from this."
1318 ;; Default: Prefer line comments to block comments, and pad with a space.
1322 ;; In C we still default to the block comment style since line
1323 ;; comments aren't entirely portable.
1328 "String that ends comments inserted with M-; etc.
1329 `comment-end' is initialized from this."
1330 ;; Default: Use block comment style if comment-start uses block
1331 ;; comments, and pad with a space in that case.
1341 "Regexp to match the start of a comment plus everything up to its body.
1342 `comment-start-skip' is initialized from this."
1343 ;; Default: Allow the last char of the comment starter(s) to be
1344 ;; repeated, then allow any amount of horizontal whitespace.
1357 ;; Regexp matching any sequence that can start syntactic whitespace.
1358 ;; The only uncertain case is '#' when there are cpp directives.
1372 ;; Regexp matching any single character that might end syntactic whitespace.
1387 ;; Regexp matching an unterminated block comment that doesn't
1388 ;; contain line breaks, or nil in languages without block comments.
1389 ;; Does not contain a \| operator at the top level.
1393 ;; It's messy to cook together a regexp that matches anything
1394 ;; but c-block-comment-ender.
1402 "[^"
1403 ;; The quoting rules inside char classes are silly. :P
1412 "]"
1420 ;; Regexp matching a block comment that doesn't contain line breaks,
1421 ;; or nil in languages without block comments. The reason we don't
1422 ;; allow line breaks is to avoid going very far and risk running out
1423 ;; of regexp stack; this regexp is intended to handle only short
1424 ;; comments that might be put in the middle of limited constructs
1425 ;; like declarations. Does not contain a \| operator at the top
1426 ;; level.
1441 ;; Regexp matching a piece of syntactic whitespace that isn't a
1442 ;; sequence of simple whitespace characters. As opposed to
1443 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1444 ;; directives as syntactic whitespace.
1456 ;; Regexp matching syntactic whitespace, including possibly the
1457 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1458 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1459 ;; not contain a \| operator at the top level.
1467 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1471 ;; Regexp matching syntactic whitespace, which is at least one
1472 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1473 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1474 ;; not contain a \| operator at the top level.
1482 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1486 ;; Regexp matching syntactic whitespace without any line breaks. As
1487 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1488 ;; regard cpp directives as syntactic whitespace. Does not contain
1489 ;; a \| operator at the top level.
1497 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1501 ;; Regexp that matches when there is no syntactically significant
1502 ;; text before eol. Macros are regarded as syntactically
1503 ;; significant text here.
1505 ;; Match eol (possibly inside a block comment or preceded
1506 ;; by a line continuation backslash), or the beginning of a
1507 ;; line comment. Note: This has to be modified for awk
1508 ;; where line comments start with '#'.
1522 \f
1523 ;;; Defun functions
1525 ;; The Emacs variables beginning-of-defun-function and
1526 ;; end-of-defun-function will be set so that commands like
1527 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1528 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1529 ;; functions, allowing optimization for large n.
1531 "Function to which beginning-of-defun-function will be set."
1532 t 'c-beginning-of-defun
1538 "Function to which end-of-defun-function will be set."
1539 t 'c-end-of-defun
1542 \f
1543 ;;; In-comment text handling.
1546 "Regexp to append to `paragraph-start'."
1547 t "$"
1553 "Regexp to append to `paragraph-separate'."
1554 t "$"
1558 \f
1559 ;;; Keyword lists.
1561 ;; Note: All and only all language constants containing keyword lists
1562 ;; should end with "-kwds"; they're automatically collected into the
1563 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1566 "Primitive type keywords. As opposed to the other keyword lists, the
1567 keywords listed here are fontified with the type face instead of the
1568 keyword face.
1570 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1571 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1572 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1573 will be handled.
1575 Do not try to modify this list for end user customizations; the
1576 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1577 the appropriate place for that."
1586 ;; Objective-C extends C, but probably not the new stuff in C99.
1593 ;; In CORBA PSDL:
1594 "ref"
1595 ;; The following can't really end a type, but we have to specify them
1596 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1597 ;; doesn't matter that much.
1600 ;; used as a builtin type.
1605 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1610 "Keywords that might act as prefixes for primitive types. Assumed to
1611 be a subset of `c-primitive-type-kwds'."
1612 t nil
1615 ;; In CORBA PSDL:
1620 of a variable declaration."
1625 ;; Adorned regexp matching `c-typedef-kwds'.
1630 "Keywords where the following name - if any - is a type name, and
1631 where the keyword together with the symbol works as a type in
1632 declarations.
1634 Note that an alternative if the second part doesn't hold is
1635 `c-type-list-kwds'. Keywords on this list are typically also present
1636 on one of the `*-decl-kwds' lists."
1637 t nil
1643 ;; Adorned regexp matching `c-type-prefix-kwds'.
1648 "Type modifier keywords. These can occur almost anywhere in types
1649 but they don't build a type of themselves. Unlike the keywords on
1650 `c-primitive-type-kwds', they are fontified with the keyword face and
1651 not the type face."
1652 t nil
1658 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1659 ;; languages without such keywords.
1665 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1666 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1676 ;; All keywords that can start a type (i.e. are either a type prefix
1677 ;; or a complete type).
1684 "Keywords introducing declarations where the following block (if any)
1685 contains another declaration level that should be considered a class.
1687 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1688 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1689 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1690 will be handled.
1692 Note that presence on this list does not automatically treat the
1693 following identifier as a type; the keyword must also be present on
1694 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1695 t nil
1703 ;; In CORBA PSDL:
1705 ;; In CORBA CIDL:
1710 ;; Regexp matching the start of a class.
1715 "Keywords introducing declarations where the following block (if
1716 any) is a brace list.
1718 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1719 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1720 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1721 will be handled."
1726 ;; Regexp matching the start of declarations where the following
1727 ;; block is a brace list.
1732 "Keywords where the following block (if any) contains another
1733 declaration level that should not be considered a class. For every
1734 keyword here, CC Mode will add a set of special syntactic symbols for
1736 `foo-open', `foo-close', and `infoo' symbols.
1738 The intention is that this category should be used for block
1739 constructs that aren't related to object orientation concepts like
1740 classes (which thus also include e.g. interfaces, templates,
1741 contracts, structs, etc). The more pragmatic distinction is that
1742 while most want some indentation inside classes, it's fairly common
1743 that they don't want it in some of these constructs, so it should be
1744 simple to configure that differently from classes. See also
1745 `c-class-decl-kwds'.
1747 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1748 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1749 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1750 will be handled."
1751 t nil
1755 ;; In CORBA CIDL:
1759 ;; Regexp matching the start of blocks besides classes that contain
1760 ;; another declaration level.
1769 'inextern-lang
1772 "Alist associating keywords in c-other-decl-block-decl-kwds with
1776 "Keywords introducing declarations where the identifier(s) being
1777 declared are types.
1779 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1780 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1781 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1782 will be handled."
1783 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1784 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1785 ;; {...}").
1788 ;; Languages that have a "typedef" construct.
1791 ;; Unlike most other languages, exception names are not handled as
1792 ;; types in IDL since they only can occur in "raises" specs.
1800 "Keywords introducing declarations where the \(first) identifier
1801 \(declarator) follows directly after the keyword, without any type.
1803 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1804 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1805 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1806 will be handled."
1807 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1808 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1809 ;; {...}").
1812 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1813 ;; `c-type-list-kwds' for IDL.
1816 ;; In CORBA PSDL:
1818 ;; In CORBA CIDL:
1824 "Keywords that can prefix normal declarations of identifiers
1825 \(and typically act as flags). Things like argument declarations
1826 inside function headers are also considered declarations in this
1827 sense.
1829 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1830 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1831 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1832 will be handled."
1833 t nil
1838 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1842 ;; In CORBA PSDL:
1844 ;; In CORBA CIDL:
1846 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1853 "Keywords that can start or prefix any declaration level construct,
1854 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1855 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1856 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1858 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1859 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1860 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1861 will be handled."
1862 t nil
1868 "Keywords that always start declarations, wherever they occur.
1869 This can be used for declarations that aren't recognized by the normal
1870 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1871 t nil
1872 ;; Classes can be declared anywhere in a Pike expression.
1876 "Keywords that can occur anywhere in a declaration level construct.
1877 This is used for self-contained things that can be tacked on anywhere
1878 on a declaration and that should be ignored to be able to recognize it
1879 correctly. Typical cases are compiler extensions like
1882 __declspec(noreturn) void foo();
1883 class __declspec(dllexport) classname {...};
1884 void foo() __attribute__((noreturn));
1886 Note that unrecognized plain symbols are skipped anyway if they occur
1887 before the type, so such things are not necessary to mention here.
1888 Mentioning them here is necessary only if they can occur in other
1889 places, or if they are followed by a construct that must be skipped
1891 examples above). In the last case, they alse need to be present on
1892 one of `c-type-list-kwds', `c-ref-list-kwds',
1893 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1894 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1895 ;; NB: These are currently not recognized in all parts of a
1896 ;; declaration. Specifically, they aren't recognized in the middle
1897 ;; of multi-token types, inside declarators, and between the
1898 ;; identifier and the arglist paren of a function declaration.
1899 ;;
1900 ;; FIXME: This ought to be user customizable since compiler stuff
1901 ;; like this usually is wrapped in project specific macros. (It'd
1902 ;; of course be even better if we could cope without knowing this.)
1903 t nil
1905 "__attribute__"
1906 ;; MSVC extension.
1910 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1915 ;; All keywords that can occur in the preamble of a declaration.
1916 ;; They typically occur before the type, but they are also matched
1917 ;; after presumptive types since we often can't be sure that
1918 ;; something is a type or just some sort of macro in front of the
1919 ;; declaration. They might be ambiguous with types or type
1920 ;; prefixes.
1933 ;; Adorned regexp of `c-prefix-spec-kwds'.
1939 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1940 ;; ambiguous with types or type prefixes. These are the keywords (like
1941 ;; extern, namespace, but NOT template) that can modify a declaration.
1950 ;; Keywords that can occur after argument list of a function header
1951 ;; declaration, i.e. in the "K&R region".
1956 ;; Adorned regexp matching all keywords that can't appear at the
1957 ;; start of a declaration.
1971 ;; The "more" for C++ is the QT keyword (as in "more slots:").
1972 ;; This variable is intended for use in c-beginning-of-statement-1.
1982 "Access protection label keywords in classes."
1983 t nil
1988 "Keywords introducing declarations that can contain a block which
1991 like that, it ends with the following ';' and not right away.
1993 The keywords on list are assumed to also be present on one of the
1994 `*-decl-kwds' lists."
1995 t nil
2000 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2001 ;; languages without such constructs.
2008 "Keywords introducing extra declaration specifiers in the region
2010 declarations."
2011 t nil
2014 "supports"
2015 ;; In CORBA PSDL:
2019 "Keywords that may be followed by a nonsymbol sexp before whatever
2020 construct it's part of continues."
2021 t nil
2025 "Keywords that may be followed by a comma separated list of type
2026 identifiers, where each optionally can be prefixed by keywords. (Can
2027 also be used for the special case when the list can contain only one
2028 element.)
2030 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2031 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2032 There's also no reason to add keywords that prefixes a normal
2033 declaration consisting of a type followed by a declarator (list), so
2034 the keywords on `c-modifier-kwds' should normally not be listed here
2035 either.
2037 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2038 or variable identifier (that's being defined)."
2039 t nil
2044 ;; In CORBA PSDL:
2049 "Keywords that may be followed by a comma separated list of
2050 reference (i.e. namespace/scope/module) identifiers, where each
2051 optionally can be prefixed by keywords. (Can also be used for the
2052 special case when the list can contain only one element.) Assumed to
2053 be mutually exclusive with `c-type-list-kwds'.
2055 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2056 or variable identifier (that's being defined)."
2057 t nil
2061 ;; In CORBA CIDL:
2066 "Keywords that may be followed (not necessarily directly) by a colon
2067 and then a comma separated list of type identifiers, where each
2068 optionally can be prefixed by keywords. (Can also be used for the
2069 special case when the list can contain only one element.)"
2070 t nil
2073 ;; In CORBA PSDL:
2077 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2078 forward to the colon. The end of the match is assumed to be directly
2080 regexp if `c-colon-type-list-kwds' isn't nil."
2082 ;; Disallow various common punctuation chars that can't come
2083 ;; before the ":" that starts the inherit list after "class"
2084 ;; or "struct" in C++. (Also used as default for other
2085 ;; languages.)
2090 "Keywords that may be followed by a parenthesis expression that doesn't
2091 contain type identifiers."
2092 t nil
2094 "__attribute__"
2095 ;; MSVC extension.
2099 "Keywords that may be followed by a parenthesis expression containing
2100 type identifiers separated by arbitrary tokens."
2101 t nil
2113 "Keywords that may be followed by an angle bracket expression
2115 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2116 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2117 if this isn't nil."
2118 t nil
2121 ;; In CORBA PSDL:
2125 "Keywords that can be followed by a C++ style template arglist; see
2126 `c-recognize-<>-arglists' for details. That language constant is
2127 assumed to be set if this isn't nil."
2128 t nil
2133 ;; All keywords that can be followed by an angle bracket sexp.
2139 ;; Adorned regexp matching keywords that can be followed by an angle
2140 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2146 "Keywords that may be followed by a brace block containing a comma
2147 separated list of identifier definitions, i.e. like the list of
2148 identifiers that follows the type in a normal declaration."
2152 "Statement keywords followed directly by a substatement."
2157 idl nil)
2160 ;; Regexp matching the start of any statement followed directly by a
2161 ;; substatement (doesn't match a bare block, however).
2166 "Statement keywords followed by a paren sexp and then by a substatement."
2171 idl nil
2176 ;; Regexp matching the start of any statement followed by a paren sexp
2177 ;; and then by a substatement.
2182 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2188 ;; Regexp matching the start of any statement that has a
2189 ;; substatement (except a bare block). Nil in languages that
2190 ;; don't have such constructs.
2199 "Statement keywords followed by an expression or nothing."
2202 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2204 idl nil
2211 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2216 "Statement keywords followed by a parenthesis expression that
2217 nevertheless contains a list separated with ';' and not ','."
2219 idl nil)
2222 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2227 "Statement keywords followed by an assembler expression."
2228 t nil
2232 ;; Regexp matching the start of an assembler statement. Nil in
2233 ;; languages that don't support that.
2242 awk nil)
2245 ;; Adorned regexp matching any "case"-like keyword.
2250 "Keywords introducing colon terminated labels in blocks."
2254 ;; Adorned regexp matching any keyword that introduces a label.
2259 "Keywords that might be followed by a label identifier."
2263 idl nil
2264 awk nil)
2267 "Keywords for constants."
2268 t nil
2277 "Keywords besides constants and operators that start primary expressions."
2278 t nil
2285 ;; Keywords that can occur anywhere in expressions. Built from
2286 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2290 t
2295 "Keywords that start lambda constructs, i.e. function definitions in
2296 expressions."
2297 t nil
2301 "Keywords that start constructs followed by statement blocks which can
2302 be used in expressions \(the gcc extension for this in C and C++ is
2303 handled separately by `c-recognize-paren-inexpr-blocks')."
2304 t nil
2308 "Keywords that can start classes inside expressions."
2309 t nil
2314 "Keywords that can start brace list blocks inside expressions.
2315 Note that Java specific rules are currently applied to tell this from
2316 `c-inexpr-class-kwds'."
2317 t nil
2321 ;; Regexp matching the start of a brace list in an expression, or
2322 ;; nil in languages that don't have such things. This should not
2323 ;; match brace lists recognized through `c-special-brace-lists'.
2330 ;; Regexp matching keywords in any construct that contain another
2331 ;; declaration level, i.e. that isn't followed by a function block
2332 ;; or brace list. When the first submatch matches, it's an
2333 ;; unambiguous construct, otherwise it's an ambiguous match that
2334 ;; might also be the return type of a function declaration.
2352 "Keywords that can introduce bitfields."
2353 t nil
2357 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2358 ;; languages without bitfield support.
2359 t nil
2364 "Keywords not accounted for by any other `*-kwds' language constant."
2365 t nil
2367 ;; In CORBA CIDL: (These are declaration keywords that never
2368 ;; can start a declaration.)
2371 \f
2372 ;;; Constants built from keywords.
2374 ;; Note: No `*-kwds' language constants may be defined below this point.
2378 ;; List of all the language constants that contain keyword lists.
2383 ;; Make the list of globally interned symbols
2384 ;; instead of ones interned in `c-lang-constants'.
2386 c-lang-constants)
2387 list)))
2390 ;; All keywords as a list.
2395 c-kwds-lang-consts)
2396 nil))
2400 ;; All keywords as an adorned regexp.
2405 ;; An alist with all the keywords in the cars. The cdr for each
2406 ;; keyword is a list of the symbols for the `*-kwds' lists that
2407 ;; contains it.
2413 c-kwds-lang-consts))))
2414 lang-const kwd-list kwd
2415 result-alist elem)
2427 result-alist))
2430 ;; An obarray containing all keywords as symbols. The property list
2431 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2432 ;; lists it's a member of.
2433 ;;
2434 ;; E.g. to see whether the string str contains a keyword on
2435 ;; `c-class-decl-kwds', one can do like this:
2436 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2437 ;; Which preferably is written using the associated functions in
2438 ;; cc-engine:
2439 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2441 ;; The obarray is not stored directly as a language constant since
2442 ;; the printed representation for obarrays used in .elc files isn't
2443 ;; complete.
2446 kwd lang-const-list
2453 ;; Emacs has an odd bug that causes `mapcan' to fail
2454 ;; with unintelligible errors. (XEmacs works.)
2455 ;;(mapcan (lambda (lang-const)
2456 ;; (list lang-const t))
2457 ;; lang-const-list)
2460 lang-const-list))))
2461 obarray))
2464 ;; Adorned regexp matching all keywords that should be fontified
2465 ;; with the keywords face. I.e. that aren't types or constants.
2475 ;; Regexp matching the start of any primary expression, i.e. any
2476 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2477 ;; exclude keywords; they are excluded afterwards unless the second
2478 ;; submatch matches. If the first but not the second submatch
2479 ;; matches then it is an ambiguous primary expression; it could also
2480 ;; be a match of e.g. an infix operator. (The case with ambiguous
2481 ;; keyword operators isn't handled.)
2487 ;; Filter out the special case prefix
2488 ;; operators that are close parens.
2493 t
2499 postfix-if-paren
2500 left-assoc
2501 right-assoc
2502 right-assoc-sequence)
2503 t))
2506 in-or-postfix-ops
2509 in-or-postfix-ops
2514 ;; Take out all symbol class operators from `prefix-ops' and make the
2515 ;; first submatch from them together with `c-primary-expr-kwds'.
2522 ;; Match all ambiguous operators.
2529 ;; Now match all other symbols.
2533 ;; The chars that can start integer and floating point
2534 ;; constants.
2538 ;; The unambiguous operators from `prefix-ops'.
2544 ;; Match string and character literals.
2551 \f
2552 ;;; Additional constants for parser-level constructs.
2555 "Regexp matching something that might precede a declaration, cast or
2556 label, such as the last token of a preceding statement or declaration.
2557 This is used in the common situation where a declaration or cast
2558 doesn't start with any specific token that can be searched for.
2560 The regexp should not match bob; that is done implicitly. It can't
2561 require a match longer than one token. The end of the token is taken
2562 to be at the end of the first submatch, which is assumed to always
2563 match. It's undefined whether identifier syntax (see
2564 `c-identifier-syntax-table') is in effect or not. This regexp is
2565 assumed to be a superset of `c-label-prefix-re' if
2566 `c-recognize-colon-labels' is set.
2568 Besides this, `c-decl-start-kwds' is used to find declarations.
2570 Note: This variable together with `c-decl-start-re' and
2572 declaration/cast/label starts. I.e. they might produce more matches
2573 but should not miss anything (or else it's necessary to use text
2574 properties - see the next note). Wherever they match, the following
2575 construct is analyzed to see if it indeed is a declaration, cast or
2576 label. That analysis is not cheap, so it's important that not too
2577 many false matches are triggered.
2579 Note: If a declaration/cast/label start can't be detected with this
2580 variable, it's necessary to use the `c-type' text property with the
2581 value `c-decl-end' on the last char of the last token preceding the
2582 declaration. See the comment blurb at the start of cc-engine.el for
2583 more info."
2585 ;; We match a sequence of characters to skip over things like \"};\"
2586 ;; more quickly. We match ")" in C for K&R region declarations, and
2587 ;; in all languages except Java for when a cpp macro definition
2588 ;; begins with a declaration.
2591 ;; Match "<" in C++ to get the first argument in a template arglist.
2592 ;; In that case there's an additional check in `c-find-decl-spots'
2593 ;; that it got open paren syntax.
2595 ;; Additionally match the protection directives in Objective-C.
2596 ;; Note that this doesn't cope with the longer directives, which we
2597 ;; would have to match from start to end since they don't end with
2598 ;; any easily recognized characters.
2602 ;; Pike is like C but we also match "[" for multiple value
2603 ;; assignments and type casts.
2609 "Regexp matching the start of any declaration, cast or label.
2610 It's used on the token after the one `c-decl-prefix-re' matched. This
2611 regexp should not try to match those constructs accurately as it's
2612 only used as a sieve to avoid spending more time checking other
2613 constructs."
2618 ;; Regexp matching something that might precede or start a
2619 ;; declaration, cast or label.
2620 ;;
2621 ;; If the first submatch matches, it's taken to match the end of a
2622 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2623 ;; It's built from `c-decl-prefix-re'.
2624 ;;
2625 ;; If the first submatch did not match, the match of the whole
2626 ;; regexp is taken to be at the first token in the declaration.
2627 ;; `c-decl-start-re' is not checked in this case.
2628 ;;
2629 ;; Design note: The reason the same regexp is used to match both
2630 ;; tokens that precede declarations and start them is to avoid an
2631 ;; extra regexp search from the previous declaration spot in
2632 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2633 ;; that it finds all declaration/cast/label starts in approximately
2634 ;; linear order, so we can't do the searches in two separate passes.
2645 ;; List containing the paren characters that can open a cast, or nil in
2646 ;; languages without casts.
2654 "List of syntactically relevant characters that never can occur before
2655 the open brace in any construct that contains a brace block, e.g. in
2658 class Foo: public Bar {int x();} a, *b;
2660 If parens can occur, the chars inside those aren't filtered with this
2661 list.
2663 '<' and '>' should be disallowed even if angle bracket arglists can
2664 occur. That since the search function needs to stop at them anyway to
2665 ensure they are given paren syntax.
2667 This is used to skip backward from the open brace to find the region
2670 possible for good performance."
2672 ;; Default to all chars that only occurs in nonsymbol tokens outside
2673 ;; identifiers.
2679 t
2680 t
2684 op pos)
2687 res))))
2689 ;; Allow cpp operations (where applicable).
2695 ;; Allow ':' for inherit list starters.
2699 ;; Allow ',' for multiple inherits.
2703 ;; Allow parentheses for anonymous inner classes in Java and class
2704 ;; initializer lists in Pike.
2708 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2713 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2714 ;; for `c-syntactic-skip-backward'.
2719 "Regexp matching the declarator operators that might precede the
2722 The end of the first submatch is taken as the end of the operator.
2723 Identifier syntax is in effect when this is matched \(see
2724 `c-identifier-syntax-table')."
2727 ;; Default to a regexp that never matches.
2729 ;; Check that there's no "=" afterwards to avoid matching tokens
2730 ;; like "*=".
2732 "[*\(]"
2738 "[*\(&]"
2743 ;; If this matches there's special treatment in
2744 ;; `c-font-lock-declarators' and
2745 ;; `c-font-lock-declarations' that check for a
2746 ;; complete name followed by ":: *".
2756 "Regexp matching the declarator operators that might follow after the
2759 it matches an open paren of some kind, the type declaration check
2760 continues at the corresponding close paren, otherwise the end of the
2761 first submatch is taken as the end of the operator. Identifier syntax
2762 is in effect when this is matched (see `c-identifier-syntax-table')."
2763 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2764 ;; function argument list parenthesis.
2772 "[\)\[\(]"
2776 ;; "throw" in `c-type-modifier-kwds' is followed
2777 ;; by a parenthesis list, but no extra measures
2778 ;; are necessary to handle that.
2788 "This regexp is matched after a declarator expression where
2789 `c-type-decl-suffix-key' has matched. If it matches then the
2790 construct is taken as a declaration. It's typically used to match the
2791 beginning of a function body or whatever might occur after the
2792 function header in a function declaration or definition. It's
2793 undefined whether identifier syntax (see `c-identifier-syntax-table')
2794 is in effect or not.
2799 t "{"
2800 ;; If K&R style declarations should be recognized then one could
2801 ;; consider to match the start of any symbol since we want to match
2802 ;; the start of the first declaration in the "K&R region". That
2803 ;; could however produce false matches on code like "FOO(bar) x"
2804 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2805 ;; on the other heuristics in that case.
2807 ;; Add on the keywords in `c-postfix-spec-kwds'.
2812 ;; Also match the colon that starts a base class initializer list in
2813 ;; C++. That can be confused with a function call before the colon
2814 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2815 ;; match before such a thing (as a declaration-level construct;
2816 ;; matches inside arglist contexts are already excluded).
2823 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2824 ;; matches ";" and ",".
2833 end of the operator. nil in languages without such operators. It's
2834 undefined whether identifier syntax (see `c-identifier-syntax-table')
2835 is in effect or not."
2836 t nil
2842 "Regexp matching operators that might follow after a type, or nil in
2843 languages that don't have such operators. The end of the first
2844 submatch is taken as the end of the operator. This should not match
2845 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2846 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2847 is in effect or not."
2848 t nil
2854 ;; Regexp matching the known type identifiers. This is initialized
2855 ;; from the type keywords and `*-font-lock-extra-types'. The first
2856 ;; submatch is the one that matches the type. Note that this regexp
2857 ;; assumes that symbol constituents like '_' and '$' have word
2858 ;; syntax.
2867 extra-types)))
2873 extra-types))))
2878 plain-strings)))
2879 regexp-strings)
2884 "List of open- and close-chars that makes up a pike-style brace list,
2886 list."
2887 t nil
2892 "Non-nil means K&R style argument declarations are valid."
2893 t nil
2894 c t)
2898 "Non-nil means function declarations without return type should be
2899 recognized. That can introduce an ambiguity with parenthesized macro
2900 calls before a brace block. This setting does not affect declarations
2901 that are preceded by a declaration starting keyword, so
2902 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2903 t nil
2909 "Non-nil means C++ style template arglists should be handled. More
2910 specifically, this means a comma separated list of types or
2912 identifier or one of the keywords on `c-<>-type-kwds' or
2913 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2914 expression is considered to be a type."
2920 "Non-nil means that parenthesis style initializers exist,
2921 i.e. constructs like
2923 Foo bar (gnu);
2925 in addition to the more classic
2927 Foo bar = gnu;"
2928 t nil
2933 "Non-nil to recognize gcc style in-expression blocks,
2934 i.e. compound statements surrounded by parentheses inside expressions."
2935 t nil
2941 ;; Regexp matching the start of angle bracket arglists in languages
2942 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2943 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2944 ;; assumed to surround the preceding symbol. The whole match is
2945 ;; assumed to end directly after the opening "<".
2955 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2956 ;; parens. The first submatch is assumed to surround
2957 ;; `c-opt-<>-arglist-start'.
2966 ;; Regexp matching the beginning of a declaration specifier in the
2967 ;; region between the header and the body of a declaration.
2968 ;;
2969 ;; TODO: This is currently not used uniformly; c++-mode and
2970 ;; java-mode each have their own ways of using it.
2971 t nil
2984 That includes labels in code and access keys in classes. This does
2985 not apply to labels recognized by `c-label-kwds' and
2986 `c-opt-extra-label-key'."
2987 t nil
2993 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2994 a generic colon label. Not used if `c-recognize-colon-labels' is
2995 nil."
3001 "Regexp matching things that can't occur in generic colon labels,
3002 neither in a statement nor in a declaration context. The regexp is
3003 tested at the beginning of every sexp in a suspected label,
3006 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3012 ;; Don't allow string literals, except in AWK. Character constants are OK.
3015 ;; Also check for open parens in C++, to catch member init lists in
3016 ;; constructors. We normally allow it so that macros with arguments
3017 ;; work in labels.
3022 "Regexp matching things that can't occur two symbols before a colon in
3030 "Optional regexp matching labels.
3031 Normally, labels are detected according to `c-nonlabel-token-key',
3032 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3033 be used if there are additional labels that aren't recognized that
3034 way."
3035 t nil
3040 ;; Regexp describing friend declarations classes, or nil in
3041 ;; languages that don't have such things.
3042 ;;
3043 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3044 ;; template skipping isn't done properly. This will disappear soon.
3045 t nil
3050 "<.+>"
3052 "friend"
3057 ;; Special regexp to match the start of Objective-C methods. The
3058 ;; first submatch is assumed to end after the + or - key.
3059 t nil
3061 ;; TODO: Ought to use a better method than anchoring on bol.
3066 "([^\)]*)"
3073 ;; Must be set in buffers where the `c-type' text property might be
3074 ;; used with the value `c-decl-end'.
3075 ;;
3076 ;; `c-decl-end' is used to mark the ends of labels and access keys
3077 ;; to make interactive refontification work better.
3080 ;; `c-decl-end' is used to mark the end of the @-style directives in
3081 ;; Objective-C.
3082 objc t)
3085 \f
3086 ;;; Wrap up the `c-lang-defvar' system.
3088 ;; Compile in the list of language variables that has been collected
3089 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3090 ;; first element of each is nil.
3094 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3095 ;; These are typically standard emacs variables such as `comment-start'.
3103 "Create a function that initializes all the language dependent variables
3104 for the given mode.
3106 This function should be evaluated at compile time, so that the
3107 function it returns is byte compiled with all the evaluated results
3108 from the language constants. Use the `c-init-language-vars' macro to
3109 accomplish that conveniently."
3115 ;; No need to byte compile this lambda since the byte compiler is
3116 ;; smart enough to detect the `funcall' construct in the
3117 ;; `c-init-language-vars' macro below and compile it all straight
3118 ;; into the function that contains `c-init-language-vars'.
3121 ;; This let sets up the context for `c-mode-var' and similar
3122 ;; that could be in the result from `cl-macroexpand-all'.
3124 current-var source-eval)
3131 ;; `c-lang-const' will expand to the evaluated
3132 ;; constant immediately in `cl-macroexpand-all'
3133 ;; below.
3139 ;; Note: The following `append' copies the
3140 ;; first argument. That list is small, so
3141 ;; this doesn't matter too much.
3145 ;; This diagnostic message isn't useful for end
3146 ;; users, so it's disabled.
3147 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3148 ;; (message ,(concat "%s compiled with CC Mode %s "
3149 ;; "but loaded with %s - evaluating "
3150 ;; "language constants from source")
3151 ;; ',mode ,c-version c-version)
3152 ;; (put ',mode 'c-has-warned-lang-consts t))
3165 current-var
3168 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3171 err)
3174 ;; Being evaluated from source. Always use the dynamic method to
3175 ;; work well when `c-lang-defvar's in this file are reevaluated
3176 ;; interactively.
3182 current-var)
3194 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3195 current-var err)
3197 ))
3200 "Initialize all the language dependent variables for the given mode.
3201 This macro is expanded at compile time to a form tailored for the mode
3202 in question, so MODE must be a constant. Therefore MODE is not
3203 evaluated and should not be quoted."
3206 \f
3209 ;;; cc-langs.el ends here