| blob | 705f723d55dc790d6509c999bb23ef5f710eb8ad |
1 ;;; cc-langs.el --- language specific settings for CC Mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2016 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 ;; OP-FILTER selects the operators. It is either t to select all
232 ;; operators, a string to select all operators for which `string-match'
233 ;; matches the operator with the string, or a function which will be
234 ;; called with the operator and should return non-nil when the operator
235 ;; is to be selected.
236 ;;
237 ;; If XLATE is given, it's a function which is called for each
238 ;; matching operator and its return value is collected instead.
239 ;; If it returns a list, the elements are spliced directly into
240 ;; the final result, which is returned as a list with duplicates
241 ;; removed using `equal'.
242 ;;
243 ;; `c-mode-syntax-table' for the current mode is in effect during
244 ;; the whole procedure.
265 t)
266 t)
271 opgroup)))
272 ops)
275 \f
276 ;;; Various mode specific values that aren't language related.
279 ;; The definition for the mode menu. The menu title is prepended to
280 ;; this before it's fed to `easy-menu-define'.
290 "----"
294 ;; Only applicable if there's a cpp preprocessor.
298 "----"
303 "----"
307 "Style Name: %s"
308 c-indentation-style)
309 t]
313 c-guess-guessed-basic-offset) ]
316 c-guess-guessed-basic-offset) ])
317 "----"
329 c-subword-mode)])))
331 \f
332 ;;; Syntax tables.
335 "Populate the given syntax table as necessary for a C-like language.
353 ;; Set up block and line oriented comments. The new C
354 ;; standard mandates both comment styles even in C, so since
355 ;; all languages now require dual comments, we make this the
356 ;; default.
358 ;; XEmacs
362 ;; Emacs
366 ;; incompatible
370 ;; Give CR the same syntax as newline, for selective-display
374 "Functions that generates the mode specific syntax tables.
375 The syntax tables aren't stored directly since they're quite large."
379 ;; Mode specific syntaxes.
381 ;; Let '@' be part of symbols in ObjC to cope with
382 ;; its compiler directives as single keyword tokens.
383 ;; This is then necessary since it's assumed that
384 ;; every keyword is a single symbol.
388 table)))
391 ;; The syntax tables in evaluated form. Only used temporarily when
392 ;; the constants in this file are evaluated.
396 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
397 ;; parenthesis characters. Used temporarily when template argument
398 ;; lists are parsed. Note that this encourages incorrect parsing of
399 ;; templates since they might contain normal operators that uses the
400 ;; '<' and '>' characters. Therefore this syntax table might go
401 ;; away when CC Mode handles templates correctly everywhere. WHILE
402 ;; THIS SYNTAX TABLE IS CURRENT, `c-parse-state' MUST _NOT_ BE
403 ;; CALLED!!!
404 t nil
409 table)))
412 ;; The next eval remove a superfluous ' from '(lambda. This
413 ;; gets rid of compilation warnings.
417 ;; A variant of the standard syntax table which is used to find matching
418 ;; "<"s and ">"s which have been marked as parens using syntax table
419 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
420 ;; non-paren syntax here. so that the list commands will work on "< ... >"
421 ;; even when there's unbalanced other parens inside them.
422 ;;
423 ;; This variable is nil for languages which don't have template stuff.
426 ;(if (c-lang-const c-recognize-<>-arglists)
434 table))))
437 ;; See comment in `c++template-syntax-table' about the next `eval'.
441 "A list that describes the modifications that should be done to the
442 mode syntax table to get a syntax table that matches all identifiers
443 and keywords as words.
445 The list is just like the one used in `font-lock-defaults': Each
446 element is a cons where the car is the character to modify and the cdr
447 the new syntax, as accepted by `modify-syntax-entry'."
448 ;; The $ character is not allowed in most languages (one exception
449 ;; is Java which allows it for legacy reasons) but we still classify
450 ;; it as an identifier character since it's often used in various
451 ;; machine generated identifiers.
462 mod)
467 table)
468 "Syntax table built on the mode syntax table but additionally
469 classifies symbol constituents like `_' and `$' as word constituents,
473 ;; For documentation see the following c-lang-defvar of the same name.
474 ;; The value here may be a list of functions or a single function.
475 t nil
477 c-before-change-check-<>-operators
478 c-invalidate-macro-cache)
480 ;; java 'c-before-change-check-<>-operators
485 fs
487 "If non-nil, a list of functions called from c-before-change-hook.
488 Typically these will record enough state to allow
489 `c-before-font-lock-function' to extend the region to fontify,
490 and may do such things as removing text-properties which must be
491 recalculated.
493 These functions will be run in the order given. Each of them
494 takes 2 parameters, the BEG and END supplied to every
495 before-change function; on entry, the buffer will have been
496 widened and match-data will have been saved; point is undefined
497 on both entry and exit; the return value is ignored.
499 The functions are called even when font locking isn't enabled.
501 When the mode is initialized, the functions are called with
505 ;; For documentation see the following c-lang-defvar of the same name.
506 ;; The value here may be a list of functions or a single function.
507 t 'c-change-expand-fl-region
509 c-change-expand-fl-region)
511 c-restore-<>-properties
512 c-change-expand-fl-region)
514 c-change-expand-fl-region)
519 fs
521 "If non-nil, a list of functions called just before font locking.
522 Typically they will extend the region about to be fontified \(see
523 below) and will set `syntax-table' text properties on the region.
525 These functions will be run in the order given. Each of them
526 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
527 after-change function; point is undefined on both entry and exit;
528 on entry, the buffer will have been widened and match-data will
529 have been saved; the return value is ignored.
531 The functions may extend the region to be fontified by setting the
532 buffer local variables c-new-BEG and c-new-END.
534 The functions are called even when font locking is disabled.
536 When the mode is initialized, these functions are called with
540 t 'c-context-expand-fl-region
541 awk nil)
542 ;; For documentation see the following c-lang-defvar of the same name.
543 ;; The value here may be a list of functions or a single function.
547 fs
549 "If non-nil, a list of functions called just before context (or
550 other non-change) fontification is done. Typically they will
551 extend the region.
553 These functions will be run in the order given. Each of them
554 takes 2 parameters, the BEG and END of the region to be
555 fontified. Point is undefined on both entry and exit. On entry,
556 the buffer will have been widened and match-data will have been
557 saved; the return value is a cons of the adjusted
560 \f
561 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
564 Such a function takes one optional parameter, a buffer position (defaults to
565 point), and returns nil or t. This variable contains nil for languages which
566 don't have EOL terminated statements. "
567 t nil
574 The (admittedly kludgy) purpose of such a function is to prevent an infinite
575 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
576 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
577 even indirectly. This variable contains nil for languages which don't have
578 EOL terminated statements."
579 t nil
585 \f
586 ;;; Lexer-level syntax (identifiers, tokens etc).
589 "Whether the language has bitfield declarations."
590 t nil
596 a “long character”. In particular, this recognizes forms of constant
597 which `c-backward-sexp' needs to be called twice to move backwards over."
598 t nil
600 ;; FIXME!!! Extend this to cover strings, if needed. 2008-04-11
604 "Regexp that matches the start of a symbol, i.e. any identifier or
606 operator at the top level."
614 "Set of characters that can be part of a symbol.
615 This is of the form that fits inside [ ] in a regexp."
616 ;; Pike note: With the backquote identifiers this would include most
617 ;; operator chars too, but they are handled with other means instead.
623 "Regexp matching a sequence of at least one identifier character."
628 "Regexp matching identifiers and keywords (with submatch 0). Assumed
629 to match if `c-symbol-start' matches on the same position."
633 ;; Use the value from C here since the operator backquote is
634 ;; covered by the other alternative.
642 ;; Number of regexp grouping parens in `c-symbol-key'.
646 "This is the set of chars that can't be part of a symbol, i.e. the
647 negation of `c-symbol-chars'."
652 "Regexp that matches any character that can't be part of a symbol.
653 It's usually appended to other regexps to avoid matching a prefix.
654 It's assumed to not contain any submatchers."
655 ;; The same thing regarding Unicode identifiers applies here as to
656 ;; `c-symbol-key'.
660 "The operators that make up fully qualified identifiers. nil in
661 languages that don't have such things. See `c-operators' for a
662 description of the format. Binary operators can concatenate symbols,
666 This value is by default merged into `c-operators'."
667 t nil
671 ;; Java has "." to concatenate identifiers but it's also used for
672 ;; normal indexing. There's special code in the Java font lock
673 ;; rules to fontify qualified identifiers based on the standard
674 ;; naming conventions. We still define "." here to make
675 ;; `c-forward-name' move over as long names as possible which is
676 ;; necessary to e.g. handle throws clauses correctly.
685 ;; Appendable adorned regexp matching the operators that join
686 ;; symbols to fully qualified identifiers, or nil in languages that
687 ;; don't have such things.
688 ;;
689 ;; This was a docstring constant in 5.30. It still works but is now
690 ;; considered internal - change `c-identifier-ops' instead.
693 t)))
701 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
705 ;; Appendable adorned regexp matching operators that might precede
706 ;; an identifier and that are part of the identifier in that case.
707 ;; nil in languages without such things.
710 t)))
715 "Operators that can occur after a binary operator on `c-identifier-ops'
716 in identifiers. nil in languages that don't have such things.
718 Operators here should also have appropriate entries in `c-operators' -
719 it's not taken care of by default."
720 t nil
721 ;; '~' for destructors in C++, '*' for member pointers.
723 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
724 ;; in import declarations. (This will also match bogus things like
725 ;; "foo.*bar" but we don't bother.)
729 ;; Regexp that must match the token after
730 ;; `c-opt-identifier-concat-key' for it to be considered an
731 ;; identifier concatenation operator (which e.g. causes the
732 ;; preceding identifier to be fontified as a reference). Assumed to
733 ;; be a string if `c-opt-identifier-concat-key' is.
734 ;;
735 ;; This was a docstring constant in 5.30. It still works but is now
736 ;; considered internal - change `c-after-id-concat-ops' instead.
744 "Regexp that matches the start of an (optionally qualified) identifier.
745 It should also match all keywords. It's unspecified how far it
746 matches."
756 C++. It does not recognize the full range of syntactic whitespace
757 between the tokens; `c-forward-name' has to be used for that. It
758 should also not match identifiers containing parenthesis groupings,
760 ;; This regexp is more complex than strictly necessary to ensure
761 ;; that it can be matched with a minimum of backtracking.
782 ;; For flexibility, consider the symbol match
783 ;; optional if we've hit a
784 ;; `c-after-id-concat-ops' operator. This is
785 ;; also necessary to handle the "*" that can
786 ;; end import declaration identifiers in Java.
800 ;; This was a docstring constant in 5.30 but it's no longer used.
801 ;; It's only kept to avoid breaking third party code.
802 ;;
803 ;; Used to identify the submatch in `c-identifier-key' that
804 ;; surrounds the last symbol in the qualified identifier. It's a
805 ;; list of submatch numbers, of which the first that has a match is
806 ;; taken. It's assumed that at least one does when the regexp has
807 ;; matched.
808 t nil)
811 "Set if the language support backslash escaped newlines inside string
812 literals."
813 t nil
819 "Set if the language supports multiline string literals without escaped
820 newlines. If t, all string literals are multiline. If a character,
821 only literals where the open quote is immediately preceded by that
822 literal are multiline."
823 t nil
824 pike ?#)
829 "The symbol which starts preprocessor constructs when in the margin."
830 t "#"
835 "Regexp matching the prefix of a cpp directive in the languages that
836 normally use that macro preprocessor. Tested at bol or at boi.
838 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
839 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
845 "Regexp matching the prefix of a cpp directive anchored to BOL,
846 in the languages that have a macro preprocessor."
852 "Regexp matching the prefix of a cpp directive including the directive
853 name, or nil in languages without preprocessor support. The first
854 submatch surrounds the directive name."
858 ;; Pike, being a scripting language, recognizes hash-bangs too.
864 "List of cpp directives (without the prefix) that are followed by a
865 string message."
871 "List of cpp directives (without the prefix) that are followed by a
872 file name in angle brackets or quotes."
878 "Cpp directive (without the prefix) that is followed by a macro
879 definition, or nil if the language doesn't have any."
886 ;; Regexp matching everything up to the macro body of a cpp define, or the
887 ;; end of the logical line if there is none. Submatch 1 is the name of the
888 ;; macro. Set if c-opt-cpp-macro-define is.
893 ;; ^ ^ #defined name
899 ;; Regexp matching everything up to the end of the identifier defined
900 ;; by a cpp define.
909 "List of cpp directives (without the prefix) that are followed by an
910 expression."
915 "Regexp which matches the start of a CPP directive which contains an
916 expression, or nil if there aren't any in the language."
925 "List of functions in cpp expressions."
931 "List of all assignment operators."
937 idl nil)
940 "List describing all operators, along with their precedence and
941 associativity. The order in the list corresponds to the precedence of
942 the operators: The operators in each element are a group with the same
943 precedence, and the group has higher precedence than the groups in all
944 following elements. The car of each element describes the type of the
945 operator group, and the cdr is a list of the operator tokens in it.
946 The operator group types are:
948 `prefix' Unary prefix operators.
949 `postfix' Unary postfix operators.
950 `postfix-if-paren'
951 Unary postfix operators if and only if the chars have
952 parenthesis syntax.
953 `left-assoc' Binary left associative operators (i.e. a+b+c means (a+b)+c).
954 `right-assoc' Binary right associative operators (i.e. a=b=c means a=(b=c)).
955 `right-assoc-sequence'
956 Right associative operator that constitutes of a
957 sequence of tokens that separate expressions. All the
958 tokens in the group are in this case taken as
959 describing the sequence in one such operator, and the
960 order between them is therefore significant.
962 Operators containing a character with paren syntax are taken to match
963 with a corresponding open/close paren somewhere else. A postfix
964 operator with close paren syntax is taken to end a postfix expression
965 started somewhere earlier, rather than start a new one at point. Vice
966 versa for prefix operators with open paren syntax.
969 often are described as postfix operators are considered binary here,
970 since CC Mode treats every identifier as an expression."
972 ;; There's currently no code in CC Mode that exploits all the info
973 ;; in this variable; precedence, associativity etc are present as a
974 ;; preparation for future work.
976 ;; FIXME!!! C++11's "auto" operators "=" and "->" need to go in here
977 ;; somewhere. 2012-03-24.
988 ;; Primary.
997 ;; Postfix.
999 ;; The following need special treatment.
1010 ;; Unary.
1017 ;; The following need special treatment.
1028 ;; Member selection.
1032 ;; Multiplicative.
1035 ;; Additive.
1038 ;; Shift.
1043 ;; Relational.
1048 ;; Equality.
1052 ;; Bitwise and.
1056 ;; Bitwise exclusive or.
1062 ;; Bitwise or.
1068 ;; Logical and.
1072 ;; Logical or.
1078 ;; Conditional.
1081 ;; Assignment.
1084 ;; Exception.
1088 ;; Sequence.
1091 ;; IDL got its own definition since it has a much smaller operator
1092 ;; set than the other languages.
1096 ;; Primary.
1098 ;; Unary.
1100 ;; Multiplicative.
1102 ;; Additive.
1104 ;; Shift.
1106 ;; And.
1108 ;; Xor.
1110 ;; Or.
1114 ;; The operators as a flat list (without duplicates).
1120 t nil
1129 ;; These work like identifiers in Pike.
1136 ;; Regexp tested after an "operator" token in C++.
1137 t nil
1143 "Regexp matching the token before the ones in
1144 `c-overloadable-operators' when operators are specified in their
1147 languages without operator functions or where the complete operator
1148 identifier is listed in `c-overloadable-operators'.
1150 This regexp is assumed to not match any non-operator identifier."
1151 t nil
1156 ;; Note: the following alias is an old name which was a mis-spelling. It has
1157 ;; been corrected above and throughout cc-engine.el. It will be removed at
1158 ;; some release very shortly in the future. ACM, 2006-04-14.
1164 "List of the tokens made up of characters in the punctuation or
1165 parenthesis syntax classes that have uses other than as expression
1166 operators."
1185 ;; List of all tokens in the punctuation and parenthesis syntax
1186 ;; classes.
1192 ;; List containing all chars not in the word, symbol or
1193 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1194 ;; parenthesis and string delimiter chars.
1196 ;; Only go through the chars in the printable ASCII range. No
1197 ;; language so far has 8-bit or widestring operators.
1203 list)))
1206 ;; Regexp matching all tokens in the punctuation and parenthesis
1207 ;; syntax classes. Note that this also matches ".", which can start
1208 ;; a float.
1211 t
1217 ;; Regexp matching all assignment operators and only them. The
1218 ;; beginning of the first submatch is used to detect the end of the
1219 ;; token, along with the end of the whole match.
1222 ;; Need special case for "=" since it's a prefix of "==".
1234 ;; Regexp matching all tokens ending in ":" which are longer than one char.
1235 ;; Currently (2016-01-07) only used in C++ Mode.
1242 ;; Regexp matching all tokens containing "<" or ">" which are longer
1243 ;; than one char.
1246 t
1252 ;; Regexp matching the second and subsequent characters of all
1253 ;; multicharacter tokens that begin with "<".
1256 t
1262 ;; A list of second and subsequent characters of all multicharacter tokens
1263 ;; that begin with ">".
1265 t
1269 t
1274 ;; Regexp matching the second and subsequent characters of all
1275 ;; multicharacter tokens that begin with ">".
1280 ;; Regexp matching the second and subsequent characters of all
1281 ;; multicharacter tokens that begin with ">" except for those beginning with
1282 ;; ">>".
1287 t
1295 ;; Regexp matching multichar tokens containing ">", except ">>"
1299 t
1305 ;; The characters that should be considered to bound statements. To
1306 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1307 ;; begin with "^" to negate the set. If ? : operators should be
1308 ;; detected then the string must end with "?:".
1313 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1319 ;; Ops which signal C++11's new auto uses.
1320 t nil
1327 ;; Op used in the new C++11 auto function definition, indicating type.
1328 t nil
1335 "List of operators following which an apparent declaration \(e.g.
1337 \(as opposed to an arithmetic expression)."
1341 \f
1342 ;;; Syntactic whitespace.
1345 "Regexp matching an ordinary whitespace character.
1347 ;; "\\s " is not enough since it doesn't match line breaks.
1351 ;; Number of regexp grouping parens in `c-simple-ws'.
1355 "String that starts line comments, or nil if such don't exist.
1356 Line comments are always terminated by newlines. At least one of
1357 `c-block-comment-starter' and this one is assumed to be set.
1359 Note that it's currently not enough to set this to support a new
1360 comment style. Other stuff like the syntax table must also be set up
1361 properly."
1362 t "//"
1367 "String that starts block comments, or nil if such don't exist.
1368 Block comments are ended by `c-block-comment-ender', which is assumed
1369 to be set if this is. At least one of `c-line-comment-starter' and
1370 this one is assumed to be set.
1372 Note that it's currently not enough to set this to support a new
1373 comment style. Other stuff like the syntax table must also be set up
1374 properly."
1375 t "/*"
1376 awk nil)
1379 "String that ends block comments, or nil if such don't exist.
1381 Note that it's currently not enough to set this to support a new
1382 comment style. Other stuff like the syntax table must also be set up
1383 properly."
1384 t "*/"
1385 awk nil)
1388 ;; Regexp to match the start of any type of comment.
1394 re)))
1398 ;; Regexp which matches the start of a block comment (if such exists in the
1399 ;; language)
1407 ;; Regexp which matches the start of a line comment (if such exists in the
1408 ;; language; it does in all 7 CC Mode languages).
1416 ;; Regexp to match the start of comments and string literals.
1425 "Regexp to match the start of documentation comments."
1427 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1435 "String that starts comments inserted with M-; etc.
1436 `comment-start' is initialized from this."
1437 ;; Default: Prefer line comments to block comments, and pad with a space.
1441 ;; In C we still default to the block comment style since line
1442 ;; comments aren't entirely portable.
1447 "String that ends comments inserted with M-; etc.
1448 `comment-end' is initialized from this."
1449 ;; Default: Use block comment style if comment-start uses block
1450 ;; comments, and pad with a space in that case.
1460 "Regexp to match the start of a comment plus everything up to its body.
1461 `comment-start-skip' is initialized from this."
1462 ;; Default: Allow the last char of the comment starter(s) to be
1463 ;; repeated, then allow any amount of horizontal whitespace.
1476 "When non-nil, escaped EOLs inside comments are valid.
1477 This works in Emacs >= 25.1."
1478 t nil
1484 ;; Regexp matching any sequence that can start syntactic whitespace.
1485 ;; The only uncertain case is '#' when there are cpp directives.
1499 ;; Regexp matching any single character that might end syntactic whitespace.
1514 ;; Regexp matching an unterminated block comment that doesn't
1515 ;; contain line breaks, or nil in languages without block comments.
1516 ;; Does not contain a \| operator at the top level.
1520 ;; It's messy to cook together a regexp that matches anything
1521 ;; but c-block-comment-ender.
1529 "[^"
1530 ;; The quoting rules inside char classes are silly. :P
1539 "]"
1547 ;; Regexp matching a block comment that doesn't contain line breaks,
1548 ;; or nil in languages without block comments. The reason we don't
1549 ;; allow line breaks is to avoid going very far and risk running out
1550 ;; of regexp stack; this regexp is intended to handle only short
1551 ;; comments that might be put in the middle of limited constructs
1552 ;; like declarations. Does not contain a \| operator at the top
1553 ;; level.
1568 ;; Regexp matching a piece of syntactic whitespace that isn't a
1569 ;; sequence of simple whitespace characters. As opposed to
1570 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1571 ;; directives as syntactic whitespace.
1583 ;; Regexp matching syntactic whitespace, including possibly the
1584 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1585 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1586 ;; not contain a \| operator at the top level.
1594 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1598 ;; Regexp matching syntactic whitespace, which is at least one
1599 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1600 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1601 ;; not contain a \| operator at the top level.
1609 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1613 ;; Regexp matching syntactic whitespace without any line breaks. As
1614 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1615 ;; regard cpp directives as syntactic whitespace. Does not contain
1616 ;; a \| operator at the top level.
1624 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1628 ;; Regexp that matches when there is no syntactically significant
1629 ;; text before eol. Macros are regarded as syntactically
1630 ;; significant text here.
1632 ;; Match eol (possibly inside a block comment or preceded
1633 ;; by a line continuation backslash), or the beginning of a
1634 ;; line comment. Note: This has to be modified for awk
1635 ;; where line comments start with '#'.
1649 \f
1650 ;;; Defun handling.
1652 ;; The Emacs variables beginning-of-defun-function and end-of-defun-function
1653 ;; will be set so that commands like `mark-defun' and `narrow-to-defun' work
1654 ;; right. In older Emacsen, the key sequences C-M-a and C-M-e are, however,
1655 ;; bound directly to the CC Mode functions, allowing optimization for large n.
1656 ;; From Emacs 23, this isn't necessary any more, since n is passed to the two
1657 ;; functions.
1659 "Function to which beginning-of-defun-function will be set."
1660 t 'c-beginning-of-defun
1666 "Function to which end-of-defun-function will be set."
1667 t 'c-end-of-defun
1670 \f
1671 ;;; In-comment text handling.
1674 "Regexp to append to `paragraph-start'."
1675 t "$"
1681 "Regexp to append to `paragraph-separate'."
1682 t "$"
1686 \f
1687 ;;; Keyword lists.
1689 ;; Note: All and only all language constants containing keyword lists
1690 ;; should end with "-kwds"; they're automatically collected into the
1691 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1694 "Primitive type keywords. As opposed to the other keyword lists, the
1695 keywords listed here are fontified with the type face instead of the
1696 keyword face.
1698 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1699 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1700 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1701 will be handled.
1703 Do not try to modify this list for end user customizations; the
1704 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1705 the appropriate place for that."
1714 ;; Objective-C extends C, but probably not the new stuff in C99.
1721 ;; In CORBA PSDL:
1722 "ref"
1723 ;; The following can't really end a type, but we have to specify them
1724 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1725 ;; doesn't matter that much.
1728 ;; used as a builtin type.
1733 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1738 "Keywords that might act as prefixes for primitive types. Assumed to
1739 be a subset of `c-primitive-type-kwds'."
1740 t nil
1743 ;; In CORBA PSDL:
1748 of a variable declaration."
1753 ;; Adorned regexp matching `c-typedef-kwds'.
1758 "Keywords followed by a parenthesized expression, which stands for
1759 the type of that expression."
1760 t nil
1765 ;; Adorned regexp matching `c-typeof-kwds'.
1770 "Keywords where the following name - if any - is a type name, and
1771 where the keyword together with the symbol works as a type in
1772 declarations.
1774 Note that an alternative if the second part doesn't hold is
1775 `c-type-list-kwds'. Keywords on this list are typically also present
1776 on one of the `*-decl-kwds' lists."
1777 t nil
1783 ;; Adorned regexp matching `c-type-prefix-kwds'.
1788 "Type modifier keywords. These can occur almost anywhere in types
1789 but they don't build a type of themselves. Unlike the keywords on
1790 `c-primitive-type-kwds', they are fontified with the keyword face and
1791 not the type face."
1792 t nil
1798 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1799 ;; languages without such keywords.
1805 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1806 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1816 ;; All keywords that can start a type (i.e. are either a type prefix
1817 ;; or a complete type).
1824 "Keywords introducing declarations where the following block (if any)
1825 contains another declaration level that should be considered a class.
1827 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1828 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1829 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1830 will be handled.
1832 Note that presence on this list does not automatically treat the
1833 following identifier as a type; the keyword must also be present on
1834 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1835 t nil
1843 ;; In CORBA PSDL:
1845 ;; In CORBA CIDL:
1850 ;; Regexp matching the start of a class.
1855 "Keywords introducing declarations where the following block (if
1856 any) is a brace list.
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."
1866 ;; Regexp matching the start of declarations where the following
1867 ;; block is a brace list.
1872 "Keywords that might follow keywords in `c-brace-list-decl-kwds'
1873 and precede the opening brace."
1874 t nil
1878 ;; Regexp matching keywords that can fall between a brace-list
1879 ;; keyword and the associated brace list.
1884 "Set to t when we recognize a colon and then a type after an enum,
1885 e.g., enum foo : int { A, B, C };"
1886 t nil
1892 "Keywords where the following block (if any) contains another
1893 declaration level that should not be considered a class. For every
1894 keyword here, CC Mode will add a set of special syntactic symbols for
1896 `foo-open', `foo-close', and `infoo' symbols.
1898 The intention is that this category should be used for block
1899 constructs that aren't related to object orientation concepts like
1900 classes (which thus also include e.g. interfaces, templates,
1901 contracts, structs, etc). The more pragmatic distinction is that
1902 while most want some indentation inside classes, it's fairly common
1903 that they don't want it in some of these constructs, so it should be
1904 simple to configure that differently from classes. See also
1905 `c-class-decl-kwds'.
1907 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1908 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1909 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1910 will be handled."
1911 t nil
1915 ;; In CORBA CIDL:
1919 ;; Regexp matching the start of blocks besides classes that contain
1920 ;; another declaration level.
1929 'inextern-lang
1932 "Alist associating keywords in c-other-decl-block-decl-kwds with
1936 "Keywords introducing declarations where the identifier(s) being
1937 declared are types.
1939 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1940 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1941 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1942 will be handled."
1943 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1944 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1945 ;; {...}").
1948 ;; Languages that have a "typedef" construct.
1951 ;; Unlike most other languages, exception names are not handled as
1952 ;; types in IDL since they only can occur in "raises" specs.
1960 "Keywords introducing declarations where the \(first) identifier
1961 \(declarator) follows directly after the keyword, without any type.
1963 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1964 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1965 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1966 will be handled."
1967 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1968 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1969 ;; {...}").
1973 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1974 ;; `c-type-list-kwds' for IDL.
1977 ;; In CORBA PSDL:
1979 ;; In CORBA CIDL:
1985 "Keywords that can prefix normal declarations of identifiers
1986 \(and typically act as flags). Things like argument declarations
1987 inside function headers are also considered declarations in this
1988 sense.
1990 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1991 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1992 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1993 will be handled."
1994 t nil
2000 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
2004 ;; In CORBA PSDL:
2006 ;; In CORBA CIDL:
2008 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
2015 "Keywords that can start or prefix any declaration level construct,
2016 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
2017 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
2018 `c-typeless-decl-kwds' and `c-modifier-kwds'.
2020 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2021 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2022 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2023 will be handled."
2024 t nil
2030 "Keywords that always start declarations, wherever they occur.
2031 This can be used for declarations that aren't recognized by the normal
2032 combination of `c-decl-prefix-re' and `c-decl-start-re'."
2033 t nil
2034 ;; Classes can be declared anywhere in a Pike expression.
2038 "Keywords that can occur anywhere in a declaration level construct.
2039 This is used for self-contained things that can be tacked on anywhere
2040 on a declaration and that should be ignored to be able to recognize it
2041 correctly. Typical cases are compiler extensions like
2044 __declspec(noreturn) void foo();
2045 class __declspec(dllexport) classname {...};
2046 void foo() __attribute__((noreturn));
2048 Note that unrecognized plain symbols are skipped anyway if they occur
2049 before the type, so such things are not necessary to mention here.
2050 Mentioning them here is necessary only if they can occur in other
2051 places, or if they are followed by a construct that must be skipped
2053 examples above). In the last case, they alse need to be present on
2054 one of `c-type-list-kwds', `c-ref-list-kwds',
2055 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2056 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
2057 ;; NB: These are currently not recognized in all parts of a
2058 ;; declaration. Specifically, they aren't recognized in the middle
2059 ;; of multi-token types, inside declarators, and between the
2060 ;; identifier and the arglist paren of a function declaration.
2061 ;;
2062 ;; FIXME: This ought to be user customizable since compiler stuff
2063 ;; like this usually is wrapped in project specific macros. (It'd
2064 ;; of course be even better if we could cope without knowing this.)
2065 t nil
2067 "__attribute__"
2068 ;; MSVC extension.
2072 ;; Adorned regexp matching `c-decl-hangon-kwds'.
2077 ;; All keywords that can occur in the preamble of a declaration.
2078 ;; They typically occur before the type, but they are also matched
2079 ;; after presumptive types since we often can't be sure that
2080 ;; something is a type or just some sort of macro in front of the
2081 ;; declaration. They might be ambiguous with types or type
2082 ;; prefixes.
2095 ;; Adorned regexp of `c-prefix-spec-kwds'.
2101 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
2102 ;; ambiguous with types or type prefixes. These are the keywords (like
2103 ;; extern, namespace, but NOT template) that can modify a declaration.
2112 ;; Keywords that can occur after argument list of a function header
2113 ;; declaration, i.e. in the "K&R region".
2118 ;; Adorned regexp matching all keywords that can't appear at the
2119 ;; start of a declaration.
2134 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2135 ;; This variable is intended for use in c-beginning-of-statement-1.
2145 "Access protection label keywords in classes."
2146 t nil
2151 "Keywords introducing declarations that can contain a block which
2154 like that, it ends with the following `;' and not right away.
2156 The keywords on list are assumed to also be present on one of the
2157 `*-decl-kwds' lists."
2158 t nil
2163 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2164 ;; languages without such constructs.
2171 "Keywords introducing extra declaration specifiers in the region
2173 declarations."
2174 t nil
2177 "supports"
2178 ;; In CORBA PSDL:
2182 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2188 "Keywords that may be followed by a nonsymbol sexp before whatever
2189 construct it's part of continues."
2190 t nil
2194 "Keywords that may be followed by a comma separated list of type
2195 identifiers, where each optionally can be prefixed by keywords. (Can
2196 also be used for the special case when the list can contain only one
2197 element.)
2199 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2200 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2201 There's also no reason to add keywords that prefixes a normal
2202 declaration consisting of a type followed by a declarator (list), so
2203 the keywords on `c-modifier-kwds' should normally not be listed here
2204 either.
2206 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2207 or variable identifier (that's being defined)."
2208 t nil
2213 ;; In CORBA PSDL:
2218 "Keywords that may be followed by a comma separated list of
2219 reference (i.e. namespace/scope/module) identifiers, where each
2220 optionally can be prefixed by keywords. (Can also be used for the
2221 special case when the list can contain only one element.) Assumed to
2222 be mutually exclusive with `c-type-list-kwds'.
2224 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2225 or variable identifier (that's being defined)."
2226 t nil
2230 ;; In CORBA CIDL:
2235 "Keywords that may be followed (not necessarily directly) by a colon
2236 and then a comma separated list of type identifiers, where each
2237 optionally can be prefixed by keywords. (Can also be used for the
2238 special case when the list can contain only one element.)"
2239 t nil
2242 ;; In CORBA PSDL:
2246 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2247 forward to the colon. The end of the match is assumed to be directly
2249 regexp if `c-colon-type-list-kwds' isn't nil."
2251 ;; Disallow various common punctuation chars that can't come
2252 ;; before the ":" that starts the inherit list after "class"
2253 ;; or "struct" in C++. (Also used as default for other
2254 ;; languages.)
2259 "Keywords that may be followed by a parenthesis expression that doesn't
2260 contain type identifiers."
2261 t nil
2263 "__attribute__"
2264 ;; MSVC extension.
2268 "Keywords that may be followed by a parenthesis expression containing
2269 type identifiers separated by arbitrary tokens."
2270 t nil
2282 "Keywords that may be followed by an angle bracket expression
2284 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2285 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2286 if this isn't nil."
2287 t nil
2290 ;; In CORBA PSDL:
2294 "Keywords that can be followed by a C++ style template arglist; see
2295 `c-recognize-<>-arglists' for details. That language constant is
2296 assumed to be set if this isn't nil."
2297 t nil
2302 ;; All keywords that can be followed by an angle bracket sexp.
2308 ;; Adorned regexp matching keywords that can be followed by an angle
2309 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2314 "Keywords which, used inside a C++ style template arglist, introduce a type."
2315 t nil
2323 "Keywords that may be followed by a brace block containing a comma
2324 separated list of identifier definitions, i.e. like the list of
2325 identifiers that follows the type in a normal declaration."
2329 "Statement keywords followed directly by a substatement."
2334 idl nil)
2337 ;; Regexp matching the start of any statement followed directly by a
2338 ;; substatement (doesn't match a bare block, however).
2343 "Statement keywords optionally followed by a paren sexp.
2344 Keywords here should also be in `c-block-stmt-1-kwds'."
2345 t nil
2349 ;; Regexp matching the start of a statement which may be followed by a
2350 ;; paren sexp and will then be followed by a substatement.
2355 "Statement keywords followed by a paren sexp and then by a substatement."
2360 idl nil
2365 ;; Regexp matching the start of any statement followed by a paren sexp
2366 ;; and then by a substatement.
2371 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2377 ;; Regexp matching the start of any statement that has a
2378 ;; substatement (except a bare block). Nil in languages that
2379 ;; don't have such constructs.
2388 "Statement keywords followed by an expression or nothing."
2391 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2393 idl nil
2400 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2405 "Statement keywords followed by a parenthesis expression that
2406 nevertheless contains a list separated with `;' and not `,'."
2408 idl nil)
2411 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2416 "Statement keywords followed by an assembler expression."
2417 t nil
2421 ;; Regexp matching the start of an assembler statement. Nil in
2422 ;; languages that don't support that.
2431 awk nil)
2434 ;; Adorned regexp matching any "case"-like keyword.
2439 "Keywords introducing colon terminated labels in blocks."
2443 ;; Adorned regexp matching any keyword that introduces a label.
2448 "Keywords that might be followed by a label identifier."
2452 idl nil
2453 awk nil)
2456 "Keywords for constants."
2457 t nil
2469 "Keywords besides constants and operators that start primary expressions."
2470 t nil
2477 ;; Keywords that can occur anywhere in expressions. Built from
2478 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2482 t
2487 "Keywords that start lambda constructs, i.e. function definitions in
2488 expressions."
2489 t nil
2493 "Keywords that start constructs followed by statement blocks which can
2494 be used in expressions \(the gcc extension for this in C and C++ is
2495 handled separately by `c-recognize-paren-inexpr-blocks')."
2496 t nil
2500 "Keywords that can start classes inside expressions."
2501 t nil
2506 "Keywords that can start brace list blocks inside expressions.
2507 Note that Java specific rules are currently applied to tell this from
2508 `c-inexpr-class-kwds'."
2509 t nil
2513 ;; Regexp matching the start of a brace list in an expression, or
2514 ;; nil in languages that don't have such things. This should not
2515 ;; match brace lists recognized through `c-special-brace-lists'.
2522 ;; Regexp matching keywords in any construct that contain another
2523 ;; declaration level, i.e. that isn't followed by a function block
2524 ;; or brace list. When the first submatch matches, it's an
2525 ;; unambiguous construct, otherwise it's an ambiguous match that
2526 ;; might also be the return type of a function declaration.
2544 "Keywords that can introduce bitfields."
2545 t nil
2549 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2550 ;; languages without bitfield support.
2551 t nil
2556 "Keywords not accounted for by any other `*-kwds' language constant."
2557 t nil
2559 ;; In CORBA CIDL: (These are declaration keywords that never
2560 ;; can start a declaration.)
2563 \f
2564 ;;; Constants built from keywords.
2566 ;; Note: No `*-kwds' language constants may be defined below this point.
2570 ;; List of all the language constants that contain keyword lists.
2575 ;; Make the list of globally interned symbols
2576 ;; instead of ones interned in `c-lang-constants'.
2578 c-lang-constants)
2579 list)))
2582 ;; All keywords as a list.
2587 c-kwds-lang-consts)
2588 nil))
2592 ;; All keywords as an adorned regexp.
2597 ;; An alist with all the keywords in the cars. The cdr for each
2598 ;; keyword is a list of the symbols for the `*-kwds' lists that
2599 ;; contains it.
2605 c-kwds-lang-consts))))
2606 lang-const kwd-list kwd
2607 result-alist elem)
2619 result-alist))
2622 ;; An obarray containing all keywords as symbols. The property list
2623 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2624 ;; lists it's a member of.
2625 ;;
2626 ;; E.g. to see whether the string str contains a keyword on
2627 ;; `c-class-decl-kwds', one can do like this:
2628 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2629 ;; Which preferably is written using the associated functions in
2630 ;; cc-engine:
2631 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2633 ;; The obarray is not stored directly as a language constant since
2634 ;; the printed representation for obarrays used in .elc files isn't
2635 ;; complete.
2638 kwd lang-const-list
2645 ;; Emacs has an odd bug that causes `mapcan' to fail
2646 ;; with unintelligible errors. (XEmacs works.)
2647 ;; (2015-06-24): This bug has not yet been fixed.
2648 ;;(mapcan (lambda (lang-const)
2649 ;; (list lang-const t))
2650 ;; lang-const-list)
2653 lang-const-list))))
2654 obarray))
2657 ;; Adorned regexp matching all keywords that should be fontified
2658 ;; with the keywords face. I.e. that aren't types or constants.
2668 ;; Regexp matching the start of any primary expression, i.e. any
2669 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2670 ;; exclude keywords; they are excluded afterwards unless the second
2671 ;; submatch matches. If the first but not the second submatch
2672 ;; matches then it is an ambiguous primary expression; it could also
2673 ;; be a match of e.g. an infix operator. (The case with ambiguous
2674 ;; keyword operators isn't handled.)
2680 ;; Filter out the special case prefix
2681 ;; operators that are close parens.
2686 t
2692 postfix-if-paren
2693 left-assoc
2694 right-assoc
2695 right-assoc-sequence)
2696 t))
2699 in-or-postfix-ops
2702 in-or-postfix-ops
2707 ;; Take out all symbol class operators from `prefix-ops' and make the
2708 ;; first submatch from them together with `c-primary-expr-kwds'.
2715 ;; Match all ambiguous operators.
2722 ;; Now match all other symbols.
2726 ;; The chars that can start integer and floating point
2727 ;; constants.
2731 ;; The unambiguous operators from `prefix-ops'.
2737 ;; Match string and character literals.
2744 \f
2745 ;;; Additional constants for parser-level constructs.
2748 "Regexp matching a keyword that is followed by a colon, where
2749 the whole construct can precede a declaration.
2757 "Regexp matching something that might precede a declaration, cast or
2758 label, such as the last token of a preceding statement or declaration.
2759 This is used in the common situation where a declaration or cast
2760 doesn't start with any specific token that can be searched for.
2762 The regexp should not match bob; that is done implicitly. It can't
2763 require a match longer than one token. The end of the token is taken
2764 to be at the end of the first submatch, which is assumed to always
2765 match. It's undefined whether identifier syntax (see
2766 `c-identifier-syntax-table') is in effect or not. This regexp is
2767 assumed to be a superset of `c-label-prefix-re' if
2768 `c-recognize-colon-labels' is set.
2770 Besides this, `c-decl-start-kwds' is used to find declarations.
2772 Note: This variable together with `c-decl-start-re' and
2774 declaration/cast/label starts. I.e. they might produce more matches
2775 but should not miss anything (or else it's necessary to use text
2776 properties - see the next note). Wherever they match, the following
2777 construct is analyzed to see if it indeed is a declaration, cast or
2778 label. That analysis is not cheap, so it's important that not too
2779 many false matches are triggered.
2781 Note: If a declaration/cast/label start can't be detected with this
2782 variable, it's necessary to use the `c-type' text property with the
2783 value `c-decl-end' on the last char of the last token preceding the
2784 declaration. See the comment blurb at the start of cc-engine.el for
2785 more info."
2787 ;; We match a sequence of characters to skip over things like \"};\"
2788 ;; more quickly. We match ")" in C for K&R region declarations, and
2789 ;; in all languages except Java for when a cpp macro definition
2790 ;; begins with a declaration.
2793 ;; Match "<" in C++ to get the first argument in a template arglist.
2794 ;; In that case there's an additional check in `c-find-decl-spots'
2795 ;; that it got open paren syntax. Match ":" to aid in picking up
2796 ;; "public:", etc. This involves additional checks in
2797 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2798 ;; or labels.
2800 ;; Additionally match the protection directives in Objective-C.
2801 ;; Note that this doesn't cope with the longer directives, which we
2802 ;; would have to match from start to end since they don't end with
2803 ;; any easily recognized characters.
2807 ;; Pike is like C but we also match "[" for multiple value
2808 ;; assignments and type casts.
2814 "Regexp matching the start of any declaration, cast or label.
2815 It's used on the token after the one `c-decl-prefix-re' matched. This
2816 regexp should not try to match those constructs accurately as it's
2817 only used as a sieve to avoid spending more time checking other
2818 constructs."
2823 ;; Regexp matching something that might precede or start a
2824 ;; declaration, cast or label.
2825 ;;
2826 ;; If the first submatch matches, it's taken to match the end of a
2827 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2828 ;; It's built from `c-decl-prefix-re'.
2829 ;;
2830 ;; If the first submatch did not match, the match of the whole
2831 ;; regexp is taken to be at the first token in the declaration.
2832 ;; `c-decl-start-re' is not checked in this case.
2833 ;;
2834 ;; Design note: The reason the same regexp is used to match both
2835 ;; tokens that precede declarations and start them is to avoid an
2836 ;; extra regexp search from the previous declaration spot in
2837 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2838 ;; that it finds all declaration/cast/label starts in approximately
2839 ;; linear order, so we can't do the searches in two separate passes.
2850 ;; List containing the paren characters that can open a cast, or nil in
2851 ;; languages without casts.
2859 "List of syntactically relevant characters that never can occur before
2860 the open brace in any construct that contains a brace block, e.g. in
2863 class Foo: public Bar {int x();} a, *b;
2865 If parens can occur, the chars inside those aren't filtered with this
2866 list.
2868 `<' and `>' should be disallowed even if angle bracket arglists can
2869 occur. That since the search function needs to stop at them anyway to
2870 ensure they are given paren syntax.
2872 This is used to skip backward from the open brace to find the region
2875 possible for good performance."
2877 ;; Default to all chars that only occurs in nonsymbol tokens outside
2878 ;; identifiers.
2884 t
2885 t
2889 op pos)
2892 res))))
2894 ;; Allow cpp operations (where applicable).
2900 ;; Allow ':' for inherit list starters.
2904 ;; Allow ',' for multiple inherits.
2908 ;; Allow parentheses for anonymous inner classes in Java and class
2909 ;; initializer lists in Pike.
2913 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2918 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2919 ;; for `c-syntactic-skip-backward'.
2924 "Regexp matching any declarator operator that might precede the
2927 The end of the first submatch is taken as the end of the operator.
2928 Identifier syntax is in effect when this is matched \(see
2929 `c-identifier-syntax-table')."
2932 ;; Default to a regexp that never matches.
2934 ;; Check that there's no "=" afterwards to avoid matching tokens
2935 ;; like "*=".
2937 "[*(]"
2943 "[*(&]"
2948 ;; If this matches there's special treatment in
2949 ;; `c-font-lock-declarators' and
2950 ;; `c-font-lock-declarations' that check for a
2951 ;; complete name followed by ":: *".
2961 "Regexp matching the declarator operators that might follow after the
2964 it matches an open paren of some kind, the type declaration check
2965 continues at the corresponding close paren, otherwise the end of the
2966 first submatch is taken as the end of the operator. Identifier syntax
2967 is in effect when this is matched (see `c-identifier-syntax-table')."
2968 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2969 ;; function argument list parenthesis.
2977 "[)[(]"
2981 ;; "throw" in `c-type-modifier-kwds' is followed
2982 ;; by a parenthesis list, but no extra measures
2983 ;; are necessary to handle that.
2994 "This regexp is matched after a declarator expression where
2995 `c-type-decl-suffix-key' has matched. If it matches then the
2996 construct is taken as a declaration. It's typically used to match the
2997 beginning of a function body or whatever might occur after the
2998 function header in a function declaration or definition. It's
2999 undefined whether identifier syntax (see `c-identifier-syntax-table')
3000 is in effect or not.
3005 t "{"
3006 ;; If K&R style declarations should be recognized then one could
3007 ;; consider to match the start of any symbol since we want to match
3008 ;; the start of the first declaration in the "K&R region". That
3009 ;; could however produce false matches on code like "FOO(bar) x"
3010 ;; where FOO is a cpp macro, so it's better to leave it out and rely
3011 ;; on the other heuristics in that case.
3013 ;; Add on the keywords in `c-postfix-spec-kwds'.
3018 ;; Also match the colon that starts a base class initializer list in
3019 ;; C++. That can be confused with a function call before the colon
3020 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
3021 ;; match before such a thing (as a declaration-level construct;
3022 ;; matches inside arglist contexts are already excluded).
3029 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
3030 ;; matches ";" and ",".
3039 end of the operator. nil in languages without such operators. It's
3040 undefined whether identifier syntax (see `c-identifier-syntax-table')
3041 is in effect or not."
3042 t nil
3048 "Regexp matching operators that might follow after a type, or nil in
3049 languages that don't have such operators. The end of the first
3050 submatch is taken as the end of the operator. This should not match
3051 things like C++ template arglists if `c-recognize-<>-arglists' is set.
3052 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
3053 is in effect or not."
3054 t nil
3060 ;; Regexp matching the known type identifiers. This is initialized
3061 ;; from the type keywords and `*-font-lock-extra-types'. The first
3062 ;; submatch is the one that matches the type. Note that this regexp
3063 ;; assumes that symbol constituents like '_' and '$' have word
3064 ;; syntax.
3071 re))
3072 extra-types)))
3076 re))
3077 extra-types))))
3082 plain-strings)))
3083 regexp-strings)
3088 "List of open- and close-chars that makes up a pike-style brace list,
3090 list."
3091 t nil
3096 "Non-nil means K&R style argument declarations are valid."
3097 t nil
3098 c t)
3102 "Non-nil means function declarations without return type should be
3103 recognized. That can introduce an ambiguity with parenthesized macro
3104 calls before a brace block. This setting does not affect declarations
3105 that are preceded by a declaration starting keyword, so
3106 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
3107 t nil
3113 "Non-nil means C++ style template arglists should be handled. More
3114 specifically, this means a comma separated list of types or
3116 identifier or one of the keywords on `c-<>-type-kwds' or
3117 `c-<>-arglist-kwds'. If there's an identifier before then the whole
3118 expression is considered to be a type."
3122 ; generics is not yet coded in CC Mode.
3126 "A regexp matching any single character notable inside a <...> construct.
3128 any character which cannot be valid inside such a construct.
3129 This is used in `c-forward-<>-arglist-recur' to try to detect
3130 sequences of tokens which cannot be a template/generic construct.
3133 present it will treat an unbalanced closing paren as a sign of
3134 the invalidity of the putative template construct."
3135 t "[<;{},|+&->)]"
3140 "Non-nil means that an enum structure can contain declarations."
3141 t nil
3142 java t)
3146 "Non-nil means that parenthesis style initializers exist,
3147 i.e. constructs like
3149 Foo bar (gnu);
3151 in addition to the more classic
3153 Foo bar = gnu;"
3154 t nil
3159 "Non-nil to recognize gcc style in-expression blocks,
3160 i.e. compound statements surrounded by parentheses inside expressions."
3161 t nil
3167 ;; Regexp matching the start of angle bracket arglists in languages
3168 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3169 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3170 ;; assumed to surround the preceding symbol. The whole match is
3171 ;; assumed to end directly after the opening "<".
3181 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3182 ;; parens. The first submatch is assumed to surround
3183 ;; `c-opt-<>-arglist-start'.
3192 ;; Regexp matching the beginning of a declaration specifier in the
3193 ;; region between the header and the body of a declaration.
3194 ;;
3195 ;; TODO: This is currently not used uniformly; c++-mode and
3196 ;; java-mode each have their own ways of using it.
3197 t nil
3210 That includes labels in code and access keys in classes. This does
3211 not apply to labels recognized by `c-label-kwds' and
3212 `c-opt-extra-label-key'."
3213 t nil
3219 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3220 a generic colon label. Not used if `c-recognize-colon-labels' is
3221 nil."
3227 "Regexp matching things that can't occur in generic colon labels,
3228 neither in a statement nor in a declaration context. The regexp is
3229 tested at the beginning of every sexp in a suspected label,
3232 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3238 ;; Don't allow string literals, except in AWK. Character constants are OK.
3241 ;; Also check for open parens in C++, to catch member init lists in
3242 ;; constructors. We normally allow it so that macros with arguments
3243 ;; work in labels.
3248 "Regexp matching things that can't occur two symbols before a colon in
3256 "Optional regexp matching labels.
3257 Normally, labels are detected according to `c-nonlabel-token-key',
3258 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3259 be used if there are additional labels that aren't recognized that
3260 way."
3261 t nil
3266 ;; Regexp describing friend declarations classes, or nil in
3267 ;; languages that don't have such things.
3268 ;;
3269 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3270 ;; template skipping isn't done properly. This will disappear soon.
3271 t nil
3276 "<.+>"
3278 "friend"
3283 ;; Special regexp to match the start of Objective-C methods. The
3284 ;; first submatch is assumed to end after the + or - key.
3285 t nil
3287 ;; TODO: Ought to use a better method than anchoring on bol.
3292 "([^)]*)"
3299 ;; Must be set in buffers where the `c-type' text property might be
3300 ;; used with the value `c-decl-end'.
3301 ;;
3302 ;; `c-decl-end' is used to mark the ends of labels and access keys
3303 ;; to make interactive refontification work better.
3306 ;; `c-decl-end' is used to mark the end of the @-style directives in
3307 ;; Objective-C.
3308 objc t)
3312 "List of faces that might be put at the start of a type when
3313 `c-font-lock-declarations' runs. This must be evaluated (with `eval') at
3314 runtime to get the actual list of faces. This ensures that face name
3315 aliases in Emacs are resolved."
3317 font-lock-type-face
3318 c-reference-face-name
3319 font-lock-keyword-face)
3324 \f
3325 ;;; Wrap up the `c-lang-defvar' system.
3327 ;; Compile in the list of language variables that has been collected
3328 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3329 ;; first element of each is nil.
3333 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3334 ;; These are typically standard emacs variables such as `comment-start'.
3342 "Create a function that initializes all the language dependent variables
3343 for the given mode.
3345 This function should be evaluated at compile time, so that the
3346 function it returns is byte compiled with all the evaluated results
3347 from the language constants. Use the `c-init-language-vars' macro to
3348 accomplish that conveniently."
3351 ;; No need to byte compile this lambda since the byte compiler is
3352 ;; smart enough to detect the `funcall' construct in the
3353 ;; `c-init-language-vars' macro below and compile it all straight
3354 ;; into the function that contains `c-init-language-vars'.
3357 ;; This let sets up the context for `c-mode-var' and similar
3358 ;; that could be in the result from `c--macroexpand-all'.
3360 current-var source-eval)
3367 ;; `c-lang-const' will expand to the evaluated
3368 ;; constant immediately in `c--macroexpand-all'
3369 ;; below.
3375 ;; Note: The following `append' copies the
3376 ;; first argument. That list is small, so
3377 ;; this doesn't matter too much.
3381 ;; This diagnostic message isn't useful for end
3382 ;; users, so it's disabled.
3383 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3384 ;; (message ,(concat "%s compiled with CC Mode %s "
3385 ;; "but loaded with %s - evaluating "
3386 ;; "language constants from source")
3387 ;; ',mode ,c-version c-version)
3388 ;; (put ',mode 'c-has-warned-lang-consts t))
3400 current-var
3403 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3406 err)
3409 ;; Being evaluated from source. Always use the dynamic method to
3410 ;; work well when `c-lang-defvar's in this file are reevaluated
3411 ;; interactively.
3417 current-var)
3428 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3429 current-var err)
3431 ))
3434 "Initialize all the language dependent variables for the given mode.
3435 This macro is expanded at compile time to a form tailored for the mode
3436 in question, so MODE must be a constant. Therefore MODE is not
3437 evaluated and should not be quoted."
3440 \f
3443 ;; Local Variables:
3444 ;; indent-tabs-mode: t
3445 ;; tab-width: 8
3446 ;; End:
3447 ;;; cc-langs.el ends here