| blob | e1ccc7924abcf187b1908cc0438afb90371666ea |
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)
484 c-depropertize-CPP
485 c-invalidate-macro-cache)
486 ;; java 'c-before-change-check-<>-operators
491 fs
493 "If non-nil, a list of functions called from c-before-change-hook.
494 Typically these will record enough state to allow
495 `c-before-font-lock-function' to extend the region to fontify,
496 and may do such things as removing text-properties which must be
497 recalculated.
499 These functions will be run in the order given. Each of them
500 takes 2 parameters, the BEG and END supplied to every
501 before-change function; on entry, the buffer will have been
502 widened and match-data will have been saved; point is undefined
503 on both entry and exit; the return value is ignored.
505 The functions are called even when font locking isn't enabled.
507 When the mode is initialized, the functions are called with
511 ;; For documentation see the following c-lang-defvar of the same name.
512 ;; The value here may be a list of functions or a single function.
514 c-change-expand-fl-region)
516 c-extend-font-lock-region-for-macros
517 c-neutralize-syntax-in-and-mark-CPP
518 c-change-expand-fl-region)
520 c-extend-font-lock-region-for-macros
521 ; c-before-after-change-extend-region-for-lambda-capture ; doesn't seem needed.
522 c-before-after-change-digit-quote
523 c-after-change-re-mark-raw-strings
524 c-neutralize-syntax-in-and-mark-CPP
525 c-restore-<>-properties
526 c-change-expand-fl-region)
528 c-restore-<>-properties
529 c-change-expand-fl-region)
531 c-awk-extend-and-syntax-tablify-region))
535 fs
537 "If non-nil, a list of functions called just before font locking.
538 Typically they will extend the region about to be fontified \(see
539 below) and will set `syntax-table' text properties on the region.
541 These functions will be run in the order given. Each of them
542 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
543 after-change function; point is undefined on both entry and exit;
544 on entry, the buffer will have been widened and match-data will
545 have been saved; the return value is ignored.
547 The functions may extend the region to be fontified by setting the
548 buffer local variables c-new-BEG and c-new-END.
550 The functions are called even when font locking is disabled.
552 When the mode is initialized, these functions are called with
556 t 'c-context-expand-fl-region
557 awk nil)
558 ;; For documentation see the following c-lang-defvar of the same name.
559 ;; The value here may be a list of functions or a single function.
563 fs
565 "If non-nil, a list of functions called just before context (or
566 other non-change) fontification is done. Typically they will
567 extend the region.
569 These functions will be run in the order given. Each of them
570 takes 2 parameters, the BEG and END of the region to be
571 fontified. Point is undefined on both entry and exit. On entry,
572 the buffer will have been widened and match-data will have been
573 saved; the return value is a cons of the adjusted
576 \f
577 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
580 Such a function takes one optional parameter, a buffer position (defaults to
581 point), and returns nil or t. This variable contains nil for languages which
582 don't have EOL terminated statements. "
583 t nil
590 The (admittedly kludgy) purpose of such a function is to prevent an infinite
591 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
592 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
593 even indirectly. This variable contains nil for languages which don't have
594 EOL terminated statements."
595 t nil
601 \f
602 ;;; Lexer-level syntax (identifiers, tokens etc).
605 "Whether the language has bitfield declarations."
606 t nil
612 a “long character”. In particular, this recognizes forms of constant
613 which `c-backward-sexp' needs to be called twice to move backwards over."
614 t nil
616 ;; FIXME!!! Extend this to cover strings, if needed. 2008-04-11
620 "Regexp that matches the start of a symbol, i.e. any identifier or
622 operator at the top level."
630 "Set of characters that can be part of a symbol.
631 This is of the form that fits inside [ ] in a regexp."
632 ;; Pike note: With the backquote identifiers this would include most
633 ;; operator chars too, but they are handled with other means instead.
639 "Regexp matching a sequence of at least one identifier character."
644 "Regexp matching identifiers and keywords (with submatch 0). Assumed
645 to match if `c-symbol-start' matches on the same position."
649 ;; Use the value from C here since the operator backquote is
650 ;; covered by the other alternative.
658 ;; Number of regexp grouping parens in `c-symbol-key'.
662 "This is the set of chars that can't be part of a symbol, i.e. the
663 negation of `c-symbol-chars'."
668 "Regexp that matches any character that can't be part of a symbol.
669 It's usually appended to other regexps to avoid matching a prefix.
670 It's assumed to not contain any submatchers."
671 ;; The same thing regarding Unicode identifiers applies here as to
672 ;; `c-symbol-key'.
676 "The operators that make up fully qualified identifiers. nil in
677 languages that don't have such things. See `c-operators' for a
678 description of the format. Binary operators can concatenate symbols,
682 This value is by default merged into `c-operators'."
683 t nil
687 ;; Java has "." to concatenate identifiers but it's also used for
688 ;; normal indexing. There's special code in the Java font lock
689 ;; rules to fontify qualified identifiers based on the standard
690 ;; naming conventions. We still define "." here to make
691 ;; `c-forward-name' move over as long names as possible which is
692 ;; necessary to e.g. handle throws clauses correctly.
701 ;; Appendable adorned regexp matching the operators that join
702 ;; symbols to fully qualified identifiers, or nil in languages that
703 ;; don't have such things.
704 ;;
705 ;; This was a docstring constant in 5.30. It still works but is now
706 ;; considered internal - change `c-identifier-ops' instead.
709 t)))
717 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
721 ;; Appendable adorned regexp matching operators that might precede
722 ;; an identifier and that are part of the identifier in that case.
723 ;; nil in languages without such things.
726 t)))
731 "Operators that can occur after a binary operator on `c-identifier-ops'
732 in identifiers. nil in languages that don't have such things.
734 Operators here should also have appropriate entries in `c-operators' -
735 it's not taken care of by default."
736 t nil
737 ;; '~' for destructors in C++, '*' for member pointers.
739 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
740 ;; in import declarations. (This will also match bogus things like
741 ;; "foo.*bar" but we don't bother.)
745 ;; Regexp that must match the token after
746 ;; `c-opt-identifier-concat-key' for it to be considered an
747 ;; identifier concatenation operator (which e.g. causes the
748 ;; preceding identifier to be fontified as a reference). Assumed to
749 ;; be a string if `c-opt-identifier-concat-key' is.
750 ;;
751 ;; This was a docstring constant in 5.30. It still works but is now
752 ;; considered internal - change `c-after-id-concat-ops' instead.
760 "Regexp that matches the start of an (optionally qualified) identifier.
761 It should also match all keywords. It's unspecified how far it
762 matches."
772 C++. It does not recognize the full range of syntactic whitespace
773 between the tokens; `c-forward-name' has to be used for that. It
774 should also not match identifiers containing parenthesis groupings,
776 ;; This regexp is more complex than strictly necessary to ensure
777 ;; that it can be matched with a minimum of backtracking.
798 ;; For flexibility, consider the symbol match
799 ;; optional if we've hit a
800 ;; `c-after-id-concat-ops' operator. This is
801 ;; also necessary to handle the "*" that can
802 ;; end import declaration identifiers in Java.
816 ;; This was a docstring constant in 5.30 but it's no longer used.
817 ;; It's only kept to avoid breaking third party code.
818 ;;
819 ;; Used to identify the submatch in `c-identifier-key' that
820 ;; surrounds the last symbol in the qualified identifier. It's a
821 ;; list of submatch numbers, of which the first that has a match is
822 ;; taken. It's assumed that at least one does when the regexp has
823 ;; matched.
824 t nil)
827 "Set if the language support backslash escaped newlines inside string
828 literals."
829 t nil
835 "Set if the language supports multiline string literals without escaped
836 newlines. If t, all string literals are multiline. If a character,
837 only literals where the open quote is immediately preceded by that
838 literal are multiline."
839 t nil
840 pike ?#)
845 "The symbol which starts preprocessor constructs when in the margin."
846 t "#"
851 "Regexp matching the prefix of a cpp directive in the languages that
852 normally use that macro preprocessor. Tested at bol or at boi.
854 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
855 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
861 "Regexp matching the prefix of a cpp directive anchored to BOL,
862 in the languages that have a macro preprocessor."
868 "Regexp matching the prefix of a cpp directive including the directive
869 name, or nil in languages without preprocessor support. The first
870 submatch surrounds the directive name."
874 ;; Pike, being a scripting language, recognizes hash-bangs too.
880 "List of cpp directives (without the prefix) that are followed by a
881 string message."
887 "List of cpp directives (without the prefix) that are followed by a
888 file name in angle brackets or quotes."
894 "Cpp directive (without the prefix) that is followed by a macro
895 definition, or nil if the language doesn't have any."
902 ;; Regexp matching everything up to the macro body of a cpp define, or the
903 ;; end of the logical line if there is none. Submatch 1 is the name of the
904 ;; macro. Set if c-opt-cpp-macro-define is.
909 ;; ^ ^ #defined name
915 ;; Regexp matching everything up to the end of the identifier defined
916 ;; by a cpp define.
925 "List of cpp directives (without the prefix) that are followed by an
926 expression."
931 "Regexp which matches the start of a CPP directive which contains an
932 expression, or nil if there aren't any in the language."
941 "List of functions in cpp expressions."
947 "List of all assignment operators."
953 idl nil)
956 "List describing all operators, along with their precedence and
957 associativity. The order in the list corresponds to the precedence of
958 the operators: The operators in each element are a group with the same
959 precedence, and the group has higher precedence than the groups in all
960 following elements. The car of each element describes the type of the
961 operator group, and the cdr is a list of the operator tokens in it.
962 The operator group types are:
964 `prefix' Unary prefix operators.
965 `postfix' Unary postfix operators.
966 `postfix-if-paren'
967 Unary postfix operators if and only if the chars have
968 parenthesis syntax.
969 `left-assoc' Binary left associative operators (i.e. a+b+c means (a+b)+c).
970 `right-assoc' Binary right associative operators (i.e. a=b=c means a=(b=c)).
971 `right-assoc-sequence'
972 Right associative operator that constitutes of a
973 sequence of tokens that separate expressions. All the
974 tokens in the group are in this case taken as
975 describing the sequence in one such operator, and the
976 order between them is therefore significant.
978 Operators containing a character with paren syntax are taken to match
979 with a corresponding open/close paren somewhere else. A postfix
980 operator with close paren syntax is taken to end a postfix expression
981 started somewhere earlier, rather than start a new one at point. Vice
982 versa for prefix operators with open paren syntax.
985 often are described as postfix operators are considered binary here,
986 since CC Mode treats every identifier as an expression."
988 ;; There's currently no code in CC Mode that exploits all the info
989 ;; in this variable; precedence, associativity etc are present as a
990 ;; preparation for future work.
992 ;; FIXME!!! C++11's "auto" operators "=" and "->" need to go in here
993 ;; somewhere. 2012-03-24.
1004 ;; Primary.
1013 ;; Postfix.
1015 ;; The following need special treatment.
1026 ;; Unary.
1033 ;; The following need special treatment.
1044 ;; Member selection.
1048 ;; Multiplicative.
1051 ;; Additive.
1054 ;; Shift.
1059 ;; Relational.
1064 ;; Equality.
1068 ;; Bitwise and.
1072 ;; Bitwise exclusive or.
1078 ;; Bitwise or.
1084 ;; Logical and.
1088 ;; Logical or.
1094 ;; Conditional.
1097 ;; Assignment.
1100 ;; Exception.
1104 ;; Sequence.
1107 ;; IDL got its own definition since it has a much smaller operator
1108 ;; set than the other languages.
1112 ;; Primary.
1114 ;; Unary.
1116 ;; Multiplicative.
1118 ;; Additive.
1120 ;; Shift.
1122 ;; And.
1124 ;; Xor.
1126 ;; Or.
1130 ;; The operators as a flat list (without duplicates).
1136 t nil
1145 ;; These work like identifiers in Pike.
1152 ;; Regexp tested after an "operator" token in C++.
1153 t nil
1159 "Regexp matching the token before the ones in
1160 `c-overloadable-operators' when operators are specified in their
1163 languages without operator functions or where the complete operator
1164 identifier is listed in `c-overloadable-operators'.
1166 This regexp is assumed to not match any non-operator identifier."
1167 t nil
1172 ;; Note: the following alias is an old name which was a mis-spelling. It has
1173 ;; been corrected above and throughout cc-engine.el. It will be removed at
1174 ;; some release very shortly in the future. ACM, 2006-04-14.
1180 "List of the tokens made up of characters in the punctuation or
1181 parenthesis syntax classes that have uses other than as expression
1182 operators."
1201 ;; List of all tokens in the punctuation and parenthesis syntax
1202 ;; classes.
1208 ;; List containing all chars not in the word, symbol or
1209 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1210 ;; parenthesis and string delimiter chars.
1212 ;; Only go through the chars in the printable ASCII range. No
1213 ;; language so far has 8-bit or widestring operators.
1219 list)))
1222 ;; Regexp matching all tokens in the punctuation and parenthesis
1223 ;; syntax classes. Note that this also matches ".", which can start
1224 ;; a float.
1227 t
1233 ;; Regexp matching all assignment operators and only them. The
1234 ;; beginning of the first submatch is used to detect the end of the
1235 ;; token, along with the end of the whole match.
1238 ;; Need special case for "=" since it's a prefix of "==".
1250 ;; Regexp matching all tokens ending in ":" which are longer than one char.
1251 ;; Currently (2016-01-07) only used in C++ Mode.
1258 ;; Regexp matching all tokens containing "<" or ">" which are longer
1259 ;; than one char.
1262 t
1268 ;; Regexp matching the second and subsequent characters of all
1269 ;; multicharacter tokens that begin with "<".
1272 t
1278 ;; A list of second and subsequent characters of all multicharacter tokens
1279 ;; that begin with ">".
1281 t
1285 t
1290 ;; Regexp matching the second and subsequent characters of all
1291 ;; multicharacter tokens that begin with ">".
1296 ;; Regexp matching the second and subsequent characters of all
1297 ;; multicharacter tokens that begin with ">" except for those beginning with
1298 ;; ">>".
1303 t
1311 ;; Regexp matching multichar tokens containing ">", except ">>"
1315 t
1321 ;; The characters that should be considered to bound statements. To
1322 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1323 ;; begin with "^" to negate the set. If ? : operators should be
1324 ;; detected then the string must end with "?:".
1329 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1336 t nil
1343 ;; Ops which signal C++11's new auto uses.
1344 t nil
1351 ;; Op used in the new C++11 auto function definition, indicating type.
1352 t nil
1359 "List of operators following which an apparent declaration \(e.g.
1361 \(as opposed to an arithmetic expression)."
1366 "List of tokens which may precede a lambda declaration.
1368 Currently (2016-08) only used in C++ mode."
1381 ;; Regexp matching any token in the list `c-pre-lambda-tokens'.
1384 \f
1385 ;;; Syntactic whitespace.
1388 "Regexp matching an ordinary whitespace character.
1390 ;; "\\s " is not enough since it doesn't match line breaks.
1394 ;; Number of regexp grouping parens in `c-simple-ws'.
1398 "String that starts line comments, or nil if such don't exist.
1399 Line comments are always terminated by newlines. At least one of
1400 `c-block-comment-starter' and this one is assumed to be set.
1402 Note that it's currently not enough to set this to support a new
1403 comment style. Other stuff like the syntax table must also be set up
1404 properly."
1405 t "//"
1410 "String that starts block comments, or nil if such don't exist.
1411 Block comments are ended by `c-block-comment-ender', which is assumed
1412 to be set if this is. At least one of `c-line-comment-starter' and
1413 this one is assumed to be set.
1415 Note that it's currently not enough to set this to support a new
1416 comment style. Other stuff like the syntax table must also be set up
1417 properly."
1418 t "/*"
1419 awk nil)
1422 "String that ends block comments, or nil if such don't exist.
1424 Note that it's currently not enough to set this to support a new
1425 comment style. Other stuff like the syntax table must also be set up
1426 properly."
1427 t "*/"
1428 awk nil)
1431 ;; Regexp to match the start of any type of comment.
1437 re)))
1441 ;; Regexp which matches the start of a block comment (if such exists in the
1442 ;; language)
1450 ;; Regexp which matches the start of a line comment (if such exists in the
1451 ;; language; it does in all 7 CC Mode languages).
1459 ;; Regexp to match the start of comments and string literals.
1468 "Regexp to match the start of documentation comments."
1470 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1478 "String that starts comments inserted with M-; etc.
1479 `comment-start' is initialized from this."
1480 ;; Default: Prefer line comments to block comments, and pad with a space.
1484 ;; In C we still default to the block comment style since line
1485 ;; comments aren't entirely portable.
1490 "String that ends comments inserted with M-; etc.
1491 `comment-end' is initialized from this."
1492 ;; Default: Use block comment style if comment-start uses block
1493 ;; comments, and pad with a space in that case.
1503 "Regexp to match the start of a comment plus everything up to its body.
1504 `comment-start-skip' is initialized from this."
1505 ;; Default: Allow the last char of the comment starter(s) to be
1506 ;; repeated, then allow any amount of horizontal whitespace.
1519 "When non-nil, escaped EOLs inside comments are valid.
1520 This works in Emacs >= 25.1."
1521 t nil
1527 ;; Regexp matching any sequence that can start syntactic whitespace.
1528 ;; The only uncertain case is '#' when there are cpp directives.
1542 ;; Regexp matching any single character that might end syntactic whitespace.
1557 ;; Regexp matching an unterminated block comment that doesn't
1558 ;; contain line breaks, or nil in languages without block comments.
1559 ;; Does not contain a \| operator at the top level.
1563 ;; It's messy to cook together a regexp that matches anything
1564 ;; but c-block-comment-ender.
1572 "[^"
1573 ;; The quoting rules inside char classes are silly. :P
1582 "]"
1590 ;; Regexp matching a block comment that doesn't contain line breaks,
1591 ;; or nil in languages without block comments. The reason we don't
1592 ;; allow line breaks is to avoid going very far and risk running out
1593 ;; of regexp stack; this regexp is intended to handle only short
1594 ;; comments that might be put in the middle of limited constructs
1595 ;; like declarations. Does not contain a \| operator at the top
1596 ;; level.
1611 ;; Regexp matching a piece of syntactic whitespace that isn't a
1612 ;; sequence of simple whitespace characters. As opposed to
1613 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1614 ;; directives as syntactic whitespace.
1626 ;; Regexp matching syntactic whitespace, including possibly the
1627 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1628 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1629 ;; not contain a \| operator at the top level.
1637 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1641 ;; Regexp matching syntactic whitespace, which is at least one
1642 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1643 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1644 ;; not contain a \| operator at the top level.
1652 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1656 ;; Regexp matching syntactic whitespace without any line breaks. As
1657 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1658 ;; regard cpp directives as syntactic whitespace. Does not contain
1659 ;; a \| operator at the top level.
1667 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1671 ;; Regexp that matches when there is no syntactically significant
1672 ;; text before eol. Macros are regarded as syntactically
1673 ;; significant text here.
1675 ;; Match eol (possibly inside a block comment or preceded
1676 ;; by a line continuation backslash), or the beginning of a
1677 ;; line comment. Note: This has to be modified for awk
1678 ;; where line comments start with '#'.
1692 \f
1693 ;;; Defun handling.
1695 ;; The Emacs variables beginning-of-defun-function and end-of-defun-function
1696 ;; will be set so that commands like `mark-defun' and `narrow-to-defun' work
1697 ;; right. In older Emacsen, the key sequences C-M-a and C-M-e are, however,
1698 ;; bound directly to the CC Mode functions, allowing optimization for large n.
1699 ;; From Emacs 23, this isn't necessary any more, since n is passed to the two
1700 ;; functions.
1702 "Function to which beginning-of-defun-function will be set."
1703 t 'c-beginning-of-defun
1709 "Function to which end-of-defun-function will be set."
1710 t 'c-end-of-defun
1713 \f
1714 ;;; In-comment text handling.
1717 "Regexp to append to `paragraph-start'."
1718 t "$"
1724 "Regexp to append to `paragraph-separate'."
1725 t "$"
1729 \f
1730 ;;; Keyword lists.
1732 ;; Note: All and only all language constants containing keyword lists
1733 ;; should end with "-kwds"; they're automatically collected into the
1734 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1737 "Primitive type keywords. As opposed to the other keyword lists, the
1738 keywords listed here are fontified with the type face instead of the
1739 keyword face.
1741 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1742 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1743 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1744 will be handled.
1746 Do not try to modify this list for end user customizations; the
1747 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1748 the appropriate place for that."
1757 ;; Objective-C extends C, but probably not the new stuff in C99.
1764 ;; In CORBA PSDL:
1765 "ref"
1766 ;; The following can't really end a type, but we have to specify them
1767 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1768 ;; doesn't matter that much.
1771 ;; used as a builtin type.
1776 "Keywords which return a value to the calling function."
1778 idl nil)
1781 ;; Adorned regexp matching `c-return-kwds'.
1786 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1791 "Keywords that might act as prefixes for primitive types. Assumed to
1792 be a subset of `c-primitive-type-kwds'."
1793 t nil
1796 ;; In CORBA PSDL:
1801 of a variable declaration."
1806 ;; Adorned regexp matching `c-typedef-kwds'.
1811 "Keywords followed by a parenthesized expression, which stands for
1812 the type of that expression."
1813 t nil
1818 ;; Adorned regexp matching `c-typeof-kwds'.
1823 "Keywords where the following name - if any - is a type name, and
1824 where the keyword together with the symbol works as a type in
1825 declarations.
1827 Note that an alternative if the second part doesn't hold is
1828 `c-type-list-kwds'. Keywords on this list are typically also present
1829 on one of the `*-decl-kwds' lists."
1830 t nil
1836 ;; Adorned regexp matching `c-type-prefix-kwds'.
1841 "Type modifier keywords. These can occur almost anywhere in types
1842 but they don't build a type of themselves. Unlike the keywords on
1843 `c-primitive-type-kwds', they are fontified with the keyword face and
1844 not the type face."
1845 t nil
1851 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1852 ;; languages without such keywords.
1858 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1859 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1869 ;; All keywords that can start a type (i.e. are either a type prefix
1870 ;; or a complete type).
1877 "Keywords introducing declarations where the following block (if any)
1878 contains another declaration level that should be considered a class.
1880 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1881 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1882 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1883 will be handled.
1885 Note that presence on this list does not automatically treat the
1886 following identifier as a type; the keyword must also be present on
1887 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1888 t nil
1896 ;; In CORBA PSDL:
1898 ;; In CORBA CIDL:
1903 ;; Regexp matching the start of a class.
1908 "Keywords introducing declarations where the following block (if
1909 any) is a brace list.
1911 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1912 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1913 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1914 will be handled."
1919 ;; Regexp matching the start of declarations where the following
1920 ;; block is a brace list.
1925 "Keywords that might follow keywords in `c-brace-list-decl-kwds'
1926 and precede the opening brace."
1927 t nil
1931 ;; Regexp matching keywords that can fall between a brace-list
1932 ;; keyword and the associated brace list.
1937 "Set to t when we recognize a colon and then a type after an enum,
1938 e.g., enum foo : int { A, B, C };"
1939 t nil
1945 "Keywords where the following block (if any) contains another
1946 declaration level that should not be considered a class. For every
1947 keyword here, CC Mode will add a set of special syntactic symbols for
1949 `foo-open', `foo-close', and `infoo' symbols.
1951 The intention is that this category should be used for block
1952 constructs that aren't related to object orientation concepts like
1953 classes (which thus also include e.g. interfaces, templates,
1954 contracts, structs, etc). The more pragmatic distinction is that
1955 while most want some indentation inside classes, it's fairly common
1956 that they don't want it in some of these constructs, so it should be
1957 simple to configure that differently from classes. See also
1958 `c-class-decl-kwds'.
1960 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1961 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1962 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1963 will be handled."
1964 t nil
1968 ;; In CORBA CIDL:
1972 ;; Regexp matching the start of blocks besides classes that contain
1973 ;; another declaration level.
1982 'inextern-lang
1985 "Alist associating keywords in c-other-decl-block-decl-kwds with
1989 "Keywords introducing declarations where the identifier(s) being
1990 declared are types.
1992 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1993 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1994 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1995 will be handled."
1996 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1997 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1998 ;; {...}").
2001 ;; Languages that have a "typedef" construct.
2004 ;; Unlike most other languages, exception names are not handled as
2005 ;; types in IDL since they only can occur in "raises" specs.
2013 "Keywords introducing declarations where the \(first) identifier
2014 \(declarator) follows directly after the keyword, without any type.
2016 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2017 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2018 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2019 will be handled."
2020 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
2021 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
2022 ;; {...}").
2026 ;; Note: "manages" for CORBA CIDL clashes with its presence on
2027 ;; `c-type-list-kwds' for IDL.
2030 ;; In CORBA PSDL:
2032 ;; In CORBA CIDL:
2038 "Keywords that can prefix normal declarations of identifiers
2039 \(and typically act as flags). Things like argument declarations
2040 inside function headers are also considered declarations in this
2041 sense.
2043 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
2044 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2045 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
2046 will be handled."
2047 t nil
2053 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
2057 ;; In CORBA PSDL:
2059 ;; In CORBA CIDL:
2061 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
2068 "Keywords that can start or prefix any declaration level construct,
2069 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
2070 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
2071 `c-typeless-decl-kwds' and `c-modifier-kwds'.
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 "Keywords that always start declarations, wherever they occur.
2084 This can be used for declarations that aren't recognized by the normal
2085 combination of `c-decl-prefix-re' and `c-decl-start-re'."
2086 t nil
2087 ;; Classes can be declared anywhere in a Pike expression.
2091 "Keywords that can occur anywhere in a declaration level construct.
2092 This is used for self-contained things that can be tacked on anywhere
2093 on a declaration and that should be ignored to be able to recognize it
2094 correctly. Typical cases are compiler extensions like
2097 __declspec(noreturn) void foo();
2098 class __declspec(dllexport) classname {...};
2099 void foo() __attribute__((noreturn));
2101 Note that unrecognized plain symbols are skipped anyway if they occur
2102 before the type, so such things are not necessary to mention here.
2103 Mentioning them here is necessary only if they can occur in other
2104 places, or if they are followed by a construct that must be skipped
2106 examples above). In the last case, they alse need to be present on
2107 one of `c-type-list-kwds', `c-ref-list-kwds',
2108 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
2109 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
2110 ;; NB: These are currently not recognized in all parts of a
2111 ;; declaration. Specifically, they aren't recognized in the middle
2112 ;; of multi-token types, inside declarators, and between the
2113 ;; identifier and the arglist paren of a function declaration.
2114 ;;
2115 ;; FIXME: This ought to be user customizable since compiler stuff
2116 ;; like this usually is wrapped in project specific macros. (It'd
2117 ;; of course be even better if we could cope without knowing this.)
2118 t nil
2120 "__attribute__"
2121 ;; MSVC extension.
2125 ;; Adorned regexp matching `c-decl-hangon-kwds'.
2130 ;; All keywords that can occur in the preamble of a declaration.
2131 ;; They typically occur before the type, but they are also matched
2132 ;; after presumptive types since we often can't be sure that
2133 ;; something is a type or just some sort of macro in front of the
2134 ;; declaration. They might be ambiguous with types or type
2135 ;; prefixes.
2148 ;; Adorned regexp of `c-prefix-spec-kwds'.
2154 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
2155 ;; ambiguous with types or type prefixes. These are the keywords (like
2156 ;; extern, namespace, but NOT template) that can modify a declaration.
2165 ;; Keywords that can occur after argument list of a function header
2166 ;; declaration, i.e. in the "K&R region".
2171 ;; Adorned regexp matching all keywords that can't appear at the
2172 ;; start of a declaration.
2187 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2188 ;; This variable is intended for use in c-beginning-of-statement-1.
2198 "Access protection label keywords in classes."
2199 t nil
2204 "Keywords introducing declarations that can contain a block which
2207 like that, it ends with the following `;' and not right away.
2209 The keywords on list are assumed to also be present on one of the
2210 `*-decl-kwds' lists."
2211 t nil
2216 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2217 ;; languages without such constructs.
2224 "Keywords introducing extra declaration specifiers in the region
2226 declarations."
2227 t nil
2230 "supports"
2231 ;; In CORBA PSDL:
2235 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2241 "Keywords that may be followed by a nonsymbol sexp before whatever
2242 construct it's part of continues."
2243 t nil
2247 "Keywords that may be followed by a comma separated list of type
2248 identifiers, where each optionally can be prefixed by keywords. (Can
2249 also be used for the special case when the list can contain only one
2250 element.)
2252 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2253 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2254 There's also no reason to add keywords that prefixes a normal
2255 declaration consisting of a type followed by a declarator (list), so
2256 the keywords on `c-modifier-kwds' should normally not be listed here
2257 either.
2259 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2260 or variable identifier (that's being defined)."
2261 t nil
2266 ;; In CORBA PSDL:
2271 "Keywords that may be followed by a comma separated list of
2272 reference (i.e. namespace/scope/module) identifiers, where each
2273 optionally can be prefixed by keywords. (Can also be used for the
2274 special case when the list can contain only one element.) Assumed to
2275 be mutually exclusive with `c-type-list-kwds'.
2277 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2278 or variable identifier (that's being defined)."
2279 t nil
2283 ;; In CORBA CIDL:
2288 "Keywords that may be followed (not necessarily directly) by a colon
2289 and then a comma separated list of type identifiers, where each
2290 optionally can be prefixed by keywords. (Can also be used for the
2291 special case when the list can contain only one element.)"
2292 t nil
2295 ;; In CORBA PSDL:
2299 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2300 forward to the colon. The end of the match is assumed to be directly
2302 regexp if `c-colon-type-list-kwds' isn't nil."
2304 ;; Disallow various common punctuation chars that can't come
2305 ;; before the ":" that starts the inherit list after "class"
2306 ;; or "struct" in C++. (Also used as default for other
2307 ;; languages.)
2312 "Keywords that may be followed by a parenthesis expression that doesn't
2313 contain type identifiers."
2314 t nil
2316 "__attribute__"
2317 ;; MSVC extension.
2326 "Keywords that may be followed by a parenthesis expression containing
2327 type identifiers separated by arbitrary tokens."
2328 t nil
2340 "Keywords that may be followed by an angle bracket expression
2342 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2343 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2344 if this isn't nil."
2345 t nil
2348 ;; In CORBA PSDL:
2352 "Keywords that can be followed by a C++ style template arglist; see
2353 `c-recognize-<>-arglists' for details. That language constant is
2354 assumed to be set if this isn't nil."
2355 t nil
2360 ;; All keywords that can be followed by an angle bracket sexp.
2366 ;; Adorned regexp matching keywords that can be followed by an angle
2367 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2372 "Keywords which, used inside a C++ style template arglist, introduce a type."
2373 t nil
2381 "Keywords that may be followed by a brace block containing a comma
2382 separated list of identifier definitions, i.e. like the list of
2383 identifiers that follows the type in a normal declaration."
2387 "Statement keywords followed directly by a substatement."
2392 idl nil)
2395 ;; Regexp matching the start of any statement followed directly by a
2396 ;; substatement (doesn't match a bare block, however).
2401 "Statement keywords optionally followed by a paren sexp.
2402 Keywords here should also be in `c-block-stmt-1-kwds'."
2403 t nil
2407 ;; Regexp matching the start of a statement which may be followed by a
2408 ;; paren sexp and will then be followed by a substatement.
2413 "Statement keywords followed by a paren sexp and then by a substatement."
2418 idl nil
2423 ;; Regexp matching the start of any statement followed by a paren sexp
2424 ;; and then by a substatement.
2429 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2435 ;; Regexp matching the start of any statement that has a
2436 ;; substatement (except a bare block). Nil in languages that
2437 ;; don't have such constructs.
2446 "Statement keywords followed by an expression or nothing."
2449 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2451 idl nil
2458 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2463 "Statement keywords followed by a parenthesis expression that
2464 nevertheless contains a list separated with `;' and not `,'."
2466 idl nil)
2469 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2474 "Statement keywords followed by an assembler expression."
2475 t nil
2479 ;; Regexp matching the start of an assembler statement. Nil in
2480 ;; languages that don't support that.
2489 awk nil)
2492 ;; Adorned regexp matching any "case"-like keyword.
2497 "Keywords introducing colon terminated labels in blocks."
2501 ;; Adorned regexp matching any keyword that introduces a label.
2506 "Keywords that might be followed by a label identifier."
2510 idl nil
2511 awk nil)
2514 "Keywords for constants."
2515 t nil
2527 "Keywords besides constants and operators that start primary expressions."
2528 t nil
2535 ;; Keywords that can occur anywhere in expressions. Built from
2536 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2540 t
2545 "Keywords that start lambda constructs, i.e. function definitions in
2546 expressions."
2547 t nil
2551 "Keywords that start constructs followed by statement blocks which can
2552 be used in expressions \(the gcc extension for this in C and C++ is
2553 handled separately by `c-recognize-paren-inexpr-blocks')."
2554 t nil
2558 "Keywords that can start classes inside expressions."
2559 t nil
2564 "Keywords that can start brace list blocks inside expressions.
2565 Note that Java specific rules are currently applied to tell this from
2566 `c-inexpr-class-kwds'."
2567 t nil
2571 ;; Regexp matching the start of a brace list in an expression, or
2572 ;; nil in languages that don't have such things. This should not
2573 ;; match brace lists recognized through `c-special-brace-lists'.
2580 ;; Regexp matching keywords in any construct that contain another
2581 ;; declaration level, i.e. that isn't followed by a function block
2582 ;; or brace list. When the first submatch matches, it's an
2583 ;; unambiguous construct, otherwise it's an ambiguous match that
2584 ;; might also be the return type of a function declaration.
2602 "Keywords that can introduce bitfields."
2603 t nil
2607 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2608 ;; languages without bitfield support.
2609 t nil
2614 "Keywords not accounted for by any other `*-kwds' language constant."
2615 t nil
2617 ;; In CORBA CIDL: (These are declaration keywords that never
2618 ;; can start a declaration.)
2621 \f
2622 ;;; Constants built from keywords.
2624 ;; Note: No `*-kwds' language constants may be defined below this point.
2628 ;; List of all the language constants that contain keyword lists.
2633 ;; Make the list of globally interned symbols
2634 ;; instead of ones interned in `c-lang-constants'.
2636 c-lang-constants)
2637 list)))
2640 ;; All keywords as a list.
2645 c-kwds-lang-consts)
2646 nil))
2650 ;; All keywords as an adorned regexp.
2655 ;; An alist with all the keywords in the cars. The cdr for each
2656 ;; keyword is a list of the symbols for the `*-kwds' lists that
2657 ;; contains it.
2663 c-kwds-lang-consts))))
2664 lang-const kwd-list kwd
2665 result-alist elem)
2677 result-alist))
2680 ;; An obarray containing all keywords as symbols. The property list
2681 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2682 ;; lists it's a member of.
2683 ;;
2684 ;; E.g. to see whether the string str contains a keyword on
2685 ;; `c-class-decl-kwds', one can do like this:
2686 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2687 ;; Which preferably is written using the associated functions in
2688 ;; cc-engine:
2689 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2691 ;; The obarray is not stored directly as a language constant since
2692 ;; the printed representation for obarrays used in .elc files isn't
2693 ;; complete.
2696 kwd lang-const-list
2703 ;; Emacs has an odd bug that causes `mapcan' to fail
2704 ;; with unintelligible errors. (XEmacs works.)
2705 ;; (2015-06-24): This bug has not yet been fixed.
2706 ;;(mapcan (lambda (lang-const)
2707 ;; (list lang-const t))
2708 ;; lang-const-list)
2711 lang-const-list))))
2712 obarray))
2715 ;; Adorned regexp matching all keywords that should be fontified
2716 ;; with the keywords face. I.e. that aren't types or constants.
2726 ;; Regexp matching the start of any primary expression, i.e. any
2727 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2728 ;; exclude keywords; they are excluded afterwards unless the second
2729 ;; submatch matches. If the first but not the second submatch
2730 ;; matches then it is an ambiguous primary expression; it could also
2731 ;; be a match of e.g. an infix operator. (The case with ambiguous
2732 ;; keyword operators isn't handled.)
2738 ;; Filter out the special case prefix
2739 ;; operators that are close parens.
2744 t
2750 postfix-if-paren
2751 left-assoc
2752 right-assoc
2753 right-assoc-sequence)
2754 t))
2757 in-or-postfix-ops
2760 in-or-postfix-ops
2765 ;; Take out all symbol class operators from `prefix-ops' and make the
2766 ;; first submatch from them together with `c-primary-expr-kwds'.
2773 ;; Match all ambiguous operators.
2780 ;; Now match all other symbols.
2784 ;; The chars that can start integer and floating point
2785 ;; constants.
2789 ;; The unambiguous operators from `prefix-ops'.
2795 ;; Match string and character literals.
2802 \f
2803 ;;; Additional constants for parser-level constructs.
2806 "Regexp matching a keyword that is followed by a colon, where
2807 the whole construct can precede a declaration.
2815 "Regexp matching something that might precede a declaration, cast or
2816 label, such as the last token of a preceding statement or declaration.
2817 This is used in the common situation where a declaration or cast
2818 doesn't start with any specific token that can be searched for.
2820 The regexp should not match bob; that is done implicitly. It can't
2821 require a match longer than one token. The end of the token is taken
2822 to be at the end of the first submatch, which is assumed to always
2823 match. It's undefined whether identifier syntax (see
2824 `c-identifier-syntax-table') is in effect or not. This regexp is
2825 assumed to be a superset of `c-label-prefix-re' if
2826 `c-recognize-colon-labels' is set.
2828 Besides this, `c-decl-start-kwds' is used to find declarations.
2830 Note: This variable together with `c-decl-start-re' and
2832 declaration/cast/label starts. I.e. they might produce more matches
2833 but should not miss anything (or else it's necessary to use text
2834 properties - see the next note). Wherever they match, the following
2835 construct is analyzed to see if it indeed is a declaration, cast or
2836 label. That analysis is not cheap, so it's important that not too
2837 many false matches are triggered.
2839 Note: If a declaration/cast/label start can't be detected with this
2840 variable, it's necessary to use the `c-type' text property with the
2841 value `c-decl-end' on the last char of the last token preceding the
2842 declaration. See the comment blurb at the start of cc-engine.el for
2843 more info."
2845 ;; We match a sequence of characters to skip over things like \"};\"
2846 ;; more quickly. We match ")" in C for K&R region declarations, and
2847 ;; in all languages except Java for when a cpp macro definition
2848 ;; begins with a declaration.
2851 ;; Match "<" in C++ to get the first argument in a template arglist.
2852 ;; In that case there's an additional check in `c-find-decl-spots'
2853 ;; that it got open paren syntax. Match ":" to aid in picking up
2854 ;; "public:", etc. This involves additional checks in
2855 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2856 ;; or labels.
2858 ;; Additionally match the protection directives in Objective-C.
2859 ;; Note that this doesn't cope with the longer directives, which we
2860 ;; would have to match from start to end since they don't end with
2861 ;; any easily recognized characters.
2865 ;; Pike is like C but we also match "[" for multiple value
2866 ;; assignments and type casts.
2872 "Regexp matching the start of any declaration, cast or label.
2873 It's used on the token after the one `c-decl-prefix-re' matched. This
2874 regexp should not try to match those constructs accurately as it's
2875 only used as a sieve to avoid spending more time checking other
2876 constructs."
2881 ;; Regexp matching something that might precede or start a
2882 ;; declaration, cast or label.
2883 ;;
2884 ;; If the first submatch matches, it's taken to match the end of a
2885 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2886 ;; It's built from `c-decl-prefix-re'.
2887 ;;
2888 ;; If the first submatch did not match, the match of the whole
2889 ;; regexp is taken to be at the first token in the declaration.
2890 ;; `c-decl-start-re' is not checked in this case.
2891 ;;
2892 ;; Design note: The reason the same regexp is used to match both
2893 ;; tokens that precede declarations and start them is to avoid an
2894 ;; extra regexp search from the previous declaration spot in
2895 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2896 ;; that it finds all declaration/cast/label starts in approximately
2897 ;; linear order, so we can't do the searches in two separate passes.
2908 ;; List containing the paren characters that can open a cast, or nil in
2909 ;; languages without casts.
2917 "List of syntactically relevant characters that never can occur before
2918 the open brace in any construct that contains a brace block, e.g. in
2921 class Foo: public Bar {int x();} a, *b;
2923 If parens can occur, the chars inside those aren't filtered with this
2924 list.
2926 `<' and `>' should be disallowed even if angle bracket arglists can
2927 occur. That since the search function needs to stop at them anyway to
2928 ensure they are given paren syntax.
2930 This is used to skip backward from the open brace to find the region
2933 possible for good performance."
2935 ;; Default to all chars that only occurs in nonsymbol tokens outside
2936 ;; identifiers.
2942 t
2943 t
2947 op pos)
2950 res))))
2952 ;; Allow cpp operations (where applicable).
2958 ;; Allow ':' for inherit list starters.
2962 ;; Allow ',' for multiple inherits.
2966 ;; Allow parentheses for anonymous inner classes in Java and class
2967 ;; initializer lists in Pike.
2971 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2976 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2977 ;; for `c-syntactic-skip-backward'.
2982 "Regexp matching any declarator operator that might precede the
2985 The end of the first submatch is taken as the end of the operator.
2986 Identifier syntax is in effect when this is matched \(see
2987 `c-identifier-syntax-table')."
2990 ;; Default to a regexp that never matches.
2992 ;; Check that there's no "=" afterwards to avoid matching tokens
2993 ;; like "*=".
2995 "[*(]"
3001 "&&"
3005 "[*(&]"
3010 ;; If this matches there's special treatment in
3011 ;; `c-font-lock-declarators' and
3012 ;; `c-font-lock-declarations' that check for a
3013 ;; complete name followed by ":: *".
3023 "Regexp matching the declarator operators that might follow after the
3026 it matches an open paren of some kind, the type declaration check
3027 continues at the corresponding close paren, otherwise the end of the
3028 first submatch is taken as the end of the operator. Identifier syntax
3029 is in effect when this is matched (see `c-identifier-syntax-table')."
3030 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
3031 ;; function argument list parenthesis.
3039 "[)[(]"
3043 ;; "throw" in `c-type-modifier-kwds' is followed
3044 ;; by a parenthesis list, but no extra measures
3045 ;; are necessary to handle that.
3056 "This regexp is matched after a declarator expression where
3057 `c-type-decl-suffix-key' has matched. If it matches then the
3058 construct is taken as a declaration. It's typically used to match the
3059 beginning of a function body or whatever might occur after the
3060 function header in a function declaration or definition. It's
3061 undefined whether identifier syntax (see `c-identifier-syntax-table')
3062 is in effect or not.
3067 t "{"
3068 ;; If K&R style declarations should be recognized then one could
3069 ;; consider to match the start of any symbol since we want to match
3070 ;; the start of the first declaration in the "K&R region". That
3071 ;; could however produce false matches on code like "FOO(bar) x"
3072 ;; where FOO is a cpp macro, so it's better to leave it out and rely
3073 ;; on the other heuristics in that case.
3075 ;; Add on the keywords in `c-postfix-spec-kwds'.
3080 ;; Also match the colon that starts a base class initializer list in
3081 ;; C++. That can be confused with a function call before the colon
3082 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
3083 ;; match before such a thing (as a declaration-level construct;
3084 ;; matches inside arglist contexts are already excluded).
3091 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
3092 ;; matches ";" and ",".
3101 end of the operator. nil in languages without such operators. It's
3102 undefined whether identifier syntax (see `c-identifier-syntax-table')
3103 is in effect or not."
3104 t nil
3110 "Regexp matching operators that might follow after a type, or nil in
3111 languages that don't have such operators. The end of the first
3112 submatch is taken as the end of the operator. This should not match
3113 things like C++ template arglists if `c-recognize-<>-arglists' is set.
3114 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
3115 is in effect or not."
3116 t nil
3122 ;; Regexp matching the known type identifiers. This is initialized
3123 ;; from the type keywords and `*-font-lock-extra-types'. The first
3124 ;; submatch is the one that matches the type. Note that this regexp
3125 ;; assumes that symbol constituents like '_' and '$' have word
3126 ;; syntax.
3133 re))
3134 extra-types)))
3138 re))
3139 extra-types))))
3144 plain-strings)))
3145 regexp-strings)
3150 "List of open- and close-chars that makes up a pike-style brace list,
3152 list."
3153 t nil
3158 "Non-nil means K&R style argument declarations are valid."
3159 t nil
3160 c t)
3164 "A regexp matching tokens which, preceding an identifier, signify a bracelist.
3165 "
3171 "Non-nil means function declarations without return type should be
3172 recognized. That can introduce an ambiguity with parenthesized macro
3173 calls before a brace block. This setting does not affect declarations
3174 that are preceded by a declaration starting keyword, so
3175 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
3176 t nil
3182 "Non-nil means C++ style template arglists should be handled. More
3183 specifically, this means a comma separated list of types or
3185 identifier or one of the keywords on `c-<>-type-kwds' or
3186 `c-<>-arglist-kwds'. If there's an identifier before then the whole
3187 expression is considered to be a type."
3191 ; generics is not yet coded in CC Mode.
3195 "A regexp matching any single character notable inside a <...> construct.
3197 any character which cannot be valid inside such a construct.
3198 This is used in `c-forward-<>-arglist-recur' to try to detect
3199 sequences of tokens which cannot be a template/generic construct.
3202 present it will treat an unbalanced closing paren as a sign of
3203 the invalidity of the putative template construct."
3204 t "[<;{},|+&->)]"
3209 "Non-nil means that an enum structure can contain declarations."
3210 t nil
3211 java t)
3215 "Non-nil means that parenthesis style initializers exist,
3216 i.e. constructs like
3218 Foo bar (gnu);
3220 in addition to the more classic
3222 Foo bar = gnu;"
3223 t nil
3228 "Non-nil to recognize gcc style in-expression blocks,
3229 i.e. compound statements surrounded by parentheses inside expressions."
3230 t nil
3236 ;; Regexp matching the start of angle bracket arglists in languages
3237 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3238 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3239 ;; assumed to surround the preceding symbol. The whole match is
3240 ;; assumed to end directly after the opening "<".
3250 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3251 ;; parens. The first submatch is assumed to surround
3252 ;; `c-opt-<>-arglist-start'.
3261 ;; Regexp matching the beginning of a declaration specifier in the
3262 ;; region between the header and the body of a declaration.
3263 ;;
3264 ;; TODO: This is currently not used uniformly; c++-mode and
3265 ;; java-mode each have their own ways of using it.
3266 t nil
3279 That includes labels in code and access keys in classes. This does
3280 not apply to labels recognized by `c-label-kwds' and
3281 `c-opt-extra-label-key'."
3282 t nil
3288 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3289 a generic colon label. Not used if `c-recognize-colon-labels' is
3290 nil."
3296 "Regexp matching things that can't occur in generic colon labels,
3297 neither in a statement nor in a declaration context. The regexp is
3298 tested at the beginning of every sexp in a suspected label,
3301 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3307 ;; Don't allow string literals, except in AWK and Java. Character constants are OK.
3310 ;; Also check for open parens in C++, to catch member init lists in
3311 ;; constructors. We normally allow it so that macros with arguments
3312 ;; work in labels.
3317 "Regexp matching things that can't occur two symbols before a colon in
3325 "Optional regexp matching labels.
3326 Normally, labels are detected according to `c-nonlabel-token-key',
3327 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3328 be used if there are additional labels that aren't recognized that
3329 way."
3330 t nil
3335 ;; Regexp describing friend declarations classes, or nil in
3336 ;; languages that don't have such things.
3337 ;;
3338 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3339 ;; template skipping isn't done properly. This will disappear soon.
3340 t nil
3345 "<.+>"
3347 "friend"
3352 ;; Special regexp to match the start of Objective-C methods. The
3353 ;; first submatch is assumed to end after the + or - key.
3354 t nil
3356 ;; TODO: Ought to use a better method than anchoring on bol.
3361 "([^)]*)"
3368 ;; Must be set in buffers where the `c-type' text property might be
3369 ;; used with the value `c-decl-end'.
3370 ;;
3371 ;; `c-decl-end' is used to mark the ends of labels and access keys
3372 ;; to make interactive refontification work better.
3375 ;; `c-decl-end' is used to mark the end of the @-style directives in
3376 ;; Objective-C.
3377 objc t)
3381 "List of faces that might be put at the start of a type when
3382 `c-font-lock-declarations' runs. This must be evaluated (with `eval') at
3383 runtime to get the actual list of faces. This ensures that face name
3384 aliases in Emacs are resolved."
3386 font-lock-type-face
3387 c-reference-face-name
3388 font-lock-keyword-face)
3393 \f
3394 ;;; Wrap up the `c-lang-defvar' system.
3396 ;; Compile in the list of language variables that has been collected
3397 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3398 ;; first element of each is nil.
3402 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3403 ;; These are typically standard emacs variables such as `comment-start'.
3411 "Create a function that initializes all the language dependent variables
3412 for the given mode.
3414 This function should be evaluated at compile time, so that the
3415 function it returns is byte compiled with all the evaluated results
3416 from the language constants. Use the `c-init-language-vars' macro to
3417 accomplish that conveniently."
3420 ;; No need to byte compile this lambda since the byte compiler is
3421 ;; smart enough to detect the `funcall' construct in the
3422 ;; `c-init-language-vars' macro below and compile it all straight
3423 ;; into the function that contains `c-init-language-vars'.
3426 ;; This let sets up the context for `c-mode-var' and similar
3427 ;; that could be in the result from `c--macroexpand-all'.
3429 current-var source-eval)
3436 ;; `c-lang-const' will expand to the evaluated
3437 ;; constant immediately in `c--macroexpand-all'
3438 ;; below.
3444 ;; Note: The following `append' copies the
3445 ;; first argument. That list is small, so
3446 ;; this doesn't matter too much.
3450 ;; This diagnostic message isn't useful for end
3451 ;; users, so it's disabled.
3452 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3453 ;; (message ,(concat "%s compiled with CC Mode %s "
3454 ;; "but loaded with %s - evaluating "
3455 ;; "language constants from source")
3456 ;; ',mode ,c-version c-version)
3457 ;; (put ',mode 'c-has-warned-lang-consts t))
3469 current-var
3472 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3475 err)
3478 ;; Being evaluated from source. Always use the dynamic method to
3479 ;; work well when `c-lang-defvar's in this file are reevaluated
3480 ;; interactively.
3486 current-var)
3497 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3498 current-var err)
3500 ))
3503 "Initialize all the language dependent variables for the given mode.
3504 This macro is expanded at compile time to a form tailored for the mode
3505 in question, so MODE must be a constant. Therefore MODE is not
3506 evaluated and should not be quoted."
3509 \f
3512 ;; Local Variables:
3513 ;; indent-tabs-mode: t
3514 ;; tab-width: 8
3515 ;; End:
3516 ;;; cc-langs.el ends here