| blob | 493f3db0961aeb18d3aaa3b273282a71f2639d6d |
1 ;;; cc-langs.el --- language specific settings for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2012 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.
216 ;; Some helper functions used when building the language constants.
219 ;; Extract a subset of the operators in the list OPS in a DWIM:ey
220 ;; way. The return value is a plain list of operators:
221 ;;
222 ;; OPS either has the structure of `c-operators', is a single
223 ;; group in `c-operators', or is a plain list of operators.
224 ;;
225 ;; OPGROUP-FILTER specifies how to select the operator groups. It
226 ;; can be t to choose all groups, a list of group type symbols
227 ;; (such as 'prefix) to accept, or a function which will be called
228 ;; with the group symbol for each group and should return non-nil
229 ;; if that group is to be included.
230 ;;
231 ;; If XLATE is given, it's a function which is called for each
232 ;; matching operator and its return value is collected instead.
233 ;; If it returns a list, the elements are spliced directly into
234 ;; the final result, which is returned as a list with duplicates
235 ;; removed using `equal'.
236 ;;
237 ;; `c-mode-syntax-table' for the current mode is in effect during
238 ;; the whole procedure.
259 t)
260 t)
265 opgroup)))
266 ops)
269 \f
270 ;;; Various mode specific values that aren't language related.
273 ;; The definition for the mode menu. The menu title is prepended to
274 ;; this before it's fed to `easy-menu-define'.
284 "----"
288 ;; Only applicable if there's a cpp preprocessor.
292 "----"
297 "----"
301 "Style Name: %s"
306 c-guess-guessed-basic-offset) ]
309 c-guess-guessed-basic-offset) ])
310 "----"
322 subword-mode)])))
324 \f
325 ;;; Syntax tables.
328 "Populate the given syntax table as necessary for a C-like language.
346 ;; Set up block and line oriented comments. The new C
347 ;; standard mandates both comment styles even in C, so since
348 ;; all languages now require dual comments, we make this the
349 ;; default.
351 ;; XEmacs
355 ;; Emacs
359 ;; incompatible
363 ;; Give CR the same syntax as newline, for selective-display
367 "Functions that generates the mode specific syntax tables.
368 The syntax tables aren't stored directly since they're quite large."
372 ;; Mode specific syntaxes.
374 ;; Let '@' be part of symbols in ObjC to cope with
375 ;; its compiler directives as single keyword tokens.
376 ;; This is then necessary since it's assumed that
377 ;; every keyword is a single symbol.
381 table)))
384 ;; The syntax tables in evaluated form. Only used temporarily when
385 ;; the constants in this file are evaluated.
389 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
390 ;; parenthesis characters. Used temporarily when template argument
391 ;; lists are parsed. Note that this encourages incorrect parsing of
392 ;; templates since they might contain normal operators that uses the
393 ;; '<' and '>' characters. Therefore this syntax table might go
394 ;; away when CC Mode handles templates correctly everywhere.
395 t nil
400 table)))
406 ;; A variant of the standard syntax table which is used to find matching
407 ;; "<"s and ">"s which have been marked as parens using syntax table
408 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
409 ;; non-paren syntax here. so that the list commands will work on "< ... >"
410 ;; even when there's unbalanced other parens inside them.
411 ;;
412 ;; This variable is nil for languages which don't have template stuff.
422 table))))
427 "A list that describes the modifications that should be done to the
428 mode syntax table to get a syntax table that matches all identifiers
429 and keywords as words.
431 The list is just like the one used in `font-lock-defaults': Each
432 element is a cons where the car is the character to modify and the cdr
433 the new syntax, as accepted by `modify-syntax-entry'."
434 ;; The $ character is not allowed in most languages (one exception
435 ;; is Java which allows it for legacy reasons) but we still classify
436 ;; it as an identifier character since it's often used in various
437 ;; machine generated identifiers.
448 mod)
453 table)
454 "Syntax table built on the mode syntax table but additionally
455 classifies symbol constituents like '_' and '$' as word constituents,
459 ;; For documentation see the following c-lang-defvar of the same name.
460 ;; The value here may be a list of functions or a single function.
461 t nil
463 c-before-change-check-<>-operators
464 c-invalidate-macro-cache)
466 ;; java 'c-before-change-check-<>-operators
471 fs
473 "If non-nil, a list of functions called from c-before-change-hook.
474 Typically these will record enough state to allow
475 `c-before-font-lock-function' to extend the region to fontify,
476 and may do such things as removing text-properties which must be
477 recalculated.
479 These functions will be run in the order given. Each of them
480 takes 2 parameters, the BEG and END supplied to every
481 before-change function; on entry, the buffer will have been
482 widened and match-data will have been saved; point is undefined
483 on both entry and exit; the return value is ignored.
485 The functions are called even when font locking isn't enabled.
487 When the mode is initialized, the functions are called with
491 ;; For documentation see the following c-lang-defvar of the same name.
492 ;; The value here may be a list of functions or a single function.
493 t 'c-change-set-fl-decl-start
495 c-change-set-fl-decl-start)
500 fs
502 "If non-nil, a list of functions called just before font locking.
503 Typically they will extend the region about to be fontified \(see
504 below) and will set `syntax-table' text properties on the region.
506 These functions will be run in the order given. Each of them
507 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
508 after-change function; point is undefined on both entry and exit;
509 on entry, the buffer will have been widened and match-data will
510 have been saved; the return value is ignored.
512 The functions may extend the region to be fontified by setting the
513 buffer local variables c-new-BEG and c-new-END.
515 The functions are called even when font locking is disabled.
517 When the mode is initialized, these functions are called with
521 awk nil
523 ;; For documentation see the following c-lang-defvar of the same name.
524 ;; The value here may be a list of functions or a single function.
528 fs
530 "If non-nil, a list of functions called just before context (or
531 other non-change) fontification is done. Typically they will
532 extend the region.
534 These functions will be run in the order given. Each of them
535 takes 2 parameters, the BEG and END of the region to be
536 fontified. Point is undefined on both entry and exit. On entry,
537 the buffer will have been widened and match-data will have been
538 saved; the return value is a cons of the adjusted
541 \f
542 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
545 Such a function takes one optional parameter, a buffer position (defaults to
546 point), and returns nil or t. This variable contains nil for languages which
547 don't have EOL terminated statements. "
548 t nil
555 The (admittedly kludgy) purpose of such a function is to prevent an infinite
556 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
557 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
558 even indirectly. This variable contains nil for languages which don't have
559 EOL terminated statements."
560 t nil
566 \f
567 ;;; Lexer-level syntax (identifiers, tokens etc).
570 "Whether the language has bitfield declarations."
571 t nil
576 "Regexp that matches the start of a symbol, i.e. any identifier or
578 operator at the top level."
586 "Set of characters that can be part of a symbol.
587 This is of the form that fits inside [ ] in a regexp."
588 ;; Pike note: With the backquote identifiers this would include most
589 ;; operator chars too, but they are handled with other means instead.
595 "Regexp matching identifiers and keywords (with submatch 0). Assumed
596 to match if `c-symbol-start' matches on the same position."
600 ;; Use the value from C here since the operator backquote is
601 ;; covered by the other alternative.
609 ;; Number of regexp grouping parens in `c-symbol-key'.
613 "This is the set of chars that can't be part of a symbol, i.e. the
614 negation of `c-symbol-chars'."
619 "Regexp that matches any character that can't be part of a symbol.
620 It's usually appended to other regexps to avoid matching a prefix.
621 It's assumed to not contain any submatchers."
622 ;; The same thing regarding Unicode identifiers applies here as to
623 ;; `c-symbol-key'.
627 "The operators that make up fully qualified identifiers. nil in
628 languages that don't have such things. See `c-operators' for a
629 description of the format. Binary operators can concatenate symbols,
633 This value is by default merged into `c-operators'."
634 t nil
638 ;; Java has "." to concatenate identifiers but it's also used for
639 ;; normal indexing. There's special code in the Java font lock
640 ;; rules to fontify qualified identifiers based on the standard
641 ;; naming conventions. We still define "." here to make
642 ;; `c-forward-name' move over as long names as possible which is
643 ;; necessary to e.g. handle throws clauses correctly.
652 ;; Appendable adorned regexp matching the operators that join
653 ;; symbols to fully qualified identifiers, or nil in languages that
654 ;; don't have such things.
655 ;;
656 ;; This was a docstring constant in 5.30. It still works but is now
657 ;; considered internal - change `c-identifier-ops' instead.
660 t)))
668 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
672 ;; Appendable adorned regexp matching operators that might precede
673 ;; an identifier and that are part of the identifier in that case.
674 ;; nil in languages without such things.
677 t)))
682 "Operators that can occur after a binary operator on `c-identifier-ops'
683 in identifiers. nil in languages that don't have such things.
685 Operators here should also have appropriate entries in `c-operators' -
686 it's not taken care of by default."
687 t nil
688 ;; '~' for destructors in C++, '*' for member pointers.
690 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
691 ;; in import declarations. (This will also match bogus things like
692 ;; "foo.*bar" but we don't bother.)
696 ;; Regexp that must match the token after
697 ;; `c-opt-identifier-concat-key' for it to be considered an
698 ;; identifier concatenation operator (which e.g. causes the
699 ;; preceding identifier to be fontified as a reference). Assumed to
700 ;; be a string if `c-opt-identifier-concat-key' is.
701 ;;
702 ;; This was a docstring constant in 5.30. It still works but is now
703 ;; considered internal - change `c-after-id-concat-ops' instead.
711 "Regexp that matches the start of an (optionally qualified) identifier.
712 It should also match all keywords. It's unspecified how far it
713 matches."
723 C++. It does not recognize the full range of syntactic whitespace
724 between the tokens; `c-forward-name' has to be used for that. It
725 should also not match identifiers containing parenthesis groupings,
727 ;; This regexp is more complex than strictly necessary to ensure
728 ;; that it can be matched with a minimum of backtracking.
749 ;; For flexibility, consider the symbol match
750 ;; optional if we've hit a
751 ;; `c-after-id-concat-ops' operator. This is
752 ;; also necessary to handle the "*" that can
753 ;; end import declaration identifiers in Java.
767 ;; This was a docstring constant in 5.30 but it's no longer used.
768 ;; It's only kept to avoid breaking third party code.
769 ;;
770 ;; Used to identify the submatch in `c-identifier-key' that
771 ;; surrounds the last symbol in the qualified identifier. It's a
772 ;; list of submatch numbers, of which the first that has a match is
773 ;; taken. It's assumed that at least one does when the regexp has
774 ;; matched.
775 t nil)
778 "Set if the language support backslash escaped newlines inside string
779 literals."
780 t nil
786 "Set if the language supports multiline string literals without escaped
787 newlines. If t, all string literals are multiline. If a character,
788 only literals where the open quote is immediately preceded by that
789 literal are multiline."
790 t nil
791 pike ?#)
796 "The symbol which starts preprocessor constructs when in the margin."
797 t "#"
802 "Regexp matching the prefix of a cpp directive in the languages that
803 normally use that macro preprocessor. Tested at bol or at boi.
805 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
806 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
812 "Regexp matching the prefix of a cpp directive anchored to BOL,
813 in the languages that have a macro preprocessor."
819 "Regexp matching the prefix of a cpp directive including the directive
820 name, or nil in languages without preprocessor support. The first
821 submatch surrounds the directive name."
825 ;; Pike, being a scripting language, recognizes hash-bangs too.
831 "List of cpp directives (without the prefix) that are followed by a
832 string message."
838 "List of cpp directives (without the prefix) that are followed by a
839 file name in angle brackets or quotes."
845 "Cpp directive (without the prefix) that is followed by a macro
846 definition, or nil if the language doesn't have any."
853 ;; Regexp matching everything up to the macro body of a cpp define, or the
854 ;; end of the logical line if there is none. Submatch 1 is the name of the
855 ;; macro. Set if c-opt-cpp-macro-define is.
860 ;; ^ ^ #defined name
866 ;; Regexp matching everything up to the end of the identifier defined
867 ;; by a cpp define.
876 "List of cpp directives (without the prefix) that are followed by an
877 expression."
882 "Regexp which matches the start of a CPP directive which contains an
883 expression, or nil if there aren't any in the language."
892 "List of functions in cpp expressions."
898 "List of all assignment operators."
904 idl nil)
907 "List describing all operators, along with their precedence and
908 associativity. The order in the list corresponds to the precedence of
909 the operators: The operators in each element are a group with the same
910 precedence, and the group has higher precedence than the groups in all
911 following elements. The car of each element describes the type of the
912 operator group, and the cdr is a list of the operator tokens in it.
913 The operator group types are:
915 'prefix Unary prefix operators.
916 'postfix Unary postfix operators.
917 'postfix-if-paren
918 Unary postfix operators if and only if the chars have
919 parenthesis syntax.
920 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
921 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
922 'right-assoc-sequence
923 Right associative operator that constitutes of a
924 sequence of tokens that separate expressions. All the
925 tokens in the group are in this case taken as
926 describing the sequence in one such operator, and the
927 order between them is therefore significant.
929 Operators containing a character with paren syntax are taken to match
930 with a corresponding open/close paren somewhere else. A postfix
931 operator with close paren syntax is taken to end a postfix expression
932 started somewhere earlier, rather than start a new one at point. Vice
933 versa for prefix operators with open paren syntax.
936 often are described as postfix operators are considered binary here,
937 since CC Mode treats every identifier as an expression."
939 ;; There's currently no code in CC Mode that exploit all the info
940 ;; in this variable; precedence, associativity etc are present as a
941 ;; preparation for future work.
952 ;; Primary.
961 ;; Postfix.
963 ;; The following need special treatment.
973 ;; Unary.
980 ;; The following need special treatment.
991 ;; Member selection.
995 ;; Multiplicative.
998 ;; Additive.
1001 ;; Shift.
1006 ;; Relational.
1011 ;; Equality.
1015 ;; Bitwise and.
1019 ;; Bitwise exclusive or.
1025 ;; Bitwise or.
1031 ;; Logical and.
1035 ;; Logical or.
1041 ;; Conditional.
1044 ;; Assignment.
1047 ;; Exception.
1051 ;; Sequence.
1054 ;; IDL got its own definition since it has a much smaller operator
1055 ;; set than the other languages.
1059 ;; Primary.
1061 ;; Unary.
1063 ;; Multiplicative.
1065 ;; Additive.
1067 ;; Shift.
1069 ;; And.
1071 ;; Xor.
1073 ;; Or.
1077 ;; The operators as a flat list (without duplicates).
1083 t nil
1092 ;; These work like identifiers in Pike.
1099 ;; Regexp tested after an "operator" token in C++.
1100 t nil
1106 "Regexp matching the token before the ones in
1107 `c-overloadable-operators' when operators are specified in their
1110 languages without operator functions or where the complete operator
1111 identifier is listed in `c-overloadable-operators'.
1113 This regexp is assumed to not match any non-operator identifier."
1114 t nil
1119 ;; Note: the following alias is an old name which was a mis-spelling. It has
1120 ;; been corrected above and throughout cc-engine.el. It will be removed at
1121 ;; some release very shortly in the future. ACM, 2006-04-14.
1127 "List of the tokens made up of characters in the punctuation or
1128 parenthesis syntax classes that have uses other than as expression
1129 operators."
1147 ;; List of all tokens in the punctuation and parenthesis syntax
1148 ;; classes.
1154 ;; List containing all chars not in the word, symbol or
1155 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1156 ;; parenthesis and string delimiter chars.
1158 ;; Only go through the chars in the printable ASCII range. No
1159 ;; language so far has 8-bit or widestring operators.
1165 list)))
1168 ;; Regexp matching all tokens in the punctuation and parenthesis
1169 ;; syntax classes. Note that this also matches ".", which can start
1170 ;; a float.
1173 t
1179 ;; Regexp matching all assignment operators and only them. The
1180 ;; beginning of the first submatch is used to detect the end of the
1181 ;; token, along with the end of the whole match.
1184 ;; Need special case for "=" since it's a prefix of "==".
1196 ;; Regexp matching all tokens containing "<" or ">" which are longer
1197 ;; than one char.
1200 t
1206 ;; Regexp matching the second and subsequent characters of all
1207 ;; multicharacter tokens that begin with "<".
1210 t
1217 ;; Regexp matching the second and subsequent characters of all
1218 ;; multicharacter tokens that begin with ">".
1221 t
1226 t
1233 ;; The characters that should be considered to bound statements. To
1234 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1235 ;; begin with "^" to negate the set. If ? : operators should be
1236 ;; detected then the string must end with "?:".
1241 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1246 \f
1247 ;;; Syntactic whitespace.
1250 "Regexp matching an ordinary whitespace character.
1252 ;; "\\s " is not enough since it doesn't match line breaks.
1256 ;; Number of regexp grouping parens in `c-simple-ws'.
1260 "String that starts line comments, or nil if such don't exist.
1261 Line comments are always terminated by newlines. At least one of
1262 `c-block-comment-starter' and this one is assumed to be set.
1264 Note that it's currently not enough to set this to support a new
1265 comment style. Other stuff like the syntax table must also be set up
1266 properly."
1267 t "//"
1272 "String that starts block comments, or nil if such don't exist.
1273 Block comments are ended by `c-block-comment-ender', which is assumed
1274 to be set if this is. At least one of `c-line-comment-starter' and
1275 this one is assumed to be set.
1277 Note that it's currently not enough to set this to support a new
1278 comment style. Other stuff like the syntax table must also be set up
1279 properly."
1280 t "/*"
1281 awk nil)
1284 "String that ends block comments, or nil if such don't exist.
1286 Note that it's currently not enough to set this to support a new
1287 comment style. Other stuff like the syntax table must also be set up
1288 properly."
1289 t "*/"
1290 awk nil)
1293 ;; Regexp to match the start of any type of comment.
1299 re)))
1303 ;; Regexp which matches the start of a block comment (if such exists in the
1304 ;; language)
1312 ;; Regexp which matches the start of a line comment (if such exists in the
1313 ;; language; it does in all 7 CC Mode languages).
1321 ;; Regexp to match the start of comments and string literals.
1330 "Regexp to match the start of documentation comments."
1332 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1340 "String that starts comments inserted with M-; etc.
1341 `comment-start' is initialized from this."
1342 ;; Default: Prefer line comments to block comments, and pad with a space.
1346 ;; In C we still default to the block comment style since line
1347 ;; comments aren't entirely portable.
1352 "String that ends comments inserted with M-; etc.
1353 `comment-end' is initialized from this."
1354 ;; Default: Use block comment style if comment-start uses block
1355 ;; comments, and pad with a space in that case.
1365 "Regexp to match the start of a comment plus everything up to its body.
1366 `comment-start-skip' is initialized from this."
1367 ;; Default: Allow the last char of the comment starter(s) to be
1368 ;; repeated, then allow any amount of horizontal whitespace.
1381 ;; Regexp matching any sequence that can start syntactic whitespace.
1382 ;; The only uncertain case is '#' when there are cpp directives.
1396 ;; Regexp matching any single character that might end syntactic whitespace.
1411 ;; Regexp matching an unterminated block comment that doesn't
1412 ;; contain line breaks, or nil in languages without block comments.
1413 ;; Does not contain a \| operator at the top level.
1417 ;; It's messy to cook together a regexp that matches anything
1418 ;; but c-block-comment-ender.
1426 "[^"
1427 ;; The quoting rules inside char classes are silly. :P
1436 "]"
1444 ;; Regexp matching a block comment that doesn't contain line breaks,
1445 ;; or nil in languages without block comments. The reason we don't
1446 ;; allow line breaks is to avoid going very far and risk running out
1447 ;; of regexp stack; this regexp is intended to handle only short
1448 ;; comments that might be put in the middle of limited constructs
1449 ;; like declarations. Does not contain a \| operator at the top
1450 ;; level.
1465 ;; Regexp matching a piece of syntactic whitespace that isn't a
1466 ;; sequence of simple whitespace characters. As opposed to
1467 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1468 ;; directives as syntactic whitespace.
1480 ;; Regexp matching syntactic whitespace, including possibly the
1481 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1482 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1483 ;; not contain a \| operator at the top level.
1491 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1495 ;; Regexp matching syntactic whitespace, which is at least one
1496 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1497 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1498 ;; not contain a \| operator at the top level.
1506 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1510 ;; Regexp matching syntactic whitespace without any line breaks. As
1511 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1512 ;; regard cpp directives as syntactic whitespace. Does not contain
1513 ;; a \| operator at the top level.
1521 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1525 ;; Regexp that matches when there is no syntactically significant
1526 ;; text before eol. Macros are regarded as syntactically
1527 ;; significant text here.
1529 ;; Match eol (possibly inside a block comment or preceded
1530 ;; by a line continuation backslash), or the beginning of a
1531 ;; line comment. Note: This has to be modified for awk
1532 ;; where line comments start with '#'.
1546 \f
1547 ;;; Defun functions
1549 ;; The Emacs variables beginning-of-defun-function and
1550 ;; end-of-defun-function will be set so that commands like
1551 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1552 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1553 ;; functions, allowing optimization for large n.
1555 "Function to which beginning-of-defun-function will be set."
1556 t 'c-beginning-of-defun
1562 "Function to which end-of-defun-function will be set."
1563 t 'c-end-of-defun
1566 \f
1567 ;;; In-comment text handling.
1570 "Regexp to append to `paragraph-start'."
1571 t "$"
1577 "Regexp to append to `paragraph-separate'."
1578 t "$"
1582 \f
1583 ;;; Keyword lists.
1585 ;; Note: All and only all language constants containing keyword lists
1586 ;; should end with "-kwds"; they're automatically collected into the
1587 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1590 "Primitive type keywords. As opposed to the other keyword lists, the
1591 keywords listed here are fontified with the type face instead of the
1592 keyword face.
1594 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1595 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1596 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1597 will be handled.
1599 Do not try to modify this list for end user customizations; the
1600 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1601 the appropriate place for that."
1610 ;; Objective-C extends C, but probably not the new stuff in C99.
1617 ;; In CORBA PSDL:
1618 "ref"
1619 ;; The following can't really end a type, but we have to specify them
1620 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1621 ;; doesn't matter that much.
1624 ;; used as a builtin type.
1629 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1634 "Keywords that might act as prefixes for primitive types. Assumed to
1635 be a subset of `c-primitive-type-kwds'."
1636 t nil
1639 ;; In CORBA PSDL:
1644 of a variable declaration."
1649 ;; Adorned regexp matching `c-typedef-kwds'.
1654 "Keywords where the following name - if any - is a type name, and
1655 where the keyword together with the symbol works as a type in
1656 declarations.
1658 Note that an alternative if the second part doesn't hold is
1659 `c-type-list-kwds'. Keywords on this list are typically also present
1660 on one of the `*-decl-kwds' lists."
1661 t nil
1667 ;; Adorned regexp matching `c-type-prefix-kwds'.
1672 "Type modifier keywords. These can occur almost anywhere in types
1673 but they don't build a type of themselves. Unlike the keywords on
1674 `c-primitive-type-kwds', they are fontified with the keyword face and
1675 not the type face."
1676 t nil
1682 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1683 ;; languages without such keywords.
1689 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1690 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1700 ;; All keywords that can start a type (i.e. are either a type prefix
1701 ;; or a complete type).
1708 "Keywords introducing declarations where the following block (if any)
1709 contains another declaration level that should be considered a class.
1711 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1712 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1713 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1714 will be handled.
1716 Note that presence on this list does not automatically treat the
1717 following identifier as a type; the keyword must also be present on
1718 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1719 t nil
1727 ;; In CORBA PSDL:
1729 ;; In CORBA CIDL:
1734 ;; Regexp matching the start of a class.
1739 "Keywords introducing declarations where the following block (if
1740 any) is a brace list.
1742 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1743 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1744 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1745 will be handled."
1750 ;; Regexp matching the start of declarations where the following
1751 ;; block is a brace list.
1756 "Keywords where the following block (if any) contains another
1757 declaration level that should not be considered a class. For every
1758 keyword here, CC Mode will add a set of special syntactic symbols for
1760 `foo-open', `foo-close', and `infoo' symbols.
1762 The intention is that this category should be used for block
1763 constructs that aren't related to object orientation concepts like
1764 classes (which thus also include e.g. interfaces, templates,
1765 contracts, structs, etc). The more pragmatic distinction is that
1766 while most want some indentation inside classes, it's fairly common
1767 that they don't want it in some of these constructs, so it should be
1768 simple to configure that differently from classes. See also
1769 `c-class-decl-kwds'.
1771 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1772 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1773 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1774 will be handled."
1775 t nil
1779 ;; In CORBA CIDL:
1783 ;; Regexp matching the start of blocks besides classes that contain
1784 ;; another declaration level.
1793 'inextern-lang
1796 "Alist associating keywords in c-other-decl-block-decl-kwds with
1800 "Keywords introducing declarations where the identifier(s) being
1801 declared are types.
1803 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1804 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1805 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1806 will be handled."
1807 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1808 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1809 ;; {...}").
1812 ;; Languages that have a "typedef" construct.
1815 ;; Unlike most other languages, exception names are not handled as
1816 ;; types in IDL since they only can occur in "raises" specs.
1824 "Keywords introducing declarations where the \(first) identifier
1825 \(declarator) follows directly after the keyword, without any type.
1827 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1828 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1829 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1830 will be handled."
1831 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1832 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1833 ;; {...}").
1836 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1837 ;; `c-type-list-kwds' for IDL.
1840 ;; In CORBA PSDL:
1842 ;; In CORBA CIDL:
1848 "Keywords that can prefix normal declarations of identifiers
1849 \(and typically act as flags). Things like argument declarations
1850 inside function headers are also considered declarations in this
1851 sense.
1853 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1854 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1855 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1856 will be handled."
1857 t nil
1862 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1866 ;; In CORBA PSDL:
1868 ;; In CORBA CIDL:
1870 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1877 "Keywords that can start or prefix any declaration level construct,
1878 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1879 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1880 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1882 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1883 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1884 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1885 will be handled."
1886 t nil
1892 "Keywords that always start declarations, wherever they occur.
1893 This can be used for declarations that aren't recognized by the normal
1894 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1895 t nil
1896 ;; Classes can be declared anywhere in a Pike expression.
1900 "Keywords that can occur anywhere in a declaration level construct.
1901 This is used for self-contained things that can be tacked on anywhere
1902 on a declaration and that should be ignored to be able to recognize it
1903 correctly. Typical cases are compiler extensions like
1906 __declspec(noreturn) void foo();
1907 class __declspec(dllexport) classname {...};
1908 void foo() __attribute__((noreturn));
1910 Note that unrecognized plain symbols are skipped anyway if they occur
1911 before the type, so such things are not necessary to mention here.
1912 Mentioning them here is necessary only if they can occur in other
1913 places, or if they are followed by a construct that must be skipped
1915 examples above). In the last case, they alse need to be present on
1916 one of `c-type-list-kwds', `c-ref-list-kwds',
1917 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1918 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1919 ;; NB: These are currently not recognized in all parts of a
1920 ;; declaration. Specifically, they aren't recognized in the middle
1921 ;; of multi-token types, inside declarators, and between the
1922 ;; identifier and the arglist paren of a function declaration.
1923 ;;
1924 ;; FIXME: This ought to be user customizable since compiler stuff
1925 ;; like this usually is wrapped in project specific macros. (It'd
1926 ;; of course be even better if we could cope without knowing this.)
1927 t nil
1929 "__attribute__"
1930 ;; MSVC extension.
1934 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1939 ;; All keywords that can occur in the preamble of a declaration.
1940 ;; They typically occur before the type, but they are also matched
1941 ;; after presumptive types since we often can't be sure that
1942 ;; something is a type or just some sort of macro in front of the
1943 ;; declaration. They might be ambiguous with types or type
1944 ;; prefixes.
1957 ;; Adorned regexp of `c-prefix-spec-kwds'.
1963 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1964 ;; ambiguous with types or type prefixes. These are the keywords (like
1965 ;; extern, namespace, but NOT template) that can modify a declaration.
1974 ;; Keywords that can occur after argument list of a function header
1975 ;; declaration, i.e. in the "K&R region".
1980 ;; Adorned regexp matching all keywords that can't appear at the
1981 ;; start of a declaration.
1995 ;; The "more" for C++ is the QT keyword (as in "more slots:").
1996 ;; This variable is intended for use in c-beginning-of-statement-1.
2006 "Access protection label keywords in classes."
2007 t nil
2012 "Keywords introducing declarations that can contain a block which
2015 like that, it ends with the following ';' and not right away.
2017 The keywords on list are assumed to also be present on one of the
2018 `*-decl-kwds' lists."
2019 t nil
2024 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2025 ;; languages without such constructs.
2032 "Keywords introducing extra declaration specifiers in the region
2034 declarations."
2035 t nil
2038 "supports"
2039 ;; In CORBA PSDL:
2043 "Keywords that may be followed by a nonsymbol sexp before whatever
2044 construct it's part of continues."
2045 t nil
2049 "Keywords that may be followed by a comma separated list of type
2050 identifiers, where each optionally can be prefixed by keywords. (Can
2051 also be used for the special case when the list can contain only one
2052 element.)
2054 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2055 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2056 There's also no reason to add keywords that prefixes a normal
2057 declaration consisting of a type followed by a declarator (list), so
2058 the keywords on `c-modifier-kwds' should normally not be listed here
2059 either.
2061 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2062 or variable identifier (that's being defined)."
2063 t nil
2068 ;; In CORBA PSDL:
2073 "Keywords that may be followed by a comma separated list of
2074 reference (i.e. namespace/scope/module) identifiers, where each
2075 optionally can be prefixed by keywords. (Can also be used for the
2076 special case when the list can contain only one element.) Assumed to
2077 be mutually exclusive with `c-type-list-kwds'.
2079 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2080 or variable identifier (that's being defined)."
2081 t nil
2085 ;; In CORBA CIDL:
2090 "Keywords that may be followed (not necessarily directly) by a colon
2091 and then a comma separated list of type identifiers, where each
2092 optionally can be prefixed by keywords. (Can also be used for the
2093 special case when the list can contain only one element.)"
2094 t nil
2097 ;; In CORBA PSDL:
2101 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2102 forward to the colon. The end of the match is assumed to be directly
2104 regexp if `c-colon-type-list-kwds' isn't nil."
2106 ;; Disallow various common punctuation chars that can't come
2107 ;; before the ":" that starts the inherit list after "class"
2108 ;; or "struct" in C++. (Also used as default for other
2109 ;; languages.)
2114 "Keywords that may be followed by a parenthesis expression that doesn't
2115 contain type identifiers."
2116 t nil
2118 "__attribute__"
2119 ;; MSVC extension.
2123 "Keywords that may be followed by a parenthesis expression containing
2124 type identifiers separated by arbitrary tokens."
2125 t nil
2137 "Keywords that may be followed by an angle bracket expression
2139 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2140 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2141 if this isn't nil."
2142 t nil
2145 ;; In CORBA PSDL:
2149 "Keywords that can be followed by a C++ style template arglist; see
2150 `c-recognize-<>-arglists' for details. That language constant is
2151 assumed to be set if this isn't nil."
2152 t nil
2157 ;; All keywords that can be followed by an angle bracket sexp.
2163 ;; Adorned regexp matching keywords that can be followed by an angle
2164 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2170 "Keywords that may be followed by a brace block containing a comma
2171 separated list of identifier definitions, i.e. like the list of
2172 identifiers that follows the type in a normal declaration."
2176 "Statement keywords followed directly by a substatement."
2181 idl nil)
2184 ;; Regexp matching the start of any statement followed directly by a
2185 ;; substatement (doesn't match a bare block, however).
2190 "Statement keywords followed by a paren sexp and then by a substatement."
2195 idl nil
2200 ;; Regexp matching the start of any statement followed by a paren sexp
2201 ;; and then by a substatement.
2206 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2212 ;; Regexp matching the start of any statement that has a
2213 ;; substatement (except a bare block). Nil in languages that
2214 ;; don't have such constructs.
2223 "Statement keywords followed by an expression or nothing."
2226 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2228 idl nil
2235 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2240 "Statement keywords followed by a parenthesis expression that
2241 nevertheless contains a list separated with ';' and not ','."
2243 idl nil)
2246 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2251 "Statement keywords followed by an assembler expression."
2252 t nil
2256 ;; Regexp matching the start of an assembler statement. Nil in
2257 ;; languages that don't support that.
2266 awk nil)
2269 ;; Adorned regexp matching any "case"-like keyword.
2274 "Keywords introducing colon terminated labels in blocks."
2278 ;; Adorned regexp matching any keyword that introduces a label.
2283 "Keywords that might be followed by a label identifier."
2287 idl nil
2288 awk nil)
2291 "Keywords for constants."
2292 t nil
2301 "Keywords besides constants and operators that start primary expressions."
2302 t nil
2309 ;; Keywords that can occur anywhere in expressions. Built from
2310 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2314 t
2319 "Keywords that start lambda constructs, i.e. function definitions in
2320 expressions."
2321 t nil
2325 "Keywords that start constructs followed by statement blocks which can
2326 be used in expressions \(the gcc extension for this in C and C++ is
2327 handled separately by `c-recognize-paren-inexpr-blocks')."
2328 t nil
2332 "Keywords that can start classes inside expressions."
2333 t nil
2338 "Keywords that can start brace list blocks inside expressions.
2339 Note that Java specific rules are currently applied to tell this from
2340 `c-inexpr-class-kwds'."
2341 t nil
2345 ;; Regexp matching the start of a brace list in an expression, or
2346 ;; nil in languages that don't have such things. This should not
2347 ;; match brace lists recognized through `c-special-brace-lists'.
2354 ;; Regexp matching keywords in any construct that contain another
2355 ;; declaration level, i.e. that isn't followed by a function block
2356 ;; or brace list. When the first submatch matches, it's an
2357 ;; unambiguous construct, otherwise it's an ambiguous match that
2358 ;; might also be the return type of a function declaration.
2376 "Keywords that can introduce bitfields."
2377 t nil
2381 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2382 ;; languages without bitfield support.
2383 t nil
2388 "Keywords not accounted for by any other `*-kwds' language constant."
2389 t nil
2391 ;; In CORBA CIDL: (These are declaration keywords that never
2392 ;; can start a declaration.)
2395 \f
2396 ;;; Constants built from keywords.
2398 ;; Note: No `*-kwds' language constants may be defined below this point.
2402 ;; List of all the language constants that contain keyword lists.
2407 ;; Make the list of globally interned symbols
2408 ;; instead of ones interned in `c-lang-constants'.
2410 c-lang-constants)
2411 list)))
2414 ;; All keywords as a list.
2419 c-kwds-lang-consts)
2420 nil))
2424 ;; All keywords as an adorned regexp.
2429 ;; An alist with all the keywords in the cars. The cdr for each
2430 ;; keyword is a list of the symbols for the `*-kwds' lists that
2431 ;; contains it.
2437 c-kwds-lang-consts))))
2438 lang-const kwd-list kwd
2439 result-alist elem)
2451 result-alist))
2454 ;; An obarray containing all keywords as symbols. The property list
2455 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2456 ;; lists it's a member of.
2457 ;;
2458 ;; E.g. to see whether the string str contains a keyword on
2459 ;; `c-class-decl-kwds', one can do like this:
2460 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2461 ;; Which preferably is written using the associated functions in
2462 ;; cc-engine:
2463 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2465 ;; The obarray is not stored directly as a language constant since
2466 ;; the printed representation for obarrays used in .elc files isn't
2467 ;; complete.
2470 kwd lang-const-list
2477 ;; Emacs has an odd bug that causes `mapcan' to fail
2478 ;; with unintelligible errors. (XEmacs works.)
2479 ;;(mapcan (lambda (lang-const)
2480 ;; (list lang-const t))
2481 ;; lang-const-list)
2484 lang-const-list))))
2485 obarray))
2488 ;; Adorned regexp matching all keywords that should be fontified
2489 ;; with the keywords face. I.e. that aren't types or constants.
2499 ;; Regexp matching the start of any primary expression, i.e. any
2500 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2501 ;; exclude keywords; they are excluded afterwards unless the second
2502 ;; submatch matches. If the first but not the second submatch
2503 ;; matches then it is an ambiguous primary expression; it could also
2504 ;; be a match of e.g. an infix operator. (The case with ambiguous
2505 ;; keyword operators isn't handled.)
2511 ;; Filter out the special case prefix
2512 ;; operators that are close parens.
2517 t
2523 postfix-if-paren
2524 left-assoc
2525 right-assoc
2526 right-assoc-sequence)
2527 t))
2530 in-or-postfix-ops
2533 in-or-postfix-ops
2538 ;; Take out all symbol class operators from `prefix-ops' and make the
2539 ;; first submatch from them together with `c-primary-expr-kwds'.
2546 ;; Match all ambiguous operators.
2553 ;; Now match all other symbols.
2557 ;; The chars that can start integer and floating point
2558 ;; constants.
2562 ;; The unambiguous operators from `prefix-ops'.
2568 ;; Match string and character literals.
2575 \f
2576 ;;; Additional constants for parser-level constructs.
2579 "Regexp matching something that might precede a declaration, cast or
2580 label, such as the last token of a preceding statement or declaration.
2581 This is used in the common situation where a declaration or cast
2582 doesn't start with any specific token that can be searched for.
2584 The regexp should not match bob; that is done implicitly. It can't
2585 require a match longer than one token. The end of the token is taken
2586 to be at the end of the first submatch, which is assumed to always
2587 match. It's undefined whether identifier syntax (see
2588 `c-identifier-syntax-table') is in effect or not. This regexp is
2589 assumed to be a superset of `c-label-prefix-re' if
2590 `c-recognize-colon-labels' is set.
2592 Besides this, `c-decl-start-kwds' is used to find declarations.
2594 Note: This variable together with `c-decl-start-re' and
2596 declaration/cast/label starts. I.e. they might produce more matches
2597 but should not miss anything (or else it's necessary to use text
2598 properties - see the next note). Wherever they match, the following
2599 construct is analyzed to see if it indeed is a declaration, cast or
2600 label. That analysis is not cheap, so it's important that not too
2601 many false matches are triggered.
2603 Note: If a declaration/cast/label start can't be detected with this
2604 variable, it's necessary to use the `c-type' text property with the
2605 value `c-decl-end' on the last char of the last token preceding the
2606 declaration. See the comment blurb at the start of cc-engine.el for
2607 more info."
2609 ;; We match a sequence of characters to skip over things like \"};\"
2610 ;; more quickly. We match ")" in C for K&R region declarations, and
2611 ;; in all languages except Java for when a cpp macro definition
2612 ;; begins with a declaration.
2615 ;; Match "<" in C++ to get the first argument in a template arglist.
2616 ;; In that case there's an additional check in `c-find-decl-spots'
2617 ;; that it got open paren syntax.
2619 ;; Additionally match the protection directives in Objective-C.
2620 ;; Note that this doesn't cope with the longer directives, which we
2621 ;; would have to match from start to end since they don't end with
2622 ;; any easily recognized characters.
2626 ;; Pike is like C but we also match "[" for multiple value
2627 ;; assignments and type casts.
2633 "Regexp matching the start of any declaration, cast or label.
2634 It's used on the token after the one `c-decl-prefix-re' matched. This
2635 regexp should not try to match those constructs accurately as it's
2636 only used as a sieve to avoid spending more time checking other
2637 constructs."
2642 ;; Regexp matching something that might precede or start a
2643 ;; declaration, cast or label.
2644 ;;
2645 ;; If the first submatch matches, it's taken to match the end of a
2646 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2647 ;; It's built from `c-decl-prefix-re'.
2648 ;;
2649 ;; If the first submatch did not match, the match of the whole
2650 ;; regexp is taken to be at the first token in the declaration.
2651 ;; `c-decl-start-re' is not checked in this case.
2652 ;;
2653 ;; Design note: The reason the same regexp is used to match both
2654 ;; tokens that precede declarations and start them is to avoid an
2655 ;; extra regexp search from the previous declaration spot in
2656 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2657 ;; that it finds all declaration/cast/label starts in approximately
2658 ;; linear order, so we can't do the searches in two separate passes.
2669 ;; List containing the paren characters that can open a cast, or nil in
2670 ;; languages without casts.
2678 "List of syntactically relevant characters that never can occur before
2679 the open brace in any construct that contains a brace block, e.g. in
2682 class Foo: public Bar {int x();} a, *b;
2684 If parens can occur, the chars inside those aren't filtered with this
2685 list.
2687 '<' and '>' should be disallowed even if angle bracket arglists can
2688 occur. That since the search function needs to stop at them anyway to
2689 ensure they are given paren syntax.
2691 This is used to skip backward from the open brace to find the region
2694 possible for good performance."
2696 ;; Default to all chars that only occurs in nonsymbol tokens outside
2697 ;; identifiers.
2703 t
2704 t
2708 op pos)
2711 res))))
2713 ;; Allow cpp operations (where applicable).
2719 ;; Allow ':' for inherit list starters.
2723 ;; Allow ',' for multiple inherits.
2727 ;; Allow parentheses for anonymous inner classes in Java and class
2728 ;; initializer lists in Pike.
2732 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2737 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2738 ;; for `c-syntactic-skip-backward'.
2743 "Regexp matching the declarator operators that might precede the
2746 The end of the first submatch is taken as the end of the operator.
2747 Identifier syntax is in effect when this is matched \(see
2748 `c-identifier-syntax-table')."
2751 ;; Default to a regexp that never matches.
2753 ;; Check that there's no "=" afterwards to avoid matching tokens
2754 ;; like "*=".
2756 "[*\(]"
2762 "[*\(&]"
2767 ;; If this matches there's special treatment in
2768 ;; `c-font-lock-declarators' and
2769 ;; `c-font-lock-declarations' that check for a
2770 ;; complete name followed by ":: *".
2780 "Regexp matching the declarator operators that might follow after the
2783 it matches an open paren of some kind, the type declaration check
2784 continues at the corresponding close paren, otherwise the end of the
2785 first submatch is taken as the end of the operator. Identifier syntax
2786 is in effect when this is matched (see `c-identifier-syntax-table')."
2787 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2788 ;; function argument list parenthesis.
2796 "[\)\[\(]"
2800 ;; "throw" in `c-type-modifier-kwds' is followed
2801 ;; by a parenthesis list, but no extra measures
2802 ;; are necessary to handle that.
2812 "This regexp is matched after a declarator expression where
2813 `c-type-decl-suffix-key' has matched. If it matches then the
2814 construct is taken as a declaration. It's typically used to match the
2815 beginning of a function body or whatever might occur after the
2816 function header in a function declaration or definition. It's
2817 undefined whether identifier syntax (see `c-identifier-syntax-table')
2818 is in effect or not.
2823 t "{"
2824 ;; If K&R style declarations should be recognized then one could
2825 ;; consider to match the start of any symbol since we want to match
2826 ;; the start of the first declaration in the "K&R region". That
2827 ;; could however produce false matches on code like "FOO(bar) x"
2828 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2829 ;; on the other heuristics in that case.
2831 ;; Add on the keywords in `c-postfix-spec-kwds'.
2836 ;; Also match the colon that starts a base class initializer list in
2837 ;; C++. That can be confused with a function call before the colon
2838 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2839 ;; match before such a thing (as a declaration-level construct;
2840 ;; matches inside arglist contexts are already excluded).
2847 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2848 ;; matches ";" and ",".
2857 end of the operator. nil in languages without such operators. It's
2858 undefined whether identifier syntax (see `c-identifier-syntax-table')
2859 is in effect or not."
2860 t nil
2866 "Regexp matching operators that might follow after a type, or nil in
2867 languages that don't have such operators. The end of the first
2868 submatch is taken as the end of the operator. This should not match
2869 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2870 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2871 is in effect or not."
2872 t nil
2878 ;; Regexp matching the known type identifiers. This is initialized
2879 ;; from the type keywords and `*-font-lock-extra-types'. The first
2880 ;; submatch is the one that matches the type. Note that this regexp
2881 ;; assumes that symbol constituents like '_' and '$' have word
2882 ;; syntax.
2891 extra-types)))
2897 extra-types))))
2902 plain-strings)))
2903 regexp-strings)
2908 "List of open- and close-chars that makes up a pike-style brace list,
2910 list."
2911 t nil
2916 "Non-nil means K&R style argument declarations are valid."
2917 t nil
2918 c t)
2922 "Non-nil means function declarations without return type should be
2923 recognized. That can introduce an ambiguity with parenthesized macro
2924 calls before a brace block. This setting does not affect declarations
2925 that are preceded by a declaration starting keyword, so
2926 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2927 t nil
2933 "Non-nil means C++ style template arglists should be handled. More
2934 specifically, this means a comma separated list of types or
2936 identifier or one of the keywords on `c-<>-type-kwds' or
2937 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2938 expression is considered to be a type."
2944 "Non-nil means that an enum structure can contain declarations."
2945 t nil
2946 java t)
2950 "Non-nil means that parenthesis style initializers exist,
2951 i.e. constructs like
2953 Foo bar (gnu);
2955 in addition to the more classic
2957 Foo bar = gnu;"
2958 t nil
2963 "Non-nil to recognize gcc style in-expression blocks,
2964 i.e. compound statements surrounded by parentheses inside expressions."
2965 t nil
2971 ;; Regexp matching the start of angle bracket arglists in languages
2972 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2973 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2974 ;; assumed to surround the preceding symbol. The whole match is
2975 ;; assumed to end directly after the opening "<".
2985 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2986 ;; parens. The first submatch is assumed to surround
2987 ;; `c-opt-<>-arglist-start'.
2996 ;; Regexp matching the beginning of a declaration specifier in the
2997 ;; region between the header and the body of a declaration.
2998 ;;
2999 ;; TODO: This is currently not used uniformly; c++-mode and
3000 ;; java-mode each have their own ways of using it.
3001 t nil
3014 That includes labels in code and access keys in classes. This does
3015 not apply to labels recognized by `c-label-kwds' and
3016 `c-opt-extra-label-key'."
3017 t nil
3023 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3024 a generic colon label. Not used if `c-recognize-colon-labels' is
3025 nil."
3031 "Regexp matching things that can't occur in generic colon labels,
3032 neither in a statement nor in a declaration context. The regexp is
3033 tested at the beginning of every sexp in a suspected label,
3036 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3042 ;; Don't allow string literals, except in AWK. Character constants are OK.
3045 ;; Also check for open parens in C++, to catch member init lists in
3046 ;; constructors. We normally allow it so that macros with arguments
3047 ;; work in labels.
3052 "Regexp matching things that can't occur two symbols before a colon in
3060 "Optional regexp matching labels.
3061 Normally, labels are detected according to `c-nonlabel-token-key',
3062 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3063 be used if there are additional labels that aren't recognized that
3064 way."
3065 t nil
3070 ;; Regexp describing friend declarations classes, or nil in
3071 ;; languages that don't have such things.
3072 ;;
3073 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3074 ;; template skipping isn't done properly. This will disappear soon.
3075 t nil
3080 "<.+>"
3082 "friend"
3087 ;; Special regexp to match the start of Objective-C methods. The
3088 ;; first submatch is assumed to end after the + or - key.
3089 t nil
3091 ;; TODO: Ought to use a better method than anchoring on bol.
3096 "([^\)]*)"
3103 ;; Must be set in buffers where the `c-type' text property might be
3104 ;; used with the value `c-decl-end'.
3105 ;;
3106 ;; `c-decl-end' is used to mark the ends of labels and access keys
3107 ;; to make interactive refontification work better.
3110 ;; `c-decl-end' is used to mark the end of the @-style directives in
3111 ;; Objective-C.
3112 objc t)
3115 \f
3116 ;;; Wrap up the `c-lang-defvar' system.
3118 ;; Compile in the list of language variables that has been collected
3119 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3120 ;; first element of each is nil.
3124 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3125 ;; These are typically standard emacs variables such as `comment-start'.
3133 "Create a function that initializes all the language dependent variables
3134 for the given mode.
3136 This function should be evaluated at compile time, so that the
3137 function it returns is byte compiled with all the evaluated results
3138 from the language constants. Use the `c-init-language-vars' macro to
3139 accomplish that conveniently."
3145 ;; No need to byte compile this lambda since the byte compiler is
3146 ;; smart enough to detect the `funcall' construct in the
3147 ;; `c-init-language-vars' macro below and compile it all straight
3148 ;; into the function that contains `c-init-language-vars'.
3151 ;; This let sets up the context for `c-mode-var' and similar
3152 ;; that could be in the result from `cl-macroexpand-all'.
3154 current-var source-eval)
3161 ;; `c-lang-const' will expand to the evaluated
3162 ;; constant immediately in `cl-macroexpand-all'
3163 ;; below.
3169 ;; Note: The following `append' copies the
3170 ;; first argument. That list is small, so
3171 ;; this doesn't matter too much.
3175 ;; This diagnostic message isn't useful for end
3176 ;; users, so it's disabled.
3177 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3178 ;; (message ,(concat "%s compiled with CC Mode %s "
3179 ;; "but loaded with %s - evaluating "
3180 ;; "language constants from source")
3181 ;; ',mode ,c-version c-version)
3182 ;; (put ',mode 'c-has-warned-lang-consts t))
3195 current-var
3198 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3201 err)
3204 ;; Being evaluated from source. Always use the dynamic method to
3205 ;; work well when `c-lang-defvar's in this file are reevaluated
3206 ;; interactively.
3212 current-var)
3224 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3225 current-var err)
3227 ))
3230 "Initialize all the language dependent variables for the given mode.
3231 This macro is expanded at compile time to a form tailored for the mode
3232 in question, so MODE must be a constant. Therefore MODE is not
3233 evaluated and should not be quoted."
3236 \f
3239 ;;; cc-langs.el ends here