| blob | 29dff4a6394ea3ac8b7d3c281d19e7fb2c00fe00 |
1 ;;; cc-langs.el --- language specific settings for CC Mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2014 Free Software Foundation, Inc.
5 ;; Authors: 2002- Alan Mackenzie
6 ;; 1998- Martin Stjernholm
7 ;; 1992-1999 Barry A. Warsaw
8 ;; 1987 Dave Detlefs
9 ;; 1987 Stewart Clamen
10 ;; 1985 Richard M. Stallman
11 ;; Maintainer: bug-cc-mode@gnu.org
12 ;; Created: 22-Apr-1997 (split from cc-mode.el)
13 ;; Keywords: c languages
14 ;; Package: cc-mode
16 ;; This file is part of GNU Emacs.
18 ;; GNU Emacs is free software: you can redistribute it and/or modify
19 ;; it under the terms of the GNU General Public License as published by
20 ;; the Free Software Foundation, either version 3 of the License, or
21 ;; (at your option) any later version.
23 ;; GNU Emacs is distributed in the hope that it will be useful,
24 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
25 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
26 ;; GNU General Public License for more details.
28 ;; You should have received a copy of the GNU General Public License
29 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
31 ;;; Commentary:
33 ;; HACKERS NOTE: There's heavy macro magic here. If you need to make
34 ;; changes in this or other files containing `c-lang-defconst' but
35 ;; don't want to read through the longer discussion below then read
36 ;; this:
37 ;;
38 ;; o A change in a `c-lang-defconst' or `c-lang-defvar' will not take
39 ;; effect if the file containing the mode init function (typically
40 ;; cc-mode.el) is byte compiled.
41 ;; o To make changes show in font locking you need to reevaluate the
42 ;; `*-font-lock-keywords-*' constants, which normally is easiest to
43 ;; do with M-x eval-buffer in cc-fonts.el.
44 ;; o In either case it's necessary to reinitialize the mode to make
45 ;; the changes show in an existing buffer.
47 ;;; Introduction to the language dependent variable system:
48 ;;
49 ;; This file contains all the language dependent variables, except
50 ;; those specific for font locking which reside in cc-fonts.el. As
51 ;; far as possible, all the differences between the languages that CC
52 ;; Mode supports are described with these variables only, so that the
53 ;; code can be shared.
54 ;;
55 ;; The language constant system (see cc-defs.el) is used to specify
56 ;; various language dependent info at a high level, such as lists of
57 ;; keywords, and then from them generate - at compile time - the
58 ;; various regexps and other low-level structures actually employed in
59 ;; the code at runtime.
60 ;;
61 ;; This system is also designed to make it easy for developers of
62 ;; derived modes to customize the source constants for new language
63 ;; variants, without having to keep up with the exact regexps etc that
64 ;; are used in each CC Mode version. It's possible from an external
65 ;; package to add a new language by inheriting an existing one, and
66 ;; then change specific constants as necessary for the new language.
67 ;; The old values for those constants (and the values of all the other
68 ;; high-level constants) may be used to build the new ones, and those
69 ;; new values will in turn be used by the low-level definitions here
70 ;; to build the runtime constants appropriately for the new language
71 ;; in the current version of CC Mode.
72 ;;
73 ;; Like elsewhere in CC Mode, the existence of a doc string signifies
74 ;; that a language constant is part of the external API, and that it
75 ;; therefore can be used with a high confidence that it will continue
76 ;; to work with future versions of CC Mode. Even so, it's not
77 ;; unlikely that such constants will change meaning slightly as this
78 ;; system is refined further; a certain degree of dependence on the CC
79 ;; Mode version is unavoidable when hooking in at this level. Also
80 ;; note that there's still work to be done to actually use these
81 ;; constants everywhere inside CC Mode; there are still hardcoded
82 ;; values in many places in the code.
83 ;;
84 ;; Separate packages will also benefit from the compile time
85 ;; evaluation; the byte compiled file(s) for them will contain the
86 ;; compiled runtime constants ready for use by (the byte compiled) CC
87 ;; Mode, and the source definitions in this file don't have to be
88 ;; loaded then. However, if a byte compiled package is loaded that
89 ;; has been compiled with a different version of CC Mode than the one
90 ;; currently loaded, then the compiled-in values will be discarded and
91 ;; new ones will be built when the mode is initialized. That will
92 ;; automatically trig a load of the file(s) containing the source
93 ;; definitions (i.e. this file and/or cc-fonts.el) if necessary.
94 ;;
95 ;; A small example of a derived mode is available at
96 ;; <http://cc-mode.sourceforge.net/derived-mode-ex.el>. It also
97 ;; contains some useful hints for derived mode developers.
99 ;;; Using language variables:
100 ;;
101 ;; The `c-lang-defvar' forms in this file comprise the language
102 ;; variables that CC Mode uses. It does not work to use
103 ;; `c-lang-defvar' anywhere else (which isn't much of a limitation
104 ;; since these variables sole purpose is to interface with the CC Mode
105 ;; core functions). The values in these `c-lang-defvar's are not
106 ;; evaluated right away but instead collected to a single large `setq'
107 ;; that can be inserted for a particular language with the
108 ;; `c-init-language-vars' macro.
110 ;; This file is only required at compile time, or when not running
111 ;; from byte compiled files, or when the source definitions for the
112 ;; language constants are requested.
114 ;;; Code:
116 ;; For Emacs < 22.2.
125 load-path)))
132 ;; This file is not always loaded. See note above.
135 \f
136 ;;; Setup for the `c-lang-defvar' system.
139 ;; These are used to collect the init forms from the subsequent
140 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
141 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
142 ;; and `make-variable-buffer-local's in cc-engine and
143 ;; `make-local-variable's in `c-init-language-vars-for'.
147 c-lang-variable-inits-tail c-lang-variable-inits)
151 c-emacs-variable-inits-tail c-emacs-variable-inits))
154 "Declares the buffer local variable VAR to get the value VAL. VAL is
155 evaluated and assigned at mode initialization. More precisely, VAL is
156 evaluated and bound to VAR when the result from the macro
157 `c-init-language-vars' is evaluated.
159 `c-lang-const' is typically used in VAL to get the right value for the
160 language being initialized, and such calls will be macro expanded to
161 the evaluated constant value at compile time."
167 ;; Special case: If there's no docstring and the value is a
168 ;; simple (c-lang-const foo) where foo is the same name as VAR
169 ;; then take the docstring from the language constant foo.
181 ;; Return the symbol, like the other def* forms.
185 "Causes the variable VAR to be made buffer local and to get set to the
186 value VAL. VAL is evaluated and assigned at mode initialization. More
187 precisely, VAL is evaluated and bound to VAR when the result from the
188 macro `c-init-language-vars' is evaluated. VAR is typically a standard
189 Emacs variable like `comment-start'.
191 `c-lang-const' is typically used in VAL to get the right value for the
192 language being initialized, and such calls will be macro expanded to
193 the evaluated constant value at compile time."
200 ;; Return the symbol, like the other def* forms.
204 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
205 ; '
209 ;; Suppress "might not be defined at runtime" warning.
210 ;; This file is only used when compiling other cc files.
211 ;; These are defined in cl as aliases to the cl- versions.
217 ;; Some helper functions used when building the language constants.
220 ;; Extract a subset of the operators in the list OPS in a DWIM:ey
221 ;; way. The return value is a plain list of operators:
222 ;;
223 ;; OPS either has the structure of `c-operators', is a single
224 ;; group in `c-operators', or is a plain list of operators.
225 ;;
226 ;; OPGROUP-FILTER specifies how to select the operator groups. It
227 ;; can be t to choose all groups, a list of group type symbols
228 ;; (such as 'prefix) to accept, or a function which will be called
229 ;; with the group symbol for each group and should return non-nil
230 ;; if that group is to be included.
231 ;;
232 ;; If XLATE is given, it's a function which is called for each
233 ;; matching operator and its return value is collected instead.
234 ;; If it returns a list, the elements are spliced directly into
235 ;; the final result, which is returned as a list with duplicates
236 ;; removed using `equal'.
237 ;;
238 ;; `c-mode-syntax-table' for the current mode is in effect during
239 ;; the whole procedure.
260 t)
261 t)
266 opgroup)))
267 ops)
270 \f
271 ;;; Various mode specific values that aren't language related.
274 ;; The definition for the mode menu. The menu title is prepended to
275 ;; this before it's fed to `easy-menu-define'.
285 "----"
289 ;; Only applicable if there's a cpp preprocessor.
293 "----"
298 "----"
302 "Style Name: %s"
307 c-guess-guessed-basic-offset) ]
310 c-guess-guessed-basic-offset) ])
311 "----"
323 subword-mode)])))
325 \f
326 ;;; Syntax tables.
329 "Populate the given syntax table as necessary for a C-like language.
347 ;; Set up block and line oriented comments. The new C
348 ;; standard mandates both comment styles even in C, so since
349 ;; all languages now require dual comments, we make this the
350 ;; default.
352 ;; XEmacs
356 ;; Emacs
360 ;; incompatible
364 ;; Give CR the same syntax as newline, for selective-display
368 "Functions that generates the mode specific syntax tables.
369 The syntax tables aren't stored directly since they're quite large."
373 ;; Mode specific syntaxes.
375 ;; Let '@' be part of symbols in ObjC to cope with
376 ;; its compiler directives as single keyword tokens.
377 ;; This is then necessary since it's assumed that
378 ;; every keyword is a single symbol.
382 table)))
385 ;; The syntax tables in evaluated form. Only used temporarily when
386 ;; the constants in this file are evaluated.
390 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
391 ;; parenthesis characters. Used temporarily when template argument
392 ;; lists are parsed. Note that this encourages incorrect parsing of
393 ;; templates since they might contain normal operators that uses the
394 ;; '<' and '>' characters. Therefore this syntax table might go
395 ;; away when CC Mode handles templates correctly everywhere.
396 t nil
401 table)))
407 ;; A variant of the standard syntax table which is used to find matching
408 ;; "<"s and ">"s which have been marked as parens using syntax table
409 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
410 ;; non-paren syntax here. so that the list commands will work on "< ... >"
411 ;; even when there's unbalanced other parens inside them.
412 ;;
413 ;; This variable is nil for languages which don't have template stuff.
423 table))))
428 "A list that describes the modifications that should be done to the
429 mode syntax table to get a syntax table that matches all identifiers
430 and keywords as words.
432 The list is just like the one used in `font-lock-defaults': Each
433 element is a cons where the car is the character to modify and the cdr
434 the new syntax, as accepted by `modify-syntax-entry'."
435 ;; The $ character is not allowed in most languages (one exception
436 ;; is Java which allows it for legacy reasons) but we still classify
437 ;; it as an identifier character since it's often used in various
438 ;; machine generated identifiers.
449 mod)
454 table)
455 "Syntax table built on the mode syntax table but additionally
456 classifies symbol constituents like '_' and '$' as word constituents,
460 ;; For documentation see the following c-lang-defvar of the same name.
461 ;; The value here may be a list of functions or a single function.
462 t nil
464 c-before-change-check-<>-operators
465 c-invalidate-macro-cache)
467 ;; java 'c-before-change-check-<>-operators
472 fs
474 "If non-nil, a list of functions called from c-before-change-hook.
475 Typically these will record enough state to allow
476 `c-before-font-lock-function' to extend the region to fontify,
477 and may do such things as removing text-properties which must be
478 recalculated.
480 These functions will be run in the order given. Each of them
481 takes 2 parameters, the BEG and END supplied to every
482 before-change function; on entry, the buffer will have been
483 widened and match-data will have been saved; point is undefined
484 on both entry and exit; the return value is ignored.
486 The functions are called even when font locking isn't enabled.
488 When the mode is initialized, the functions are called with
492 ;; For documentation see the following c-lang-defvar of the same name.
493 ;; The value here may be a list of functions or a single function.
494 t 'c-change-set-fl-decl-start
496 c-change-set-fl-decl-start)
501 fs
503 "If non-nil, a list of functions called just before font locking.
504 Typically they will extend the region about to be fontified \(see
505 below) and will set `syntax-table' text properties on the region.
507 These functions will be run in the order given. Each of them
508 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
509 after-change function; point is undefined on both entry and exit;
510 on entry, the buffer will have been widened and match-data will
511 have been saved; the return value is ignored.
513 The functions may extend the region to be fontified by setting the
514 buffer local variables c-new-BEG and c-new-END.
516 The functions are called even when font locking is disabled.
518 When the mode is initialized, these functions are called with
522 awk nil
524 ;; For documentation see the following c-lang-defvar of the same name.
525 ;; The value here may be a list of functions or a single function.
529 fs
531 "If non-nil, a list of functions called just before context (or
532 other non-change) fontification is done. Typically they will
533 extend the region.
535 These functions will be run in the order given. Each of them
536 takes 2 parameters, the BEG and END of the region to be
537 fontified. Point is undefined on both entry and exit. On entry,
538 the buffer will have been widened and match-data will have been
539 saved; the return value is a cons of the adjusted
542 \f
543 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
546 Such a function takes one optional parameter, a buffer position (defaults to
547 point), and returns nil or t. This variable contains nil for languages which
548 don't have EOL terminated statements. "
549 t nil
556 The (admittedly kludgy) purpose of such a function is to prevent an infinite
557 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
558 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
559 even indirectly. This variable contains nil for languages which don't have
560 EOL terminated statements."
561 t nil
567 \f
568 ;;; Lexer-level syntax (identifiers, tokens etc).
571 "Whether the language has bitfield declarations."
572 t nil
577 "Regexp that matches the start of a symbol, i.e. any identifier or
579 operator at the top level."
587 "Set of characters that can be part of a symbol.
588 This is of the form that fits inside [ ] in a regexp."
589 ;; Pike note: With the backquote identifiers this would include most
590 ;; operator chars too, but they are handled with other means instead.
596 "Regexp matching identifiers and keywords (with submatch 0). Assumed
597 to match if `c-symbol-start' matches on the same position."
601 ;; Use the value from C here since the operator backquote is
602 ;; covered by the other alternative.
610 ;; Number of regexp grouping parens in `c-symbol-key'.
614 "This is the set of chars that can't be part of a symbol, i.e. the
615 negation of `c-symbol-chars'."
620 "Regexp that matches any character that can't be part of a symbol.
621 It's usually appended to other regexps to avoid matching a prefix.
622 It's assumed to not contain any submatchers."
623 ;; The same thing regarding Unicode identifiers applies here as to
624 ;; `c-symbol-key'.
628 "The operators that make up fully qualified identifiers. nil in
629 languages that don't have such things. See `c-operators' for a
630 description of the format. Binary operators can concatenate symbols,
634 This value is by default merged into `c-operators'."
635 t nil
639 ;; Java has "." to concatenate identifiers but it's also used for
640 ;; normal indexing. There's special code in the Java font lock
641 ;; rules to fontify qualified identifiers based on the standard
642 ;; naming conventions. We still define "." here to make
643 ;; `c-forward-name' move over as long names as possible which is
644 ;; necessary to e.g. handle throws clauses correctly.
653 ;; Appendable adorned regexp matching the operators that join
654 ;; symbols to fully qualified identifiers, or nil in languages that
655 ;; don't have such things.
656 ;;
657 ;; This was a docstring constant in 5.30. It still works but is now
658 ;; considered internal - change `c-identifier-ops' instead.
661 t)))
669 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
673 ;; Appendable adorned regexp matching operators that might precede
674 ;; an identifier and that are part of the identifier in that case.
675 ;; nil in languages without such things.
678 t)))
683 "Operators that can occur after a binary operator on `c-identifier-ops'
684 in identifiers. nil in languages that don't have such things.
686 Operators here should also have appropriate entries in `c-operators' -
687 it's not taken care of by default."
688 t nil
689 ;; '~' for destructors in C++, '*' for member pointers.
691 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
692 ;; in import declarations. (This will also match bogus things like
693 ;; "foo.*bar" but we don't bother.)
697 ;; Regexp that must match the token after
698 ;; `c-opt-identifier-concat-key' for it to be considered an
699 ;; identifier concatenation operator (which e.g. causes the
700 ;; preceding identifier to be fontified as a reference). Assumed to
701 ;; be a string if `c-opt-identifier-concat-key' is.
702 ;;
703 ;; This was a docstring constant in 5.30. It still works but is now
704 ;; considered internal - change `c-after-id-concat-ops' instead.
712 "Regexp that matches the start of an (optionally qualified) identifier.
713 It should also match all keywords. It's unspecified how far it
714 matches."
724 C++. It does not recognize the full range of syntactic whitespace
725 between the tokens; `c-forward-name' has to be used for that. It
726 should also not match identifiers containing parenthesis groupings,
728 ;; This regexp is more complex than strictly necessary to ensure
729 ;; that it can be matched with a minimum of backtracking.
750 ;; For flexibility, consider the symbol match
751 ;; optional if we've hit a
752 ;; `c-after-id-concat-ops' operator. This is
753 ;; also necessary to handle the "*" that can
754 ;; end import declaration identifiers in Java.
768 ;; This was a docstring constant in 5.30 but it's no longer used.
769 ;; It's only kept to avoid breaking third party code.
770 ;;
771 ;; Used to identify the submatch in `c-identifier-key' that
772 ;; surrounds the last symbol in the qualified identifier. It's a
773 ;; list of submatch numbers, of which the first that has a match is
774 ;; taken. It's assumed that at least one does when the regexp has
775 ;; matched.
776 t nil)
779 "Set if the language support backslash escaped newlines inside string
780 literals."
781 t nil
787 "Set if the language supports multiline string literals without escaped
788 newlines. If t, all string literals are multiline. If a character,
789 only literals where the open quote is immediately preceded by that
790 literal are multiline."
791 t nil
792 pike ?#)
797 "The symbol which starts preprocessor constructs when in the margin."
798 t "#"
803 "Regexp matching the prefix of a cpp directive in the languages that
804 normally use that macro preprocessor. Tested at bol or at boi.
806 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
807 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
813 "Regexp matching the prefix of a cpp directive anchored to BOL,
814 in the languages that have a macro preprocessor."
820 "Regexp matching the prefix of a cpp directive including the directive
821 name, or nil in languages without preprocessor support. The first
822 submatch surrounds the directive name."
826 ;; Pike, being a scripting language, recognizes hash-bangs too.
832 "List of cpp directives (without the prefix) that are followed by a
833 string message."
839 "List of cpp directives (without the prefix) that are followed by a
840 file name in angle brackets or quotes."
846 "Cpp directive (without the prefix) that is followed by a macro
847 definition, or nil if the language doesn't have any."
854 ;; Regexp matching everything up to the macro body of a cpp define, or the
855 ;; end of the logical line if there is none. Submatch 1 is the name of the
856 ;; macro. Set if c-opt-cpp-macro-define is.
861 ;; ^ ^ #defined name
867 ;; Regexp matching everything up to the end of the identifier defined
868 ;; by a cpp define.
877 "List of cpp directives (without the prefix) that are followed by an
878 expression."
883 "Regexp which matches the start of a CPP directive which contains an
884 expression, or nil if there aren't any in the language."
893 "List of functions in cpp expressions."
899 "List of all assignment operators."
905 idl nil)
908 "List describing all operators, along with their precedence and
909 associativity. The order in the list corresponds to the precedence of
910 the operators: The operators in each element are a group with the same
911 precedence, and the group has higher precedence than the groups in all
912 following elements. The car of each element describes the type of the
913 operator group, and the cdr is a list of the operator tokens in it.
914 The operator group types are:
916 'prefix Unary prefix operators.
917 'postfix Unary postfix operators.
918 'postfix-if-paren
919 Unary postfix operators if and only if the chars have
920 parenthesis syntax.
921 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
922 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
923 'right-assoc-sequence
924 Right associative operator that constitutes of a
925 sequence of tokens that separate expressions. All the
926 tokens in the group are in this case taken as
927 describing the sequence in one such operator, and the
928 order between them is therefore significant.
930 Operators containing a character with paren syntax are taken to match
931 with a corresponding open/close paren somewhere else. A postfix
932 operator with close paren syntax is taken to end a postfix expression
933 started somewhere earlier, rather than start a new one at point. Vice
934 versa for prefix operators with open paren syntax.
937 often are described as postfix operators are considered binary here,
938 since CC Mode treats every identifier as an expression."
940 ;; There's currently no code in CC Mode that exploit all the info
941 ;; in this variable; precedence, associativity etc are present as a
942 ;; preparation for future work.
953 ;; Primary.
962 ;; Postfix.
964 ;; The following need special treatment.
974 ;; Unary.
981 ;; The following need special treatment.
992 ;; Member selection.
996 ;; Multiplicative.
999 ;; Additive.
1002 ;; Shift.
1007 ;; Relational.
1012 ;; Equality.
1016 ;; Bitwise and.
1020 ;; Bitwise exclusive or.
1026 ;; Bitwise or.
1032 ;; Logical and.
1036 ;; Logical or.
1042 ;; Conditional.
1045 ;; Assignment.
1048 ;; Exception.
1052 ;; Sequence.
1055 ;; IDL got its own definition since it has a much smaller operator
1056 ;; set than the other languages.
1060 ;; Primary.
1062 ;; Unary.
1064 ;; Multiplicative.
1066 ;; Additive.
1068 ;; Shift.
1070 ;; And.
1072 ;; Xor.
1074 ;; Or.
1078 ;; The operators as a flat list (without duplicates).
1084 t nil
1093 ;; These work like identifiers in Pike.
1100 ;; Regexp tested after an "operator" token in C++.
1101 t nil
1107 "Regexp matching the token before the ones in
1108 `c-overloadable-operators' when operators are specified in their
1111 languages without operator functions or where the complete operator
1112 identifier is listed in `c-overloadable-operators'.
1114 This regexp is assumed to not match any non-operator identifier."
1115 t nil
1120 ;; Note: the following alias is an old name which was a mis-spelling. It has
1121 ;; been corrected above and throughout cc-engine.el. It will be removed at
1122 ;; some release very shortly in the future. ACM, 2006-04-14.
1128 "List of the tokens made up of characters in the punctuation or
1129 parenthesis syntax classes that have uses other than as expression
1130 operators."
1148 ;; List of all tokens in the punctuation and parenthesis syntax
1149 ;; classes.
1155 ;; List containing all chars not in the word, symbol or
1156 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1157 ;; parenthesis and string delimiter chars.
1159 ;; Only go through the chars in the printable ASCII range. No
1160 ;; language so far has 8-bit or widestring operators.
1166 list)))
1169 ;; Regexp matching all tokens in the punctuation and parenthesis
1170 ;; syntax classes. Note that this also matches ".", which can start
1171 ;; a float.
1174 t
1180 ;; Regexp matching all assignment operators and only them. The
1181 ;; beginning of the first submatch is used to detect the end of the
1182 ;; token, along with the end of the whole match.
1185 ;; Need special case for "=" since it's a prefix of "==".
1197 ;; Regexp matching all tokens containing "<" or ">" which are longer
1198 ;; than one char.
1201 t
1207 ;; Regexp matching the second and subsequent characters of all
1208 ;; multicharacter tokens that begin with "<".
1211 t
1218 ;; Regexp matching the second and subsequent characters of all
1219 ;; multicharacter tokens that begin with ">".
1222 t
1227 t
1234 ;; The characters that should be considered to bound statements. To
1235 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1236 ;; begin with "^" to negate the set. If ? : operators should be
1237 ;; detected then the string must end with "?:".
1242 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1247 \f
1248 ;;; Syntactic whitespace.
1251 "Regexp matching an ordinary whitespace character.
1253 ;; "\\s " is not enough since it doesn't match line breaks.
1257 ;; Number of regexp grouping parens in `c-simple-ws'.
1261 "String that starts line comments, or nil if such don't exist.
1262 Line comments are always terminated by newlines. At least one of
1263 `c-block-comment-starter' and this one is assumed to be set.
1265 Note that it's currently not enough to set this to support a new
1266 comment style. Other stuff like the syntax table must also be set up
1267 properly."
1268 t "//"
1273 "String that starts block comments, or nil if such don't exist.
1274 Block comments are ended by `c-block-comment-ender', which is assumed
1275 to be set if this is. At least one of `c-line-comment-starter' and
1276 this one is assumed to be set.
1278 Note that it's currently not enough to set this to support a new
1279 comment style. Other stuff like the syntax table must also be set up
1280 properly."
1281 t "/*"
1282 awk nil)
1285 "String that ends block comments, or nil if such don't exist.
1287 Note that it's currently not enough to set this to support a new
1288 comment style. Other stuff like the syntax table must also be set up
1289 properly."
1290 t "*/"
1291 awk nil)
1294 ;; Regexp to match the start of any type of comment.
1300 re)))
1304 ;; Regexp which matches the start of a block comment (if such exists in the
1305 ;; language)
1313 ;; Regexp which matches the start of a line comment (if such exists in the
1314 ;; language; it does in all 7 CC Mode languages).
1322 ;; Regexp to match the start of comments and string literals.
1331 "Regexp to match the start of documentation comments."
1333 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1341 "String that starts comments inserted with M-; etc.
1342 `comment-start' is initialized from this."
1343 ;; Default: Prefer line comments to block comments, and pad with a space.
1347 ;; In C we still default to the block comment style since line
1348 ;; comments aren't entirely portable.
1353 "String that ends comments inserted with M-; etc.
1354 `comment-end' is initialized from this."
1355 ;; Default: Use block comment style if comment-start uses block
1356 ;; comments, and pad with a space in that case.
1366 "Regexp to match the start of a comment plus everything up to its body.
1367 `comment-start-skip' is initialized from this."
1368 ;; Default: Allow the last char of the comment starter(s) to be
1369 ;; repeated, then allow any amount of horizontal whitespace.
1382 ;; Regexp matching any sequence that can start syntactic whitespace.
1383 ;; The only uncertain case is '#' when there are cpp directives.
1397 ;; Regexp matching any single character that might end syntactic whitespace.
1412 ;; Regexp matching an unterminated block comment that doesn't
1413 ;; contain line breaks, or nil in languages without block comments.
1414 ;; Does not contain a \| operator at the top level.
1418 ;; It's messy to cook together a regexp that matches anything
1419 ;; but c-block-comment-ender.
1427 "[^"
1428 ;; The quoting rules inside char classes are silly. :P
1437 "]"
1445 ;; Regexp matching a block comment that doesn't contain line breaks,
1446 ;; or nil in languages without block comments. The reason we don't
1447 ;; allow line breaks is to avoid going very far and risk running out
1448 ;; of regexp stack; this regexp is intended to handle only short
1449 ;; comments that might be put in the middle of limited constructs
1450 ;; like declarations. Does not contain a \| operator at the top
1451 ;; level.
1466 ;; Regexp matching a piece of syntactic whitespace that isn't a
1467 ;; sequence of simple whitespace characters. As opposed to
1468 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1469 ;; directives as syntactic whitespace.
1481 ;; Regexp matching syntactic whitespace, including possibly the
1482 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1483 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1484 ;; not contain a \| operator at the top level.
1492 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1496 ;; Regexp matching syntactic whitespace, which is at least one
1497 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1498 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1499 ;; not contain a \| operator at the top level.
1507 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1511 ;; Regexp matching syntactic whitespace without any line breaks. As
1512 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1513 ;; regard cpp directives as syntactic whitespace. Does not contain
1514 ;; a \| operator at the top level.
1522 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1526 ;; Regexp that matches when there is no syntactically significant
1527 ;; text before eol. Macros are regarded as syntactically
1528 ;; significant text here.
1530 ;; Match eol (possibly inside a block comment or preceded
1531 ;; by a line continuation backslash), or the beginning of a
1532 ;; line comment. Note: This has to be modified for awk
1533 ;; where line comments start with '#'.
1547 \f
1548 ;;; Defun functions
1550 ;; The Emacs variables beginning-of-defun-function and
1551 ;; end-of-defun-function will be set so that commands like
1552 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1553 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1554 ;; functions, allowing optimization for large n.
1556 "Function to which beginning-of-defun-function will be set."
1557 t 'c-beginning-of-defun
1563 "Function to which end-of-defun-function will be set."
1564 t 'c-end-of-defun
1567 \f
1568 ;;; In-comment text handling.
1571 "Regexp to append to `paragraph-start'."
1572 t "$"
1578 "Regexp to append to `paragraph-separate'."
1579 t "$"
1583 \f
1584 ;;; Keyword lists.
1586 ;; Note: All and only all language constants containing keyword lists
1587 ;; should end with "-kwds"; they're automatically collected into the
1588 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1591 "Primitive type keywords. As opposed to the other keyword lists, the
1592 keywords listed here are fontified with the type face instead of the
1593 keyword face.
1595 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1596 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1597 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1598 will be handled.
1600 Do not try to modify this list for end user customizations; the
1601 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1602 the appropriate place for that."
1611 ;; Objective-C extends C, but probably not the new stuff in C99.
1618 ;; In CORBA PSDL:
1619 "ref"
1620 ;; The following can't really end a type, but we have to specify them
1621 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1622 ;; doesn't matter that much.
1625 ;; used as a builtin type.
1630 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1635 "Keywords that might act as prefixes for primitive types. Assumed to
1636 be a subset of `c-primitive-type-kwds'."
1637 t nil
1640 ;; In CORBA PSDL:
1645 of a variable declaration."
1650 ;; Adorned regexp matching `c-typedef-kwds'.
1655 "Keywords where the following name - if any - is a type name, and
1656 where the keyword together with the symbol works as a type in
1657 declarations.
1659 Note that an alternative if the second part doesn't hold is
1660 `c-type-list-kwds'. Keywords on this list are typically also present
1661 on one of the `*-decl-kwds' lists."
1662 t nil
1668 ;; Adorned regexp matching `c-type-prefix-kwds'.
1673 "Type modifier keywords. These can occur almost anywhere in types
1674 but they don't build a type of themselves. Unlike the keywords on
1675 `c-primitive-type-kwds', they are fontified with the keyword face and
1676 not the type face."
1677 t nil
1683 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1684 ;; languages without such keywords.
1690 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1691 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1701 ;; All keywords that can start a type (i.e. are either a type prefix
1702 ;; or a complete type).
1709 "Keywords introducing declarations where the following block (if any)
1710 contains another declaration level that should be considered a class.
1712 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1713 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1714 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1715 will be handled.
1717 Note that presence on this list does not automatically treat the
1718 following identifier as a type; the keyword must also be present on
1719 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1720 t nil
1728 ;; In CORBA PSDL:
1730 ;; In CORBA CIDL:
1735 ;; Regexp matching the start of a class.
1740 "Keywords introducing declarations where the following block (if
1741 any) is a brace list.
1743 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1744 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1745 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1746 will be handled."
1751 ;; Regexp matching the start of declarations where the following
1752 ;; block is a brace list.
1757 "Keywords where the following block (if any) contains another
1758 declaration level that should not be considered a class. For every
1759 keyword here, CC Mode will add a set of special syntactic symbols for
1761 `foo-open', `foo-close', and `infoo' symbols.
1763 The intention is that this category should be used for block
1764 constructs that aren't related to object orientation concepts like
1765 classes (which thus also include e.g. interfaces, templates,
1766 contracts, structs, etc). The more pragmatic distinction is that
1767 while most want some indentation inside classes, it's fairly common
1768 that they don't want it in some of these constructs, so it should be
1769 simple to configure that differently from classes. See also
1770 `c-class-decl-kwds'.
1772 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1773 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1774 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1775 will be handled."
1776 t nil
1780 ;; In CORBA CIDL:
1784 ;; Regexp matching the start of blocks besides classes that contain
1785 ;; another declaration level.
1794 'inextern-lang
1797 "Alist associating keywords in c-other-decl-block-decl-kwds with
1801 "Keywords introducing declarations where the identifier(s) being
1802 declared are types.
1804 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1805 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1806 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1807 will be handled."
1808 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1809 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1810 ;; {...}").
1813 ;; Languages that have a "typedef" construct.
1816 ;; Unlike most other languages, exception names are not handled as
1817 ;; types in IDL since they only can occur in "raises" specs.
1825 "Keywords introducing declarations where the \(first) identifier
1826 \(declarator) follows directly after the keyword, without any type.
1828 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1829 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1830 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1831 will be handled."
1832 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1833 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1834 ;; {...}").
1837 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1838 ;; `c-type-list-kwds' for IDL.
1841 ;; In CORBA PSDL:
1843 ;; In CORBA CIDL:
1849 "Keywords that can prefix normal declarations of identifiers
1850 \(and typically act as flags). Things like argument declarations
1851 inside function headers are also considered declarations in this
1852 sense.
1854 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1855 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1856 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1857 will be handled."
1858 t nil
1863 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1867 ;; In CORBA PSDL:
1869 ;; In CORBA CIDL:
1871 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1878 "Keywords that can start or prefix any declaration level construct,
1879 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1880 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1881 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1883 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1884 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1885 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1886 will be handled."
1887 t nil
1893 "Keywords that always start declarations, wherever they occur.
1894 This can be used for declarations that aren't recognized by the normal
1895 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1896 t nil
1897 ;; Classes can be declared anywhere in a Pike expression.
1901 "Keywords that can occur anywhere in a declaration level construct.
1902 This is used for self-contained things that can be tacked on anywhere
1903 on a declaration and that should be ignored to be able to recognize it
1904 correctly. Typical cases are compiler extensions like
1907 __declspec(noreturn) void foo();
1908 class __declspec(dllexport) classname {...};
1909 void foo() __attribute__((noreturn));
1911 Note that unrecognized plain symbols are skipped anyway if they occur
1912 before the type, so such things are not necessary to mention here.
1913 Mentioning them here is necessary only if they can occur in other
1914 places, or if they are followed by a construct that must be skipped
1916 examples above). In the last case, they alse need to be present on
1917 one of `c-type-list-kwds', `c-ref-list-kwds',
1918 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1919 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1920 ;; NB: These are currently not recognized in all parts of a
1921 ;; declaration. Specifically, they aren't recognized in the middle
1922 ;; of multi-token types, inside declarators, and between the
1923 ;; identifier and the arglist paren of a function declaration.
1924 ;;
1925 ;; FIXME: This ought to be user customizable since compiler stuff
1926 ;; like this usually is wrapped in project specific macros. (It'd
1927 ;; of course be even better if we could cope without knowing this.)
1928 t nil
1930 "__attribute__"
1931 ;; MSVC extension.
1935 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1940 ;; All keywords that can occur in the preamble of a declaration.
1941 ;; They typically occur before the type, but they are also matched
1942 ;; after presumptive types since we often can't be sure that
1943 ;; something is a type or just some sort of macro in front of the
1944 ;; declaration. They might be ambiguous with types or type
1945 ;; prefixes.
1958 ;; Adorned regexp of `c-prefix-spec-kwds'.
1964 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1965 ;; ambiguous with types or type prefixes. These are the keywords (like
1966 ;; extern, namespace, but NOT template) that can modify a declaration.
1975 ;; Keywords that can occur after argument list of a function header
1976 ;; declaration, i.e. in the "K&R region".
1981 ;; Adorned regexp matching all keywords that can't appear at the
1982 ;; start of a declaration.
1996 ;; The "more" for C++ is the QT keyword (as in "more slots:").
1997 ;; This variable is intended for use in c-beginning-of-statement-1.
2007 "Access protection label keywords in classes."
2008 t nil
2013 "Keywords introducing declarations that can contain a block which
2016 like that, it ends with the following ';' and not right away.
2018 The keywords on list are assumed to also be present on one of the
2019 `*-decl-kwds' lists."
2020 t nil
2025 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2026 ;; languages without such constructs.
2033 "Keywords introducing extra declaration specifiers in the region
2035 declarations."
2036 t nil
2039 "supports"
2040 ;; In CORBA PSDL:
2044 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2050 "Keywords that may be followed by a nonsymbol sexp before whatever
2051 construct it's part of continues."
2052 t nil
2056 "Keywords that may be followed by a comma separated list of type
2057 identifiers, where each optionally can be prefixed by keywords. (Can
2058 also be used for the special case when the list can contain only one
2059 element.)
2061 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2062 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2063 There's also no reason to add keywords that prefixes a normal
2064 declaration consisting of a type followed by a declarator (list), so
2065 the keywords on `c-modifier-kwds' should normally not be listed here
2066 either.
2068 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2069 or variable identifier (that's being defined)."
2070 t nil
2075 ;; In CORBA PSDL:
2080 "Keywords that may be followed by a comma separated list of
2081 reference (i.e. namespace/scope/module) identifiers, where each
2082 optionally can be prefixed by keywords. (Can also be used for the
2083 special case when the list can contain only one element.) Assumed to
2084 be mutually exclusive with `c-type-list-kwds'.
2086 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2087 or variable identifier (that's being defined)."
2088 t nil
2092 ;; In CORBA CIDL:
2097 "Keywords that may be followed (not necessarily directly) by a colon
2098 and then a comma separated list of type identifiers, where each
2099 optionally can be prefixed by keywords. (Can also be used for the
2100 special case when the list can contain only one element.)"
2101 t nil
2104 ;; In CORBA PSDL:
2108 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2109 forward to the colon. The end of the match is assumed to be directly
2111 regexp if `c-colon-type-list-kwds' isn't nil."
2113 ;; Disallow various common punctuation chars that can't come
2114 ;; before the ":" that starts the inherit list after "class"
2115 ;; or "struct" in C++. (Also used as default for other
2116 ;; languages.)
2121 "Keywords that may be followed by a parenthesis expression that doesn't
2122 contain type identifiers."
2123 t nil
2125 "__attribute__"
2126 ;; MSVC extension.
2130 "Keywords that may be followed by a parenthesis expression containing
2131 type identifiers separated by arbitrary tokens."
2132 t nil
2144 "Keywords that may be followed by an angle bracket expression
2146 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2147 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2148 if this isn't nil."
2149 t nil
2152 ;; In CORBA PSDL:
2156 "Keywords that can be followed by a C++ style template arglist; see
2157 `c-recognize-<>-arglists' for details. That language constant is
2158 assumed to be set if this isn't nil."
2159 t nil
2164 ;; All keywords that can be followed by an angle bracket sexp.
2170 ;; Adorned regexp matching keywords that can be followed by an angle
2171 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2176 "Keywords that may be followed by a brace block containing a comma
2177 separated list of identifier definitions, i.e. like the list of
2178 identifiers that follows the type in a normal declaration."
2182 "Statement keywords followed directly by a substatement."
2187 idl nil)
2190 ;; Regexp matching the start of any statement followed directly by a
2191 ;; substatement (doesn't match a bare block, however).
2196 "Statement keywords optionally followed by a paren sexp.
2197 Keywords here should also be in `c-block-stmt-1-kwds'."
2198 t nil
2202 ;; Regexp matching the start of a statement which may be followed by a
2203 ;; paren sexp and will then be followed by a substatement.
2208 "Statement keywords followed by a paren sexp and then by a substatement."
2213 idl nil
2218 ;; Regexp matching the start of any statement followed by a paren sexp
2219 ;; and then by a substatement.
2224 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2230 ;; Regexp matching the start of any statement that has a
2231 ;; substatement (except a bare block). Nil in languages that
2232 ;; don't have such constructs.
2241 "Statement keywords followed by an expression or nothing."
2244 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2246 idl nil
2253 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2258 "Statement keywords followed by a parenthesis expression that
2259 nevertheless contains a list separated with ';' and not ','."
2261 idl nil)
2264 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2269 "Statement keywords followed by an assembler expression."
2270 t nil
2274 ;; Regexp matching the start of an assembler statement. Nil in
2275 ;; languages that don't support that.
2284 awk nil)
2287 ;; Adorned regexp matching any "case"-like keyword.
2292 "Keywords introducing colon terminated labels in blocks."
2296 ;; Adorned regexp matching any keyword that introduces a label.
2301 "Keywords that might be followed by a label identifier."
2305 idl nil
2306 awk nil)
2309 "Keywords for constants."
2310 t nil
2319 "Keywords besides constants and operators that start primary expressions."
2320 t nil
2327 ;; Keywords that can occur anywhere in expressions. Built from
2328 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2332 t
2337 "Keywords that start lambda constructs, i.e. function definitions in
2338 expressions."
2339 t nil
2343 "Keywords that start constructs followed by statement blocks which can
2344 be used in expressions \(the gcc extension for this in C and C++ is
2345 handled separately by `c-recognize-paren-inexpr-blocks')."
2346 t nil
2350 "Keywords that can start classes inside expressions."
2351 t nil
2356 "Keywords that can start brace list blocks inside expressions.
2357 Note that Java specific rules are currently applied to tell this from
2358 `c-inexpr-class-kwds'."
2359 t nil
2363 ;; Regexp matching the start of a brace list in an expression, or
2364 ;; nil in languages that don't have such things. This should not
2365 ;; match brace lists recognized through `c-special-brace-lists'.
2372 ;; Regexp matching keywords in any construct that contain another
2373 ;; declaration level, i.e. that isn't followed by a function block
2374 ;; or brace list. When the first submatch matches, it's an
2375 ;; unambiguous construct, otherwise it's an ambiguous match that
2376 ;; might also be the return type of a function declaration.
2394 "Keywords that can introduce bitfields."
2395 t nil
2399 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2400 ;; languages without bitfield support.
2401 t nil
2406 "Keywords not accounted for by any other `*-kwds' language constant."
2407 t nil
2409 ;; In CORBA CIDL: (These are declaration keywords that never
2410 ;; can start a declaration.)
2413 \f
2414 ;;; Constants built from keywords.
2416 ;; Note: No `*-kwds' language constants may be defined below this point.
2420 ;; List of all the language constants that contain keyword lists.
2425 ;; Make the list of globally interned symbols
2426 ;; instead of ones interned in `c-lang-constants'.
2428 c-lang-constants)
2429 list)))
2432 ;; All keywords as a list.
2437 c-kwds-lang-consts)
2438 nil))
2442 ;; All keywords as an adorned regexp.
2447 ;; An alist with all the keywords in the cars. The cdr for each
2448 ;; keyword is a list of the symbols for the `*-kwds' lists that
2449 ;; contains it.
2455 c-kwds-lang-consts))))
2456 lang-const kwd-list kwd
2457 result-alist elem)
2469 result-alist))
2472 ;; An obarray containing all keywords as symbols. The property list
2473 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2474 ;; lists it's a member of.
2475 ;;
2476 ;; E.g. to see whether the string str contains a keyword on
2477 ;; `c-class-decl-kwds', one can do like this:
2478 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2479 ;; Which preferably is written using the associated functions in
2480 ;; cc-engine:
2481 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2483 ;; The obarray is not stored directly as a language constant since
2484 ;; the printed representation for obarrays used in .elc files isn't
2485 ;; complete.
2488 kwd lang-const-list
2495 ;; Emacs has an odd bug that causes `mapcan' to fail
2496 ;; with unintelligible errors. (XEmacs works.)
2497 ;;(mapcan (lambda (lang-const)
2498 ;; (list lang-const t))
2499 ;; lang-const-list)
2502 lang-const-list))))
2503 obarray))
2506 ;; Adorned regexp matching all keywords that should be fontified
2507 ;; with the keywords face. I.e. that aren't types or constants.
2517 ;; Regexp matching the start of any primary expression, i.e. any
2518 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2519 ;; exclude keywords; they are excluded afterwards unless the second
2520 ;; submatch matches. If the first but not the second submatch
2521 ;; matches then it is an ambiguous primary expression; it could also
2522 ;; be a match of e.g. an infix operator. (The case with ambiguous
2523 ;; keyword operators isn't handled.)
2529 ;; Filter out the special case prefix
2530 ;; operators that are close parens.
2535 t
2541 postfix-if-paren
2542 left-assoc
2543 right-assoc
2544 right-assoc-sequence)
2545 t))
2548 in-or-postfix-ops
2551 in-or-postfix-ops
2556 ;; Take out all symbol class operators from `prefix-ops' and make the
2557 ;; first submatch from them together with `c-primary-expr-kwds'.
2564 ;; Match all ambiguous operators.
2571 ;; Now match all other symbols.
2575 ;; The chars that can start integer and floating point
2576 ;; constants.
2580 ;; The unambiguous operators from `prefix-ops'.
2586 ;; Match string and character literals.
2593 \f
2594 ;;; Additional constants for parser-level constructs.
2597 "Regexp matching a keyword that is followed by a colon, where
2598 the whole construct can precede a declaration.
2606 "Regexp matching something that might precede a declaration, cast or
2607 label, such as the last token of a preceding statement or declaration.
2608 This is used in the common situation where a declaration or cast
2609 doesn't start with any specific token that can be searched for.
2611 The regexp should not match bob; that is done implicitly. It can't
2612 require a match longer than one token. The end of the token is taken
2613 to be at the end of the first submatch, which is assumed to always
2614 match. It's undefined whether identifier syntax (see
2615 `c-identifier-syntax-table') is in effect or not. This regexp is
2616 assumed to be a superset of `c-label-prefix-re' if
2617 `c-recognize-colon-labels' is set.
2619 Besides this, `c-decl-start-kwds' is used to find declarations.
2621 Note: This variable together with `c-decl-start-re' and
2623 declaration/cast/label starts. I.e. they might produce more matches
2624 but should not miss anything (or else it's necessary to use text
2625 properties - see the next note). Wherever they match, the following
2626 construct is analyzed to see if it indeed is a declaration, cast or
2627 label. That analysis is not cheap, so it's important that not too
2628 many false matches are triggered.
2630 Note: If a declaration/cast/label start can't be detected with this
2631 variable, it's necessary to use the `c-type' text property with the
2632 value `c-decl-end' on the last char of the last token preceding the
2633 declaration. See the comment blurb at the start of cc-engine.el for
2634 more info."
2636 ;; We match a sequence of characters to skip over things like \"};\"
2637 ;; more quickly. We match ")" in C for K&R region declarations, and
2638 ;; in all languages except Java for when a cpp macro definition
2639 ;; begins with a declaration.
2642 ;; Match "<" in C++ to get the first argument in a template arglist.
2643 ;; In that case there's an additional check in `c-find-decl-spots'
2644 ;; that it got open paren syntax. Match ":" to aid in picking up
2645 ;; "public:", etc. This involves additional checks in
2646 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2647 ;; or labels.
2649 ;; Additionally match the protection directives in Objective-C.
2650 ;; Note that this doesn't cope with the longer directives, which we
2651 ;; would have to match from start to end since they don't end with
2652 ;; any easily recognized characters.
2656 ;; Pike is like C but we also match "[" for multiple value
2657 ;; assignments and type casts.
2663 "Regexp matching the start of any declaration, cast or label.
2664 It's used on the token after the one `c-decl-prefix-re' matched. This
2665 regexp should not try to match those constructs accurately as it's
2666 only used as a sieve to avoid spending more time checking other
2667 constructs."
2672 ;; Regexp matching something that might precede or start a
2673 ;; declaration, cast or label.
2674 ;;
2675 ;; If the first submatch matches, it's taken to match the end of a
2676 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2677 ;; It's built from `c-decl-prefix-re'.
2678 ;;
2679 ;; If the first submatch did not match, the match of the whole
2680 ;; regexp is taken to be at the first token in the declaration.
2681 ;; `c-decl-start-re' is not checked in this case.
2682 ;;
2683 ;; Design note: The reason the same regexp is used to match both
2684 ;; tokens that precede declarations and start them is to avoid an
2685 ;; extra regexp search from the previous declaration spot in
2686 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2687 ;; that it finds all declaration/cast/label starts in approximately
2688 ;; linear order, so we can't do the searches in two separate passes.
2699 ;; List containing the paren characters that can open a cast, or nil in
2700 ;; languages without casts.
2708 "List of syntactically relevant characters that never can occur before
2709 the open brace in any construct that contains a brace block, e.g. in
2712 class Foo: public Bar {int x();} a, *b;
2714 If parens can occur, the chars inside those aren't filtered with this
2715 list.
2717 '<' and '>' should be disallowed even if angle bracket arglists can
2718 occur. That since the search function needs to stop at them anyway to
2719 ensure they are given paren syntax.
2721 This is used to skip backward from the open brace to find the region
2724 possible for good performance."
2726 ;; Default to all chars that only occurs in nonsymbol tokens outside
2727 ;; identifiers.
2733 t
2734 t
2738 op pos)
2741 res))))
2743 ;; Allow cpp operations (where applicable).
2749 ;; Allow ':' for inherit list starters.
2753 ;; Allow ',' for multiple inherits.
2757 ;; Allow parentheses for anonymous inner classes in Java and class
2758 ;; initializer lists in Pike.
2762 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2767 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2768 ;; for `c-syntactic-skip-backward'.
2773 "Regexp matching the declarator operators that might precede the
2776 The end of the first submatch is taken as the end of the operator.
2777 Identifier syntax is in effect when this is matched \(see
2778 `c-identifier-syntax-table')."
2781 ;; Default to a regexp that never matches.
2783 ;; Check that there's no "=" afterwards to avoid matching tokens
2784 ;; like "*=".
2786 "[*\(]"
2792 "[*\(&]"
2797 ;; If this matches there's special treatment in
2798 ;; `c-font-lock-declarators' and
2799 ;; `c-font-lock-declarations' that check for a
2800 ;; complete name followed by ":: *".
2810 "Regexp matching the declarator operators that might follow after the
2813 it matches an open paren of some kind, the type declaration check
2814 continues at the corresponding close paren, otherwise the end of the
2815 first submatch is taken as the end of the operator. Identifier syntax
2816 is in effect when this is matched (see `c-identifier-syntax-table')."
2817 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2818 ;; function argument list parenthesis.
2826 "[\)\[\(]"
2830 ;; "throw" in `c-type-modifier-kwds' is followed
2831 ;; by a parenthesis list, but no extra measures
2832 ;; are necessary to handle that.
2843 "This regexp is matched after a declarator expression where
2844 `c-type-decl-suffix-key' has matched. If it matches then the
2845 construct is taken as a declaration. It's typically used to match the
2846 beginning of a function body or whatever might occur after the
2847 function header in a function declaration or definition. It's
2848 undefined whether identifier syntax (see `c-identifier-syntax-table')
2849 is in effect or not.
2854 t "{"
2855 ;; If K&R style declarations should be recognized then one could
2856 ;; consider to match the start of any symbol since we want to match
2857 ;; the start of the first declaration in the "K&R region". That
2858 ;; could however produce false matches on code like "FOO(bar) x"
2859 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2860 ;; on the other heuristics in that case.
2862 ;; Add on the keywords in `c-postfix-spec-kwds'.
2867 ;; Also match the colon that starts a base class initializer list in
2868 ;; C++. That can be confused with a function call before the colon
2869 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2870 ;; match before such a thing (as a declaration-level construct;
2871 ;; matches inside arglist contexts are already excluded).
2878 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2879 ;; matches ";" and ",".
2888 end of the operator. nil in languages without such operators. It's
2889 undefined whether identifier syntax (see `c-identifier-syntax-table')
2890 is in effect or not."
2891 t nil
2897 "Regexp matching operators that might follow after a type, or nil in
2898 languages that don't have such operators. The end of the first
2899 submatch is taken as the end of the operator. This should not match
2900 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2901 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2902 is in effect or not."
2903 t nil
2909 ;; Regexp matching the known type identifiers. This is initialized
2910 ;; from the type keywords and `*-font-lock-extra-types'. The first
2911 ;; submatch is the one that matches the type. Note that this regexp
2912 ;; assumes that symbol constituents like '_' and '$' have word
2913 ;; syntax.
2922 extra-types)))
2928 extra-types))))
2933 plain-strings)))
2934 regexp-strings)
2939 "List of open- and close-chars that makes up a pike-style brace list,
2941 list."
2942 t nil
2947 "Non-nil means K&R style argument declarations are valid."
2948 t nil
2949 c t)
2953 "Non-nil means function declarations without return type should be
2954 recognized. That can introduce an ambiguity with parenthesized macro
2955 calls before a brace block. This setting does not affect declarations
2956 that are preceded by a declaration starting keyword, so
2957 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2958 t nil
2964 "Non-nil means C++ style template arglists should be handled. More
2965 specifically, this means a comma separated list of types or
2967 identifier or one of the keywords on `c-<>-type-kwds' or
2968 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2969 expression is considered to be a type."
2972 java t)
2976 "Non-nil means that an enum structure can contain declarations."
2977 t nil
2978 java t)
2982 "Non-nil means that parenthesis style initializers exist,
2983 i.e. constructs like
2985 Foo bar (gnu);
2987 in addition to the more classic
2989 Foo bar = gnu;"
2990 t nil
2995 "Non-nil to recognize gcc style in-expression blocks,
2996 i.e. compound statements surrounded by parentheses inside expressions."
2997 t nil
3003 ;; Regexp matching the start of angle bracket arglists in languages
3004 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3005 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3006 ;; assumed to surround the preceding symbol. The whole match is
3007 ;; assumed to end directly after the opening "<".
3017 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3018 ;; parens. The first submatch is assumed to surround
3019 ;; `c-opt-<>-arglist-start'.
3028 ;; Regexp matching the beginning of a declaration specifier in the
3029 ;; region between the header and the body of a declaration.
3030 ;;
3031 ;; TODO: This is currently not used uniformly; c++-mode and
3032 ;; java-mode each have their own ways of using it.
3033 t nil
3046 That includes labels in code and access keys in classes. This does
3047 not apply to labels recognized by `c-label-kwds' and
3048 `c-opt-extra-label-key'."
3049 t nil
3055 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3056 a generic colon label. Not used if `c-recognize-colon-labels' is
3057 nil."
3063 "Regexp matching things that can't occur in generic colon labels,
3064 neither in a statement nor in a declaration context. The regexp is
3065 tested at the beginning of every sexp in a suspected label,
3068 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3074 ;; Don't allow string literals, except in AWK. Character constants are OK.
3077 ;; Also check for open parens in C++, to catch member init lists in
3078 ;; constructors. We normally allow it so that macros with arguments
3079 ;; work in labels.
3084 "Regexp matching things that can't occur two symbols before a colon in
3092 "Optional regexp matching labels.
3093 Normally, labels are detected according to `c-nonlabel-token-key',
3094 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3095 be used if there are additional labels that aren't recognized that
3096 way."
3097 t nil
3102 ;; Regexp describing friend declarations classes, or nil in
3103 ;; languages that don't have such things.
3104 ;;
3105 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3106 ;; template skipping isn't done properly. This will disappear soon.
3107 t nil
3112 "<.+>"
3114 "friend"
3119 ;; Special regexp to match the start of Objective-C methods. The
3120 ;; first submatch is assumed to end after the + or - key.
3121 t nil
3123 ;; TODO: Ought to use a better method than anchoring on bol.
3128 "([^\)]*)"
3135 ;; Must be set in buffers where the `c-type' text property might be
3136 ;; used with the value `c-decl-end'.
3137 ;;
3138 ;; `c-decl-end' is used to mark the ends of labels and access keys
3139 ;; to make interactive refontification work better.
3142 ;; `c-decl-end' is used to mark the end of the @-style directives in
3143 ;; Objective-C.
3144 objc t)
3147 \f
3148 ;;; Wrap up the `c-lang-defvar' system.
3150 ;; Compile in the list of language variables that has been collected
3151 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3152 ;; first element of each is nil.
3156 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3157 ;; These are typically standard emacs variables such as `comment-start'.
3165 "Create a function that initializes all the language dependent variables
3166 for the given mode.
3168 This function should be evaluated at compile time, so that the
3169 function it returns is byte compiled with all the evaluated results
3170 from the language constants. Use the `c-init-language-vars' macro to
3171 accomplish that conveniently."
3177 ;; No need to byte compile this lambda since the byte compiler is
3178 ;; smart enough to detect the `funcall' construct in the
3179 ;; `c-init-language-vars' macro below and compile it all straight
3180 ;; into the function that contains `c-init-language-vars'.
3183 ;; This let sets up the context for `c-mode-var' and similar
3184 ;; that could be in the result from `cl-macroexpand-all'.
3186 current-var source-eval)
3193 ;; `c-lang-const' will expand to the evaluated
3194 ;; constant immediately in `cl-macroexpand-all'
3195 ;; below.
3201 ;; Note: The following `append' copies the
3202 ;; first argument. That list is small, so
3203 ;; this doesn't matter too much.
3207 ;; This diagnostic message isn't useful for end
3208 ;; users, so it's disabled.
3209 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3210 ;; (message ,(concat "%s compiled with CC Mode %s "
3211 ;; "but loaded with %s - evaluating "
3212 ;; "language constants from source")
3213 ;; ',mode ,c-version c-version)
3214 ;; (put ',mode 'c-has-warned-lang-consts t))
3227 current-var
3230 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3233 err)
3236 ;; Being evaluated from source. Always use the dynamic method to
3237 ;; work well when `c-lang-defvar's in this file are reevaluated
3238 ;; interactively.
3244 current-var)
3256 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3257 current-var err)
3259 ))
3262 "Initialize all the language dependent variables for the given mode.
3263 This macro is expanded at compile time to a form tailored for the mode
3264 in question, so MODE must be a constant. Therefore MODE is not
3265 evaluated and should not be quoted."
3268 \f
3271 ;;; cc-langs.el ends here