| blob | 2bf660a32eb9bd041651de8a1814326e22defcb2 |
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.
133 ;; Except it is always loaded - see bug#17463.
134 ;;;(cc-external-require 'cl)
137 \f
138 ;;; Setup for the `c-lang-defvar' system.
141 ;; These are used to collect the init forms from the subsequent
142 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
143 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
144 ;; and `make-variable-buffer-local's in cc-engine and
145 ;; `make-local-variable's in `c-init-language-vars-for'.
149 c-lang-variable-inits-tail c-lang-variable-inits)
153 c-emacs-variable-inits-tail c-emacs-variable-inits))
156 "Declares the buffer local variable VAR to get the value VAL. VAL is
157 evaluated and assigned at mode initialization. More precisely, VAL is
158 evaluated and bound to VAR when the result from the macro
159 `c-init-language-vars' is evaluated.
161 `c-lang-const' is typically used in VAL to get the right value for the
162 language being initialized, and such calls will be macro expanded to
163 the evaluated constant value at compile time."
169 ;; Special case: If there's no docstring and the value is a
170 ;; simple (c-lang-const foo) where foo is the same name as VAR
171 ;; then take the docstring from the language constant foo.
183 ;; Return the symbol, like the other def* forms.
187 "Causes the variable VAR to be made buffer local and to get set to the
188 value VAL. VAL is evaluated and assigned at mode initialization. More
189 precisely, VAL is evaluated and bound to VAR when the result from the
190 macro `c-init-language-vars' is evaluated. VAR is typically a standard
191 Emacs variable like `comment-start'.
193 `c-lang-const' is typically used in VAL to get the right value for the
194 language being initialized, and such calls will be macro expanded to
195 the evaluated constant value at compile time."
202 ;; Return the symbol, like the other def* forms.
206 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
207 ; '
211 ;; Suppress "might not be defined at runtime" warning.
212 ;; This file is only used when compiling other cc files.
213 ;; These are defined in cl as aliases to the cl- versions.
214 ;(declare-function delete-duplicates "cl-seq" (cl-seq &rest cl-keys) t)
215 ;(declare-function mapcan "cl-extra" (cl-func cl-seq &rest cl-rest) t)
218 ;; Some helper functions used when building the language constants.
221 ;; Extract a subset of the operators in the list OPS in a DWIM:ey
222 ;; way. The return value is a plain list of operators:
223 ;;
224 ;; OPS either has the structure of `c-operators', is a single
225 ;; group in `c-operators', or is a plain list of operators.
226 ;;
227 ;; OPGROUP-FILTER specifies how to select the operator groups. It
228 ;; can be t to choose all groups, a list of group type symbols
229 ;; (such as 'prefix) to accept, or a function which will be called
230 ;; with the group symbol for each group and should return non-nil
231 ;; if that group is to be included.
232 ;;
233 ;; If XLATE is given, it's a function which is called for each
234 ;; matching operator and its return value is collected instead.
235 ;; If it returns a list, the elements are spliced directly into
236 ;; the final result, which is returned as a list with duplicates
237 ;; removed using `equal'.
238 ;;
239 ;; `c-mode-syntax-table' for the current mode is in effect during
240 ;; the whole procedure.
261 t)
262 t)
267 opgroup)))
268 ops)
271 \f
272 ;;; Various mode specific values that aren't language related.
275 ;; The definition for the mode menu. The menu title is prepended to
276 ;; this before it's fed to `easy-menu-define'.
286 "----"
290 ;; Only applicable if there's a cpp preprocessor.
294 "----"
299 "----"
303 "Style Name: %s"
308 c-guess-guessed-basic-offset) ]
311 c-guess-guessed-basic-offset) ])
312 "----"
324 subword-mode)])))
326 \f
327 ;;; Syntax tables.
330 "Populate the given syntax table as necessary for a C-like language.
348 ;; Set up block and line oriented comments. The new C
349 ;; standard mandates both comment styles even in C, so since
350 ;; all languages now require dual comments, we make this the
351 ;; default.
353 ;; XEmacs
357 ;; Emacs
361 ;; incompatible
365 ;; Give CR the same syntax as newline, for selective-display
369 "Functions that generates the mode specific syntax tables.
370 The syntax tables aren't stored directly since they're quite large."
374 ;; Mode specific syntaxes.
376 ;; Let '@' be part of symbols in ObjC to cope with
377 ;; its compiler directives as single keyword tokens.
378 ;; This is then necessary since it's assumed that
379 ;; every keyword is a single symbol.
383 table)))
386 ;; The syntax tables in evaluated form. Only used temporarily when
387 ;; the constants in this file are evaluated.
391 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
392 ;; parenthesis characters. Used temporarily when template argument
393 ;; lists are parsed. Note that this encourages incorrect parsing of
394 ;; templates since they might contain normal operators that uses the
395 ;; '<' and '>' characters. Therefore this syntax table might go
396 ;; away when CC Mode handles templates correctly everywhere. WHILE
397 ;; THIS SYNTAX TABLE IS CURRENT, `c-parse-state' MUST _NOT_ BE
398 ;; CALLED!!!
399 t nil
404 table)))
410 ;; A variant of the standard syntax table which is used to find matching
411 ;; "<"s and ">"s which have been marked as parens using syntax table
412 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
413 ;; non-paren syntax here. so that the list commands will work on "< ... >"
414 ;; even when there's unbalanced other parens inside them.
415 ;;
416 ;; This variable is nil for languages which don't have template stuff.
426 table))))
431 "A list that describes the modifications that should be done to the
432 mode syntax table to get a syntax table that matches all identifiers
433 and keywords as words.
435 The list is just like the one used in `font-lock-defaults': Each
436 element is a cons where the car is the character to modify and the cdr
437 the new syntax, as accepted by `modify-syntax-entry'."
438 ;; The $ character is not allowed in most languages (one exception
439 ;; is Java which allows it for legacy reasons) but we still classify
440 ;; it as an identifier character since it's often used in various
441 ;; machine generated identifiers.
452 mod)
457 table)
458 "Syntax table built on the mode syntax table but additionally
459 classifies symbol constituents like '_' and '$' as word constituents,
463 ;; For documentation see the following c-lang-defvar of the same name.
464 ;; The value here may be a list of functions or a single function.
465 t nil
467 c-before-change-check-<>-operators
468 c-invalidate-macro-cache)
470 ;; java 'c-before-change-check-<>-operators
475 fs
477 "If non-nil, a list of functions called from c-before-change-hook.
478 Typically these will record enough state to allow
479 `c-before-font-lock-function' to extend the region to fontify,
480 and may do such things as removing text-properties which must be
481 recalculated.
483 These functions will be run in the order given. Each of them
484 takes 2 parameters, the BEG and END supplied to every
485 before-change function; on entry, the buffer will have been
486 widened and match-data will have been saved; point is undefined
487 on both entry and exit; the return value is ignored.
489 The functions are called even when font locking isn't enabled.
491 When the mode is initialized, the functions are called with
495 ;; For documentation see the following c-lang-defvar of the same name.
496 ;; The value here may be a list of functions or a single function.
497 t 'c-change-set-fl-decl-start
499 c-change-set-fl-decl-start)
504 fs
506 "If non-nil, a list of functions called just before font locking.
507 Typically they will extend the region about to be fontified \(see
508 below) and will set `syntax-table' text properties on the region.
510 These functions will be run in the order given. Each of them
511 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
512 after-change function; point is undefined on both entry and exit;
513 on entry, the buffer will have been widened and match-data will
514 have been saved; the return value is ignored.
516 The functions may extend the region to be fontified by setting the
517 buffer local variables c-new-BEG and c-new-END.
519 The functions are called even when font locking is disabled.
521 When the mode is initialized, these functions are called with
525 awk nil
527 ;; For documentation see the following c-lang-defvar of the same name.
528 ;; The value here may be a list of functions or a single function.
532 fs
534 "If non-nil, a list of functions called just before context (or
535 other non-change) fontification is done. Typically they will
536 extend the region.
538 These functions will be run in the order given. Each of them
539 takes 2 parameters, the BEG and END of the region to be
540 fontified. Point is undefined on both entry and exit. On entry,
541 the buffer will have been widened and match-data will have been
542 saved; the return value is a cons of the adjusted
545 \f
546 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
549 Such a function takes one optional parameter, a buffer position (defaults to
550 point), and returns nil or t. This variable contains nil for languages which
551 don't have EOL terminated statements. "
552 t nil
559 The (admittedly kludgy) purpose of such a function is to prevent an infinite
560 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
561 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
562 even indirectly. This variable contains nil for languages which don't have
563 EOL terminated statements."
564 t nil
570 \f
571 ;;; Lexer-level syntax (identifiers, tokens etc).
574 "Whether the language has bitfield declarations."
575 t nil
580 "Regexp that matches the start of a symbol, i.e. any identifier or
582 operator at the top level."
590 "Set of characters that can be part of a symbol.
591 This is of the form that fits inside [ ] in a regexp."
592 ;; Pike note: With the backquote identifiers this would include most
593 ;; operator chars too, but they are handled with other means instead.
599 "Regexp matching identifiers and keywords (with submatch 0). Assumed
600 to match if `c-symbol-start' matches on the same position."
604 ;; Use the value from C here since the operator backquote is
605 ;; covered by the other alternative.
613 ;; Number of regexp grouping parens in `c-symbol-key'.
617 "This is the set of chars that can't be part of a symbol, i.e. the
618 negation of `c-symbol-chars'."
623 "Regexp that matches any character that can't be part of a symbol.
624 It's usually appended to other regexps to avoid matching a prefix.
625 It's assumed to not contain any submatchers."
626 ;; The same thing regarding Unicode identifiers applies here as to
627 ;; `c-symbol-key'.
631 "The operators that make up fully qualified identifiers. nil in
632 languages that don't have such things. See `c-operators' for a
633 description of the format. Binary operators can concatenate symbols,
637 This value is by default merged into `c-operators'."
638 t nil
642 ;; Java has "." to concatenate identifiers but it's also used for
643 ;; normal indexing. There's special code in the Java font lock
644 ;; rules to fontify qualified identifiers based on the standard
645 ;; naming conventions. We still define "." here to make
646 ;; `c-forward-name' move over as long names as possible which is
647 ;; necessary to e.g. handle throws clauses correctly.
656 ;; Appendable adorned regexp matching the operators that join
657 ;; symbols to fully qualified identifiers, or nil in languages that
658 ;; don't have such things.
659 ;;
660 ;; This was a docstring constant in 5.30. It still works but is now
661 ;; considered internal - change `c-identifier-ops' instead.
664 t)))
672 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
676 ;; Appendable adorned regexp matching operators that might precede
677 ;; an identifier and that are part of the identifier in that case.
678 ;; nil in languages without such things.
681 t)))
686 "Operators that can occur after a binary operator on `c-identifier-ops'
687 in identifiers. nil in languages that don't have such things.
689 Operators here should also have appropriate entries in `c-operators' -
690 it's not taken care of by default."
691 t nil
692 ;; '~' for destructors in C++, '*' for member pointers.
694 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
695 ;; in import declarations. (This will also match bogus things like
696 ;; "foo.*bar" but we don't bother.)
700 ;; Regexp that must match the token after
701 ;; `c-opt-identifier-concat-key' for it to be considered an
702 ;; identifier concatenation operator (which e.g. causes the
703 ;; preceding identifier to be fontified as a reference). Assumed to
704 ;; be a string if `c-opt-identifier-concat-key' is.
705 ;;
706 ;; This was a docstring constant in 5.30. It still works but is now
707 ;; considered internal - change `c-after-id-concat-ops' instead.
715 "Regexp that matches the start of an (optionally qualified) identifier.
716 It should also match all keywords. It's unspecified how far it
717 matches."
727 C++. It does not recognize the full range of syntactic whitespace
728 between the tokens; `c-forward-name' has to be used for that. It
729 should also not match identifiers containing parenthesis groupings,
731 ;; This regexp is more complex than strictly necessary to ensure
732 ;; that it can be matched with a minimum of backtracking.
753 ;; For flexibility, consider the symbol match
754 ;; optional if we've hit a
755 ;; `c-after-id-concat-ops' operator. This is
756 ;; also necessary to handle the "*" that can
757 ;; end import declaration identifiers in Java.
771 ;; This was a docstring constant in 5.30 but it's no longer used.
772 ;; It's only kept to avoid breaking third party code.
773 ;;
774 ;; Used to identify the submatch in `c-identifier-key' that
775 ;; surrounds the last symbol in the qualified identifier. It's a
776 ;; list of submatch numbers, of which the first that has a match is
777 ;; taken. It's assumed that at least one does when the regexp has
778 ;; matched.
779 t nil)
782 "Set if the language support backslash escaped newlines inside string
783 literals."
784 t nil
790 "Set if the language supports multiline string literals without escaped
791 newlines. If t, all string literals are multiline. If a character,
792 only literals where the open quote is immediately preceded by that
793 literal are multiline."
794 t nil
795 pike ?#)
800 "The symbol which starts preprocessor constructs when in the margin."
801 t "#"
806 "Regexp matching the prefix of a cpp directive in the languages that
807 normally use that macro preprocessor. Tested at bol or at boi.
809 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
810 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
816 "Regexp matching the prefix of a cpp directive anchored to BOL,
817 in the languages that have a macro preprocessor."
823 "Regexp matching the prefix of a cpp directive including the directive
824 name, or nil in languages without preprocessor support. The first
825 submatch surrounds the directive name."
829 ;; Pike, being a scripting language, recognizes hash-bangs too.
835 "List of cpp directives (without the prefix) that are followed by a
836 string message."
842 "List of cpp directives (without the prefix) that are followed by a
843 file name in angle brackets or quotes."
849 "Cpp directive (without the prefix) that is followed by a macro
850 definition, or nil if the language doesn't have any."
857 ;; Regexp matching everything up to the macro body of a cpp define, or the
858 ;; end of the logical line if there is none. Submatch 1 is the name of the
859 ;; macro. Set if c-opt-cpp-macro-define is.
864 ;; ^ ^ #defined name
870 ;; Regexp matching everything up to the end of the identifier defined
871 ;; by a cpp define.
880 "List of cpp directives (without the prefix) that are followed by an
881 expression."
886 "Regexp which matches the start of a CPP directive which contains an
887 expression, or nil if there aren't any in the language."
896 "List of functions in cpp expressions."
902 "List of all assignment operators."
908 idl nil)
911 "List describing all operators, along with their precedence and
912 associativity. The order in the list corresponds to the precedence of
913 the operators: The operators in each element are a group with the same
914 precedence, and the group has higher precedence than the groups in all
915 following elements. The car of each element describes the type of the
916 operator group, and the cdr is a list of the operator tokens in it.
917 The operator group types are:
919 'prefix Unary prefix operators.
920 'postfix Unary postfix operators.
921 'postfix-if-paren
922 Unary postfix operators if and only if the chars have
923 parenthesis syntax.
924 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
925 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
926 'right-assoc-sequence
927 Right associative operator that constitutes of a
928 sequence of tokens that separate expressions. All the
929 tokens in the group are in this case taken as
930 describing the sequence in one such operator, and the
931 order between them is therefore significant.
933 Operators containing a character with paren syntax are taken to match
934 with a corresponding open/close paren somewhere else. A postfix
935 operator with close paren syntax is taken to end a postfix expression
936 started somewhere earlier, rather than start a new one at point. Vice
937 versa for prefix operators with open paren syntax.
940 often are described as postfix operators are considered binary here,
941 since CC Mode treats every identifier as an expression."
943 ;; There's currently no code in CC Mode that exploit all the info
944 ;; in this variable; precedence, associativity etc are present as a
945 ;; preparation for future work.
956 ;; Primary.
965 ;; Postfix.
967 ;; The following need special treatment.
977 ;; Unary.
984 ;; The following need special treatment.
995 ;; Member selection.
999 ;; Multiplicative.
1002 ;; Additive.
1005 ;; Shift.
1010 ;; Relational.
1015 ;; Equality.
1019 ;; Bitwise and.
1023 ;; Bitwise exclusive or.
1029 ;; Bitwise or.
1035 ;; Logical and.
1039 ;; Logical or.
1045 ;; Conditional.
1048 ;; Assignment.
1051 ;; Exception.
1055 ;; Sequence.
1058 ;; IDL got its own definition since it has a much smaller operator
1059 ;; set than the other languages.
1063 ;; Primary.
1065 ;; Unary.
1067 ;; Multiplicative.
1069 ;; Additive.
1071 ;; Shift.
1073 ;; And.
1075 ;; Xor.
1077 ;; Or.
1081 ;; The operators as a flat list (without duplicates).
1087 t nil
1096 ;; These work like identifiers in Pike.
1103 ;; Regexp tested after an "operator" token in C++.
1104 t nil
1110 "Regexp matching the token before the ones in
1111 `c-overloadable-operators' when operators are specified in their
1114 languages without operator functions or where the complete operator
1115 identifier is listed in `c-overloadable-operators'.
1117 This regexp is assumed to not match any non-operator identifier."
1118 t nil
1123 ;; Note: the following alias is an old name which was a mis-spelling. It has
1124 ;; been corrected above and throughout cc-engine.el. It will be removed at
1125 ;; some release very shortly in the future. ACM, 2006-04-14.
1131 "List of the tokens made up of characters in the punctuation or
1132 parenthesis syntax classes that have uses other than as expression
1133 operators."
1151 ;; List of all tokens in the punctuation and parenthesis syntax
1152 ;; classes.
1158 ;; List containing all chars not in the word, symbol or
1159 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1160 ;; parenthesis and string delimiter chars.
1162 ;; Only go through the chars in the printable ASCII range. No
1163 ;; language so far has 8-bit or widestring operators.
1169 list)))
1172 ;; Regexp matching all tokens in the punctuation and parenthesis
1173 ;; syntax classes. Note that this also matches ".", which can start
1174 ;; a float.
1177 t
1183 ;; Regexp matching all assignment operators and only them. The
1184 ;; beginning of the first submatch is used to detect the end of the
1185 ;; token, along with the end of the whole match.
1188 ;; Need special case for "=" since it's a prefix of "==".
1200 ;; Regexp matching all tokens containing "<" or ">" which are longer
1201 ;; than one char.
1204 t
1210 ;; Regexp matching the second and subsequent characters of all
1211 ;; multicharacter tokens that begin with "<".
1214 t
1221 ;; A list of second and subsequent characters of all multicharacter tokens
1222 ;; that begin with ">".
1224 t
1228 t
1233 ;; Regexp matching the second and subsequent characters of all
1234 ;; multicharacter tokens that begin with ">".
1240 ;; Regexp matching the second and subsequent characters of all
1241 ;; multicharacter tokens that begin with ">" except for those beginning with
1242 ;; ">>".
1247 t
1256 ;; The characters that should be considered to bound statements. To
1257 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1258 ;; begin with "^" to negate the set. If ? : operators should be
1259 ;; detected then the string must end with "?:".
1264 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1269 \f
1270 ;;; Syntactic whitespace.
1273 "Regexp matching an ordinary whitespace character.
1275 ;; "\\s " is not enough since it doesn't match line breaks.
1279 ;; Number of regexp grouping parens in `c-simple-ws'.
1283 "String that starts line comments, or nil if such don't exist.
1284 Line comments are always terminated by newlines. At least one of
1285 `c-block-comment-starter' and this one is assumed to be set.
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 "//"
1295 "String that starts block comments, or nil if such don't exist.
1296 Block comments are ended by `c-block-comment-ender', which is assumed
1297 to be set if this is. At least one of `c-line-comment-starter' and
1298 this one is assumed to be set.
1300 Note that it's currently not enough to set this to support a new
1301 comment style. Other stuff like the syntax table must also be set up
1302 properly."
1303 t "/*"
1304 awk nil)
1307 "String that ends block comments, or nil if such don't exist.
1309 Note that it's currently not enough to set this to support a new
1310 comment style. Other stuff like the syntax table must also be set up
1311 properly."
1312 t "*/"
1313 awk nil)
1316 ;; Regexp to match the start of any type of comment.
1322 re)))
1326 ;; Regexp which matches the start of a block comment (if such exists in the
1327 ;; language)
1335 ;; Regexp which matches the start of a line comment (if such exists in the
1336 ;; language; it does in all 7 CC Mode languages).
1344 ;; Regexp to match the start of comments and string literals.
1353 "Regexp to match the start of documentation comments."
1355 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1363 "String that starts comments inserted with M-; etc.
1364 `comment-start' is initialized from this."
1365 ;; Default: Prefer line comments to block comments, and pad with a space.
1369 ;; In C we still default to the block comment style since line
1370 ;; comments aren't entirely portable.
1375 "String that ends comments inserted with M-; etc.
1376 `comment-end' is initialized from this."
1377 ;; Default: Use block comment style if comment-start uses block
1378 ;; comments, and pad with a space in that case.
1388 "Regexp to match the start of a comment plus everything up to its body.
1389 `comment-start-skip' is initialized from this."
1390 ;; Default: Allow the last char of the comment starter(s) to be
1391 ;; repeated, then allow any amount of horizontal whitespace.
1404 ;; Regexp matching any sequence that can start syntactic whitespace.
1405 ;; The only uncertain case is '#' when there are cpp directives.
1419 ;; Regexp matching any single character that might end syntactic whitespace.
1434 ;; Regexp matching an unterminated block comment that doesn't
1435 ;; contain line breaks, or nil in languages without block comments.
1436 ;; Does not contain a \| operator at the top level.
1440 ;; It's messy to cook together a regexp that matches anything
1441 ;; but c-block-comment-ender.
1449 "[^"
1450 ;; The quoting rules inside char classes are silly. :P
1459 "]"
1467 ;; Regexp matching a block comment that doesn't contain line breaks,
1468 ;; or nil in languages without block comments. The reason we don't
1469 ;; allow line breaks is to avoid going very far and risk running out
1470 ;; of regexp stack; this regexp is intended to handle only short
1471 ;; comments that might be put in the middle of limited constructs
1472 ;; like declarations. Does not contain a \| operator at the top
1473 ;; level.
1488 ;; Regexp matching a piece of syntactic whitespace that isn't a
1489 ;; sequence of simple whitespace characters. As opposed to
1490 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1491 ;; directives as syntactic whitespace.
1503 ;; Regexp matching syntactic whitespace, including possibly the
1504 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1505 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1506 ;; not contain a \| operator at the top level.
1514 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1518 ;; Regexp matching syntactic whitespace, which is at least one
1519 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1520 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1521 ;; not contain a \| operator at the top level.
1529 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1533 ;; Regexp matching syntactic whitespace without any line breaks. As
1534 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1535 ;; regard cpp directives as syntactic whitespace. Does not contain
1536 ;; a \| operator at the top level.
1544 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1548 ;; Regexp that matches when there is no syntactically significant
1549 ;; text before eol. Macros are regarded as syntactically
1550 ;; significant text here.
1552 ;; Match eol (possibly inside a block comment or preceded
1553 ;; by a line continuation backslash), or the beginning of a
1554 ;; line comment. Note: This has to be modified for awk
1555 ;; where line comments start with '#'.
1569 \f
1570 ;;; Defun functions
1572 ;; The Emacs variables beginning-of-defun-function and
1573 ;; end-of-defun-function will be set so that commands like
1574 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1575 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1576 ;; functions, allowing optimization for large n.
1578 "Function to which beginning-of-defun-function will be set."
1579 t 'c-beginning-of-defun
1585 "Function to which end-of-defun-function will be set."
1586 t 'c-end-of-defun
1589 \f
1590 ;;; In-comment text handling.
1593 "Regexp to append to `paragraph-start'."
1594 t "$"
1600 "Regexp to append to `paragraph-separate'."
1601 t "$"
1605 \f
1606 ;;; Keyword lists.
1608 ;; Note: All and only all language constants containing keyword lists
1609 ;; should end with "-kwds"; they're automatically collected into the
1610 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1613 "Primitive type keywords. As opposed to the other keyword lists, the
1614 keywords listed here are fontified with the type face instead of the
1615 keyword face.
1617 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1618 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1619 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1620 will be handled.
1622 Do not try to modify this list for end user customizations; the
1623 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1624 the appropriate place for that."
1633 ;; Objective-C extends C, but probably not the new stuff in C99.
1640 ;; In CORBA PSDL:
1641 "ref"
1642 ;; The following can't really end a type, but we have to specify them
1643 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1644 ;; doesn't matter that much.
1647 ;; used as a builtin type.
1652 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1657 "Keywords that might act as prefixes for primitive types. Assumed to
1658 be a subset of `c-primitive-type-kwds'."
1659 t nil
1662 ;; In CORBA PSDL:
1667 of a variable declaration."
1672 ;; Adorned regexp matching `c-typedef-kwds'.
1677 "Keywords where the following name - if any - is a type name, and
1678 where the keyword together with the symbol works as a type in
1679 declarations.
1681 Note that an alternative if the second part doesn't hold is
1682 `c-type-list-kwds'. Keywords on this list are typically also present
1683 on one of the `*-decl-kwds' lists."
1684 t nil
1690 ;; Adorned regexp matching `c-type-prefix-kwds'.
1695 "Type modifier keywords. These can occur almost anywhere in types
1696 but they don't build a type of themselves. Unlike the keywords on
1697 `c-primitive-type-kwds', they are fontified with the keyword face and
1698 not the type face."
1699 t nil
1705 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1706 ;; languages without such keywords.
1712 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1713 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1723 ;; All keywords that can start a type (i.e. are either a type prefix
1724 ;; or a complete type).
1731 "Keywords introducing declarations where the following block (if any)
1732 contains another declaration level that should be considered a class.
1734 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1735 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1736 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1737 will be handled.
1739 Note that presence on this list does not automatically treat the
1740 following identifier as a type; the keyword must also be present on
1741 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1742 t nil
1750 ;; In CORBA PSDL:
1752 ;; In CORBA CIDL:
1757 ;; Regexp matching the start of a class.
1762 "Keywords introducing declarations where the following block (if
1763 any) is a brace list.
1765 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1766 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1767 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1768 will be handled."
1773 ;; Regexp matching the start of declarations where the following
1774 ;; block is a brace list.
1779 "Keywords where the following block (if any) contains another
1780 declaration level that should not be considered a class. For every
1781 keyword here, CC Mode will add a set of special syntactic symbols for
1783 `foo-open', `foo-close', and `infoo' symbols.
1785 The intention is that this category should be used for block
1786 constructs that aren't related to object orientation concepts like
1787 classes (which thus also include e.g. interfaces, templates,
1788 contracts, structs, etc). The more pragmatic distinction is that
1789 while most want some indentation inside classes, it's fairly common
1790 that they don't want it in some of these constructs, so it should be
1791 simple to configure that differently from classes. See also
1792 `c-class-decl-kwds'.
1794 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1795 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1796 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1797 will be handled."
1798 t nil
1802 ;; In CORBA CIDL:
1806 ;; Regexp matching the start of blocks besides classes that contain
1807 ;; another declaration level.
1816 'inextern-lang
1819 "Alist associating keywords in c-other-decl-block-decl-kwds with
1823 "Keywords introducing declarations where the identifier(s) being
1824 declared are types.
1826 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1827 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1828 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1829 will be handled."
1830 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1831 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1832 ;; {...}").
1835 ;; Languages that have a "typedef" construct.
1838 ;; Unlike most other languages, exception names are not handled as
1839 ;; types in IDL since they only can occur in "raises" specs.
1847 "Keywords introducing declarations where the \(first) identifier
1848 \(declarator) follows directly after the keyword, without any type.
1850 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1851 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1852 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1853 will be handled."
1854 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1855 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1856 ;; {...}").
1859 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1860 ;; `c-type-list-kwds' for IDL.
1863 ;; In CORBA PSDL:
1865 ;; In CORBA CIDL:
1871 "Keywords that can prefix normal declarations of identifiers
1872 \(and typically act as flags). Things like argument declarations
1873 inside function headers are also considered declarations in this
1874 sense.
1876 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1877 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1878 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1879 will be handled."
1880 t nil
1885 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1889 ;; In CORBA PSDL:
1891 ;; In CORBA CIDL:
1893 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1900 "Keywords that can start or prefix any declaration level construct,
1901 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1902 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1903 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1905 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1906 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1907 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1908 will be handled."
1909 t nil
1915 "Keywords that always start declarations, wherever they occur.
1916 This can be used for declarations that aren't recognized by the normal
1917 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1918 t nil
1919 ;; Classes can be declared anywhere in a Pike expression.
1923 "Keywords that can occur anywhere in a declaration level construct.
1924 This is used for self-contained things that can be tacked on anywhere
1925 on a declaration and that should be ignored to be able to recognize it
1926 correctly. Typical cases are compiler extensions like
1929 __declspec(noreturn) void foo();
1930 class __declspec(dllexport) classname {...};
1931 void foo() __attribute__((noreturn));
1933 Note that unrecognized plain symbols are skipped anyway if they occur
1934 before the type, so such things are not necessary to mention here.
1935 Mentioning them here is necessary only if they can occur in other
1936 places, or if they are followed by a construct that must be skipped
1938 examples above). In the last case, they alse need to be present on
1939 one of `c-type-list-kwds', `c-ref-list-kwds',
1940 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1941 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1942 ;; NB: These are currently not recognized in all parts of a
1943 ;; declaration. Specifically, they aren't recognized in the middle
1944 ;; of multi-token types, inside declarators, and between the
1945 ;; identifier and the arglist paren of a function declaration.
1946 ;;
1947 ;; FIXME: This ought to be user customizable since compiler stuff
1948 ;; like this usually is wrapped in project specific macros. (It'd
1949 ;; of course be even better if we could cope without knowing this.)
1950 t nil
1952 "__attribute__"
1953 ;; MSVC extension.
1957 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1962 ;; All keywords that can occur in the preamble of a declaration.
1963 ;; They typically occur before the type, but they are also matched
1964 ;; after presumptive types since we often can't be sure that
1965 ;; something is a type or just some sort of macro in front of the
1966 ;; declaration. They might be ambiguous with types or type
1967 ;; prefixes.
1980 ;; Adorned regexp of `c-prefix-spec-kwds'.
1986 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1987 ;; ambiguous with types or type prefixes. These are the keywords (like
1988 ;; extern, namespace, but NOT template) that can modify a declaration.
1997 ;; Keywords that can occur after argument list of a function header
1998 ;; declaration, i.e. in the "K&R region".
2003 ;; Adorned regexp matching all keywords that can't appear at the
2004 ;; start of a declaration.
2018 ;; The "more" for C++ is the QT keyword (as in "more slots:").
2019 ;; This variable is intended for use in c-beginning-of-statement-1.
2029 "Access protection label keywords in classes."
2030 t nil
2035 "Keywords introducing declarations that can contain a block which
2038 like that, it ends with the following ';' and not right away.
2040 The keywords on list are assumed to also be present on one of the
2041 `*-decl-kwds' lists."
2042 t nil
2047 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2048 ;; languages without such constructs.
2055 "Keywords introducing extra declaration specifiers in the region
2057 declarations."
2058 t nil
2061 "supports"
2062 ;; In CORBA PSDL:
2066 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2072 "Keywords that may be followed by a nonsymbol sexp before whatever
2073 construct it's part of continues."
2074 t nil
2078 "Keywords that may be followed by a comma separated list of type
2079 identifiers, where each optionally can be prefixed by keywords. (Can
2080 also be used for the special case when the list can contain only one
2081 element.)
2083 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2084 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2085 There's also no reason to add keywords that prefixes a normal
2086 declaration consisting of a type followed by a declarator (list), so
2087 the keywords on `c-modifier-kwds' should normally not be listed here
2088 either.
2090 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2091 or variable identifier (that's being defined)."
2092 t nil
2097 ;; In CORBA PSDL:
2102 "Keywords that may be followed by a comma separated list of
2103 reference (i.e. namespace/scope/module) identifiers, where each
2104 optionally can be prefixed by keywords. (Can also be used for the
2105 special case when the list can contain only one element.) Assumed to
2106 be mutually exclusive with `c-type-list-kwds'.
2108 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2109 or variable identifier (that's being defined)."
2110 t nil
2114 ;; In CORBA CIDL:
2119 "Keywords that may be followed (not necessarily directly) by a colon
2120 and then a comma separated list of type identifiers, where each
2121 optionally can be prefixed by keywords. (Can also be used for the
2122 special case when the list can contain only one element.)"
2123 t nil
2126 ;; In CORBA PSDL:
2130 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2131 forward to the colon. The end of the match is assumed to be directly
2133 regexp if `c-colon-type-list-kwds' isn't nil."
2135 ;; Disallow various common punctuation chars that can't come
2136 ;; before the ":" that starts the inherit list after "class"
2137 ;; or "struct" in C++. (Also used as default for other
2138 ;; languages.)
2143 "Keywords that may be followed by a parenthesis expression that doesn't
2144 contain type identifiers."
2145 t nil
2147 "__attribute__"
2148 ;; MSVC extension.
2152 "Keywords that may be followed by a parenthesis expression containing
2153 type identifiers separated by arbitrary tokens."
2154 t nil
2166 "Keywords that may be followed by an angle bracket expression
2168 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2169 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2170 if this isn't nil."
2171 t nil
2174 ;; In CORBA PSDL:
2178 "Keywords that can be followed by a C++ style template arglist; see
2179 `c-recognize-<>-arglists' for details. That language constant is
2180 assumed to be set if this isn't nil."
2181 t nil
2186 ;; All keywords that can be followed by an angle bracket sexp.
2192 ;; Adorned regexp matching keywords that can be followed by an angle
2193 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2198 "Keywords that may be followed by a brace block containing a comma
2199 separated list of identifier definitions, i.e. like the list of
2200 identifiers that follows the type in a normal declaration."
2204 "Statement keywords followed directly by a substatement."
2209 idl nil)
2212 ;; Regexp matching the start of any statement followed directly by a
2213 ;; substatement (doesn't match a bare block, however).
2218 "Statement keywords optionally followed by a paren sexp.
2219 Keywords here should also be in `c-block-stmt-1-kwds'."
2220 t nil
2224 ;; Regexp matching the start of a statement which may be followed by a
2225 ;; paren sexp and will then be followed by a substatement.
2230 "Statement keywords followed by a paren sexp and then by a substatement."
2235 idl nil
2240 ;; Regexp matching the start of any statement followed by a paren sexp
2241 ;; and then by a substatement.
2246 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2252 ;; Regexp matching the start of any statement that has a
2253 ;; substatement (except a bare block). Nil in languages that
2254 ;; don't have such constructs.
2263 "Statement keywords followed by an expression or nothing."
2266 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2268 idl nil
2275 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2280 "Statement keywords followed by a parenthesis expression that
2281 nevertheless contains a list separated with ';' and not ','."
2283 idl nil)
2286 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2291 "Statement keywords followed by an assembler expression."
2292 t nil
2296 ;; Regexp matching the start of an assembler statement. Nil in
2297 ;; languages that don't support that.
2306 awk nil)
2309 ;; Adorned regexp matching any "case"-like keyword.
2314 "Keywords introducing colon terminated labels in blocks."
2318 ;; Adorned regexp matching any keyword that introduces a label.
2323 "Keywords that might be followed by a label identifier."
2327 idl nil
2328 awk nil)
2331 "Keywords for constants."
2332 t nil
2341 "Keywords besides constants and operators that start primary expressions."
2342 t nil
2349 ;; Keywords that can occur anywhere in expressions. Built from
2350 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2354 t
2359 "Keywords that start lambda constructs, i.e. function definitions in
2360 expressions."
2361 t nil
2365 "Keywords that start constructs followed by statement blocks which can
2366 be used in expressions \(the gcc extension for this in C and C++ is
2367 handled separately by `c-recognize-paren-inexpr-blocks')."
2368 t nil
2372 "Keywords that can start classes inside expressions."
2373 t nil
2378 "Keywords that can start brace list blocks inside expressions.
2379 Note that Java specific rules are currently applied to tell this from
2380 `c-inexpr-class-kwds'."
2381 t nil
2385 ;; Regexp matching the start of a brace list in an expression, or
2386 ;; nil in languages that don't have such things. This should not
2387 ;; match brace lists recognized through `c-special-brace-lists'.
2394 ;; Regexp matching keywords in any construct that contain another
2395 ;; declaration level, i.e. that isn't followed by a function block
2396 ;; or brace list. When the first submatch matches, it's an
2397 ;; unambiguous construct, otherwise it's an ambiguous match that
2398 ;; might also be the return type of a function declaration.
2416 "Keywords that can introduce bitfields."
2417 t nil
2421 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2422 ;; languages without bitfield support.
2423 t nil
2428 "Keywords not accounted for by any other `*-kwds' language constant."
2429 t nil
2431 ;; In CORBA CIDL: (These are declaration keywords that never
2432 ;; can start a declaration.)
2435 \f
2436 ;;; Constants built from keywords.
2438 ;; Note: No `*-kwds' language constants may be defined below this point.
2442 ;; List of all the language constants that contain keyword lists.
2447 ;; Make the list of globally interned symbols
2448 ;; instead of ones interned in `c-lang-constants'.
2450 c-lang-constants)
2451 list)))
2454 ;; All keywords as a list.
2459 c-kwds-lang-consts)
2460 nil))
2464 ;; All keywords as an adorned regexp.
2469 ;; An alist with all the keywords in the cars. The cdr for each
2470 ;; keyword is a list of the symbols for the `*-kwds' lists that
2471 ;; contains it.
2477 c-kwds-lang-consts))))
2478 lang-const kwd-list kwd
2479 result-alist elem)
2491 result-alist))
2494 ;; An obarray containing all keywords as symbols. The property list
2495 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2496 ;; lists it's a member of.
2497 ;;
2498 ;; E.g. to see whether the string str contains a keyword on
2499 ;; `c-class-decl-kwds', one can do like this:
2500 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2501 ;; Which preferably is written using the associated functions in
2502 ;; cc-engine:
2503 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2505 ;; The obarray is not stored directly as a language constant since
2506 ;; the printed representation for obarrays used in .elc files isn't
2507 ;; complete.
2510 kwd lang-const-list
2517 ;; Emacs has an odd bug that causes `mapcan' to fail
2518 ;; with unintelligible errors. (XEmacs works.)
2519 ;;(mapcan (lambda (lang-const)
2520 ;; (list lang-const t))
2521 ;; lang-const-list)
2524 lang-const-list))))
2525 obarray))
2528 ;; Adorned regexp matching all keywords that should be fontified
2529 ;; with the keywords face. I.e. that aren't types or constants.
2539 ;; Regexp matching the start of any primary expression, i.e. any
2540 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2541 ;; exclude keywords; they are excluded afterwards unless the second
2542 ;; submatch matches. If the first but not the second submatch
2543 ;; matches then it is an ambiguous primary expression; it could also
2544 ;; be a match of e.g. an infix operator. (The case with ambiguous
2545 ;; keyword operators isn't handled.)
2551 ;; Filter out the special case prefix
2552 ;; operators that are close parens.
2557 t
2563 postfix-if-paren
2564 left-assoc
2565 right-assoc
2566 right-assoc-sequence)
2567 t))
2570 in-or-postfix-ops
2573 in-or-postfix-ops
2578 ;; Take out all symbol class operators from `prefix-ops' and make the
2579 ;; first submatch from them together with `c-primary-expr-kwds'.
2586 ;; Match all ambiguous operators.
2593 ;; Now match all other symbols.
2597 ;; The chars that can start integer and floating point
2598 ;; constants.
2602 ;; The unambiguous operators from `prefix-ops'.
2608 ;; Match string and character literals.
2615 \f
2616 ;;; Additional constants for parser-level constructs.
2619 "Regexp matching a keyword that is followed by a colon, where
2620 the whole construct can precede a declaration.
2628 "Regexp matching something that might precede a declaration, cast or
2629 label, such as the last token of a preceding statement or declaration.
2630 This is used in the common situation where a declaration or cast
2631 doesn't start with any specific token that can be searched for.
2633 The regexp should not match bob; that is done implicitly. It can't
2634 require a match longer than one token. The end of the token is taken
2635 to be at the end of the first submatch, which is assumed to always
2636 match. It's undefined whether identifier syntax (see
2637 `c-identifier-syntax-table') is in effect or not. This regexp is
2638 assumed to be a superset of `c-label-prefix-re' if
2639 `c-recognize-colon-labels' is set.
2641 Besides this, `c-decl-start-kwds' is used to find declarations.
2643 Note: This variable together with `c-decl-start-re' and
2645 declaration/cast/label starts. I.e. they might produce more matches
2646 but should not miss anything (or else it's necessary to use text
2647 properties - see the next note). Wherever they match, the following
2648 construct is analyzed to see if it indeed is a declaration, cast or
2649 label. That analysis is not cheap, so it's important that not too
2650 many false matches are triggered.
2652 Note: If a declaration/cast/label start can't be detected with this
2653 variable, it's necessary to use the `c-type' text property with the
2654 value `c-decl-end' on the last char of the last token preceding the
2655 declaration. See the comment blurb at the start of cc-engine.el for
2656 more info."
2658 ;; We match a sequence of characters to skip over things like \"};\"
2659 ;; more quickly. We match ")" in C for K&R region declarations, and
2660 ;; in all languages except Java for when a cpp macro definition
2661 ;; begins with a declaration.
2664 ;; Match "<" in C++ to get the first argument in a template arglist.
2665 ;; In that case there's an additional check in `c-find-decl-spots'
2666 ;; that it got open paren syntax. Match ":" to aid in picking up
2667 ;; "public:", etc. This involves additional checks in
2668 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2669 ;; or labels.
2671 ;; Additionally match the protection directives in Objective-C.
2672 ;; Note that this doesn't cope with the longer directives, which we
2673 ;; would have to match from start to end since they don't end with
2674 ;; any easily recognized characters.
2678 ;; Pike is like C but we also match "[" for multiple value
2679 ;; assignments and type casts.
2685 "Regexp matching the start of any declaration, cast or label.
2686 It's used on the token after the one `c-decl-prefix-re' matched. This
2687 regexp should not try to match those constructs accurately as it's
2688 only used as a sieve to avoid spending more time checking other
2689 constructs."
2694 ;; Regexp matching something that might precede or start a
2695 ;; declaration, cast or label.
2696 ;;
2697 ;; If the first submatch matches, it's taken to match the end of a
2698 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2699 ;; It's built from `c-decl-prefix-re'.
2700 ;;
2701 ;; If the first submatch did not match, the match of the whole
2702 ;; regexp is taken to be at the first token in the declaration.
2703 ;; `c-decl-start-re' is not checked in this case.
2704 ;;
2705 ;; Design note: The reason the same regexp is used to match both
2706 ;; tokens that precede declarations and start them is to avoid an
2707 ;; extra regexp search from the previous declaration spot in
2708 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2709 ;; that it finds all declaration/cast/label starts in approximately
2710 ;; linear order, so we can't do the searches in two separate passes.
2721 ;; List containing the paren characters that can open a cast, or nil in
2722 ;; languages without casts.
2730 "List of syntactically relevant characters that never can occur before
2731 the open brace in any construct that contains a brace block, e.g. in
2734 class Foo: public Bar {int x();} a, *b;
2736 If parens can occur, the chars inside those aren't filtered with this
2737 list.
2739 '<' and '>' should be disallowed even if angle bracket arglists can
2740 occur. That since the search function needs to stop at them anyway to
2741 ensure they are given paren syntax.
2743 This is used to skip backward from the open brace to find the region
2746 possible for good performance."
2748 ;; Default to all chars that only occurs in nonsymbol tokens outside
2749 ;; identifiers.
2755 t
2756 t
2760 op pos)
2763 res))))
2765 ;; Allow cpp operations (where applicable).
2771 ;; Allow ':' for inherit list starters.
2775 ;; Allow ',' for multiple inherits.
2779 ;; Allow parentheses for anonymous inner classes in Java and class
2780 ;; initializer lists in Pike.
2784 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2789 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2790 ;; for `c-syntactic-skip-backward'.
2795 "Regexp matching the declarator operators that might precede the
2798 The end of the first submatch is taken as the end of the operator.
2799 Identifier syntax is in effect when this is matched \(see
2800 `c-identifier-syntax-table')."
2803 ;; Default to a regexp that never matches.
2805 ;; Check that there's no "=" afterwards to avoid matching tokens
2806 ;; like "*=".
2808 "[*\(]"
2814 "[*\(&]"
2819 ;; If this matches there's special treatment in
2820 ;; `c-font-lock-declarators' and
2821 ;; `c-font-lock-declarations' that check for a
2822 ;; complete name followed by ":: *".
2832 "Regexp matching the declarator operators that might follow after the
2835 it matches an open paren of some kind, the type declaration check
2836 continues at the corresponding close paren, otherwise the end of the
2837 first submatch is taken as the end of the operator. Identifier syntax
2838 is in effect when this is matched (see `c-identifier-syntax-table')."
2839 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2840 ;; function argument list parenthesis.
2848 "[\)\[\(]"
2852 ;; "throw" in `c-type-modifier-kwds' is followed
2853 ;; by a parenthesis list, but no extra measures
2854 ;; are necessary to handle that.
2865 "This regexp is matched after a declarator expression where
2866 `c-type-decl-suffix-key' has matched. If it matches then the
2867 construct is taken as a declaration. It's typically used to match the
2868 beginning of a function body or whatever might occur after the
2869 function header in a function declaration or definition. It's
2870 undefined whether identifier syntax (see `c-identifier-syntax-table')
2871 is in effect or not.
2876 t "{"
2877 ;; If K&R style declarations should be recognized then one could
2878 ;; consider to match the start of any symbol since we want to match
2879 ;; the start of the first declaration in the "K&R region". That
2880 ;; could however produce false matches on code like "FOO(bar) x"
2881 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2882 ;; on the other heuristics in that case.
2884 ;; Add on the keywords in `c-postfix-spec-kwds'.
2889 ;; Also match the colon that starts a base class initializer list in
2890 ;; C++. That can be confused with a function call before the colon
2891 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2892 ;; match before such a thing (as a declaration-level construct;
2893 ;; matches inside arglist contexts are already excluded).
2900 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2901 ;; matches ";" and ",".
2910 end of the operator. nil in languages without such operators. It's
2911 undefined whether identifier syntax (see `c-identifier-syntax-table')
2912 is in effect or not."
2913 t nil
2919 "Regexp matching operators that might follow after a type, or nil in
2920 languages that don't have such operators. The end of the first
2921 submatch is taken as the end of the operator. This should not match
2922 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2923 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2924 is in effect or not."
2925 t nil
2931 ;; Regexp matching the known type identifiers. This is initialized
2932 ;; from the type keywords and `*-font-lock-extra-types'. The first
2933 ;; submatch is the one that matches the type. Note that this regexp
2934 ;; assumes that symbol constituents like '_' and '$' have word
2935 ;; syntax.
2944 extra-types)))
2950 extra-types))))
2955 plain-strings)))
2956 regexp-strings)
2961 "List of open- and close-chars that makes up a pike-style brace list,
2963 list."
2964 t nil
2969 "Non-nil means K&R style argument declarations are valid."
2970 t nil
2971 c t)
2975 "Non-nil means function declarations without return type should be
2976 recognized. That can introduce an ambiguity with parenthesized macro
2977 calls before a brace block. This setting does not affect declarations
2978 that are preceded by a declaration starting keyword, so
2979 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2980 t nil
2986 "Non-nil means C++ style template arglists should be handled. More
2987 specifically, this means a comma separated list of types or
2989 identifier or one of the keywords on `c-<>-type-kwds' or
2990 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2991 expression is considered to be a type."
2994 java t)
2998 "Non-nil means that an enum structure can contain declarations."
2999 t nil
3000 java t)
3004 "Non-nil means that parenthesis style initializers exist,
3005 i.e. constructs like
3007 Foo bar (gnu);
3009 in addition to the more classic
3011 Foo bar = gnu;"
3012 t nil
3017 "Non-nil to recognize gcc style in-expression blocks,
3018 i.e. compound statements surrounded by parentheses inside expressions."
3019 t nil
3025 ;; Regexp matching the start of angle bracket arglists in languages
3026 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3027 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3028 ;; assumed to surround the preceding symbol. The whole match is
3029 ;; assumed to end directly after the opening "<".
3039 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3040 ;; parens. The first submatch is assumed to surround
3041 ;; `c-opt-<>-arglist-start'.
3050 ;; Regexp matching the beginning of a declaration specifier in the
3051 ;; region between the header and the body of a declaration.
3052 ;;
3053 ;; TODO: This is currently not used uniformly; c++-mode and
3054 ;; java-mode each have their own ways of using it.
3055 t nil
3068 That includes labels in code and access keys in classes. This does
3069 not apply to labels recognized by `c-label-kwds' and
3070 `c-opt-extra-label-key'."
3071 t nil
3077 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3078 a generic colon label. Not used if `c-recognize-colon-labels' is
3079 nil."
3085 "Regexp matching things that can't occur in generic colon labels,
3086 neither in a statement nor in a declaration context. The regexp is
3087 tested at the beginning of every sexp in a suspected label,
3090 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3096 ;; Don't allow string literals, except in AWK. Character constants are OK.
3099 ;; Also check for open parens in C++, to catch member init lists in
3100 ;; constructors. We normally allow it so that macros with arguments
3101 ;; work in labels.
3106 "Regexp matching things that can't occur two symbols before a colon in
3114 "Optional regexp matching labels.
3115 Normally, labels are detected according to `c-nonlabel-token-key',
3116 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3117 be used if there are additional labels that aren't recognized that
3118 way."
3119 t nil
3124 ;; Regexp describing friend declarations classes, or nil in
3125 ;; languages that don't have such things.
3126 ;;
3127 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3128 ;; template skipping isn't done properly. This will disappear soon.
3129 t nil
3134 "<.+>"
3136 "friend"
3141 ;; Special regexp to match the start of Objective-C methods. The
3142 ;; first submatch is assumed to end after the + or - key.
3143 t nil
3145 ;; TODO: Ought to use a better method than anchoring on bol.
3150 "([^\)]*)"
3157 ;; Must be set in buffers where the `c-type' text property might be
3158 ;; used with the value `c-decl-end'.
3159 ;;
3160 ;; `c-decl-end' is used to mark the ends of labels and access keys
3161 ;; to make interactive refontification work better.
3164 ;; `c-decl-end' is used to mark the end of the @-style directives in
3165 ;; Objective-C.
3166 objc t)
3169 \f
3170 ;;; Wrap up the `c-lang-defvar' system.
3172 ;; Compile in the list of language variables that has been collected
3173 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3174 ;; first element of each is nil.
3178 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3179 ;; These are typically standard emacs variables such as `comment-start'.
3187 "Create a function that initializes all the language dependent variables
3188 for the given mode.
3190 This function should be evaluated at compile time, so that the
3191 function it returns is byte compiled with all the evaluated results
3192 from the language constants. Use the `c-init-language-vars' macro to
3193 accomplish that conveniently."
3199 ;; No need to byte compile this lambda since the byte compiler is
3200 ;; smart enough to detect the `funcall' construct in the
3201 ;; `c-init-language-vars' macro below and compile it all straight
3202 ;; into the function that contains `c-init-language-vars'.
3205 ;; This let sets up the context for `c-mode-var' and similar
3206 ;; that could be in the result from `macroexpand-all'.
3208 current-var source-eval)
3215 ;; `c-lang-const' will expand to the evaluated
3216 ;; constant immediately in `macroexpand-all'
3217 ;; below.
3223 ;; Note: The following `append' copies the
3224 ;; first argument. That list is small, so
3225 ;; this doesn't matter too much.
3229 ;; This diagnostic message isn't useful for end
3230 ;; users, so it's disabled.
3231 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3232 ;; (message ,(concat "%s compiled with CC Mode %s "
3233 ;; "but loaded with %s - evaluating "
3234 ;; "language constants from source")
3235 ;; ',mode ,c-version c-version)
3236 ;; (put ',mode 'c-has-warned-lang-consts t))
3249 current-var
3252 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3255 err)
3258 ;; Being evaluated from source. Always use the dynamic method to
3259 ;; work well when `c-lang-defvar's in this file are reevaluated
3260 ;; interactively.
3266 current-var)
3278 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3279 current-var err)
3281 ))
3284 "Initialize all the language dependent variables for the given mode.
3285 This macro is expanded at compile time to a form tailored for the mode
3286 in question, so MODE must be a constant. Therefore MODE is not
3287 evaluated and should not be quoted."
3290 \f
3293 ;;; cc-langs.el ends here