| blob | 5b670833d45bc8bf1f133d079dcd99eba6ec4aad |
1 ;;; cc-langs.el --- language specific settings for CC Mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2015 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 c-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)))
406 ;; The next eval remove a superfluous ' from '(lambda. This
407 ;; gets rid of compilation warnings.
411 ;; A variant of the standard syntax table which is used to find matching
412 ;; "<"s and ">"s which have been marked as parens using syntax table
413 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
414 ;; non-paren syntax here. so that the list commands will work on "< ... >"
415 ;; even when there's unbalanced other parens inside them.
416 ;;
417 ;; This variable is nil for languages which don't have template stuff.
420 ;(if (c-lang-const c-recognize-<>-arglists)
428 table))))
431 ;; See comment in `c++template-syntax-table' about the next `eval'.
435 "A list that describes the modifications that should be done to the
436 mode syntax table to get a syntax table that matches all identifiers
437 and keywords as words.
439 The list is just like the one used in `font-lock-defaults': Each
440 element is a cons where the car is the character to modify and the cdr
441 the new syntax, as accepted by `modify-syntax-entry'."
442 ;; The $ character is not allowed in most languages (one exception
443 ;; is Java which allows it for legacy reasons) but we still classify
444 ;; it as an identifier character since it's often used in various
445 ;; machine generated identifiers.
456 mod)
461 table)
462 "Syntax table built on the mode syntax table but additionally
463 classifies symbol constituents like `_' and `$' as word constituents,
467 ;; For documentation see the following c-lang-defvar of the same name.
468 ;; The value here may be a list of functions or a single function.
469 t nil
471 c-before-change-check-<>-operators
472 c-invalidate-macro-cache)
474 ;; java 'c-before-change-check-<>-operators
479 fs
481 "If non-nil, a list of functions called from c-before-change-hook.
482 Typically these will record enough state to allow
483 `c-before-font-lock-function' to extend the region to fontify,
484 and may do such things as removing text-properties which must be
485 recalculated.
487 These functions will be run in the order given. Each of them
488 takes 2 parameters, the BEG and END supplied to every
489 before-change function; on entry, the buffer will have been
490 widened and match-data will have been saved; point is undefined
491 on both entry and exit; the return value is ignored.
493 The functions are called even when font locking isn't enabled.
495 When the mode is initialized, the functions are called with
499 ;; For documentation see the following c-lang-defvar of the same name.
500 ;; The value here may be a list of functions or a single function.
501 t 'c-change-expand-fl-region
503 c-change-expand-fl-region)
508 fs
510 "If non-nil, a list of functions called just before font locking.
511 Typically they will extend the region about to be fontified \(see
512 below) and will set `syntax-table' text properties on the region.
514 These functions will be run in the order given. Each of them
515 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
516 after-change function; point is undefined on both entry and exit;
517 on entry, the buffer will have been widened and match-data will
518 have been saved; the return value is ignored.
520 The functions may extend the region to be fontified by setting the
521 buffer local variables c-new-BEG and c-new-END.
523 The functions are called even when font locking is disabled.
525 When the mode is initialized, these functions are called with
529 awk nil
531 ;; For documentation see the following c-lang-defvar of the same name.
532 ;; The value here may be a list of functions or a single function.
536 fs
538 "If non-nil, a list of functions called just before context (or
539 other non-change) fontification is done. Typically they will
540 extend the region.
542 These functions will be run in the order given. Each of them
543 takes 2 parameters, the BEG and END of the region to be
544 fontified. Point is undefined on both entry and exit. On entry,
545 the buffer will have been widened and match-data will have been
546 saved; the return value is a cons of the adjusted
549 \f
550 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
553 Such a function takes one optional parameter, a buffer position (defaults to
554 point), and returns nil or t. This variable contains nil for languages which
555 don't have EOL terminated statements. "
556 t nil
563 The (admittedly kludgy) purpose of such a function is to prevent an infinite
564 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
565 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
566 even indirectly. This variable contains nil for languages which don't have
567 EOL terminated statements."
568 t nil
574 \f
575 ;;; Lexer-level syntax (identifiers, tokens etc).
578 "Whether the language has bitfield declarations."
579 t nil
585 a “long character”. In particular, this recognizes forms of constant
586 which `c-backward-sexp' needs to be called twice to move backwards over."
587 t nil
589 ;; FIXME!!! Extend this to cover strings, if needed. 2008-04-11
593 "Regexp that matches the start of a symbol, i.e. any identifier or
595 operator at the top level."
603 "Set of characters that can be part of a symbol.
604 This is of the form that fits inside [ ] in a regexp."
605 ;; Pike note: With the backquote identifiers this would include most
606 ;; operator chars too, but they are handled with other means instead.
612 "Regexp matching identifiers and keywords (with submatch 0). Assumed
613 to match if `c-symbol-start' matches on the same position."
617 ;; Use the value from C here since the operator backquote is
618 ;; covered by the other alternative.
626 ;; Number of regexp grouping parens in `c-symbol-key'.
630 "This is the set of chars that can't be part of a symbol, i.e. the
631 negation of `c-symbol-chars'."
636 "Regexp that matches any character that can't be part of a symbol.
637 It's usually appended to other regexps to avoid matching a prefix.
638 It's assumed to not contain any submatchers."
639 ;; The same thing regarding Unicode identifiers applies here as to
640 ;; `c-symbol-key'.
644 "The operators that make up fully qualified identifiers. nil in
645 languages that don't have such things. See `c-operators' for a
646 description of the format. Binary operators can concatenate symbols,
650 This value is by default merged into `c-operators'."
651 t nil
655 ;; Java has "." to concatenate identifiers but it's also used for
656 ;; normal indexing. There's special code in the Java font lock
657 ;; rules to fontify qualified identifiers based on the standard
658 ;; naming conventions. We still define "." here to make
659 ;; `c-forward-name' move over as long names as possible which is
660 ;; necessary to e.g. handle throws clauses correctly.
669 ;; Appendable adorned regexp matching the operators that join
670 ;; symbols to fully qualified identifiers, or nil in languages that
671 ;; don't have such things.
672 ;;
673 ;; This was a docstring constant in 5.30. It still works but is now
674 ;; considered internal - change `c-identifier-ops' instead.
677 t)))
685 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
689 ;; Appendable adorned regexp matching operators that might precede
690 ;; an identifier and that are part of the identifier in that case.
691 ;; nil in languages without such things.
694 t)))
699 "Operators that can occur after a binary operator on `c-identifier-ops'
700 in identifiers. nil in languages that don't have such things.
702 Operators here should also have appropriate entries in `c-operators' -
703 it's not taken care of by default."
704 t nil
705 ;; '~' for destructors in C++, '*' for member pointers.
707 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
708 ;; in import declarations. (This will also match bogus things like
709 ;; "foo.*bar" but we don't bother.)
713 ;; Regexp that must match the token after
714 ;; `c-opt-identifier-concat-key' for it to be considered an
715 ;; identifier concatenation operator (which e.g. causes the
716 ;; preceding identifier to be fontified as a reference). Assumed to
717 ;; be a string if `c-opt-identifier-concat-key' is.
718 ;;
719 ;; This was a docstring constant in 5.30. It still works but is now
720 ;; considered internal - change `c-after-id-concat-ops' instead.
728 "Regexp that matches the start of an (optionally qualified) identifier.
729 It should also match all keywords. It's unspecified how far it
730 matches."
740 C++. It does not recognize the full range of syntactic whitespace
741 between the tokens; `c-forward-name' has to be used for that. It
742 should also not match identifiers containing parenthesis groupings,
744 ;; This regexp is more complex than strictly necessary to ensure
745 ;; that it can be matched with a minimum of backtracking.
766 ;; For flexibility, consider the symbol match
767 ;; optional if we've hit a
768 ;; `c-after-id-concat-ops' operator. This is
769 ;; also necessary to handle the "*" that can
770 ;; end import declaration identifiers in Java.
784 ;; This was a docstring constant in 5.30 but it's no longer used.
785 ;; It's only kept to avoid breaking third party code.
786 ;;
787 ;; Used to identify the submatch in `c-identifier-key' that
788 ;; surrounds the last symbol in the qualified identifier. It's a
789 ;; list of submatch numbers, of which the first that has a match is
790 ;; taken. It's assumed that at least one does when the regexp has
791 ;; matched.
792 t nil)
795 "Set if the language support backslash escaped newlines inside string
796 literals."
797 t nil
803 "Set if the language supports multiline string literals without escaped
804 newlines. If t, all string literals are multiline. If a character,
805 only literals where the open quote is immediately preceded by that
806 literal are multiline."
807 t nil
808 pike ?#)
813 "The symbol which starts preprocessor constructs when in the margin."
814 t "#"
819 "Regexp matching the prefix of a cpp directive in the languages that
820 normally use that macro preprocessor. Tested at bol or at boi.
822 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
823 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
829 "Regexp matching the prefix of a cpp directive anchored to BOL,
830 in the languages that have a macro preprocessor."
836 "Regexp matching the prefix of a cpp directive including the directive
837 name, or nil in languages without preprocessor support. The first
838 submatch surrounds the directive name."
842 ;; Pike, being a scripting language, recognizes hash-bangs too.
848 "List of cpp directives (without the prefix) that are followed by a
849 string message."
855 "List of cpp directives (without the prefix) that are followed by a
856 file name in angle brackets or quotes."
862 "Cpp directive (without the prefix) that is followed by a macro
863 definition, or nil if the language doesn't have any."
870 ;; Regexp matching everything up to the macro body of a cpp define, or the
871 ;; end of the logical line if there is none. Submatch 1 is the name of the
872 ;; macro. Set if c-opt-cpp-macro-define is.
877 ;; ^ ^ #defined name
883 ;; Regexp matching everything up to the end of the identifier defined
884 ;; by a cpp define.
893 "List of cpp directives (without the prefix) that are followed by an
894 expression."
899 "Regexp which matches the start of a CPP directive which contains an
900 expression, or nil if there aren't any in the language."
909 "List of functions in cpp expressions."
915 "List of all assignment operators."
921 idl nil)
924 "List describing all operators, along with their precedence and
925 associativity. The order in the list corresponds to the precedence of
926 the operators: The operators in each element are a group with the same
927 precedence, and the group has higher precedence than the groups in all
928 following elements. The car of each element describes the type of the
929 operator group, and the cdr is a list of the operator tokens in it.
930 The operator group types are:
932 `prefix' Unary prefix operators.
933 `postfix' Unary postfix operators.
934 `postfix-if-paren'
935 Unary postfix operators if and only if the chars have
936 parenthesis syntax.
937 `left-assoc' Binary left associative operators (i.e. a+b+c means (a+b)+c).
938 `right-assoc' Binary right associative operators (i.e. a=b=c means a=(b=c)).
939 `right-assoc-sequence'
940 Right associative operator that constitutes of a
941 sequence of tokens that separate expressions. All the
942 tokens in the group are in this case taken as
943 describing the sequence in one such operator, and the
944 order between them is therefore significant.
946 Operators containing a character with paren syntax are taken to match
947 with a corresponding open/close paren somewhere else. A postfix
948 operator with close paren syntax is taken to end a postfix expression
949 started somewhere earlier, rather than start a new one at point. Vice
950 versa for prefix operators with open paren syntax.
953 often are described as postfix operators are considered binary here,
954 since CC Mode treats every identifier as an expression."
956 ;; There's currently no code in CC Mode that exploits all the info
957 ;; in this variable; precedence, associativity etc are present as a
958 ;; preparation for future work.
960 ;; FIXME!!! C++11's "auto" operators "=" and "->" need to go in here
961 ;; somewhere. 2012-03-24.
972 ;; Primary.
981 ;; Postfix.
983 ;; The following need special treatment.
994 ;; Unary.
1001 ;; The following need special treatment.
1012 ;; Member selection.
1016 ;; Multiplicative.
1019 ;; Additive.
1022 ;; Shift.
1027 ;; Relational.
1032 ;; Equality.
1036 ;; Bitwise and.
1040 ;; Bitwise exclusive or.
1046 ;; Bitwise or.
1052 ;; Logical and.
1056 ;; Logical or.
1062 ;; Conditional.
1065 ;; Assignment.
1068 ;; Exception.
1072 ;; Sequence.
1075 ;; IDL got its own definition since it has a much smaller operator
1076 ;; set than the other languages.
1080 ;; Primary.
1082 ;; Unary.
1084 ;; Multiplicative.
1086 ;; Additive.
1088 ;; Shift.
1090 ;; And.
1092 ;; Xor.
1094 ;; Or.
1098 ;; The operators as a flat list (without duplicates).
1104 t nil
1113 ;; These work like identifiers in Pike.
1120 ;; Regexp tested after an "operator" token in C++.
1121 t nil
1127 "Regexp matching the token before the ones in
1128 `c-overloadable-operators' when operators are specified in their
1131 languages without operator functions or where the complete operator
1132 identifier is listed in `c-overloadable-operators'.
1134 This regexp is assumed to not match any non-operator identifier."
1135 t nil
1140 ;; Note: the following alias is an old name which was a mis-spelling. It has
1141 ;; been corrected above and throughout cc-engine.el. It will be removed at
1142 ;; some release very shortly in the future. ACM, 2006-04-14.
1148 "List of the tokens made up of characters in the punctuation or
1149 parenthesis syntax classes that have uses other than as expression
1150 operators."
1169 ;; List of all tokens in the punctuation and parenthesis syntax
1170 ;; classes.
1176 ;; List containing all chars not in the word, symbol or
1177 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1178 ;; parenthesis and string delimiter chars.
1180 ;; Only go through the chars in the printable ASCII range. No
1181 ;; language so far has 8-bit or widestring operators.
1187 list)))
1190 ;; Regexp matching all tokens in the punctuation and parenthesis
1191 ;; syntax classes. Note that this also matches ".", which can start
1192 ;; a float.
1195 t
1201 ;; Regexp matching all assignment operators and only them. The
1202 ;; beginning of the first submatch is used to detect the end of the
1203 ;; token, along with the end of the whole match.
1206 ;; Need special case for "=" since it's a prefix of "==".
1218 ;; Regexp matching all tokens containing "<" or ">" which are longer
1219 ;; than one char.
1222 t
1228 ;; Regexp matching the second and subsequent characters of all
1229 ;; multicharacter tokens that begin with "<".
1232 t
1239 ;; A list of second and subsequent characters of all multicharacter tokens
1240 ;; that begin with ">".
1242 t
1246 t
1251 ;; Regexp matching the second and subsequent characters of all
1252 ;; multicharacter tokens that begin with ">".
1258 ;; Regexp matching the second and subsequent characters of all
1259 ;; multicharacter tokens that begin with ">" except for those beginning with
1260 ;; ">>".
1265 t
1274 ;; The characters that should be considered to bound statements. To
1275 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1276 ;; begin with "^" to negate the set. If ? : operators should be
1277 ;; detected then the string must end with "?:".
1282 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1288 ;; Ops which signal C++11's new auto uses.
1289 t nil
1296 ;; Op used in the new C++11 auto function definition, indicating type.
1297 t nil
1302 \f
1303 ;;; Syntactic whitespace.
1306 "Regexp matching an ordinary whitespace character.
1308 ;; "\\s " is not enough since it doesn't match line breaks.
1312 ;; Number of regexp grouping parens in `c-simple-ws'.
1316 "String that starts line comments, or nil if such don't exist.
1317 Line comments are always terminated by newlines. At least one of
1318 `c-block-comment-starter' and this one is assumed to be set.
1320 Note that it's currently not enough to set this to support a new
1321 comment style. Other stuff like the syntax table must also be set up
1322 properly."
1323 t "//"
1328 "String that starts block comments, or nil if such don't exist.
1329 Block comments are ended by `c-block-comment-ender', which is assumed
1330 to be set if this is. At least one of `c-line-comment-starter' and
1331 this one is assumed to be set.
1333 Note that it's currently not enough to set this to support a new
1334 comment style. Other stuff like the syntax table must also be set up
1335 properly."
1336 t "/*"
1337 awk nil)
1340 "String that ends block comments, or nil if such don't exist.
1342 Note that it's currently not enough to set this to support a new
1343 comment style. Other stuff like the syntax table must also be set up
1344 properly."
1345 t "*/"
1346 awk nil)
1349 ;; Regexp to match the start of any type of comment.
1355 re)))
1359 ;; Regexp which matches the start of a block comment (if such exists in the
1360 ;; language)
1368 ;; Regexp which matches the start of a line comment (if such exists in the
1369 ;; language; it does in all 7 CC Mode languages).
1377 ;; Regexp to match the start of comments and string literals.
1386 "Regexp to match the start of documentation comments."
1388 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1396 "String that starts comments inserted with M-; etc.
1397 `comment-start' is initialized from this."
1398 ;; Default: Prefer line comments to block comments, and pad with a space.
1402 ;; In C we still default to the block comment style since line
1403 ;; comments aren't entirely portable.
1408 "String that ends comments inserted with M-; etc.
1409 `comment-end' is initialized from this."
1410 ;; Default: Use block comment style if comment-start uses block
1411 ;; comments, and pad with a space in that case.
1421 "Regexp to match the start of a comment plus everything up to its body.
1422 `comment-start-skip' is initialized from this."
1423 ;; Default: Allow the last char of the comment starter(s) to be
1424 ;; repeated, then allow any amount of horizontal whitespace.
1437 ;; Regexp matching any sequence that can start syntactic whitespace.
1438 ;; The only uncertain case is '#' when there are cpp directives.
1452 ;; Regexp matching any single character that might end syntactic whitespace.
1467 ;; Regexp matching an unterminated block comment that doesn't
1468 ;; contain line breaks, or nil in languages without block comments.
1469 ;; Does not contain a \| operator at the top level.
1473 ;; It's messy to cook together a regexp that matches anything
1474 ;; but c-block-comment-ender.
1482 "[^"
1483 ;; The quoting rules inside char classes are silly. :P
1492 "]"
1500 ;; Regexp matching a block comment that doesn't contain line breaks,
1501 ;; or nil in languages without block comments. The reason we don't
1502 ;; allow line breaks is to avoid going very far and risk running out
1503 ;; of regexp stack; this regexp is intended to handle only short
1504 ;; comments that might be put in the middle of limited constructs
1505 ;; like declarations. Does not contain a \| operator at the top
1506 ;; level.
1521 ;; Regexp matching a piece of syntactic whitespace that isn't a
1522 ;; sequence of simple whitespace characters. As opposed to
1523 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1524 ;; directives as syntactic whitespace.
1536 ;; Regexp matching syntactic whitespace, including possibly the
1537 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1538 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1539 ;; not contain a \| operator at the top level.
1547 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1551 ;; Regexp matching syntactic whitespace, which is at least one
1552 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1553 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1554 ;; not contain a \| operator at the top level.
1562 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1566 ;; Regexp matching syntactic whitespace without any line breaks. As
1567 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1568 ;; regard cpp directives as syntactic whitespace. Does not contain
1569 ;; a \| operator at the top level.
1577 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1581 ;; Regexp that matches when there is no syntactically significant
1582 ;; text before eol. Macros are regarded as syntactically
1583 ;; significant text here.
1585 ;; Match eol (possibly inside a block comment or preceded
1586 ;; by a line continuation backslash), or the beginning of a
1587 ;; line comment. Note: This has to be modified for awk
1588 ;; where line comments start with '#'.
1602 \f
1603 ;;; Defun handling.
1605 ;; The Emacs variables beginning-of-defun-function and end-of-defun-function
1606 ;; will be set so that commands like `mark-defun' and `narrow-to-defun' work
1607 ;; right. In older Emacsen, the key sequences C-M-a and C-M-e are, however,
1608 ;; bound directly to the CC Mode functions, allowing optimization for large n.
1609 ;; From Emacs 23, this isn't necessary any more, since n is passed to the two
1610 ;; functions.
1612 "Function to which beginning-of-defun-function will be set."
1613 t 'c-beginning-of-defun
1619 "Function to which end-of-defun-function will be set."
1620 t 'c-end-of-defun
1623 \f
1624 ;;; In-comment text handling.
1627 "Regexp to append to `paragraph-start'."
1628 t "$"
1634 "Regexp to append to `paragraph-separate'."
1635 t "$"
1639 \f
1640 ;;; Keyword lists.
1642 ;; Note: All and only all language constants containing keyword lists
1643 ;; should end with "-kwds"; they're automatically collected into the
1644 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1647 "Primitive type keywords. As opposed to the other keyword lists, the
1648 keywords listed here are fontified with the type face instead of the
1649 keyword face.
1651 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1652 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1653 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1654 will be handled.
1656 Do not try to modify this list for end user customizations; the
1657 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1658 the appropriate place for that."
1667 ;; Objective-C extends C, but probably not the new stuff in C99.
1674 ;; In CORBA PSDL:
1675 "ref"
1676 ;; The following can't really end a type, but we have to specify them
1677 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1678 ;; doesn't matter that much.
1681 ;; used as a builtin type.
1686 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1691 "Keywords that might act as prefixes for primitive types. Assumed to
1692 be a subset of `c-primitive-type-kwds'."
1693 t nil
1696 ;; In CORBA PSDL:
1701 of a variable declaration."
1706 ;; Adorned regexp matching `c-typedef-kwds'.
1711 "Keywords followed by a parenthesized expression, which stands for
1712 the type of that expression."
1713 t nil
1718 ;; Adorned regexp matching `c-typeof-kwds'.
1723 "Keywords where the following name - if any - is a type name, and
1724 where the keyword together with the symbol works as a type in
1725 declarations.
1727 Note that an alternative if the second part doesn't hold is
1728 `c-type-list-kwds'. Keywords on this list are typically also present
1729 on one of the `*-decl-kwds' lists."
1730 t nil
1736 ;; Adorned regexp matching `c-type-prefix-kwds'.
1741 "Type modifier keywords. These can occur almost anywhere in types
1742 but they don't build a type of themselves. Unlike the keywords on
1743 `c-primitive-type-kwds', they are fontified with the keyword face and
1744 not the type face."
1745 t nil
1751 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1752 ;; languages without such keywords.
1758 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1759 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1769 ;; All keywords that can start a type (i.e. are either a type prefix
1770 ;; or a complete type).
1777 "Keywords introducing declarations where the following block (if any)
1778 contains another declaration level that should be considered a class.
1780 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1781 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1782 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1783 will be handled.
1785 Note that presence on this list does not automatically treat the
1786 following identifier as a type; the keyword must also be present on
1787 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1788 t nil
1796 ;; In CORBA PSDL:
1798 ;; In CORBA CIDL:
1803 ;; Regexp matching the start of a class.
1808 "Keywords introducing declarations where the following block (if
1809 any) is a brace list.
1811 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1812 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1813 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1814 will be handled."
1819 ;; Regexp matching the start of declarations where the following
1820 ;; block is a brace list.
1825 "Keywords that might follow keywords in `c-brace-list-decl-kwds'
1826 and precede the opening brace."
1827 t nil
1831 ;; Regexp matching keywords that can fall between a brace-list
1832 ;; keyword and the associated brace list.
1837 "Set to t when we recognize a colon and then a type after an enum,
1838 e.g., enum foo : int { A, B, C };"
1839 t nil
1845 "Keywords where the following block (if any) contains another
1846 declaration level that should not be considered a class. For every
1847 keyword here, CC Mode will add a set of special syntactic symbols for
1849 `foo-open', `foo-close', and `infoo' symbols.
1851 The intention is that this category should be used for block
1852 constructs that aren't related to object orientation concepts like
1853 classes (which thus also include e.g. interfaces, templates,
1854 contracts, structs, etc). The more pragmatic distinction is that
1855 while most want some indentation inside classes, it's fairly common
1856 that they don't want it in some of these constructs, so it should be
1857 simple to configure that differently from classes. See also
1858 `c-class-decl-kwds'.
1860 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1861 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1862 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1863 will be handled."
1864 t nil
1868 ;; In CORBA CIDL:
1872 ;; Regexp matching the start of blocks besides classes that contain
1873 ;; another declaration level.
1882 'inextern-lang
1885 "Alist associating keywords in c-other-decl-block-decl-kwds with
1889 "Keywords introducing declarations where the identifier(s) being
1890 declared are types.
1892 If any of these also are on `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' then the associated clauses
1895 will be handled."
1896 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1897 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1898 ;; {...}").
1901 ;; Languages that have a "typedef" construct.
1904 ;; Unlike most other languages, exception names are not handled as
1905 ;; types in IDL since they only can occur in "raises" specs.
1913 "Keywords introducing declarations where the \(first) identifier
1914 \(declarator) follows directly after the keyword, without any type.
1916 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1917 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1918 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1919 will be handled."
1920 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1921 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1922 ;; {...}").
1926 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1927 ;; `c-type-list-kwds' for IDL.
1930 ;; In CORBA PSDL:
1932 ;; In CORBA CIDL:
1938 "Keywords that can prefix normal declarations of identifiers
1939 \(and typically act as flags). Things like argument declarations
1940 inside function headers are also considered declarations in this
1941 sense.
1943 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1944 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1945 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1946 will be handled."
1947 t nil
1953 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1957 ;; In CORBA PSDL:
1959 ;; In CORBA CIDL:
1961 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1968 "Keywords that can start or prefix any declaration level construct,
1969 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1970 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1971 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1973 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1974 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1975 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1976 will be handled."
1977 t nil
1983 "Keywords that always start declarations, wherever they occur.
1984 This can be used for declarations that aren't recognized by the normal
1985 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1986 t nil
1987 ;; Classes can be declared anywhere in a Pike expression.
1991 "Keywords that can occur anywhere in a declaration level construct.
1992 This is used for self-contained things that can be tacked on anywhere
1993 on a declaration and that should be ignored to be able to recognize it
1994 correctly. Typical cases are compiler extensions like
1997 __declspec(noreturn) void foo();
1998 class __declspec(dllexport) classname {...};
1999 void foo() __attribute__((noreturn));
2001 Note that unrecognized plain symbols are skipped anyway if they occur
2002 before the type, so such things are not necessary to mention here.
2003 Mentioning them here is necessary only if they can occur in other
2004 places, or if they are followed by a construct that must be skipped
2006 examples above). In the last case, they alse need to be present on
2007 one of `c-type-list-kwds', `c-ref-list-kwds',
2008 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2009 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
2010 ;; NB: These are currently not recognized in all parts of a
2011 ;; declaration. Specifically, they aren't recognized in the middle
2012 ;; of multi-token types, inside declarators, and between the
2013 ;; identifier and the arglist paren of a function declaration.
2014 ;;
2015 ;; FIXME: This ought to be user customizable since compiler stuff
2016 ;; like this usually is wrapped in project specific macros. (It'd
2017 ;; of course be even better if we could cope without knowing this.)
2018 t nil
2020 "__attribute__"
2021 ;; MSVC extension.
2025 ;; Adorned regexp matching `c-decl-hangon-kwds'.
2030 ;; All keywords that can occur in the preamble of a declaration.
2031 ;; They typically occur before the type, but they are also matched
2032 ;; after presumptive types since we often can't be sure that
2033 ;; something is a type or just some sort of macro in front of the
2034 ;; declaration. They might be ambiguous with types or type
2035 ;; prefixes.
2048 ;; Adorned regexp of `c-prefix-spec-kwds'.
2054 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
2055 ;; ambiguous with types or type prefixes. These are the keywords (like
2056 ;; extern, namespace, but NOT template) that can modify a declaration.
2065 ;; Keywords that can occur after argument list of a function header
2066 ;; declaration, i.e. in the "K&R region".
2071 ;; Adorned regexp matching all keywords that can't appear at the
2072 ;; start of a declaration.
2087 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2088 ;; This variable is intended for use in c-beginning-of-statement-1.
2098 "Access protection label keywords in classes."
2099 t nil
2104 "Keywords introducing declarations that can contain a block which
2107 like that, it ends with the following `;' and not right away.
2109 The keywords on list are assumed to also be present on one of the
2110 `*-decl-kwds' lists."
2111 t nil
2116 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2117 ;; languages without such constructs.
2124 "Keywords introducing extra declaration specifiers in the region
2126 declarations."
2127 t nil
2130 "supports"
2131 ;; In CORBA PSDL:
2135 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2141 "Keywords that may be followed by a nonsymbol sexp before whatever
2142 construct it's part of continues."
2143 t nil
2147 "Keywords that may be followed by a comma separated list of type
2148 identifiers, where each optionally can be prefixed by keywords. (Can
2149 also be used for the special case when the list can contain only one
2150 element.)
2152 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2153 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2154 There's also no reason to add keywords that prefixes a normal
2155 declaration consisting of a type followed by a declarator (list), so
2156 the keywords on `c-modifier-kwds' should normally not be listed here
2157 either.
2159 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2160 or variable identifier (that's being defined)."
2161 t nil
2166 ;; In CORBA PSDL:
2171 "Keywords that may be followed by a comma separated list of
2172 reference (i.e. namespace/scope/module) identifiers, where each
2173 optionally can be prefixed by keywords. (Can also be used for the
2174 special case when the list can contain only one element.) Assumed to
2175 be mutually exclusive with `c-type-list-kwds'.
2177 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2178 or variable identifier (that's being defined)."
2179 t nil
2183 ;; In CORBA CIDL:
2188 "Keywords that may be followed (not necessarily directly) by a colon
2189 and then a comma separated list of type identifiers, where each
2190 optionally can be prefixed by keywords. (Can also be used for the
2191 special case when the list can contain only one element.)"
2192 t nil
2195 ;; In CORBA PSDL:
2199 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2200 forward to the colon. The end of the match is assumed to be directly
2202 regexp if `c-colon-type-list-kwds' isn't nil."
2204 ;; Disallow various common punctuation chars that can't come
2205 ;; before the ":" that starts the inherit list after "class"
2206 ;; or "struct" in C++. (Also used as default for other
2207 ;; languages.)
2212 "Keywords that may be followed by a parenthesis expression that doesn't
2213 contain type identifiers."
2214 t nil
2216 "__attribute__"
2217 ;; MSVC extension.
2221 "Keywords that may be followed by a parenthesis expression containing
2222 type identifiers separated by arbitrary tokens."
2223 t nil
2235 "Keywords that may be followed by an angle bracket expression
2237 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2238 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2239 if this isn't nil."
2240 t nil
2243 ;; In CORBA PSDL:
2247 "Keywords that can be followed by a C++ style template arglist; see
2248 `c-recognize-<>-arglists' for details. That language constant is
2249 assumed to be set if this isn't nil."
2250 t nil
2255 ;; All keywords that can be followed by an angle bracket sexp.
2261 ;; Adorned regexp matching keywords that can be followed by an angle
2262 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2267 "Keywords that may be followed by a brace block containing a comma
2268 separated list of identifier definitions, i.e. like the list of
2269 identifiers that follows the type in a normal declaration."
2273 "Statement keywords followed directly by a substatement."
2278 idl nil)
2281 ;; Regexp matching the start of any statement followed directly by a
2282 ;; substatement (doesn't match a bare block, however).
2287 "Statement keywords optionally followed by a paren sexp.
2288 Keywords here should also be in `c-block-stmt-1-kwds'."
2289 t nil
2293 ;; Regexp matching the start of a statement which may be followed by a
2294 ;; paren sexp and will then be followed by a substatement.
2299 "Statement keywords followed by a paren sexp and then by a substatement."
2304 idl nil
2309 ;; Regexp matching the start of any statement followed by a paren sexp
2310 ;; and then by a substatement.
2315 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2321 ;; Regexp matching the start of any statement that has a
2322 ;; substatement (except a bare block). Nil in languages that
2323 ;; don't have such constructs.
2332 "Statement keywords followed by an expression or nothing."
2335 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2337 idl nil
2344 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2349 "Statement keywords followed by a parenthesis expression that
2350 nevertheless contains a list separated with `;' and not `,'."
2352 idl nil)
2355 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2360 "Statement keywords followed by an assembler expression."
2361 t nil
2365 ;; Regexp matching the start of an assembler statement. Nil in
2366 ;; languages that don't support that.
2375 awk nil)
2378 ;; Adorned regexp matching any "case"-like keyword.
2383 "Keywords introducing colon terminated labels in blocks."
2387 ;; Adorned regexp matching any keyword that introduces a label.
2392 "Keywords that might be followed by a label identifier."
2396 idl nil
2397 awk nil)
2400 "Keywords for constants."
2401 t nil
2413 "Keywords besides constants and operators that start primary expressions."
2414 t nil
2421 ;; Keywords that can occur anywhere in expressions. Built from
2422 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2426 t
2431 "Keywords that start lambda constructs, i.e. function definitions in
2432 expressions."
2433 t nil
2437 "Keywords that start constructs followed by statement blocks which can
2438 be used in expressions \(the gcc extension for this in C and C++ is
2439 handled separately by `c-recognize-paren-inexpr-blocks')."
2440 t nil
2444 "Keywords that can start classes inside expressions."
2445 t nil
2450 "Keywords that can start brace list blocks inside expressions.
2451 Note that Java specific rules are currently applied to tell this from
2452 `c-inexpr-class-kwds'."
2453 t nil
2457 ;; Regexp matching the start of a brace list in an expression, or
2458 ;; nil in languages that don't have such things. This should not
2459 ;; match brace lists recognized through `c-special-brace-lists'.
2466 ;; Regexp matching keywords in any construct that contain another
2467 ;; declaration level, i.e. that isn't followed by a function block
2468 ;; or brace list. When the first submatch matches, it's an
2469 ;; unambiguous construct, otherwise it's an ambiguous match that
2470 ;; might also be the return type of a function declaration.
2488 "Keywords that can introduce bitfields."
2489 t nil
2493 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2494 ;; languages without bitfield support.
2495 t nil
2500 "Keywords not accounted for by any other `*-kwds' language constant."
2501 t nil
2503 ;; In CORBA CIDL: (These are declaration keywords that never
2504 ;; can start a declaration.)
2507 \f
2508 ;;; Constants built from keywords.
2510 ;; Note: No `*-kwds' language constants may be defined below this point.
2514 ;; List of all the language constants that contain keyword lists.
2519 ;; Make the list of globally interned symbols
2520 ;; instead of ones interned in `c-lang-constants'.
2522 c-lang-constants)
2523 list)))
2526 ;; All keywords as a list.
2531 c-kwds-lang-consts)
2532 nil))
2536 ;; All keywords as an adorned regexp.
2541 ;; An alist with all the keywords in the cars. The cdr for each
2542 ;; keyword is a list of the symbols for the `*-kwds' lists that
2543 ;; contains it.
2549 c-kwds-lang-consts))))
2550 lang-const kwd-list kwd
2551 result-alist elem)
2563 result-alist))
2566 ;; An obarray containing all keywords as symbols. The property list
2567 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2568 ;; lists it's a member of.
2569 ;;
2570 ;; E.g. to see whether the string str contains a keyword on
2571 ;; `c-class-decl-kwds', one can do like this:
2572 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2573 ;; Which preferably is written using the associated functions in
2574 ;; cc-engine:
2575 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2577 ;; The obarray is not stored directly as a language constant since
2578 ;; the printed representation for obarrays used in .elc files isn't
2579 ;; complete.
2582 kwd lang-const-list
2589 ;; Emacs has an odd bug that causes `mapcan' to fail
2590 ;; with unintelligible errors. (XEmacs works.)
2591 ;; (2015-06-24): This bug has not yet been fixed.
2592 ;;(mapcan (lambda (lang-const)
2593 ;; (list lang-const t))
2594 ;; lang-const-list)
2597 lang-const-list))))
2598 obarray))
2601 ;; Adorned regexp matching all keywords that should be fontified
2602 ;; with the keywords face. I.e. that aren't types or constants.
2612 ;; Regexp matching the start of any primary expression, i.e. any
2613 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2614 ;; exclude keywords; they are excluded afterwards unless the second
2615 ;; submatch matches. If the first but not the second submatch
2616 ;; matches then it is an ambiguous primary expression; it could also
2617 ;; be a match of e.g. an infix operator. (The case with ambiguous
2618 ;; keyword operators isn't handled.)
2624 ;; Filter out the special case prefix
2625 ;; operators that are close parens.
2630 t
2636 postfix-if-paren
2637 left-assoc
2638 right-assoc
2639 right-assoc-sequence)
2640 t))
2643 in-or-postfix-ops
2646 in-or-postfix-ops
2651 ;; Take out all symbol class operators from `prefix-ops' and make the
2652 ;; first submatch from them together with `c-primary-expr-kwds'.
2659 ;; Match all ambiguous operators.
2666 ;; Now match all other symbols.
2670 ;; The chars that can start integer and floating point
2671 ;; constants.
2675 ;; The unambiguous operators from `prefix-ops'.
2681 ;; Match string and character literals.
2688 \f
2689 ;;; Additional constants for parser-level constructs.
2692 "Regexp matching a keyword that is followed by a colon, where
2693 the whole construct can precede a declaration.
2701 "Regexp matching something that might precede a declaration, cast or
2702 label, such as the last token of a preceding statement or declaration.
2703 This is used in the common situation where a declaration or cast
2704 doesn't start with any specific token that can be searched for.
2706 The regexp should not match bob; that is done implicitly. It can't
2707 require a match longer than one token. The end of the token is taken
2708 to be at the end of the first submatch, which is assumed to always
2709 match. It's undefined whether identifier syntax (see
2710 `c-identifier-syntax-table') is in effect or not. This regexp is
2711 assumed to be a superset of `c-label-prefix-re' if
2712 `c-recognize-colon-labels' is set.
2714 Besides this, `c-decl-start-kwds' is used to find declarations.
2716 Note: This variable together with `c-decl-start-re' and
2718 declaration/cast/label starts. I.e. they might produce more matches
2719 but should not miss anything (or else it's necessary to use text
2720 properties - see the next note). Wherever they match, the following
2721 construct is analyzed to see if it indeed is a declaration, cast or
2722 label. That analysis is not cheap, so it's important that not too
2723 many false matches are triggered.
2725 Note: If a declaration/cast/label start can't be detected with this
2726 variable, it's necessary to use the `c-type' text property with the
2727 value `c-decl-end' on the last char of the last token preceding the
2728 declaration. See the comment blurb at the start of cc-engine.el for
2729 more info."
2731 ;; We match a sequence of characters to skip over things like \"};\"
2732 ;; more quickly. We match ")" in C for K&R region declarations, and
2733 ;; in all languages except Java for when a cpp macro definition
2734 ;; begins with a declaration.
2737 ;; Match "<" in C++ to get the first argument in a template arglist.
2738 ;; In that case there's an additional check in `c-find-decl-spots'
2739 ;; that it got open paren syntax. Match ":" to aid in picking up
2740 ;; "public:", etc. This involves additional checks in
2741 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2742 ;; or labels.
2744 ;; Additionally match the protection directives in Objective-C.
2745 ;; Note that this doesn't cope with the longer directives, which we
2746 ;; would have to match from start to end since they don't end with
2747 ;; any easily recognized characters.
2751 ;; Pike is like C but we also match "[" for multiple value
2752 ;; assignments and type casts.
2758 "Regexp matching the start of any declaration, cast or label.
2759 It's used on the token after the one `c-decl-prefix-re' matched. This
2760 regexp should not try to match those constructs accurately as it's
2761 only used as a sieve to avoid spending more time checking other
2762 constructs."
2767 ;; Regexp matching something that might precede or start a
2768 ;; declaration, cast or label.
2769 ;;
2770 ;; If the first submatch matches, it's taken to match the end of a
2771 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2772 ;; It's built from `c-decl-prefix-re'.
2773 ;;
2774 ;; If the first submatch did not match, the match of the whole
2775 ;; regexp is taken to be at the first token in the declaration.
2776 ;; `c-decl-start-re' is not checked in this case.
2777 ;;
2778 ;; Design note: The reason the same regexp is used to match both
2779 ;; tokens that precede declarations and start them is to avoid an
2780 ;; extra regexp search from the previous declaration spot in
2781 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2782 ;; that it finds all declaration/cast/label starts in approximately
2783 ;; linear order, so we can't do the searches in two separate passes.
2794 ;; List containing the paren characters that can open a cast, or nil in
2795 ;; languages without casts.
2803 "List of syntactically relevant characters that never can occur before
2804 the open brace in any construct that contains a brace block, e.g. in
2807 class Foo: public Bar {int x();} a, *b;
2809 If parens can occur, the chars inside those aren't filtered with this
2810 list.
2812 `<' and `>' should be disallowed even if angle bracket arglists can
2813 occur. That since the search function needs to stop at them anyway to
2814 ensure they are given paren syntax.
2816 This is used to skip backward from the open brace to find the region
2819 possible for good performance."
2821 ;; Default to all chars that only occurs in nonsymbol tokens outside
2822 ;; identifiers.
2828 t
2829 t
2833 op pos)
2836 res))))
2838 ;; Allow cpp operations (where applicable).
2844 ;; Allow ':' for inherit list starters.
2848 ;; Allow ',' for multiple inherits.
2852 ;; Allow parentheses for anonymous inner classes in Java and class
2853 ;; initializer lists in Pike.
2857 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2862 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2863 ;; for `c-syntactic-skip-backward'.
2868 "Regexp matching any declarator operator that might precede the
2871 The end of the first submatch is taken as the end of the operator.
2872 Identifier syntax is in effect when this is matched \(see
2873 `c-identifier-syntax-table')."
2876 ;; Default to a regexp that never matches.
2878 ;; Check that there's no "=" afterwards to avoid matching tokens
2879 ;; like "*=".
2881 "[*(]"
2887 "[*(&]"
2892 ;; If this matches there's special treatment in
2893 ;; `c-font-lock-declarators' and
2894 ;; `c-font-lock-declarations' that check for a
2895 ;; complete name followed by ":: *".
2905 "Regexp matching the declarator operators that might follow after the
2908 it matches an open paren of some kind, the type declaration check
2909 continues at the corresponding close paren, otherwise the end of the
2910 first submatch is taken as the end of the operator. Identifier syntax
2911 is in effect when this is matched (see `c-identifier-syntax-table')."
2912 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2913 ;; function argument list parenthesis.
2921 "[)[(]"
2925 ;; "throw" in `c-type-modifier-kwds' is followed
2926 ;; by a parenthesis list, but no extra measures
2927 ;; are necessary to handle that.
2938 "This regexp is matched after a declarator expression where
2939 `c-type-decl-suffix-key' has matched. If it matches then the
2940 construct is taken as a declaration. It's typically used to match the
2941 beginning of a function body or whatever might occur after the
2942 function header in a function declaration or definition. It's
2943 undefined whether identifier syntax (see `c-identifier-syntax-table')
2944 is in effect or not.
2949 t "{"
2950 ;; If K&R style declarations should be recognized then one could
2951 ;; consider to match the start of any symbol since we want to match
2952 ;; the start of the first declaration in the "K&R region". That
2953 ;; could however produce false matches on code like "FOO(bar) x"
2954 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2955 ;; on the other heuristics in that case.
2957 ;; Add on the keywords in `c-postfix-spec-kwds'.
2962 ;; Also match the colon that starts a base class initializer list in
2963 ;; C++. That can be confused with a function call before the colon
2964 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2965 ;; match before such a thing (as a declaration-level construct;
2966 ;; matches inside arglist contexts are already excluded).
2973 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2974 ;; matches ";" and ",".
2983 end of the operator. nil in languages without such operators. It's
2984 undefined whether identifier syntax (see `c-identifier-syntax-table')
2985 is in effect or not."
2986 t nil
2992 "Regexp matching operators that might follow after a type, or nil in
2993 languages that don't have such operators. The end of the first
2994 submatch is taken as the end of the operator. This should not match
2995 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2996 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2997 is in effect or not."
2998 t nil
3004 ;; Regexp matching the known type identifiers. This is initialized
3005 ;; from the type keywords and `*-font-lock-extra-types'. The first
3006 ;; submatch is the one that matches the type. Note that this regexp
3007 ;; assumes that symbol constituents like '_' and '$' have word
3008 ;; syntax.
3015 re))
3016 extra-types)))
3020 re))
3021 extra-types))))
3026 plain-strings)))
3027 regexp-strings)
3032 "List of open- and close-chars that makes up a pike-style brace list,
3034 list."
3035 t nil
3040 "Non-nil means K&R style argument declarations are valid."
3041 t nil
3042 c t)
3046 "Non-nil means function declarations without return type should be
3047 recognized. That can introduce an ambiguity with parenthesized macro
3048 calls before a brace block. This setting does not affect declarations
3049 that are preceded by a declaration starting keyword, so
3050 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
3051 t nil
3057 "Non-nil means C++ style template arglists should be handled. More
3058 specifically, this means a comma separated list of types or
3060 identifier or one of the keywords on `c-<>-type-kwds' or
3061 `c-<>-arglist-kwds'. If there's an identifier before then the whole
3062 expression is considered to be a type."
3066 ; generics is not yet coded in CC Mode.
3070 "Non-nil means that an enum structure can contain declarations."
3071 t nil
3072 java t)
3076 "Non-nil means that parenthesis style initializers exist,
3077 i.e. constructs like
3079 Foo bar (gnu);
3081 in addition to the more classic
3083 Foo bar = gnu;"
3084 t nil
3089 "Non-nil to recognize gcc style in-expression blocks,
3090 i.e. compound statements surrounded by parentheses inside expressions."
3091 t nil
3097 ;; Regexp matching the start of angle bracket arglists in languages
3098 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3099 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3100 ;; assumed to surround the preceding symbol. The whole match is
3101 ;; assumed to end directly after the opening "<".
3111 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3112 ;; parens. The first submatch is assumed to surround
3113 ;; `c-opt-<>-arglist-start'.
3122 ;; Regexp matching the beginning of a declaration specifier in the
3123 ;; region between the header and the body of a declaration.
3124 ;;
3125 ;; TODO: This is currently not used uniformly; c++-mode and
3126 ;; java-mode each have their own ways of using it.
3127 t nil
3140 That includes labels in code and access keys in classes. This does
3141 not apply to labels recognized by `c-label-kwds' and
3142 `c-opt-extra-label-key'."
3143 t nil
3149 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3150 a generic colon label. Not used if `c-recognize-colon-labels' is
3151 nil."
3157 "Regexp matching things that can't occur in generic colon labels,
3158 neither in a statement nor in a declaration context. The regexp is
3159 tested at the beginning of every sexp in a suspected label,
3162 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3168 ;; Don't allow string literals, except in AWK. Character constants are OK.
3171 ;; Also check for open parens in C++, to catch member init lists in
3172 ;; constructors. We normally allow it so that macros with arguments
3173 ;; work in labels.
3178 "Regexp matching things that can't occur two symbols before a colon in
3186 "Optional regexp matching labels.
3187 Normally, labels are detected according to `c-nonlabel-token-key',
3188 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3189 be used if there are additional labels that aren't recognized that
3190 way."
3191 t nil
3196 ;; Regexp describing friend declarations classes, or nil in
3197 ;; languages that don't have such things.
3198 ;;
3199 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3200 ;; template skipping isn't done properly. This will disappear soon.
3201 t nil
3206 "<.+>"
3208 "friend"
3213 ;; Special regexp to match the start of Objective-C methods. The
3214 ;; first submatch is assumed to end after the + or - key.
3215 t nil
3217 ;; TODO: Ought to use a better method than anchoring on bol.
3222 "([^)]*)"
3229 ;; Must be set in buffers where the `c-type' text property might be
3230 ;; used with the value `c-decl-end'.
3231 ;;
3232 ;; `c-decl-end' is used to mark the ends of labels and access keys
3233 ;; to make interactive refontification work better.
3236 ;; `c-decl-end' is used to mark the end of the @-style directives in
3237 ;; Objective-C.
3238 objc t)
3241 \f
3242 ;;; Wrap up the `c-lang-defvar' system.
3244 ;; Compile in the list of language variables that has been collected
3245 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3246 ;; first element of each is nil.
3250 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3251 ;; These are typically standard emacs variables such as `comment-start'.
3259 "Create a function that initializes all the language dependent variables
3260 for the given mode.
3262 This function should be evaluated at compile time, so that the
3263 function it returns is byte compiled with all the evaluated results
3264 from the language constants. Use the `c-init-language-vars' macro to
3265 accomplish that conveniently."
3268 ;; No need to byte compile this lambda since the byte compiler is
3269 ;; smart enough to detect the `funcall' construct in the
3270 ;; `c-init-language-vars' macro below and compile it all straight
3271 ;; into the function that contains `c-init-language-vars'.
3274 ;; This let sets up the context for `c-mode-var' and similar
3275 ;; that could be in the result from `c--macroexpand-all'.
3277 current-var source-eval)
3284 ;; `c-lang-const' will expand to the evaluated
3285 ;; constant immediately in `c--macroexpand-all'
3286 ;; below.
3292 ;; Note: The following `append' copies the
3293 ;; first argument. That list is small, so
3294 ;; this doesn't matter too much.
3298 ;; This diagnostic message isn't useful for end
3299 ;; users, so it's disabled.
3300 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3301 ;; (message ,(concat "%s compiled with CC Mode %s "
3302 ;; "but loaded with %s - evaluating "
3303 ;; "language constants from source")
3304 ;; ',mode ,c-version c-version)
3305 ;; (put ',mode 'c-has-warned-lang-consts t))
3317 current-var
3320 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3323 err)
3326 ;; Being evaluated from source. Always use the dynamic method to
3327 ;; work well when `c-lang-defvar's in this file are reevaluated
3328 ;; interactively.
3334 current-var)
3345 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3346 current-var err)
3348 ))
3351 "Initialize all the language dependent variables for the given mode.
3352 This macro is expanded at compile time to a form tailored for the mode
3353 in question, so MODE must be a constant. Therefore MODE is not
3354 evaluated and should not be quoted."
3357 \f
3360 ;; Local Variables:
3361 ;; indent-tabs-mode: t
3362 ;; tab-width: 8
3363 ;; End:
3364 ;;; cc-langs.el ends here