| blob | a8dc3b8968c3ef9eaa91373eff8851c9e059be5e |
1 ;;; cc-langs.el --- language specific settings for CC Mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2014 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.
211 ;; These are defined in cl as aliases to the cl- versions.
212 ;(declare-function delete-duplicates "cl-seq" (cl-seq &rest cl-keys) t)
213 ;(declare-function mapcan "cl-extra" (cl-func cl-seq &rest cl-rest) t)
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"
302 c-indentation-style)
303 t]
307 c-guess-guessed-basic-offset) ]
310 c-guess-guessed-basic-offset) ])
311 "----"
323 subword-mode)])))
325 \f
326 ;;; Syntax tables.
329 "Populate the given syntax table as necessary for a C-like language.
347 ;; Set up block and line oriented comments. The new C
348 ;; standard mandates both comment styles even in C, so since
349 ;; all languages now require dual comments, we make this the
350 ;; default.
352 ;; XEmacs
356 ;; Emacs
360 ;; incompatible
364 ;; Give CR the same syntax as newline, for selective-display
368 "Functions that generates the mode specific syntax tables.
369 The syntax tables aren't stored directly since they're quite large."
373 ;; Mode specific syntaxes.
375 ;; Let '@' be part of symbols in ObjC to cope with
376 ;; its compiler directives as single keyword tokens.
377 ;; This is then necessary since it's assumed that
378 ;; every keyword is a single symbol.
382 table)))
385 ;; The syntax tables in evaluated form. Only used temporarily when
386 ;; the constants in this file are evaluated.
390 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
391 ;; parenthesis characters. Used temporarily when template argument
392 ;; lists are parsed. Note that this encourages incorrect parsing of
393 ;; templates since they might contain normal operators that uses the
394 ;; '<' and '>' characters. Therefore this syntax table might go
395 ;; away when CC Mode handles templates correctly everywhere. WHILE
396 ;; THIS SYNTAX TABLE IS CURRENT, `c-parse-state' MUST _NOT_ BE
397 ;; CALLED!!!
398 t nil
403 table)))
409 ;; A variant of the standard syntax table which is used to find matching
410 ;; "<"s and ">"s which have been marked as parens using syntax table
411 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
412 ;; non-paren syntax here. so that the list commands will work on "< ... >"
413 ;; even when there's unbalanced other parens inside them.
414 ;;
415 ;; This variable is nil for languages which don't have template stuff.
418 ;(if (c-lang-const c-recognize-<>-arglists)
426 table))))
432 "A list that describes the modifications that should be done to the
433 mode syntax table to get a syntax table that matches all identifiers
434 and keywords as words.
436 The list is just like the one used in `font-lock-defaults': Each
437 element is a cons where the car is the character to modify and the cdr
438 the new syntax, as accepted by `modify-syntax-entry'."
439 ;; The $ character is not allowed in most languages (one exception
440 ;; is Java which allows it for legacy reasons) but we still classify
441 ;; it as an identifier character since it's often used in various
442 ;; machine generated identifiers.
453 mod)
458 table)
459 "Syntax table built on the mode syntax table but additionally
460 classifies symbol constituents like '_' and '$' as word constituents,
464 ;; For documentation see the following c-lang-defvar of the same name.
465 ;; The value here may be a list of functions or a single function.
466 t nil
468 c-before-change-check-<>-operators
469 c-invalidate-macro-cache)
471 ;; java 'c-before-change-check-<>-operators
476 fs
478 "If non-nil, a list of functions called from c-before-change-hook.
479 Typically these will record enough state to allow
480 `c-before-font-lock-function' to extend the region to fontify,
481 and may do such things as removing text-properties which must be
482 recalculated.
484 These functions will be run in the order given. Each of them
485 takes 2 parameters, the BEG and END supplied to every
486 before-change function; on entry, the buffer will have been
487 widened and match-data will have been saved; point is undefined
488 on both entry and exit; the return value is ignored.
490 The functions are called even when font locking isn't enabled.
492 When the mode is initialized, the functions are called with
496 ;; For documentation see the following c-lang-defvar of the same name.
497 ;; The value here may be a list of functions or a single function.
498 t 'c-change-set-fl-decl-start
500 c-change-set-fl-decl-start)
505 fs
507 "If non-nil, a list of functions called just before font locking.
508 Typically they will extend the region about to be fontified \(see
509 below) and will set `syntax-table' text properties on the region.
511 These functions will be run in the order given. Each of them
512 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
513 after-change function; point is undefined on both entry and exit;
514 on entry, the buffer will have been widened and match-data will
515 have been saved; the return value is ignored.
517 The functions may extend the region to be fontified by setting the
518 buffer local variables c-new-BEG and c-new-END.
520 The functions are called even when font locking is disabled.
522 When the mode is initialized, these functions are called with
526 awk nil
528 ;; For documentation see the following c-lang-defvar of the same name.
529 ;; The value here may be a list of functions or a single function.
533 fs
535 "If non-nil, a list of functions called just before context (or
536 other non-change) fontification is done. Typically they will
537 extend the region.
539 These functions will be run in the order given. Each of them
540 takes 2 parameters, the BEG and END of the region to be
541 fontified. Point is undefined on both entry and exit. On entry,
542 the buffer will have been widened and match-data will have been
543 saved; the return value is a cons of the adjusted
546 \f
547 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
550 Such a function takes one optional parameter, a buffer position (defaults to
551 point), and returns nil or t. This variable contains nil for languages which
552 don't have EOL terminated statements. "
553 t nil
560 The (admittedly kludgy) purpose of such a function is to prevent an infinite
561 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
562 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
563 even indirectly. This variable contains nil for languages which don't have
564 EOL terminated statements."
565 t nil
571 \f
572 ;;; Lexer-level syntax (identifiers, tokens etc).
575 "Whether the language has bitfield declarations."
576 t nil
581 "Regexp that matches the start of a symbol, i.e. any identifier or
583 operator at the top level."
591 "Set of characters that can be part of a symbol.
592 This is of the form that fits inside [ ] in a regexp."
593 ;; Pike note: With the backquote identifiers this would include most
594 ;; operator chars too, but they are handled with other means instead.
600 "Regexp matching identifiers and keywords (with submatch 0). Assumed
601 to match if `c-symbol-start' matches on the same position."
605 ;; Use the value from C here since the operator backquote is
606 ;; covered by the other alternative.
614 ;; Number of regexp grouping parens in `c-symbol-key'.
618 "This is the set of chars that can't be part of a symbol, i.e. the
619 negation of `c-symbol-chars'."
624 "Regexp that matches any character that can't be part of a symbol.
625 It's usually appended to other regexps to avoid matching a prefix.
626 It's assumed to not contain any submatchers."
627 ;; The same thing regarding Unicode identifiers applies here as to
628 ;; `c-symbol-key'.
632 "The operators that make up fully qualified identifiers. nil in
633 languages that don't have such things. See `c-operators' for a
634 description of the format. Binary operators can concatenate symbols,
638 This value is by default merged into `c-operators'."
639 t nil
643 ;; Java has "." to concatenate identifiers but it's also used for
644 ;; normal indexing. There's special code in the Java font lock
645 ;; rules to fontify qualified identifiers based on the standard
646 ;; naming conventions. We still define "." here to make
647 ;; `c-forward-name' move over as long names as possible which is
648 ;; necessary to e.g. handle throws clauses correctly.
657 ;; Appendable adorned regexp matching the operators that join
658 ;; symbols to fully qualified identifiers, or nil in languages that
659 ;; don't have such things.
660 ;;
661 ;; This was a docstring constant in 5.30. It still works but is now
662 ;; considered internal - change `c-identifier-ops' instead.
665 t)))
673 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
677 ;; Appendable adorned regexp matching operators that might precede
678 ;; an identifier and that are part of the identifier in that case.
679 ;; nil in languages without such things.
682 t)))
687 "Operators that can occur after a binary operator on `c-identifier-ops'
688 in identifiers. nil in languages that don't have such things.
690 Operators here should also have appropriate entries in `c-operators' -
691 it's not taken care of by default."
692 t nil
693 ;; '~' for destructors in C++, '*' for member pointers.
695 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
696 ;; in import declarations. (This will also match bogus things like
697 ;; "foo.*bar" but we don't bother.)
701 ;; Regexp that must match the token after
702 ;; `c-opt-identifier-concat-key' for it to be considered an
703 ;; identifier concatenation operator (which e.g. causes the
704 ;; preceding identifier to be fontified as a reference). Assumed to
705 ;; be a string if `c-opt-identifier-concat-key' is.
706 ;;
707 ;; This was a docstring constant in 5.30. It still works but is now
708 ;; considered internal - change `c-after-id-concat-ops' instead.
716 "Regexp that matches the start of an (optionally qualified) identifier.
717 It should also match all keywords. It's unspecified how far it
718 matches."
728 C++. It does not recognize the full range of syntactic whitespace
729 between the tokens; `c-forward-name' has to be used for that. It
730 should also not match identifiers containing parenthesis groupings,
732 ;; This regexp is more complex than strictly necessary to ensure
733 ;; that it can be matched with a minimum of backtracking.
754 ;; For flexibility, consider the symbol match
755 ;; optional if we've hit a
756 ;; `c-after-id-concat-ops' operator. This is
757 ;; also necessary to handle the "*" that can
758 ;; end import declaration identifiers in Java.
772 ;; This was a docstring constant in 5.30 but it's no longer used.
773 ;; It's only kept to avoid breaking third party code.
774 ;;
775 ;; Used to identify the submatch in `c-identifier-key' that
776 ;; surrounds the last symbol in the qualified identifier. It's a
777 ;; list of submatch numbers, of which the first that has a match is
778 ;; taken. It's assumed that at least one does when the regexp has
779 ;; matched.
780 t nil)
783 "Set if the language support backslash escaped newlines inside string
784 literals."
785 t nil
791 "Set if the language supports multiline string literals without escaped
792 newlines. If t, all string literals are multiline. If a character,
793 only literals where the open quote is immediately preceded by that
794 literal are multiline."
795 t nil
796 pike ?#)
801 "The symbol which starts preprocessor constructs when in the margin."
802 t "#"
807 "Regexp matching the prefix of a cpp directive in the languages that
808 normally use that macro preprocessor. Tested at bol or at boi.
810 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
811 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
817 "Regexp matching the prefix of a cpp directive anchored to BOL,
818 in the languages that have a macro preprocessor."
824 "Regexp matching the prefix of a cpp directive including the directive
825 name, or nil in languages without preprocessor support. The first
826 submatch surrounds the directive name."
830 ;; Pike, being a scripting language, recognizes hash-bangs too.
836 "List of cpp directives (without the prefix) that are followed by a
837 string message."
843 "List of cpp directives (without the prefix) that are followed by a
844 file name in angle brackets or quotes."
850 "Cpp directive (without the prefix) that is followed by a macro
851 definition, or nil if the language doesn't have any."
858 ;; Regexp matching everything up to the macro body of a cpp define, or the
859 ;; end of the logical line if there is none. Submatch 1 is the name of the
860 ;; macro. Set if c-opt-cpp-macro-define is.
865 ;; ^ ^ #defined name
871 ;; Regexp matching everything up to the end of the identifier defined
872 ;; by a cpp define.
881 "List of cpp directives (without the prefix) that are followed by an
882 expression."
887 "Regexp which matches the start of a CPP directive which contains an
888 expression, or nil if there aren't any in the language."
897 "List of functions in cpp expressions."
903 "List of all assignment operators."
909 idl nil)
912 "List describing all operators, along with their precedence and
913 associativity. The order in the list corresponds to the precedence of
914 the operators: The operators in each element are a group with the same
915 precedence, and the group has higher precedence than the groups in all
916 following elements. The car of each element describes the type of the
917 operator group, and the cdr is a list of the operator tokens in it.
918 The operator group types are:
920 'prefix Unary prefix operators.
921 'postfix Unary postfix operators.
922 'postfix-if-paren
923 Unary postfix operators if and only if the chars have
924 parenthesis syntax.
925 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
926 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
927 'right-assoc-sequence
928 Right associative operator that constitutes of a
929 sequence of tokens that separate expressions. All the
930 tokens in the group are in this case taken as
931 describing the sequence in one such operator, and the
932 order between them is therefore significant.
934 Operators containing a character with paren syntax are taken to match
935 with a corresponding open/close paren somewhere else. A postfix
936 operator with close paren syntax is taken to end a postfix expression
937 started somewhere earlier, rather than start a new one at point. Vice
938 versa for prefix operators with open paren syntax.
941 often are described as postfix operators are considered binary here,
942 since CC Mode treats every identifier as an expression."
944 ;; There's currently no code in CC Mode that exploits all the info
945 ;; in this variable; precedence, associativity etc are present as a
946 ;; preparation for future work.
948 ;; FIXME!!! C++11's "auto" operators "=" and "->" need to go in here
949 ;; somewhere. 2012-03-24.
960 ;; Primary.
969 ;; Postfix.
971 ;; The following need special treatment.
981 ;; Unary.
988 ;; The following need special treatment.
999 ;; Member selection.
1003 ;; Multiplicative.
1006 ;; Additive.
1009 ;; Shift.
1014 ;; Relational.
1019 ;; Equality.
1023 ;; Bitwise and.
1027 ;; Bitwise exclusive or.
1033 ;; Bitwise or.
1039 ;; Logical and.
1043 ;; Logical or.
1049 ;; Conditional.
1052 ;; Assignment.
1055 ;; Exception.
1059 ;; Sequence.
1062 ;; IDL got its own definition since it has a much smaller operator
1063 ;; set than the other languages.
1067 ;; Primary.
1069 ;; Unary.
1071 ;; Multiplicative.
1073 ;; Additive.
1075 ;; Shift.
1077 ;; And.
1079 ;; Xor.
1081 ;; Or.
1085 ;; The operators as a flat list (without duplicates).
1091 t nil
1100 ;; These work like identifiers in Pike.
1107 ;; Regexp tested after an "operator" token in C++.
1108 t nil
1114 "Regexp matching the token before the ones in
1115 `c-overloadable-operators' when operators are specified in their
1118 languages without operator functions or where the complete operator
1119 identifier is listed in `c-overloadable-operators'.
1121 This regexp is assumed to not match any non-operator identifier."
1122 t nil
1127 ;; Note: the following alias is an old name which was a mis-spelling. It has
1128 ;; been corrected above and throughout cc-engine.el. It will be removed at
1129 ;; some release very shortly in the future. ACM, 2006-04-14.
1135 "List of the tokens made up of characters in the punctuation or
1136 parenthesis syntax classes that have uses other than as expression
1137 operators."
1155 ;; List of all tokens in the punctuation and parenthesis syntax
1156 ;; classes.
1162 ;; List containing all chars not in the word, symbol or
1163 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1164 ;; parenthesis and string delimiter chars.
1166 ;; Only go through the chars in the printable ASCII range. No
1167 ;; language so far has 8-bit or widestring operators.
1173 list)))
1176 ;; Regexp matching all tokens in the punctuation and parenthesis
1177 ;; syntax classes. Note that this also matches ".", which can start
1178 ;; a float.
1181 t
1187 ;; Regexp matching all assignment operators and only them. The
1188 ;; beginning of the first submatch is used to detect the end of the
1189 ;; token, along with the end of the whole match.
1192 ;; Need special case for "=" since it's a prefix of "==".
1204 ;; Regexp matching all tokens containing "<" or ">" which are longer
1205 ;; than one char.
1208 t
1214 ;; Regexp matching the second and subsequent characters of all
1215 ;; multicharacter tokens that begin with "<".
1218 t
1225 ;; A list of second and subsequent characters of all multicharacter tokens
1226 ;; that begin with ">".
1228 t
1232 t
1237 ;; Regexp matching the second and subsequent characters of all
1238 ;; multicharacter tokens that begin with ">".
1244 ;; Regexp matching the second and subsequent characters of all
1245 ;; multicharacter tokens that begin with ">" except for those beginning with
1246 ;; ">>".
1251 t
1260 ;; The characters that should be considered to bound statements. To
1261 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1262 ;; begin with "^" to negate the set. If ? : operators should be
1263 ;; detected then the string must end with "?:".
1268 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1274 ;; Ops which signal C++11's new auto uses.
1275 t nil
1282 ;; Op used in the new C++11 auto function definition, indicating type.
1283 t nil
1288 \f
1289 ;;; Syntactic whitespace.
1292 "Regexp matching an ordinary whitespace character.
1294 ;; "\\s " is not enough since it doesn't match line breaks.
1298 ;; Number of regexp grouping parens in `c-simple-ws'.
1302 "String that starts line comments, or nil if such don't exist.
1303 Line comments are always terminated by newlines. At least one of
1304 `c-block-comment-starter' and this one is assumed to be set.
1306 Note that it's currently not enough to set this to support a new
1307 comment style. Other stuff like the syntax table must also be set up
1308 properly."
1309 t "//"
1314 "String that starts block comments, or nil if such don't exist.
1315 Block comments are ended by `c-block-comment-ender', which is assumed
1316 to be set if this is. At least one of `c-line-comment-starter' and
1317 this one is assumed to be set.
1319 Note that it's currently not enough to set this to support a new
1320 comment style. Other stuff like the syntax table must also be set up
1321 properly."
1322 t "/*"
1323 awk nil)
1326 "String that ends block comments, or nil if such don't exist.
1328 Note that it's currently not enough to set this to support a new
1329 comment style. Other stuff like the syntax table must also be set up
1330 properly."
1331 t "*/"
1332 awk nil)
1335 ;; Regexp to match the start of any type of comment.
1341 re)))
1345 ;; Regexp which matches the start of a block comment (if such exists in the
1346 ;; language)
1354 ;; Regexp which matches the start of a line comment (if such exists in the
1355 ;; language; it does in all 7 CC Mode languages).
1363 ;; Regexp to match the start of comments and string literals.
1372 "Regexp to match the start of documentation comments."
1374 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1382 "String that starts comments inserted with M-; etc.
1383 `comment-start' is initialized from this."
1384 ;; Default: Prefer line comments to block comments, and pad with a space.
1388 ;; In C we still default to the block comment style since line
1389 ;; comments aren't entirely portable.
1394 "String that ends comments inserted with M-; etc.
1395 `comment-end' is initialized from this."
1396 ;; Default: Use block comment style if comment-start uses block
1397 ;; comments, and pad with a space in that case.
1407 "Regexp to match the start of a comment plus everything up to its body.
1408 `comment-start-skip' is initialized from this."
1409 ;; Default: Allow the last char of the comment starter(s) to be
1410 ;; repeated, then allow any amount of horizontal whitespace.
1423 ;; Regexp matching any sequence that can start syntactic whitespace.
1424 ;; The only uncertain case is '#' when there are cpp directives.
1438 ;; Regexp matching any single character that might end syntactic whitespace.
1453 ;; Regexp matching an unterminated block comment that doesn't
1454 ;; contain line breaks, or nil in languages without block comments.
1455 ;; Does not contain a \| operator at the top level.
1459 ;; It's messy to cook together a regexp that matches anything
1460 ;; but c-block-comment-ender.
1468 "[^"
1469 ;; The quoting rules inside char classes are silly. :P
1478 "]"
1486 ;; Regexp matching a block comment that doesn't contain line breaks,
1487 ;; or nil in languages without block comments. The reason we don't
1488 ;; allow line breaks is to avoid going very far and risk running out
1489 ;; of regexp stack; this regexp is intended to handle only short
1490 ;; comments that might be put in the middle of limited constructs
1491 ;; like declarations. Does not contain a \| operator at the top
1492 ;; level.
1507 ;; Regexp matching a piece of syntactic whitespace that isn't a
1508 ;; sequence of simple whitespace characters. As opposed to
1509 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1510 ;; directives as syntactic whitespace.
1522 ;; Regexp matching syntactic whitespace, including possibly the
1523 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1524 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1525 ;; not contain a \| operator at the top level.
1533 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1537 ;; Regexp matching syntactic whitespace, which is at least one
1538 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1539 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1540 ;; not contain a \| operator at the top level.
1548 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1552 ;; Regexp matching syntactic whitespace without any line breaks. As
1553 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1554 ;; regard cpp directives as syntactic whitespace. Does not contain
1555 ;; a \| operator at the top level.
1563 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1567 ;; Regexp that matches when there is no syntactically significant
1568 ;; text before eol. Macros are regarded as syntactically
1569 ;; significant text here.
1571 ;; Match eol (possibly inside a block comment or preceded
1572 ;; by a line continuation backslash), or the beginning of a
1573 ;; line comment. Note: This has to be modified for awk
1574 ;; where line comments start with '#'.
1588 \f
1589 ;;; Defun handling.
1591 ;; The Emacs variables beginning-of-defun-function and end-of-defun-function
1592 ;; will be set so that commands like `mark-defun' and `narrow-to-defun' work
1593 ;; right. In older Emacsen, the key sequences C-M-a and C-M-e are, however,
1594 ;; bound directly to the CC Mode functions, allowing optimization for large n.
1595 ;; From Emacs 23, this isn't necessary any more, since n is passed to the two
1596 ;; functions.
1598 "Function to which beginning-of-defun-function will be set."
1599 t 'c-beginning-of-defun
1605 "Function to which end-of-defun-function will be set."
1606 t 'c-end-of-defun
1609 \f
1610 ;;; In-comment text handling.
1613 "Regexp to append to `paragraph-start'."
1614 t "$"
1620 "Regexp to append to `paragraph-separate'."
1621 t "$"
1625 \f
1626 ;;; Keyword lists.
1628 ;; Note: All and only all language constants containing keyword lists
1629 ;; should end with "-kwds"; they're automatically collected into the
1630 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1633 "Primitive type keywords. As opposed to the other keyword lists, the
1634 keywords listed here are fontified with the type face instead of the
1635 keyword face.
1637 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1638 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1639 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1640 will be handled.
1642 Do not try to modify this list for end user customizations; the
1643 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1644 the appropriate place for that."
1653 ;; Objective-C extends C, but probably not the new stuff in C99.
1660 ;; In CORBA PSDL:
1661 "ref"
1662 ;; The following can't really end a type, but we have to specify them
1663 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1664 ;; doesn't matter that much.
1667 ;; used as a builtin type.
1672 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1677 "Keywords that might act as prefixes for primitive types. Assumed to
1678 be a subset of `c-primitive-type-kwds'."
1679 t nil
1682 ;; In CORBA PSDL:
1687 of a variable declaration."
1692 ;; Adorned regexp matching `c-typedef-kwds'.
1697 "Keywords followed by a parenthesized expression, which stands for
1698 the type of that expression."
1699 t nil
1704 ;; Adorned regexp matching `c-typeof-kwds'.
1709 "Keywords where the following name - if any - is a type name, and
1710 where the keyword together with the symbol works as a type in
1711 declarations.
1713 Note that an alternative if the second part doesn't hold is
1714 `c-type-list-kwds'. Keywords on this list are typically also present
1715 on one of the `*-decl-kwds' lists."
1716 t nil
1722 ;; Adorned regexp matching `c-type-prefix-kwds'.
1727 "Type modifier keywords. These can occur almost anywhere in types
1728 but they don't build a type of themselves. Unlike the keywords on
1729 `c-primitive-type-kwds', they are fontified with the keyword face and
1730 not the type face."
1731 t nil
1737 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1738 ;; languages without such keywords.
1744 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1745 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1755 ;; All keywords that can start a type (i.e. are either a type prefix
1756 ;; or a complete type).
1763 "Keywords introducing declarations where the following block (if any)
1764 contains another declaration level that should be considered a class.
1766 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1767 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1768 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1769 will be handled.
1771 Note that presence on this list does not automatically treat the
1772 following identifier as a type; the keyword must also be present on
1773 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1774 t nil
1782 ;; In CORBA PSDL:
1784 ;; In CORBA CIDL:
1789 ;; Regexp matching the start of a class.
1794 "Keywords introducing declarations where the following block (if
1795 any) is a brace list.
1797 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1798 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1799 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1800 will be handled."
1805 ;; Regexp matching the start of declarations where the following
1806 ;; block is a brace list.
1811 "Keywords where the following block (if any) contains another
1812 declaration level that should not be considered a class. For every
1813 keyword here, CC Mode will add a set of special syntactic symbols for
1815 `foo-open', `foo-close', and `infoo' symbols.
1817 The intention is that this category should be used for block
1818 constructs that aren't related to object orientation concepts like
1819 classes (which thus also include e.g. interfaces, templates,
1820 contracts, structs, etc). The more pragmatic distinction is that
1821 while most want some indentation inside classes, it's fairly common
1822 that they don't want it in some of these constructs, so it should be
1823 simple to configure that differently from classes. See also
1824 `c-class-decl-kwds'.
1826 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1827 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1828 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1829 will be handled."
1830 t nil
1834 ;; In CORBA CIDL:
1838 ;; Regexp matching the start of blocks besides classes that contain
1839 ;; another declaration level.
1848 'inextern-lang
1851 "Alist associating keywords in c-other-decl-block-decl-kwds with
1855 "Keywords introducing declarations where the identifier(s) being
1856 declared are types.
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 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1863 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1864 ;; {...}").
1867 ;; Languages that have a "typedef" construct.
1870 ;; Unlike most other languages, exception names are not handled as
1871 ;; types in IDL since they only can occur in "raises" specs.
1879 "Keywords introducing declarations where the \(first) identifier
1880 \(declarator) follows directly after the keyword, without any type.
1882 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1883 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1884 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1885 will be handled."
1886 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1887 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1888 ;; {...}").
1892 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1893 ;; `c-type-list-kwds' for IDL.
1896 ;; In CORBA PSDL:
1898 ;; In CORBA CIDL:
1904 "Keywords that can prefix normal declarations of identifiers
1905 \(and typically act as flags). Things like argument declarations
1906 inside function headers are also considered declarations in this
1907 sense.
1909 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1910 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1911 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1912 will be handled."
1913 t nil
1918 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1922 ;; In CORBA PSDL:
1924 ;; In CORBA CIDL:
1926 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1933 "Keywords that can start or prefix any declaration level construct,
1934 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1935 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1936 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1938 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1939 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1940 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1941 will be handled."
1942 t nil
1948 "Keywords that always start declarations, wherever they occur.
1949 This can be used for declarations that aren't recognized by the normal
1950 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1951 t nil
1952 ;; Classes can be declared anywhere in a Pike expression.
1956 "Keywords that can occur anywhere in a declaration level construct.
1957 This is used for self-contained things that can be tacked on anywhere
1958 on a declaration and that should be ignored to be able to recognize it
1959 correctly. Typical cases are compiler extensions like
1962 __declspec(noreturn) void foo();
1963 class __declspec(dllexport) classname {...};
1964 void foo() __attribute__((noreturn));
1966 Note that unrecognized plain symbols are skipped anyway if they occur
1967 before the type, so such things are not necessary to mention here.
1968 Mentioning them here is necessary only if they can occur in other
1969 places, or if they are followed by a construct that must be skipped
1971 examples above). In the last case, they alse need to be present on
1972 one of `c-type-list-kwds', `c-ref-list-kwds',
1973 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1974 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1975 ;; NB: These are currently not recognized in all parts of a
1976 ;; declaration. Specifically, they aren't recognized in the middle
1977 ;; of multi-token types, inside declarators, and between the
1978 ;; identifier and the arglist paren of a function declaration.
1979 ;;
1980 ;; FIXME: This ought to be user customizable since compiler stuff
1981 ;; like this usually is wrapped in project specific macros. (It'd
1982 ;; of course be even better if we could cope without knowing this.)
1983 t nil
1985 "__attribute__"
1986 ;; MSVC extension.
1990 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1995 ;; All keywords that can occur in the preamble of a declaration.
1996 ;; They typically occur before the type, but they are also matched
1997 ;; after presumptive types since we often can't be sure that
1998 ;; something is a type or just some sort of macro in front of the
1999 ;; declaration. They might be ambiguous with types or type
2000 ;; prefixes.
2013 ;; Adorned regexp of `c-prefix-spec-kwds'.
2019 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
2020 ;; ambiguous with types or type prefixes. These are the keywords (like
2021 ;; extern, namespace, but NOT template) that can modify a declaration.
2030 ;; Keywords that can occur after argument list of a function header
2031 ;; declaration, i.e. in the "K&R region".
2036 ;; Adorned regexp matching all keywords that can't appear at the
2037 ;; start of a declaration.
2052 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2053 ;; This variable is intended for use in c-beginning-of-statement-1.
2063 "Access protection label keywords in classes."
2064 t nil
2069 "Keywords introducing declarations that can contain a block which
2072 like that, it ends with the following ';' and not right away.
2074 The keywords on list are assumed to also be present on one of the
2075 `*-decl-kwds' lists."
2076 t nil
2081 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2082 ;; languages without such constructs.
2089 "Keywords introducing extra declaration specifiers in the region
2091 declarations."
2092 t nil
2095 "supports"
2096 ;; In CORBA PSDL:
2100 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2106 "Keywords that may be followed by a nonsymbol sexp before whatever
2107 construct it's part of continues."
2108 t nil
2112 "Keywords that may be followed by a comma separated list of type
2113 identifiers, where each optionally can be prefixed by keywords. (Can
2114 also be used for the special case when the list can contain only one
2115 element.)
2117 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2118 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2119 There's also no reason to add keywords that prefixes a normal
2120 declaration consisting of a type followed by a declarator (list), so
2121 the keywords on `c-modifier-kwds' should normally not be listed here
2122 either.
2124 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2125 or variable identifier (that's being defined)."
2126 t nil
2131 ;; In CORBA PSDL:
2136 "Keywords that may be followed by a comma separated list of
2137 reference (i.e. namespace/scope/module) identifiers, where each
2138 optionally can be prefixed by keywords. (Can also be used for the
2139 special case when the list can contain only one element.) Assumed to
2140 be mutually exclusive with `c-type-list-kwds'.
2142 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2143 or variable identifier (that's being defined)."
2144 t nil
2148 ;; In CORBA CIDL:
2153 "Keywords that may be followed (not necessarily directly) by a colon
2154 and then a comma separated list of type identifiers, where each
2155 optionally can be prefixed by keywords. (Can also be used for the
2156 special case when the list can contain only one element.)"
2157 t nil
2160 ;; In CORBA PSDL:
2164 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2165 forward to the colon. The end of the match is assumed to be directly
2167 regexp if `c-colon-type-list-kwds' isn't nil."
2169 ;; Disallow various common punctuation chars that can't come
2170 ;; before the ":" that starts the inherit list after "class"
2171 ;; or "struct" in C++. (Also used as default for other
2172 ;; languages.)
2177 "Keywords that may be followed by a parenthesis expression that doesn't
2178 contain type identifiers."
2179 t nil
2181 "__attribute__"
2182 ;; MSVC extension.
2186 "Keywords that may be followed by a parenthesis expression containing
2187 type identifiers separated by arbitrary tokens."
2188 t nil
2200 "Keywords that may be followed by an angle bracket expression
2202 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2203 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2204 if this isn't nil."
2205 t nil
2208 ;; In CORBA PSDL:
2212 "Keywords that can be followed by a C++ style template arglist; see
2213 `c-recognize-<>-arglists' for details. That language constant is
2214 assumed to be set if this isn't nil."
2215 t nil
2220 ;; All keywords that can be followed by an angle bracket sexp.
2226 ;; Adorned regexp matching keywords that can be followed by an angle
2227 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2232 "Keywords that may be followed by a brace block containing a comma
2233 separated list of identifier definitions, i.e. like the list of
2234 identifiers that follows the type in a normal declaration."
2238 "Statement keywords followed directly by a substatement."
2243 idl nil)
2246 ;; Regexp matching the start of any statement followed directly by a
2247 ;; substatement (doesn't match a bare block, however).
2252 "Statement keywords optionally followed by a paren sexp.
2253 Keywords here should also be in `c-block-stmt-1-kwds'."
2254 t nil
2258 ;; Regexp matching the start of a statement which may be followed by a
2259 ;; paren sexp and will then be followed by a substatement.
2264 "Statement keywords followed by a paren sexp and then by a substatement."
2269 idl nil
2274 ;; Regexp matching the start of any statement followed by a paren sexp
2275 ;; and then by a substatement.
2280 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2286 ;; Regexp matching the start of any statement that has a
2287 ;; substatement (except a bare block). Nil in languages that
2288 ;; don't have such constructs.
2297 "Statement keywords followed by an expression or nothing."
2300 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2302 idl nil
2309 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2314 "Statement keywords followed by a parenthesis expression that
2315 nevertheless contains a list separated with ';' and not ','."
2317 idl nil)
2320 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2325 "Statement keywords followed by an assembler expression."
2326 t nil
2330 ;; Regexp matching the start of an assembler statement. Nil in
2331 ;; languages that don't support that.
2340 awk nil)
2343 ;; Adorned regexp matching any "case"-like keyword.
2348 "Keywords introducing colon terminated labels in blocks."
2352 ;; Adorned regexp matching any keyword that introduces a label.
2357 "Keywords that might be followed by a label identifier."
2361 idl nil
2362 awk nil)
2365 "Keywords for constants."
2366 t nil
2375 "Keywords besides constants and operators that start primary expressions."
2376 t nil
2383 ;; Keywords that can occur anywhere in expressions. Built from
2384 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2388 t
2393 "Keywords that start lambda constructs, i.e. function definitions in
2394 expressions."
2395 t nil
2399 "Keywords that start constructs followed by statement blocks which can
2400 be used in expressions \(the gcc extension for this in C and C++ is
2401 handled separately by `c-recognize-paren-inexpr-blocks')."
2402 t nil
2406 "Keywords that can start classes inside expressions."
2407 t nil
2412 "Keywords that can start brace list blocks inside expressions.
2413 Note that Java specific rules are currently applied to tell this from
2414 `c-inexpr-class-kwds'."
2415 t nil
2419 ;; Regexp matching the start of a brace list in an expression, or
2420 ;; nil in languages that don't have such things. This should not
2421 ;; match brace lists recognized through `c-special-brace-lists'.
2428 ;; Regexp matching keywords in any construct that contain another
2429 ;; declaration level, i.e. that isn't followed by a function block
2430 ;; or brace list. When the first submatch matches, it's an
2431 ;; unambiguous construct, otherwise it's an ambiguous match that
2432 ;; might also be the return type of a function declaration.
2450 "Keywords that can introduce bitfields."
2451 t nil
2455 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2456 ;; languages without bitfield support.
2457 t nil
2462 "Keywords not accounted for by any other `*-kwds' language constant."
2463 t nil
2465 ;; In CORBA CIDL: (These are declaration keywords that never
2466 ;; can start a declaration.)
2469 \f
2470 ;;; Constants built from keywords.
2472 ;; Note: No `*-kwds' language constants may be defined below this point.
2476 ;; List of all the language constants that contain keyword lists.
2481 ;; Make the list of globally interned symbols
2482 ;; instead of ones interned in `c-lang-constants'.
2484 c-lang-constants)
2485 list)))
2488 ;; All keywords as a list.
2493 c-kwds-lang-consts)
2494 nil))
2498 ;; All keywords as an adorned regexp.
2503 ;; An alist with all the keywords in the cars. The cdr for each
2504 ;; keyword is a list of the symbols for the `*-kwds' lists that
2505 ;; contains it.
2511 c-kwds-lang-consts))))
2512 lang-const kwd-list kwd
2513 result-alist elem)
2525 result-alist))
2528 ;; An obarray containing all keywords as symbols. The property list
2529 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2530 ;; lists it's a member of.
2531 ;;
2532 ;; E.g. to see whether the string str contains a keyword on
2533 ;; `c-class-decl-kwds', one can do like this:
2534 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2535 ;; Which preferably is written using the associated functions in
2536 ;; cc-engine:
2537 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2539 ;; The obarray is not stored directly as a language constant since
2540 ;; the printed representation for obarrays used in .elc files isn't
2541 ;; complete.
2544 kwd lang-const-list
2551 ;; Emacs has an odd bug that causes `mapcan' to fail
2552 ;; with unintelligible errors. (XEmacs works.)
2553 ;;(mapcan (lambda (lang-const)
2554 ;; (list lang-const t))
2555 ;; lang-const-list)
2558 lang-const-list))))
2559 obarray))
2562 ;; Adorned regexp matching all keywords that should be fontified
2563 ;; with the keywords face. I.e. that aren't types or constants.
2573 ;; Regexp matching the start of any primary expression, i.e. any
2574 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2575 ;; exclude keywords; they are excluded afterwards unless the second
2576 ;; submatch matches. If the first but not the second submatch
2577 ;; matches then it is an ambiguous primary expression; it could also
2578 ;; be a match of e.g. an infix operator. (The case with ambiguous
2579 ;; keyword operators isn't handled.)
2585 ;; Filter out the special case prefix
2586 ;; operators that are close parens.
2591 t
2597 postfix-if-paren
2598 left-assoc
2599 right-assoc
2600 right-assoc-sequence)
2601 t))
2604 in-or-postfix-ops
2607 in-or-postfix-ops
2612 ;; Take out all symbol class operators from `prefix-ops' and make the
2613 ;; first submatch from them together with `c-primary-expr-kwds'.
2620 ;; Match all ambiguous operators.
2627 ;; Now match all other symbols.
2631 ;; The chars that can start integer and floating point
2632 ;; constants.
2636 ;; The unambiguous operators from `prefix-ops'.
2642 ;; Match string and character literals.
2649 \f
2650 ;;; Additional constants for parser-level constructs.
2653 "Regexp matching a keyword that is followed by a colon, where
2654 the whole construct can precede a declaration.
2662 "Regexp matching something that might precede a declaration, cast or
2663 label, such as the last token of a preceding statement or declaration.
2664 This is used in the common situation where a declaration or cast
2665 doesn't start with any specific token that can be searched for.
2667 The regexp should not match bob; that is done implicitly. It can't
2668 require a match longer than one token. The end of the token is taken
2669 to be at the end of the first submatch, which is assumed to always
2670 match. It's undefined whether identifier syntax (see
2671 `c-identifier-syntax-table') is in effect or not. This regexp is
2672 assumed to be a superset of `c-label-prefix-re' if
2673 `c-recognize-colon-labels' is set.
2675 Besides this, `c-decl-start-kwds' is used to find declarations.
2677 Note: This variable together with `c-decl-start-re' and
2679 declaration/cast/label starts. I.e. they might produce more matches
2680 but should not miss anything (or else it's necessary to use text
2681 properties - see the next note). Wherever they match, the following
2682 construct is analyzed to see if it indeed is a declaration, cast or
2683 label. That analysis is not cheap, so it's important that not too
2684 many false matches are triggered.
2686 Note: If a declaration/cast/label start can't be detected with this
2687 variable, it's necessary to use the `c-type' text property with the
2688 value `c-decl-end' on the last char of the last token preceding the
2689 declaration. See the comment blurb at the start of cc-engine.el for
2690 more info."
2692 ;; We match a sequence of characters to skip over things like \"};\"
2693 ;; more quickly. We match ")" in C for K&R region declarations, and
2694 ;; in all languages except Java for when a cpp macro definition
2695 ;; begins with a declaration.
2698 ;; Match "<" in C++ to get the first argument in a template arglist.
2699 ;; In that case there's an additional check in `c-find-decl-spots'
2700 ;; that it got open paren syntax. Match ":" to aid in picking up
2701 ;; "public:", etc. This involves additional checks in
2702 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2703 ;; or labels.
2705 ;; Additionally match the protection directives in Objective-C.
2706 ;; Note that this doesn't cope with the longer directives, which we
2707 ;; would have to match from start to end since they don't end with
2708 ;; any easily recognized characters.
2712 ;; Pike is like C but we also match "[" for multiple value
2713 ;; assignments and type casts.
2719 "Regexp matching the start of any declaration, cast or label.
2720 It's used on the token after the one `c-decl-prefix-re' matched. This
2721 regexp should not try to match those constructs accurately as it's
2722 only used as a sieve to avoid spending more time checking other
2723 constructs."
2728 ;; Regexp matching something that might precede or start a
2729 ;; declaration, cast or label.
2730 ;;
2731 ;; If the first submatch matches, it's taken to match the end of a
2732 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2733 ;; It's built from `c-decl-prefix-re'.
2734 ;;
2735 ;; If the first submatch did not match, the match of the whole
2736 ;; regexp is taken to be at the first token in the declaration.
2737 ;; `c-decl-start-re' is not checked in this case.
2738 ;;
2739 ;; Design note: The reason the same regexp is used to match both
2740 ;; tokens that precede declarations and start them is to avoid an
2741 ;; extra regexp search from the previous declaration spot in
2742 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2743 ;; that it finds all declaration/cast/label starts in approximately
2744 ;; linear order, so we can't do the searches in two separate passes.
2755 ;; List containing the paren characters that can open a cast, or nil in
2756 ;; languages without casts.
2764 "List of syntactically relevant characters that never can occur before
2765 the open brace in any construct that contains a brace block, e.g. in
2768 class Foo: public Bar {int x();} a, *b;
2770 If parens can occur, the chars inside those aren't filtered with this
2771 list.
2773 '<' and '>' should be disallowed even if angle bracket arglists can
2774 occur. That since the search function needs to stop at them anyway to
2775 ensure they are given paren syntax.
2777 This is used to skip backward from the open brace to find the region
2780 possible for good performance."
2782 ;; Default to all chars that only occurs in nonsymbol tokens outside
2783 ;; identifiers.
2789 t
2790 t
2794 op pos)
2797 res))))
2799 ;; Allow cpp operations (where applicable).
2805 ;; Allow ':' for inherit list starters.
2809 ;; Allow ',' for multiple inherits.
2813 ;; Allow parentheses for anonymous inner classes in Java and class
2814 ;; initializer lists in Pike.
2818 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2823 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2824 ;; for `c-syntactic-skip-backward'.
2829 "Regexp matching any declarator operator that might precede the
2832 The end of the first submatch is taken as the end of the operator.
2833 Identifier syntax is in effect when this is matched \(see
2834 `c-identifier-syntax-table')."
2837 ;; Default to a regexp that never matches.
2839 ;; Check that there's no "=" afterwards to avoid matching tokens
2840 ;; like "*=".
2842 "[*\(]"
2848 "[*\(&]"
2853 ;; If this matches there's special treatment in
2854 ;; `c-font-lock-declarators' and
2855 ;; `c-font-lock-declarations' that check for a
2856 ;; complete name followed by ":: *".
2866 "Regexp matching the declarator operators that might follow after the
2869 it matches an open paren of some kind, the type declaration check
2870 continues at the corresponding close paren, otherwise the end of the
2871 first submatch is taken as the end of the operator. Identifier syntax
2872 is in effect when this is matched (see `c-identifier-syntax-table')."
2873 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2874 ;; function argument list parenthesis.
2882 "[\)\[\(]"
2886 ;; "throw" in `c-type-modifier-kwds' is followed
2887 ;; by a parenthesis list, but no extra measures
2888 ;; are necessary to handle that.
2899 "This regexp is matched after a declarator expression where
2900 `c-type-decl-suffix-key' has matched. If it matches then the
2901 construct is taken as a declaration. It's typically used to match the
2902 beginning of a function body or whatever might occur after the
2903 function header in a function declaration or definition. It's
2904 undefined whether identifier syntax (see `c-identifier-syntax-table')
2905 is in effect or not.
2910 t "{"
2911 ;; If K&R style declarations should be recognized then one could
2912 ;; consider to match the start of any symbol since we want to match
2913 ;; the start of the first declaration in the "K&R region". That
2914 ;; could however produce false matches on code like "FOO(bar) x"
2915 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2916 ;; on the other heuristics in that case.
2918 ;; Add on the keywords in `c-postfix-spec-kwds'.
2923 ;; Also match the colon that starts a base class initializer list in
2924 ;; C++. That can be confused with a function call before the colon
2925 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2926 ;; match before such a thing (as a declaration-level construct;
2927 ;; matches inside arglist contexts are already excluded).
2934 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2935 ;; matches ";" and ",".
2944 end of the operator. nil in languages without such operators. It's
2945 undefined whether identifier syntax (see `c-identifier-syntax-table')
2946 is in effect or not."
2947 t nil
2953 "Regexp matching operators that might follow after a type, or nil in
2954 languages that don't have such operators. The end of the first
2955 submatch is taken as the end of the operator. This should not match
2956 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2957 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2958 is in effect or not."
2959 t nil
2965 ;; Regexp matching the known type identifiers. This is initialized
2966 ;; from the type keywords and `*-font-lock-extra-types'. The first
2967 ;; submatch is the one that matches the type. Note that this regexp
2968 ;; assumes that symbol constituents like '_' and '$' have word
2969 ;; syntax.
2978 extra-types)))
2984 extra-types))))
2989 plain-strings)))
2990 regexp-strings)
2995 "List of open- and close-chars that makes up a pike-style brace list,
2997 list."
2998 t nil
3003 "Non-nil means K&R style argument declarations are valid."
3004 t nil
3005 c t)
3009 "Non-nil means function declarations without return type should be
3010 recognized. That can introduce an ambiguity with parenthesized macro
3011 calls before a brace block. This setting does not affect declarations
3012 that are preceded by a declaration starting keyword, so
3013 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
3014 t nil
3020 "Non-nil means C++ style template arglists should be handled. More
3021 specifically, this means a comma separated list of types or
3023 identifier or one of the keywords on `c-<>-type-kwds' or
3024 `c-<>-arglist-kwds'. If there's an identifier before then the whole
3025 expression is considered to be a type."
3029 ; generics is not yet coded in CC Mode.
3033 "Non-nil means that an enum structure can contain declarations."
3034 t nil
3035 java t)
3039 "Non-nil means that parenthesis style initializers exist,
3040 i.e. constructs like
3042 Foo bar (gnu);
3044 in addition to the more classic
3046 Foo bar = gnu;"
3047 t nil
3052 "Non-nil to recognize gcc style in-expression blocks,
3053 i.e. compound statements surrounded by parentheses inside expressions."
3054 t nil
3060 ;; Regexp matching the start of angle bracket arglists in languages
3061 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3062 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3063 ;; assumed to surround the preceding symbol. The whole match is
3064 ;; assumed to end directly after the opening "<".
3074 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3075 ;; parens. The first submatch is assumed to surround
3076 ;; `c-opt-<>-arglist-start'.
3085 ;; Regexp matching the beginning of a declaration specifier in the
3086 ;; region between the header and the body of a declaration.
3087 ;;
3088 ;; TODO: This is currently not used uniformly; c++-mode and
3089 ;; java-mode each have their own ways of using it.
3090 t nil
3103 That includes labels in code and access keys in classes. This does
3104 not apply to labels recognized by `c-label-kwds' and
3105 `c-opt-extra-label-key'."
3106 t nil
3112 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3113 a generic colon label. Not used if `c-recognize-colon-labels' is
3114 nil."
3120 "Regexp matching things that can't occur in generic colon labels,
3121 neither in a statement nor in a declaration context. The regexp is
3122 tested at the beginning of every sexp in a suspected label,
3125 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3131 ;; Don't allow string literals, except in AWK. Character constants are OK.
3134 ;; Also check for open parens in C++, to catch member init lists in
3135 ;; constructors. We normally allow it so that macros with arguments
3136 ;; work in labels.
3141 "Regexp matching things that can't occur two symbols before a colon in
3149 "Optional regexp matching labels.
3150 Normally, labels are detected according to `c-nonlabel-token-key',
3151 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3152 be used if there are additional labels that aren't recognized that
3153 way."
3154 t nil
3159 ;; Regexp describing friend declarations classes, or nil in
3160 ;; languages that don't have such things.
3161 ;;
3162 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3163 ;; template skipping isn't done properly. This will disappear soon.
3164 t nil
3169 "<.+>"
3171 "friend"
3176 ;; Special regexp to match the start of Objective-C methods. The
3177 ;; first submatch is assumed to end after the + or - key.
3178 t nil
3180 ;; TODO: Ought to use a better method than anchoring on bol.
3185 "([^\)]*)"
3192 ;; Must be set in buffers where the `c-type' text property might be
3193 ;; used with the value `c-decl-end'.
3194 ;;
3195 ;; `c-decl-end' is used to mark the ends of labels and access keys
3196 ;; to make interactive refontification work better.
3199 ;; `c-decl-end' is used to mark the end of the @-style directives in
3200 ;; Objective-C.
3201 objc t)
3204 \f
3205 ;;; Wrap up the `c-lang-defvar' system.
3207 ;; Compile in the list of language variables that has been collected
3208 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3209 ;; first element of each is nil.
3213 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3214 ;; These are typically standard emacs variables such as `comment-start'.
3222 "Create a function that initializes all the language dependent variables
3223 for the given mode.
3225 This function should be evaluated at compile time, so that the
3226 function it returns is byte compiled with all the evaluated results
3227 from the language constants. Use the `c-init-language-vars' macro to
3228 accomplish that conveniently."
3234 ;; No need to byte compile this lambda since the byte compiler is
3235 ;; smart enough to detect the `funcall' construct in the
3236 ;; `c-init-language-vars' macro below and compile it all straight
3237 ;; into the function that contains `c-init-language-vars'.
3240 ;; This let sets up the context for `c-mode-var' and similar
3241 ;; that could be in the result from `c--macroexpand-all'.
3243 current-var source-eval)
3250 ;; `c-lang-const' will expand to the evaluated
3251 ;; constant immediately in `c--macroexpand-all'
3252 ;; below.
3258 ;; Note: The following `append' copies the
3259 ;; first argument. That list is small, so
3260 ;; this doesn't matter too much.
3264 ;; This diagnostic message isn't useful for end
3265 ;; users, so it's disabled.
3266 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3267 ;; (message ,(concat "%s compiled with CC Mode %s "
3268 ;; "but loaded with %s - evaluating "
3269 ;; "language constants from source")
3270 ;; ',mode ,c-version c-version)
3271 ;; (put ',mode 'c-has-warned-lang-consts t))
3284 current-var
3287 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3290 err)
3293 ;; Being evaluated from source. Always use the dynamic method to
3294 ;; work well when `c-lang-defvar's in this file are reevaluated
3295 ;; interactively.
3301 current-var)
3313 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3314 current-var err)
3316 ))
3319 "Initialize all the language dependent variables for the given mode.
3320 This macro is expanded at compile time to a form tailored for the mode
3321 in question, so MODE must be a constant. Therefore MODE is not
3322 evaluated and should not be quoted."
3325 \f
3328 ;;; cc-langs.el ends here