| blob | 83b8db3657e572776461890fb3fa4f8f96cafce0 |
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-after-change-extend-region-for-lambda-capture ; doesn't seem needed.
478 c-before-change-check-raw-strings
479 c-before-change-check-<>-operators
480 c-depropertize-CPP
481 c-before-after-change-digit-quote
482 c-invalidate-macro-cache
483 c-truncate-bs-cache)
485 c-depropertize-CPP
486 c-invalidate-macro-cache
487 c-truncate-bs-cache)
488 ;; java 'c-before-change-check-<>-operators
493 fs
495 "If non-nil, a list of functions called from c-before-change-hook.
496 Typically these will record enough state to allow
497 `c-before-font-lock-function' to extend the region to fontify,
498 and may do such things as removing text-properties which must be
499 recalculated.
501 These functions will be run in the order given. Each of them
502 takes 2 parameters, the BEG and END supplied to every
503 before-change function; on entry, the buffer will have been
504 widened and match-data will have been saved; point is undefined
505 on both entry and exit; the return value is ignored.
507 The functions are called even when font locking isn't enabled.
509 When the mode is initialized, the functions are called with
513 ;; For documentation see the following c-lang-defvar of the same name.
514 ;; The value here may be a list of functions or a single function.
516 c-change-expand-fl-region)
518 c-extend-font-lock-region-for-macros
519 c-neutralize-syntax-in-and-mark-CPP
520 c-change-expand-fl-region)
522 c-extend-font-lock-region-for-macros
523 ; c-before-after-change-extend-region-for-lambda-capture ; doesn't seem needed.
524 c-before-after-change-digit-quote
525 c-after-change-re-mark-raw-strings
526 c-neutralize-syntax-in-and-mark-CPP
527 c-restore-<>-properties
528 c-change-expand-fl-region)
530 c-restore-<>-properties
531 c-change-expand-fl-region)
533 c-awk-extend-and-syntax-tablify-region))
537 fs
539 "If non-nil, a list of functions called just before font locking.
540 Typically they will extend the region about to be fontified \(see
541 below) and will set `syntax-table' text properties on the region.
543 These functions will be run in the order given. Each of them
544 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
545 after-change function; point is undefined on both entry and exit;
546 on entry, the buffer will have been widened and match-data will
547 have been saved; the return value is ignored.
549 The functions may extend the region to be fontified by setting the
550 buffer local variables c-new-BEG and c-new-END.
552 The functions are called even when font locking is disabled.
554 When the mode is initialized, these functions are called with
558 t 'c-context-expand-fl-region
559 awk nil)
560 ;; For documentation see the following c-lang-defvar of the same name.
561 ;; The value here may be a list of functions or a single function.
565 fs
567 "If non-nil, a list of functions called just before context (or
568 other non-change) fontification is done. Typically they will
569 extend the region.
571 These functions will be run in the order given. Each of them
572 takes 2 parameters, the BEG and END of the region to be
573 fontified. Point is undefined on both entry and exit. On entry,
574 the buffer will have been widened and match-data will have been
575 saved; the return value is a cons of the adjusted
578 \f
579 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
582 Such a function takes one optional parameter, a buffer position (defaults to
583 point), and returns nil or t. This variable contains nil for languages which
584 don't have EOL terminated statements. "
585 t nil
592 The (admittedly kludgy) purpose of such a function is to prevent an infinite
593 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
594 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
595 even indirectly. This variable contains nil for languages which don't have
596 EOL terminated statements."
597 t nil
603 \f
604 ;;; Lexer-level syntax (identifiers, tokens etc).
607 "Whether the language has bitfield declarations."
608 t nil
614 a “long character”. In particular, this recognizes forms of constant
615 which `c-backward-sexp' needs to be called twice to move backwards over."
616 t nil
618 ;; FIXME!!! Extend this to cover strings, if needed. 2008-04-11
622 "Regexp that matches the start of a symbol, i.e. any identifier or
624 operator at the top level."
632 "Set of characters that can be part of a symbol.
633 This is of the form that fits inside [ ] in a regexp."
634 ;; Pike note: With the backquote identifiers this would include most
635 ;; operator chars too, but they are handled with other means instead.
641 "Regexp matching a sequence of at least one identifier character."
646 "Regexp matching identifiers and keywords (with submatch 0). Assumed
647 to match if `c-symbol-start' matches on the same position."
651 ;; Use the value from C here since the operator backquote is
652 ;; covered by the other alternative.
660 ;; Number of regexp grouping parens in `c-symbol-key'.
664 "This is the set of chars that can't be part of a symbol, i.e. the
665 negation of `c-symbol-chars'."
670 "Regexp that matches any character that can't be part of a symbol.
671 It's usually appended to other regexps to avoid matching a prefix.
672 It's assumed to not contain any submatchers."
673 ;; The same thing regarding Unicode identifiers applies here as to
674 ;; `c-symbol-key'.
678 "The operators that make up fully qualified identifiers. nil in
679 languages that don't have such things. See `c-operators' for a
680 description of the format. Binary operators can concatenate symbols,
684 This value is by default merged into `c-operators'."
685 t nil
689 ;; Java has "." to concatenate identifiers but it's also used for
690 ;; normal indexing. There's special code in the Java font lock
691 ;; rules to fontify qualified identifiers based on the standard
692 ;; naming conventions. We still define "." here to make
693 ;; `c-forward-name' move over as long names as possible which is
694 ;; necessary to e.g. handle throws clauses correctly.
703 ;; Appendable adorned regexp matching the operators that join
704 ;; symbols to fully qualified identifiers, or nil in languages that
705 ;; don't have such things.
706 ;;
707 ;; This was a docstring constant in 5.30. It still works but is now
708 ;; considered internal - change `c-identifier-ops' instead.
711 t)))
719 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
723 ;; Appendable adorned regexp matching operators that might precede
724 ;; an identifier and that are part of the identifier in that case.
725 ;; nil in languages without such things.
728 t)))
733 "Operators that can occur after a binary operator on `c-identifier-ops'
734 in identifiers. nil in languages that don't have such things.
736 Operators here should also have appropriate entries in `c-operators' -
737 it's not taken care of by default."
738 t nil
739 ;; '~' for destructors in C++, '*' for member pointers.
741 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
742 ;; in import declarations. (This will also match bogus things like
743 ;; "foo.*bar" but we don't bother.)
747 ;; Regexp that must match the token after
748 ;; `c-opt-identifier-concat-key' for it to be considered an
749 ;; identifier concatenation operator (which e.g. causes the
750 ;; preceding identifier to be fontified as a reference). Assumed to
751 ;; be a string if `c-opt-identifier-concat-key' is.
752 ;;
753 ;; This was a docstring constant in 5.30. It still works but is now
754 ;; considered internal - change `c-after-id-concat-ops' instead.
762 "Regexp that matches the start of an (optionally qualified) identifier.
763 It should also match all keywords. It's unspecified how far it
764 matches."
774 C++. It does not recognize the full range of syntactic whitespace
775 between the tokens; `c-forward-name' has to be used for that. It
776 should also not match identifiers containing parenthesis groupings,
778 ;; This regexp is more complex than strictly necessary to ensure
779 ;; that it can be matched with a minimum of backtracking.
800 ;; For flexibility, consider the symbol match
801 ;; optional if we've hit a
802 ;; `c-after-id-concat-ops' operator. This is
803 ;; also necessary to handle the "*" that can
804 ;; end import declaration identifiers in Java.
818 ;; This was a docstring constant in 5.30 but it's no longer used.
819 ;; It's only kept to avoid breaking third party code.
820 ;;
821 ;; Used to identify the submatch in `c-identifier-key' that
822 ;; surrounds the last symbol in the qualified identifier. It's a
823 ;; list of submatch numbers, of which the first that has a match is
824 ;; taken. It's assumed that at least one does when the regexp has
825 ;; matched.
826 t nil)
829 "Set if the language support backslash escaped newlines inside string
830 literals."
831 t nil
837 "Set if the language supports multiline string literals without escaped
838 newlines. If t, all string literals are multiline. If a character,
839 only literals where the open quote is immediately preceded by that
840 literal are multiline."
841 t nil
842 pike ?#)
847 "The symbol which starts preprocessor constructs when in the margin."
848 t "#"
853 "Regexp matching the prefix of a cpp directive in the languages that
854 normally use that macro preprocessor. Tested at bol or at boi.
856 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
857 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
863 "Regexp matching the prefix of a cpp directive anchored to BOL,
864 in the languages that have a macro preprocessor."
870 "Regexp matching the prefix of a cpp directive including the directive
871 name, or nil in languages without preprocessor support. The first
872 submatch surrounds the directive name."
876 ;; Pike, being a scripting language, recognizes hash-bangs too.
882 "List of cpp directives (without the prefix) that are followed by a
883 string message."
889 "List of cpp directives (without the prefix) that are followed by a
890 file name in angle brackets or quotes."
896 "Cpp directive (without the prefix) that is followed by a macro
897 definition, or nil if the language doesn't have any."
904 ;; Regexp matching everything up to the macro body of a cpp define, or the
905 ;; end of the logical line if there is none. Submatch 1 is the name of the
906 ;; macro. Set if c-opt-cpp-macro-define is.
911 ;; ^ ^ #defined name
917 ;; Regexp matching everything up to the end of the identifier defined
918 ;; by a cpp define.
927 "List of cpp directives (without the prefix) that are followed by an
928 expression."
933 "Regexp which matches the start of a CPP directive which contains an
934 expression, or nil if there aren't any in the language."
943 "List of functions in cpp expressions."
949 "List of all assignment operators."
955 idl nil)
958 "List describing all operators, along with their precedence and
959 associativity. The order in the list corresponds to the precedence of
960 the operators: The operators in each element are a group with the same
961 precedence, and the group has higher precedence than the groups in all
962 following elements. The car of each element describes the type of the
963 operator group, and the cdr is a list of the operator tokens in it.
964 The operator group types are:
966 `prefix' Unary prefix operators.
967 `postfix' Unary postfix operators.
968 `postfix-if-paren'
969 Unary postfix operators if and only if the chars have
970 parenthesis syntax.
971 `left-assoc' Binary left associative operators (i.e. a+b+c means (a+b)+c).
972 `right-assoc' Binary right associative operators (i.e. a=b=c means a=(b=c)).
973 `right-assoc-sequence'
974 Right associative operator that constitutes of a
975 sequence of tokens that separate expressions. All the
976 tokens in the group are in this case taken as
977 describing the sequence in one such operator, and the
978 order between them is therefore significant.
980 Operators containing a character with paren syntax are taken to match
981 with a corresponding open/close paren somewhere else. A postfix
982 operator with close paren syntax is taken to end a postfix expression
983 started somewhere earlier, rather than start a new one at point. Vice
984 versa for prefix operators with open paren syntax.
987 often are described as postfix operators are considered binary here,
988 since CC Mode treats every identifier as an expression."
990 ;; There's currently no code in CC Mode that exploits all the info
991 ;; in this variable; precedence, associativity etc are present as a
992 ;; preparation for future work.
994 ;; FIXME!!! C++11's "auto" operators "=" and "->" need to go in here
995 ;; somewhere. 2012-03-24.
1006 ;; Primary.
1015 ;; Postfix.
1017 ;; The following need special treatment.
1028 ;; Unary.
1035 ;; The following need special treatment.
1046 ;; Member selection.
1050 ;; Multiplicative.
1053 ;; Additive.
1056 ;; Shift.
1061 ;; Relational.
1066 ;; Equality.
1070 ;; Bitwise and.
1074 ;; Bitwise exclusive or.
1080 ;; Bitwise or.
1086 ;; Logical and.
1090 ;; Logical or.
1096 ;; Conditional.
1099 ;; Assignment.
1102 ;; Exception.
1106 ;; Sequence.
1109 ;; IDL got its own definition since it has a much smaller operator
1110 ;; set than the other languages.
1114 ;; Primary.
1116 ;; Unary.
1118 ;; Multiplicative.
1120 ;; Additive.
1122 ;; Shift.
1124 ;; And.
1126 ;; Xor.
1128 ;; Or.
1132 ;; The operators as a flat list (without duplicates).
1138 t nil
1147 ;; These work like identifiers in Pike.
1154 ;; Regexp tested after an "operator" token in C++.
1155 t nil
1161 "Regexp matching the token before the ones in
1162 `c-overloadable-operators' when operators are specified in their
1165 languages without operator functions or where the complete operator
1166 identifier is listed in `c-overloadable-operators'.
1168 This regexp is assumed to not match any non-operator identifier."
1169 t nil
1174 ;; Note: the following alias is an old name which was a mis-spelling. It has
1175 ;; been corrected above and throughout cc-engine.el. It will be removed at
1176 ;; some release very shortly in the future. ACM, 2006-04-14.
1182 "List of the tokens made up of characters in the punctuation or
1183 parenthesis syntax classes that have uses other than as expression
1184 operators."
1203 ;; List of all tokens in the punctuation and parenthesis syntax
1204 ;; classes.
1210 ;; List containing all chars not in the word, symbol or
1211 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1212 ;; parenthesis and string delimiter chars.
1214 ;; Only go through the chars in the printable ASCII range. No
1215 ;; language so far has 8-bit or widestring operators.
1221 list)))
1224 ;; Regexp matching all tokens in the punctuation and parenthesis
1225 ;; syntax classes. Note that this also matches ".", which can start
1226 ;; a float.
1229 t
1235 ;; Regexp matching all assignment operators and only them. The
1236 ;; beginning of the first submatch is used to detect the end of the
1237 ;; token, along with the end of the whole match.
1240 ;; Need special case for "=" since it's a prefix of "==".
1253 ;; Note: in the following, there are too many operators for AWK and IDL.
1268 ;; Regexp matching all tokens ending in ":" which are longer than one char.
1269 ;; Currently (2016-01-07) only used in C++ Mode.
1276 ;; Regexp matching all tokens containing "<" or ">" which are longer
1277 ;; than one char.
1280 t
1286 ;; Regexp matching the second and subsequent characters of all
1287 ;; multicharacter tokens that begin with "<".
1290 t
1296 ;; A list of second and subsequent characters of all multicharacter tokens
1297 ;; that begin with ">".
1299 t
1303 t
1308 ;; Regexp matching the second and subsequent characters of all
1309 ;; multicharacter tokens that begin with ">".
1314 ;; Regexp matching the second and subsequent characters of all
1315 ;; multicharacter tokens that begin with ">" except for those beginning with
1316 ;; ">>".
1321 t
1329 ;; Regexp matching multichar tokens containing ">", except ">>"
1333 t
1339 ;; The characters that should be considered to bound statements. To
1340 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1341 ;; begin with "^" to negate the set. If ? : operators should be
1342 ;; detected then the string must end with "?:".
1347 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1354 t nil
1361 ;; Ops which signal C++11's new auto uses.
1362 t nil
1369 ;; Op used in the new C++11 auto function definition, indicating type.
1370 t nil
1377 "List of operators following which an apparent declaration \(e.g.
1379 \(as opposed to an arithmetic expression)."
1384 "List of tokens which may precede a lambda declaration.
1386 Currently (2016-08) only used in C++ mode."
1399 ;; Regexp matching any token in the list `c-pre-lambda-tokens'.
1402 \f
1403 ;;; Syntactic whitespace.
1406 "Regexp matching an ordinary whitespace character.
1408 ;; "\\s " is not enough since it doesn't match line breaks.
1412 ;; Number of regexp grouping parens in `c-simple-ws'.
1416 "String that starts line comments, or nil if such don't exist.
1417 Line comments are always terminated by newlines. At least one of
1418 `c-block-comment-starter' and this one is assumed to be set.
1420 Note that it's currently not enough to set this to support a new
1421 comment style. Other stuff like the syntax table must also be set up
1422 properly."
1423 t "//"
1428 "String that starts block comments, or nil if such don't exist.
1429 Block comments are ended by `c-block-comment-ender', which is assumed
1430 to be set if this is. At least one of `c-line-comment-starter' and
1431 this one is assumed to be set.
1433 Note that it's currently not enough to set this to support a new
1434 comment style. Other stuff like the syntax table must also be set up
1435 properly."
1436 t "/*"
1437 awk nil)
1440 "String that ends block comments, or nil if such don't exist.
1442 Note that it's currently not enough to set this to support a new
1443 comment style. Other stuff like the syntax table must also be set up
1444 properly."
1445 t "*/"
1446 awk nil)
1449 ;; Regexp to match the start of any type of comment.
1455 re)))
1459 ;; Regexp which matches the start of a block comment (if such exists in the
1460 ;; language)
1468 ;; Regexp which matches the start of a line comment (if such exists in the
1469 ;; language; it does in all 7 CC Mode languages).
1477 ;; Regexp to match the start of comments and string literals.
1486 "Regexp to match the start of documentation comments."
1488 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1496 "String that starts comments inserted with M-; etc.
1497 `comment-start' is initialized from this."
1498 ;; Default: Prefer line comments to block comments, and pad with a space.
1502 ;; In C we still default to the block comment style since line
1503 ;; comments aren't entirely portable.
1508 "String that ends comments inserted with M-; etc.
1509 `comment-end' is initialized from this."
1510 ;; Default: Use block comment style if comment-start uses block
1511 ;; comments, and pad with a space in that case.
1521 "Regexp to match the start of a comment plus everything up to its body.
1522 `comment-start-skip' is initialized from this."
1523 ;; Default: Allow the last char of the comment starter(s) to be
1524 ;; repeated, then allow any amount of horizontal whitespace.
1537 "When non-nil, escaped EOLs inside comments are valid.
1538 This works in Emacs >= 25.1."
1539 t nil
1545 ;; Regexp matching any sequence that can start syntactic whitespace.
1546 ;; The only uncertain case is '#' when there are cpp directives.
1560 ;; Regexp matching any single character that might end syntactic whitespace.
1575 ;; Regexp matching an unterminated block comment that doesn't
1576 ;; contain line breaks, or nil in languages without block comments.
1577 ;; Does not contain a \| operator at the top level.
1581 ;; It's messy to cook together a regexp that matches anything
1582 ;; but c-block-comment-ender.
1590 "[^"
1591 ;; The quoting rules inside char classes are silly. :P
1600 "]"
1608 ;; Regexp matching a block comment that doesn't contain line breaks,
1609 ;; or nil in languages without block comments. The reason we don't
1610 ;; allow line breaks is to avoid going very far and risk running out
1611 ;; of regexp stack; this regexp is intended to handle only short
1612 ;; comments that might be put in the middle of limited constructs
1613 ;; like declarations. Does not contain a \| operator at the top
1614 ;; level.
1629 ;; Regexp matching a piece of syntactic whitespace that isn't a
1630 ;; sequence of simple whitespace characters. As opposed to
1631 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1632 ;; directives as syntactic whitespace.
1644 ;; Regexp matching syntactic whitespace, including possibly the
1645 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1646 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1647 ;; not contain a \| operator at the top level.
1655 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1659 ;; Regexp matching syntactic whitespace, which is at least one
1660 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1661 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1662 ;; not contain a \| operator at the top level.
1670 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1674 ;; Regexp matching syntactic whitespace without any line breaks. As
1675 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1676 ;; regard cpp directives as syntactic whitespace. Does not contain
1677 ;; a \| operator at the top level.
1685 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1689 ;; Regexp that matches when there is no syntactically significant
1690 ;; text before eol. Macros are regarded as syntactically
1691 ;; significant text here.
1693 ;; Match eol (possibly inside a block comment or preceded
1694 ;; by a line continuation backslash), or the beginning of a
1695 ;; line comment. Note: This has to be modified for awk
1696 ;; where line comments start with '#'.
1710 \f
1711 ;;; Defun handling.
1713 ;; The Emacs variables beginning-of-defun-function and end-of-defun-function
1714 ;; will be set so that commands like `mark-defun' and `narrow-to-defun' work
1715 ;; right. In older Emacsen, the key sequences C-M-a and C-M-e are, however,
1716 ;; bound directly to the CC Mode functions, allowing optimization for large n.
1717 ;; From Emacs 23, this isn't necessary any more, since n is passed to the two
1718 ;; functions.
1720 "Function to which beginning-of-defun-function will be set."
1721 t 'c-beginning-of-defun
1727 "Function to which end-of-defun-function will be set."
1728 t 'c-end-of-defun
1731 \f
1732 ;;; In-comment text handling.
1735 "Regexp to append to `paragraph-start'."
1736 t "$"
1742 "Regexp to append to `paragraph-separate'."
1743 t "$"
1747 \f
1748 ;;; Keyword lists.
1750 ;; Note: All and only all language constants containing keyword lists
1751 ;; should end with "-kwds"; they're automatically collected into the
1752 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1755 "Primitive type keywords. As opposed to the other keyword lists, the
1756 keywords listed here are fontified with the type face instead of the
1757 keyword face.
1759 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1760 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1761 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1762 will be handled.
1764 Do not try to modify this list for end user customizations; the
1765 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1766 the appropriate place for that."
1775 ;; Objective-C extends C, but probably not the new stuff in C99.
1782 ;; In CORBA PSDL:
1783 "ref"
1784 ;; The following can't really end a type, but we have to specify them
1785 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1786 ;; doesn't matter that much.
1789 ;; used as a builtin type.
1794 "Keywords which return a value to the calling function."
1796 idl nil)
1799 ;; Adorned regexp matching `c-return-kwds'.
1804 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1809 "Keywords that might act as prefixes for primitive types. Assumed to
1810 be a subset of `c-primitive-type-kwds'."
1811 t nil
1814 ;; In CORBA PSDL:
1819 of a variable declaration."
1824 ;; Adorned regexp matching `c-typedef-kwds'.
1829 "Keywords followed by a parenthesized expression, which stands for
1830 the type of that expression."
1831 t nil
1836 ;; Adorned regexp matching `c-typeof-kwds'.
1841 "Keywords where the following name - if any - is a type name, and
1842 where the keyword together with the symbol works as a type in
1843 declarations.
1845 Note that an alternative if the second part doesn't hold is
1846 `c-type-list-kwds'. Keywords on this list are typically also present
1847 on one of the `*-decl-kwds' lists."
1848 t nil
1854 ;; Adorned regexp matching `c-type-prefix-kwds'.
1859 "Type modifier keywords. These can occur almost anywhere in types
1860 but they don't build a type of themselves. Unlike the keywords on
1861 `c-primitive-type-kwds', they are fontified with the keyword face and
1862 not the type face."
1863 t nil
1869 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1870 ;; languages without such keywords.
1876 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1877 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1887 ;; All keywords that can start a type (i.e. are either a type prefix
1888 ;; or a complete type).
1896 effect in the declaration, but are syntactically like whitespace."
1897 t nil
1901 ;; An adorned regexp matching `c-type-decl-suffix-ws-ids-kwds'.
1907 "Keywords introducing declarations where the following block (if any)
1908 contains another declaration level that should be considered a class.
1910 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1911 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1912 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1913 will be handled.
1915 Note that presence on this list does not automatically treat the
1916 following identifier as a type; the keyword must also be present on
1917 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1918 t nil
1926 ;; In CORBA PSDL:
1928 ;; In CORBA CIDL:
1933 ;; Regexp matching the start of a class.
1938 "Keywords introducing declarations where the following block (if
1939 any) is a brace list.
1941 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1942 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1943 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1944 will be handled."
1949 ;; Regexp matching the start of declarations where the following
1950 ;; block is a brace list.
1955 "Keywords that might follow keywords in `c-brace-list-decl-kwds'
1956 and precede the opening brace."
1957 t nil
1961 ;; Regexp matching keywords that can fall between a brace-list
1962 ;; keyword and the associated brace list.
1967 "Set to t when we recognize a colon and then a type after an enum,
1968 e.g., enum foo : int { A, B, C };"
1969 t nil
1975 "Keywords where the following block (if any) contains another
1976 declaration level that should not be considered a class. For every
1977 keyword here, CC Mode will add a set of special syntactic symbols for
1979 `foo-open', `foo-close', and `infoo' symbols.
1981 The intention is that this category should be used for block
1982 constructs that aren't related to object orientation concepts like
1983 classes (which thus also include e.g. interfaces, templates,
1984 contracts, structs, etc). The more pragmatic distinction is that
1985 while most want some indentation inside classes, it's fairly common
1986 that they don't want it in some of these constructs, so it should be
1987 simple to configure that differently from classes. See also
1988 `c-class-decl-kwds'.
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
1998 ;; In CORBA CIDL:
2002 ;; Regexp matching the start of blocks besides classes that contain
2003 ;; another declaration level.
2012 'inextern-lang
2015 "Alist associating keywords in c-other-decl-block-decl-kwds with
2019 "Keywords introducing declarations where the identifier(s) being
2020 declared are types.
2022 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2023 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2024 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2025 will be handled."
2026 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
2027 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
2028 ;; {...}").
2031 ;; Languages that have a "typedef" construct.
2034 ;; Unlike most other languages, exception names are not handled as
2035 ;; types in IDL since they only can occur in "raises" specs.
2043 "Keywords introducing declarations where the \(first) identifier
2044 \(declarator) follows directly after the keyword, without any type.
2046 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2047 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2048 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2049 will be handled."
2050 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
2051 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
2052 ;; {...}").
2056 ;; Note: "manages" for CORBA CIDL clashes with its presence on
2057 ;; `c-type-list-kwds' for IDL.
2060 ;; In CORBA PSDL:
2062 ;; In CORBA CIDL:
2068 "Keywords that can prefix normal declarations of identifiers
2069 \(and typically act as flags). Things like argument declarations
2070 inside function headers are also considered declarations in this
2071 sense.
2073 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2074 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2075 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2076 will be handled."
2077 t nil
2083 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
2087 ;; In CORBA PSDL:
2089 ;; In CORBA CIDL:
2091 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
2098 "Keywords that can start or prefix any declaration level construct,
2099 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
2100 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
2101 `c-typeless-decl-kwds' and `c-modifier-kwds'.
2103 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2104 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2105 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2106 will be handled."
2107 t nil
2113 "Keywords that always start declarations, wherever they occur.
2114 This can be used for declarations that aren't recognized by the normal
2115 combination of `c-decl-prefix-re' and `c-decl-start-re'."
2116 t nil
2117 ;; Classes can be declared anywhere in a Pike expression.
2121 "Keywords that can occur anywhere in a declaration level construct.
2122 This is used for self-contained things that can be tacked on anywhere
2123 on a declaration and that should be ignored to be able to recognize it
2124 correctly. Typical cases are compiler extensions like
2127 __declspec(noreturn) void foo();
2128 class __declspec(dllexport) classname {...};
2129 void foo() __attribute__((noreturn));
2131 Note that unrecognized plain symbols are skipped anyway if they occur
2132 before the type, so such things are not necessary to mention here.
2133 Mentioning them here is necessary only if they can occur in other
2134 places, or if they are followed by a construct that must be skipped
2136 examples above). In the last case, they alse need to be present on
2137 one of `c-type-list-kwds', `c-ref-list-kwds',
2138 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2139 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
2140 ;; NB: These are currently not recognized in all parts of a
2141 ;; declaration. Specifically, they aren't recognized in the middle
2142 ;; of multi-token types, inside declarators, and between the
2143 ;; identifier and the arglist paren of a function declaration.
2144 ;;
2145 ;; FIXME: This ought to be user customizable since compiler stuff
2146 ;; like this usually is wrapped in project specific macros. (It'd
2147 ;; of course be even better if we could cope without knowing this.)
2148 t nil
2150 "__attribute__"
2151 ;; MSVC extension.
2155 ;; Adorned regexp matching `c-decl-hangon-kwds'.
2160 ;; All keywords that can occur in the preamble of a declaration.
2161 ;; They typically occur before the type, but they are also matched
2162 ;; after presumptive types since we often can't be sure that
2163 ;; something is a type or just some sort of macro in front of the
2164 ;; declaration. They might be ambiguous with types or type
2165 ;; prefixes.
2178 ;; Adorned regexp of `c-prefix-spec-kwds'.
2184 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
2185 ;; ambiguous with types or type prefixes. These are the keywords (like
2186 ;; extern, namespace, but NOT template) that can modify a declaration.
2195 ;; Keywords that can occur after argument list of a function header
2196 ;; declaration, i.e. in the "K&R region".
2201 ;; Adorned regexp matching all keywords that can't appear at the
2202 ;; start of a declaration.
2217 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2218 ;; This variable is intended for use in c-beginning-of-statement-1.
2228 "Access protection label keywords in classes."
2229 t nil
2234 "Keywords introducing declarations that can contain a block which
2237 like that, it ends with the following `;' and not right away.
2239 The keywords on list are assumed to also be present on one of the
2240 `*-decl-kwds' lists."
2241 t nil
2246 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2247 ;; languages without such constructs.
2254 "Keywords introducing extra declaration specifiers in the region
2256 declarations."
2257 t nil
2260 "supports"
2261 ;; In CORBA PSDL:
2265 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2271 "Keywords that may be followed by a nonsymbol sexp before whatever
2272 construct it's part of continues."
2273 t nil
2277 "Keywords that may be followed by a comma separated list of type
2278 identifiers, where each optionally can be prefixed by keywords. (Can
2279 also be used for the special case when the list can contain only one
2280 element.)
2282 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2283 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2284 There's also no reason to add keywords that prefixes a normal
2285 declaration consisting of a type followed by a declarator (list), so
2286 the keywords on `c-modifier-kwds' should normally not be listed here
2287 either.
2289 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2290 or variable identifier (that's being defined)."
2291 t nil
2296 ;; In CORBA PSDL:
2301 "Keywords that may be followed by a comma separated list of
2302 reference (i.e. namespace/scope/module) identifiers, where each
2303 optionally can be prefixed by keywords. (Can also be used for the
2304 special case when the list can contain only one element.) Assumed to
2305 be mutually exclusive with `c-type-list-kwds'.
2307 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2308 or variable identifier (that's being defined)."
2309 t nil
2313 ;; In CORBA CIDL:
2318 "Keywords that may be followed (not necessarily directly) by a colon
2319 and then a comma separated list of type identifiers, where each
2320 optionally can be prefixed by keywords. (Can also be used for the
2321 special case when the list can contain only one element.)"
2322 t nil
2325 ;; In CORBA PSDL:
2329 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2330 forward to the colon. The end of the match is assumed to be directly
2332 regexp if `c-colon-type-list-kwds' isn't nil."
2334 ;; Disallow various common punctuation chars that can't come
2335 ;; before the ":" that starts the inherit list after "class"
2336 ;; or "struct" in C++. (Also used as default for other
2337 ;; languages.)
2342 "Keywords that may be followed by a parenthesis expression that doesn't
2343 contain type identifiers."
2344 t nil
2346 "__attribute__"
2347 ;; MSVC extension.
2356 "Keywords that may be followed by a parenthesis expression containing
2357 type identifiers separated by arbitrary tokens."
2358 t nil
2370 "Keywords that may be followed by an angle bracket expression
2372 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2373 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2374 if this isn't nil."
2375 t nil
2378 ;; In CORBA PSDL:
2382 "Keywords that can be followed by a C++ style template arglist; see
2383 `c-recognize-<>-arglists' for details. That language constant is
2384 assumed to be set if this isn't nil."
2385 t nil
2390 ;; All keywords that can be followed by an angle bracket sexp.
2396 ;; Adorned regexp matching keywords that can be followed by an angle
2397 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2402 "Keywords which, used inside a C++ style template arglist, introduce a type."
2403 t nil
2411 "Keywords that may be followed by a brace block containing a comma
2412 separated list of identifier definitions, i.e. like the list of
2413 identifiers that follows the type in a normal declaration."
2417 "Statement keywords followed directly by a substatement."
2422 idl nil)
2425 ;; Regexp matching the start of any statement followed directly by a
2426 ;; substatement (doesn't match a bare block, however).
2431 "Statement keywords optionally followed by a paren sexp.
2432 Keywords here should also be in `c-block-stmt-1-kwds'."
2433 t nil
2437 ;; Regexp matching the start of a statement which may be followed by a
2438 ;; paren sexp and will then be followed by a substatement.
2443 "Statement keywords followed by a paren sexp and then by a substatement."
2448 idl nil
2453 ;; Regexp matching the start of any statement followed by a paren sexp
2454 ;; and then by a substatement.
2459 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2465 ;; Regexp matching the start of any statement that has a
2466 ;; substatement (except a bare block). Nil in languages that
2467 ;; don't have such constructs.
2476 "Statement keywords followed by an expression or nothing."
2479 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2481 idl nil
2488 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2493 "Statement keywords followed by a parenthesis expression that
2494 nevertheless contains a list separated with `;' and not `,'."
2496 idl nil)
2499 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2504 "Statement keywords followed by an assembler expression."
2505 t nil
2509 ;; Regexp matching the start of an assembler statement. Nil in
2510 ;; languages that don't support that.
2519 awk nil)
2522 ;; Adorned regexp matching any "case"-like keyword.
2527 "Keywords introducing colon terminated labels in blocks."
2531 ;; Adorned regexp matching any keyword that introduces a label.
2536 "Keywords that might be followed by a label identifier."
2540 idl nil
2541 awk nil)
2544 "Keywords for constants."
2545 t nil
2557 "Keywords besides constants and operators that start primary expressions."
2558 t nil
2565 ;; Keywords that can occur anywhere in expressions. Built from
2566 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2570 t
2575 "Keywords that start lambda constructs, i.e. function definitions in
2576 expressions."
2577 t nil
2581 "Keywords that start constructs followed by statement blocks which can
2582 be used in expressions \(the gcc extension for this in C and C++ is
2583 handled separately by `c-recognize-paren-inexpr-blocks')."
2584 t nil
2588 "Keywords that can start classes inside expressions."
2589 t nil
2594 "Keywords that can start brace list blocks inside expressions.
2595 Note that Java specific rules are currently applied to tell this from
2596 `c-inexpr-class-kwds'."
2597 t nil
2601 ;; Regexp matching the start of a brace list in an expression, or
2602 ;; nil in languages that don't have such things. This should not
2603 ;; match brace lists recognized through `c-special-brace-lists'.
2610 ;; Keywords that can introduce another declaration level, i.e. where a
2611 ;; following "{" isn't a function block or brace list. Note that, for
2612 ;; historical reasons, `c-decl-block-key' is NOT constructed from this lang
2613 ;; const.
2621 ;; Regexp matching any keyword or operator relevant to the brace stack (see
2622 ;; `c-update-brace-stack' in cc-engine.el).
2632 ;; Regexp matching any keyword or operator relevant to the brace stack when
2633 ;; a semicolon is not relevant (see `c-update-brace-stack' in
2634 ;; cc-engine.el).
2645 ;; Regexp matching keywords in any construct that contain another
2646 ;; declaration level, i.e. that isn't followed by a function block
2647 ;; or brace list. When the first submatch matches, it's an
2648 ;; unambiguous construct, otherwise it's an ambiguous match that
2649 ;; might also be the return type of a function declaration.
2667 "Keywords that can introduce bitfields."
2668 t nil
2672 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2673 ;; languages without bitfield support.
2674 t nil
2679 "Keywords not accounted for by any other `*-kwds' language constant."
2680 t nil
2682 ;; In CORBA CIDL: (These are declaration keywords that never
2683 ;; can start a declaration.)
2686 \f
2687 ;;; Constants built from keywords.
2689 ;; Note: No `*-kwds' language constants may be defined below this point.
2693 ;; List of all the language constants that contain keyword lists.
2698 ;; Make the list of globally interned symbols
2699 ;; instead of ones interned in `c-lang-constants'.
2701 c-lang-constants)
2702 list)))
2705 ;; All keywords as a list.
2710 c-kwds-lang-consts)
2711 nil))
2715 ;; All keywords as an adorned regexp.
2720 ;; An alist with all the keywords in the cars. The cdr for each
2721 ;; keyword is a list of the symbols for the `*-kwds' lists that
2722 ;; contains it.
2728 c-kwds-lang-consts))))
2729 lang-const kwd-list kwd
2730 result-alist elem)
2742 result-alist))
2745 ;; An obarray containing all keywords as symbols. The property list
2746 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2747 ;; lists it's a member of.
2748 ;;
2749 ;; E.g. to see whether the string str contains a keyword on
2750 ;; `c-class-decl-kwds', one can do like this:
2751 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2752 ;; Which preferably is written using the associated functions in
2753 ;; cc-engine:
2754 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2756 ;; The obarray is not stored directly as a language constant since
2757 ;; the printed representation for obarrays used in .elc files isn't
2758 ;; complete.
2761 kwd lang-const-list
2768 ;; Emacs has an odd bug that causes `mapcan' to fail
2769 ;; with unintelligible errors. (XEmacs works.)
2770 ;; (2015-06-24): This bug has not yet been fixed.
2771 ;;(mapcan (lambda (lang-const)
2772 ;; (list lang-const t))
2773 ;; lang-const-list)
2776 lang-const-list))))
2777 obarray))
2780 ;; Adorned regexp matching all keywords that should be fontified
2781 ;; with the keywords face. I.e. that aren't types or constants.
2791 ;; Regexp matching the start of any primary expression, i.e. any
2792 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2793 ;; exclude keywords; they are excluded afterwards unless the second
2794 ;; submatch matches. If the first but not the second submatch
2795 ;; matches then it is an ambiguous primary expression; it could also
2796 ;; be a match of e.g. an infix operator. (The case with ambiguous
2797 ;; keyword operators isn't handled.)
2803 ;; Filter out the special case prefix
2804 ;; operators that are close parens.
2809 t
2815 postfix-if-paren
2816 left-assoc
2817 right-assoc
2818 right-assoc-sequence)
2819 t))
2822 in-or-postfix-ops
2825 in-or-postfix-ops
2830 ;; Take out all symbol class operators from `prefix-ops' and make the
2831 ;; first submatch from them together with `c-primary-expr-kwds'.
2838 ;; Match all ambiguous operators.
2845 ;; Now match all other symbols.
2849 ;; The chars that can start integer and floating point
2850 ;; constants.
2854 ;; The unambiguous operators from `prefix-ops'.
2860 ;; Match string and character literals.
2867 \f
2868 ;;; Additional constants for parser-level constructs.
2871 "Regexp matching a keyword that is followed by a colon, where
2872 the whole construct can precede a declaration.
2880 "Regexp matching something that might precede a declaration, cast or
2881 label, such as the last token of a preceding statement or declaration.
2882 This is used in the common situation where a declaration or cast
2883 doesn't start with any specific token that can be searched for.
2885 The regexp should not match bob; that is done implicitly. It can't
2886 require a match longer than one token. The end of the token is taken
2887 to be at the end of the first submatch, which is assumed to always
2888 match. It's undefined whether identifier syntax (see
2889 `c-identifier-syntax-table') is in effect or not. This regexp is
2890 assumed to be a superset of `c-label-prefix-re' if
2891 `c-recognize-colon-labels' is set.
2893 Besides this, `c-decl-start-kwds' is used to find declarations.
2895 Note: This variable together with `c-decl-start-re' and
2897 declaration/cast/label starts. I.e. they might produce more matches
2898 but should not miss anything (or else it's necessary to use text
2899 properties - see the next note). Wherever they match, the following
2900 construct is analyzed to see if it indeed is a declaration, cast or
2901 label. That analysis is not cheap, so it's important that not too
2902 many false matches are triggered.
2904 Note: If a declaration/cast/label start can't be detected with this
2905 variable, it's necessary to use the `c-type' text property with the
2906 value `c-decl-end' on the last char of the last token preceding the
2907 declaration. See the comment blurb at the start of cc-engine.el for
2908 more info."
2910 ;; We match a sequence of characters to skip over things like \"};\"
2911 ;; more quickly. We match ")" in C for K&R region declarations, and
2912 ;; in all languages except Java for when a cpp macro definition
2913 ;; begins with a declaration.
2916 ;; Match "<" in C++ to get the first argument in a template arglist.
2917 ;; In that case there's an additional check in `c-find-decl-spots'
2918 ;; that it got open paren syntax. Match ":" to aid in picking up
2919 ;; "public:", etc. This involves additional checks in
2920 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2921 ;; or labels.
2923 ;; Additionally match the protection directives in Objective-C.
2924 ;; Note that this doesn't cope with the longer directives, which we
2925 ;; would have to match from start to end since they don't end with
2926 ;; any easily recognized characters.
2930 ;; Pike is like C but we also match "[" for multiple value
2931 ;; assignments and type casts.
2937 "Regexp matching the start of any declaration, cast or label.
2938 It's used on the token after the one `c-decl-prefix-re' matched. This
2939 regexp should not try to match those constructs accurately as it's
2940 only used as a sieve to avoid spending more time checking other
2941 constructs."
2946 ;; Regexp matching something that might precede or start a
2947 ;; declaration, cast or label.
2948 ;;
2949 ;; If the first submatch matches, it's taken to match the end of a
2950 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2951 ;; It's built from `c-decl-prefix-re'.
2952 ;;
2953 ;; If the first submatch did not match, the match of the whole
2954 ;; regexp is taken to be at the first token in the declaration.
2955 ;; `c-decl-start-re' is not checked in this case.
2956 ;;
2957 ;; Design note: The reason the same regexp is used to match both
2958 ;; tokens that precede declarations and start them is to avoid an
2959 ;; extra regexp search from the previous declaration spot in
2960 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2961 ;; that it finds all declaration/cast/label starts in approximately
2962 ;; linear order, so we can't do the searches in two separate passes.
2973 ;; List containing the paren characters that can open a cast, or nil in
2974 ;; languages without casts.
2982 "List of syntactically relevant characters that never can occur before
2983 the open brace in any construct that contains a brace block, e.g. in
2986 class Foo: public Bar {int x();} a, *b;
2988 If parens can occur, the chars inside those aren't filtered with this
2989 list.
2991 `<' and `>' should be disallowed even if angle bracket arglists can
2992 occur. That since the search function needs to stop at them anyway to
2993 ensure they are given paren syntax.
2995 This is used to skip backward from the open brace to find the region
2998 possible for good performance."
3000 ;; Default to all chars that only occurs in nonsymbol tokens outside
3001 ;; identifiers.
3007 t
3008 t
3012 op pos)
3015 res))))
3017 ;; Allow cpp operations (where applicable).
3023 ;; Allow ':' for inherit list starters.
3027 ;; Allow ',' for multiple inherits.
3031 ;; Allow parentheses for anonymous inner classes in Java and class
3032 ;; initializer lists in Pike.
3036 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
3041 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
3042 ;; for `c-syntactic-skip-backward'.
3047 "Regexp matching any declarator operator that might precede the
3050 The end of the first submatch is taken as the end of the operator.
3051 Identifier syntax is in effect when this is matched \(see
3052 `c-identifier-syntax-table')."
3055 ;; Default to a regexp that never matches.
3057 ;; Check that there's no "=" afterwards to avoid matching tokens
3058 ;; like "*=".
3060 "[*(]"
3066 "&&"
3070 "[*(&]"
3075 ;; If this matches there's special treatment in
3076 ;; `c-font-lock-declarators' and
3077 ;; `c-font-lock-declarations' that check for a
3078 ;; complete name followed by ":: *".
3088 "Regexp matching any declarator operator which isn't a keyword
3089 that might precede the identifier in a declaration, e.g. the
3091 as the end of the operator. Identifier syntax is in effect when
3092 this is matched \(see `c-identifier-syntax-table')."
3093 t ;; Default to a regexp that never matches.
3095 ;; Check that there's no "=" afterwards to avoid matching tokens
3096 ;; like "*=".
3110 "Regexp matching the declarator operators that might follow after the
3113 it matches an open paren of some kind, the type declaration check
3114 continues at the corresponding close paren, otherwise the end of the
3115 first submatch is taken as the end of the operator. Identifier syntax
3116 is in effect when this is matched (see `c-identifier-syntax-table')."
3117 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
3118 ;; function argument list parenthesis.
3126 "[)[(]"
3130 ;; "throw" in `c-type-modifier-kwds' is followed
3131 ;; by a parenthesis list, but no extra measures
3132 ;; are necessary to handle that.
3143 "This regexp is matched after a declarator expression where
3144 `c-type-decl-suffix-key' has matched. If it matches then the
3145 construct is taken as a declaration. It's typically used to match the
3146 beginning of a function body or whatever might occur after the
3147 function header in a function declaration or definition. It's
3148 undefined whether identifier syntax (see `c-identifier-syntax-table')
3149 is in effect or not.
3154 t "{"
3155 ;; If K&R style declarations should be recognized then one could
3156 ;; consider to match the start of any symbol since we want to match
3157 ;; the start of the first declaration in the "K&R region". That
3158 ;; could however produce false matches on code like "FOO(bar) x"
3159 ;; where FOO is a cpp macro, so it's better to leave it out and rely
3160 ;; on the other heuristics in that case.
3162 ;; Add on the keywords in `c-postfix-spec-kwds'.
3167 ;; Also match the colon that starts a base class initializer list in
3168 ;; C++. That can be confused with a function call before the colon
3169 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
3170 ;; match before such a thing (as a declaration-level construct;
3171 ;; matches inside arglist contexts are already excluded).
3178 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
3179 ;; matches ";" and ",".
3188 end of the operator. nil in languages without such operators. It's
3189 undefined whether identifier syntax (see `c-identifier-syntax-table')
3190 is in effect or not."
3191 t nil
3197 "Regexp matching operators that might follow after a type, or nil in
3198 languages that don't have such operators. The end of the first
3199 submatch is taken as the end of the operator. This should not match
3200 things like C++ template arglists if `c-recognize-<>-arglists' is set.
3201 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
3202 is in effect or not."
3203 t nil
3209 ;; Regexp matching the known type identifiers. This is initialized
3210 ;; from the type keywords and `*-font-lock-extra-types'. The first
3211 ;; submatch is the one that matches the type. Note that this regexp
3212 ;; assumes that symbol constituents like '_' and '$' have word
3213 ;; syntax.
3220 re))
3221 extra-types)))
3225 re))
3226 extra-types))))
3231 plain-strings)))
3232 regexp-strings)
3237 "List of open- and close-chars that makes up a pike-style brace list,
3239 list."
3240 t nil
3245 "Non-nil means K&R style argument declarations are valid."
3246 t nil
3247 c t)
3251 "A regexp matching tokens which, preceding an identifier, signify a bracelist.
3252 "
3258 "Non-nil means function declarations without return type should be
3259 recognized. That can introduce an ambiguity with parenthesized macro
3260 calls before a brace block. This setting does not affect declarations
3261 that are preceded by a declaration starting keyword, so
3262 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
3263 t nil
3269 "Non-nil means C++ style template arglists should be handled. More
3270 specifically, this means a comma separated list of types or
3272 identifier or one of the keywords on `c-<>-type-kwds' or
3273 `c-<>-arglist-kwds'. If there's an identifier before then the whole
3274 expression is considered to be a type."
3278 ; generics is not yet coded in CC Mode.
3282 "A regexp matching any single character notable inside a <...> construct.
3284 any character which cannot be valid inside such a construct.
3285 This is used in `c-forward-<>-arglist-recur' to try to detect
3286 sequences of tokens which cannot be a template/generic construct.
3289 present it will treat an unbalanced closing paren as a sign of
3290 the invalidity of the putative template construct."
3291 t "[<;{},|+&->)]"
3296 "Non-nil means that an enum structure can contain declarations."
3297 t nil
3298 java t)
3302 "Non-nil means that parenthesis style initializers exist,
3303 i.e. constructs like
3305 Foo bar (gnu);
3307 in addition to the more classic
3309 Foo bar = gnu;"
3310 t nil
3315 "Non-nil to recognize gcc style in-expression blocks,
3316 i.e. compound statements surrounded by parentheses inside expressions."
3317 t nil
3323 ;; Regexp matching the start of angle bracket arglists in languages
3324 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3325 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3326 ;; assumed to surround the preceding symbol. The whole match is
3327 ;; assumed to end directly after the opening "<".
3337 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3338 ;; parens. The first submatch is assumed to surround
3339 ;; `c-opt-<>-arglist-start'.
3348 ;; Regexp matching the beginning of a declaration specifier in the
3349 ;; region between the header and the body of a declaration.
3350 ;;
3351 ;; TODO: This is currently not used uniformly; c++-mode and
3352 ;; java-mode each have their own ways of using it.
3353 t nil
3366 That includes labels in code and access keys in classes. This does
3367 not apply to labels recognized by `c-label-kwds' and
3368 `c-opt-extra-label-key'."
3369 t nil
3375 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3376 a generic colon label. Not used if `c-recognize-colon-labels' is
3377 nil."
3383 "Regexp matching things that can't occur in generic colon labels,
3384 neither in a statement nor in a declaration context. The regexp is
3385 tested at the beginning of every sexp in a suspected label,
3388 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3394 ;; Don't allow string literals, except in AWK and Java. Character constants are OK.
3397 ;; Also check for open parens in C++, to catch member init lists in
3398 ;; constructors. We normally allow it so that macros with arguments
3399 ;; work in labels.
3404 "Regexp matching things that can't occur two symbols before a colon in
3412 "Optional regexp matching labels.
3413 Normally, labels are detected according to `c-nonlabel-token-key',
3414 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3415 be used if there are additional labels that aren't recognized that
3416 way."
3417 t nil
3422 ;; Regexp describing friend declarations classes, or nil in
3423 ;; languages that don't have such things.
3424 ;;
3425 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3426 ;; template skipping isn't done properly. This will disappear soon.
3427 t nil
3432 "<.+>"
3434 "friend"
3439 ;; Special regexp to match the start of Objective-C methods. The
3440 ;; first submatch is assumed to end after the + or - key.
3441 t nil
3443 ;; TODO: Ought to use a better method than anchoring on bol.
3448 "([^)]*)"
3455 ;; Must be set in buffers where the `c-type' text property might be
3456 ;; used with the value `c-decl-end'.
3457 ;;
3458 ;; `c-decl-end' is used to mark the ends of labels and access keys
3459 ;; to make interactive refontification work better.
3462 ;; `c-decl-end' is used to mark the end of the @-style directives in
3463 ;; Objective-C.
3464 objc t)
3468 "List of faces that might be put at the start of a type when
3469 `c-font-lock-declarations' runs. This must be evaluated (with `eval') at
3470 runtime to get the actual list of faces. This ensures that face name
3471 aliases in Emacs are resolved."
3473 font-lock-type-face
3474 c-reference-face-name
3475 font-lock-keyword-face)
3480 \f
3481 ;;; Wrap up the `c-lang-defvar' system.
3483 ;; Compile in the list of language variables that has been collected
3484 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3485 ;; first element of each is nil.
3489 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3490 ;; These are typically standard emacs variables such as `comment-start'.
3498 "Create a function that initializes all the language dependent variables
3499 for the given mode.
3501 This function should be evaluated at compile time, so that the
3502 function it returns is byte compiled with all the evaluated results
3503 from the language constants. Use the `c-init-language-vars' macro to
3504 accomplish that conveniently."
3507 ;; No need to byte compile this lambda since the byte compiler is
3508 ;; smart enough to detect the `funcall' construct in the
3509 ;; `c-init-language-vars' macro below and compile it all straight
3510 ;; into the function that contains `c-init-language-vars'.
3513 ;; This let sets up the context for `c-mode-var' and similar
3514 ;; that could be in the result from `c--macroexpand-all'.
3516 current-var source-eval)
3523 ;; `c-lang-const' will expand to the evaluated
3524 ;; constant immediately in `c--macroexpand-all'
3525 ;; below.
3531 ;; Note: The following `append' copies the
3532 ;; first argument. That list is small, so
3533 ;; this doesn't matter too much.
3537 ;; This diagnostic message isn't useful for end
3538 ;; users, so it's disabled.
3539 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3540 ;; (message ,(concat "%s compiled with CC Mode %s "
3541 ;; "but loaded with %s - evaluating "
3542 ;; "language constants from source")
3543 ;; ',mode ,c-version c-version)
3544 ;; (put ',mode 'c-has-warned-lang-consts t))
3556 current-var
3559 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3562 err)
3565 ;; Being evaluated from source. Always use the dynamic method to
3566 ;; work well when `c-lang-defvar's in this file are reevaluated
3567 ;; interactively.
3573 current-var)
3584 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3585 current-var err)
3587 ))
3590 "Initialize all the language dependent variables for the given mode.
3591 This macro is expanded at compile time to a form tailored for the mode
3592 in question, so MODE must be a constant. Therefore MODE is not
3593 evaluated and should not be quoted."
3596 \f
3599 ;; Local Variables:
3600 ;; indent-tabs-mode: t
3601 ;; tab-width: 8
3602 ;; End:
3603 ;;; cc-langs.el ends here