| blob | 575c25d65199d877df3240f347712d8b5ece31bf |
1 ;;; cc-langs.el --- language specific settings for CC Mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2015 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.
397 t nil
402 table)))
408 ;; A variant of the standard syntax table which is used to find matching
409 ;; "<"s and ">"s which have been marked as parens using syntax table
410 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
411 ;; non-paren syntax here. so that the list commands will work on "< ... >"
412 ;; even when there's unbalanced other parens inside them.
413 ;;
414 ;; This variable is nil for languages which don't have template stuff.
424 table))))
429 "A list that describes the modifications that should be done to the
430 mode syntax table to get a syntax table that matches all identifiers
431 and keywords as words.
433 The list is just like the one used in `font-lock-defaults': Each
434 element is a cons where the car is the character to modify and the cdr
435 the new syntax, as accepted by `modify-syntax-entry'."
436 ;; The $ character is not allowed in most languages (one exception
437 ;; is Java which allows it for legacy reasons) but we still classify
438 ;; it as an identifier character since it's often used in various
439 ;; machine generated identifiers.
450 mod)
455 table)
456 "Syntax table built on the mode syntax table but additionally
457 classifies symbol constituents like '_' and '$' as word constituents,
461 ;; For documentation see the following c-lang-defvar of the same name.
462 ;; The value here may be a list of functions or a single function.
463 t nil
465 c-before-change-check-<>-operators
466 c-invalidate-macro-cache)
468 ;; java 'c-before-change-check-<>-operators
473 fs
475 "If non-nil, a list of functions called from c-before-change-hook.
476 Typically these will record enough state to allow
477 `c-before-font-lock-function' to extend the region to fontify,
478 and may do such things as removing text-properties which must be
479 recalculated.
481 These functions will be run in the order given. Each of them
482 takes 2 parameters, the BEG and END supplied to every
483 before-change function; on entry, the buffer will have been
484 widened and match-data will have been saved; point is undefined
485 on both entry and exit; the return value is ignored.
487 The functions are called even when font locking isn't enabled.
489 When the mode is initialized, the functions are called with
493 ;; For documentation see the following c-lang-defvar of the same name.
494 ;; The value here may be a list of functions or a single function.
495 t 'c-change-set-fl-decl-start
497 c-change-set-fl-decl-start)
502 fs
504 "If non-nil, a list of functions called just before font locking.
505 Typically they will extend the region about to be fontified \(see
506 below) and will set `syntax-table' text properties on the region.
508 These functions will be run in the order given. Each of them
509 takes 3 parameters, the BEG, END, and OLD-LEN supplied to every
510 after-change function; point is undefined on both entry and exit;
511 on entry, the buffer will have been widened and match-data will
512 have been saved; the return value is ignored.
514 The functions may extend the region to be fontified by setting the
515 buffer local variables c-new-BEG and c-new-END.
517 The functions are called even when font locking is disabled.
519 When the mode is initialized, these functions are called with
523 awk nil
525 ;; For documentation see the following c-lang-defvar of the same name.
526 ;; The value here may be a list of functions or a single function.
530 fs
532 "If non-nil, a list of functions called just before context (or
533 other non-change) fontification is done. Typically they will
534 extend the region.
536 These functions will be run in the order given. Each of them
537 takes 2 parameters, the BEG and END of the region to be
538 fontified. Point is undefined on both entry and exit. On entry,
539 the buffer will have been widened and match-data will have been
540 saved; the return value is a cons of the adjusted
543 \f
544 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
547 Such a function takes one optional parameter, a buffer position (defaults to
548 point), and returns nil or t. This variable contains nil for languages which
549 don't have EOL terminated statements. "
550 t nil
557 The (admittedly kludgy) purpose of such a function is to prevent an infinite
558 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
559 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
560 even indirectly. This variable contains nil for languages which don't have
561 EOL terminated statements."
562 t nil
568 \f
569 ;;; Lexer-level syntax (identifiers, tokens etc).
572 "Whether the language has bitfield declarations."
573 t nil
578 "Regexp that matches the start of a symbol, i.e. any identifier or
580 operator at the top level."
588 "Set of characters that can be part of a symbol.
589 This is of the form that fits inside [ ] in a regexp."
590 ;; Pike note: With the backquote identifiers this would include most
591 ;; operator chars too, but they are handled with other means instead.
597 "Regexp matching identifiers and keywords (with submatch 0). Assumed
598 to match if `c-symbol-start' matches on the same position."
602 ;; Use the value from C here since the operator backquote is
603 ;; covered by the other alternative.
611 ;; Number of regexp grouping parens in `c-symbol-key'.
615 "This is the set of chars that can't be part of a symbol, i.e. the
616 negation of `c-symbol-chars'."
621 "Regexp that matches any character that can't be part of a symbol.
622 It's usually appended to other regexps to avoid matching a prefix.
623 It's assumed to not contain any submatchers."
624 ;; The same thing regarding Unicode identifiers applies here as to
625 ;; `c-symbol-key'.
629 "The operators that make up fully qualified identifiers. nil in
630 languages that don't have such things. See `c-operators' for a
631 description of the format. Binary operators can concatenate symbols,
635 This value is by default merged into `c-operators'."
636 t nil
640 ;; Java has "." to concatenate identifiers but it's also used for
641 ;; normal indexing. There's special code in the Java font lock
642 ;; rules to fontify qualified identifiers based on the standard
643 ;; naming conventions. We still define "." here to make
644 ;; `c-forward-name' move over as long names as possible which is
645 ;; necessary to e.g. handle throws clauses correctly.
654 ;; Appendable adorned regexp matching the operators that join
655 ;; symbols to fully qualified identifiers, or nil in languages that
656 ;; don't have such things.
657 ;;
658 ;; This was a docstring constant in 5.30. It still works but is now
659 ;; considered internal - change `c-identifier-ops' instead.
662 t)))
670 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
674 ;; Appendable adorned regexp matching operators that might precede
675 ;; an identifier and that are part of the identifier in that case.
676 ;; nil in languages without such things.
679 t)))
684 "Operators that can occur after a binary operator on `c-identifier-ops'
685 in identifiers. nil in languages that don't have such things.
687 Operators here should also have appropriate entries in `c-operators' -
688 it's not taken care of by default."
689 t nil
690 ;; '~' for destructors in C++, '*' for member pointers.
692 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
693 ;; in import declarations. (This will also match bogus things like
694 ;; "foo.*bar" but we don't bother.)
698 ;; Regexp that must match the token after
699 ;; `c-opt-identifier-concat-key' for it to be considered an
700 ;; identifier concatenation operator (which e.g. causes the
701 ;; preceding identifier to be fontified as a reference). Assumed to
702 ;; be a string if `c-opt-identifier-concat-key' is.
703 ;;
704 ;; This was a docstring constant in 5.30. It still works but is now
705 ;; considered internal - change `c-after-id-concat-ops' instead.
713 "Regexp that matches the start of an (optionally qualified) identifier.
714 It should also match all keywords. It's unspecified how far it
715 matches."
725 C++. It does not recognize the full range of syntactic whitespace
726 between the tokens; `c-forward-name' has to be used for that. It
727 should also not match identifiers containing parenthesis groupings,
729 ;; This regexp is more complex than strictly necessary to ensure
730 ;; that it can be matched with a minimum of backtracking.
751 ;; For flexibility, consider the symbol match
752 ;; optional if we've hit a
753 ;; `c-after-id-concat-ops' operator. This is
754 ;; also necessary to handle the "*" that can
755 ;; end import declaration identifiers in Java.
769 ;; This was a docstring constant in 5.30 but it's no longer used.
770 ;; It's only kept to avoid breaking third party code.
771 ;;
772 ;; Used to identify the submatch in `c-identifier-key' that
773 ;; surrounds the last symbol in the qualified identifier. It's a
774 ;; list of submatch numbers, of which the first that has a match is
775 ;; taken. It's assumed that at least one does when the regexp has
776 ;; matched.
777 t nil)
780 "Set if the language support backslash escaped newlines inside string
781 literals."
782 t nil
788 "Set if the language supports multiline string literals without escaped
789 newlines. If t, all string literals are multiline. If a character,
790 only literals where the open quote is immediately preceded by that
791 literal are multiline."
792 t nil
793 pike ?#)
798 "The symbol which starts preprocessor constructs when in the margin."
799 t "#"
804 "Regexp matching the prefix of a cpp directive in the languages that
805 normally use that macro preprocessor. Tested at bol or at boi.
807 ;; TODO (ACM, 2005-04-01). Amend the following to recognize escaped NLs;
808 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
814 "Regexp matching the prefix of a cpp directive anchored to BOL,
815 in the languages that have a macro preprocessor."
821 "Regexp matching the prefix of a cpp directive including the directive
822 name, or nil in languages without preprocessor support. The first
823 submatch surrounds the directive name."
827 ;; Pike, being a scripting language, recognizes hash-bangs too.
833 "List of cpp directives (without the prefix) that are followed by a
834 string message."
840 "List of cpp directives (without the prefix) that are followed by a
841 file name in angle brackets or quotes."
847 "Cpp directive (without the prefix) that is followed by a macro
848 definition, or nil if the language doesn't have any."
855 ;; Regexp matching everything up to the macro body of a cpp define, or the
856 ;; end of the logical line if there is none. Submatch 1 is the name of the
857 ;; macro. Set if c-opt-cpp-macro-define is.
862 ;; ^ ^ #defined name
868 ;; Regexp matching everything up to the end of the identifier defined
869 ;; by a cpp define.
878 "List of cpp directives (without the prefix) that are followed by an
879 expression."
884 "Regexp which matches the start of a CPP directive which contains an
885 expression, or nil if there aren't any in the language."
894 "List of functions in cpp expressions."
900 "List of all assignment operators."
906 idl nil)
909 "List describing all operators, along with their precedence and
910 associativity. The order in the list corresponds to the precedence of
911 the operators: The operators in each element are a group with the same
912 precedence, and the group has higher precedence than the groups in all
913 following elements. The car of each element describes the type of the
914 operator group, and the cdr is a list of the operator tokens in it.
915 The operator group types are:
917 'prefix Unary prefix operators.
918 'postfix Unary postfix operators.
919 'postfix-if-paren
920 Unary postfix operators if and only if the chars have
921 parenthesis syntax.
922 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
923 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
924 'right-assoc-sequence
925 Right associative operator that constitutes of a
926 sequence of tokens that separate expressions. All the
927 tokens in the group are in this case taken as
928 describing the sequence in one such operator, and the
929 order between them is therefore significant.
931 Operators containing a character with paren syntax are taken to match
932 with a corresponding open/close paren somewhere else. A postfix
933 operator with close paren syntax is taken to end a postfix expression
934 started somewhere earlier, rather than start a new one at point. Vice
935 versa for prefix operators with open paren syntax.
938 often are described as postfix operators are considered binary here,
939 since CC Mode treats every identifier as an expression."
941 ;; There's currently no code in CC Mode that exploit all the info
942 ;; in this variable; precedence, associativity etc are present as a
943 ;; preparation for future work.
954 ;; Primary.
963 ;; Postfix.
965 ;; The following need special treatment.
975 ;; Unary.
982 ;; The following need special treatment.
993 ;; Member selection.
997 ;; Multiplicative.
1000 ;; Additive.
1003 ;; Shift.
1008 ;; Relational.
1013 ;; Equality.
1017 ;; Bitwise and.
1021 ;; Bitwise exclusive or.
1027 ;; Bitwise or.
1033 ;; Logical and.
1037 ;; Logical or.
1043 ;; Conditional.
1046 ;; Assignment.
1049 ;; Exception.
1053 ;; Sequence.
1056 ;; IDL got its own definition since it has a much smaller operator
1057 ;; set than the other languages.
1061 ;; Primary.
1063 ;; Unary.
1065 ;; Multiplicative.
1067 ;; Additive.
1069 ;; Shift.
1071 ;; And.
1073 ;; Xor.
1075 ;; Or.
1079 ;; The operators as a flat list (without duplicates).
1085 t nil
1094 ;; These work like identifiers in Pike.
1101 ;; Regexp tested after an "operator" token in C++.
1102 t nil
1108 "Regexp matching the token before the ones in
1109 `c-overloadable-operators' when operators are specified in their
1112 languages without operator functions or where the complete operator
1113 identifier is listed in `c-overloadable-operators'.
1115 This regexp is assumed to not match any non-operator identifier."
1116 t nil
1121 ;; Note: the following alias is an old name which was a mis-spelling. It has
1122 ;; been corrected above and throughout cc-engine.el. It will be removed at
1123 ;; some release very shortly in the future. ACM, 2006-04-14.
1129 "List of the tokens made up of characters in the punctuation or
1130 parenthesis syntax classes that have uses other than as expression
1131 operators."
1149 ;; List of all tokens in the punctuation and parenthesis syntax
1150 ;; classes.
1156 ;; List containing all chars not in the word, symbol or
1157 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1158 ;; parenthesis and string delimiter chars.
1160 ;; Only go through the chars in the printable ASCII range. No
1161 ;; language so far has 8-bit or widestring operators.
1167 list)))
1170 ;; Regexp matching all tokens in the punctuation and parenthesis
1171 ;; syntax classes. Note that this also matches ".", which can start
1172 ;; a float.
1175 t
1181 ;; Regexp matching all assignment operators and only them. The
1182 ;; beginning of the first submatch is used to detect the end of the
1183 ;; token, along with the end of the whole match.
1186 ;; Need special case for "=" since it's a prefix of "==".
1198 ;; Regexp matching all tokens containing "<" or ">" which are longer
1199 ;; than one char.
1202 t
1208 ;; Regexp matching the second and subsequent characters of all
1209 ;; multicharacter tokens that begin with "<".
1212 t
1219 ;; Regexp matching the second and subsequent characters of all
1220 ;; multicharacter tokens that begin with ">".
1223 t
1228 t
1235 ;; The characters that should be considered to bound statements. To
1236 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1237 ;; begin with "^" to negate the set. If ? : operators should be
1238 ;; detected then the string must end with "?:".
1243 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1248 \f
1249 ;;; Syntactic whitespace.
1252 "Regexp matching an ordinary whitespace character.
1254 ;; "\\s " is not enough since it doesn't match line breaks.
1258 ;; Number of regexp grouping parens in `c-simple-ws'.
1262 "String that starts line comments, or nil if such don't exist.
1263 Line comments are always terminated by newlines. At least one of
1264 `c-block-comment-starter' and this one is assumed to be set.
1266 Note that it's currently not enough to set this to support a new
1267 comment style. Other stuff like the syntax table must also be set up
1268 properly."
1269 t "//"
1274 "String that starts block comments, or nil if such don't exist.
1275 Block comments are ended by `c-block-comment-ender', which is assumed
1276 to be set if this is. At least one of `c-line-comment-starter' and
1277 this one is assumed to be set.
1279 Note that it's currently not enough to set this to support a new
1280 comment style. Other stuff like the syntax table must also be set up
1281 properly."
1282 t "/*"
1283 awk nil)
1286 "String that ends block comments, or nil if such don't exist.
1288 Note that it's currently not enough to set this to support a new
1289 comment style. Other stuff like the syntax table must also be set up
1290 properly."
1291 t "*/"
1292 awk nil)
1295 ;; Regexp to match the start of any type of comment.
1301 re)))
1305 ;; Regexp which matches the start of a block comment (if such exists in the
1306 ;; language)
1314 ;; Regexp which matches the start of a line comment (if such exists in the
1315 ;; language; it does in all 7 CC Mode languages).
1323 ;; Regexp to match the start of comments and string literals.
1332 "Regexp to match the start of documentation comments."
1334 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1342 "String that starts comments inserted with M-; etc.
1343 `comment-start' is initialized from this."
1344 ;; Default: Prefer line comments to block comments, and pad with a space.
1348 ;; In C we still default to the block comment style since line
1349 ;; comments aren't entirely portable.
1354 "String that ends comments inserted with M-; etc.
1355 `comment-end' is initialized from this."
1356 ;; Default: Use block comment style if comment-start uses block
1357 ;; comments, and pad with a space in that case.
1367 "Regexp to match the start of a comment plus everything up to its body.
1368 `comment-start-skip' is initialized from this."
1369 ;; Default: Allow the last char of the comment starter(s) to be
1370 ;; repeated, then allow any amount of horizontal whitespace.
1383 ;; Regexp matching any sequence that can start syntactic whitespace.
1384 ;; The only uncertain case is '#' when there are cpp directives.
1398 ;; Regexp matching any single character that might end syntactic whitespace.
1413 ;; Regexp matching an unterminated block comment that doesn't
1414 ;; contain line breaks, or nil in languages without block comments.
1415 ;; Does not contain a \| operator at the top level.
1419 ;; It's messy to cook together a regexp that matches anything
1420 ;; but c-block-comment-ender.
1428 "[^"
1429 ;; The quoting rules inside char classes are silly. :P
1438 "]"
1446 ;; Regexp matching a block comment that doesn't contain line breaks,
1447 ;; or nil in languages without block comments. The reason we don't
1448 ;; allow line breaks is to avoid going very far and risk running out
1449 ;; of regexp stack; this regexp is intended to handle only short
1450 ;; comments that might be put in the middle of limited constructs
1451 ;; like declarations. Does not contain a \| operator at the top
1452 ;; level.
1467 ;; Regexp matching a piece of syntactic whitespace that isn't a
1468 ;; sequence of simple whitespace characters. As opposed to
1469 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1470 ;; directives as syntactic whitespace.
1482 ;; Regexp matching syntactic whitespace, including possibly the
1483 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1484 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1485 ;; not contain a \| operator at the top level.
1493 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1497 ;; Regexp matching syntactic whitespace, which is at least one
1498 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1499 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1500 ;; not contain a \| operator at the top level.
1508 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1512 ;; Regexp matching syntactic whitespace without any line breaks. As
1513 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1514 ;; regard cpp directives as syntactic whitespace. Does not contain
1515 ;; a \| operator at the top level.
1523 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1527 ;; Regexp that matches when there is no syntactically significant
1528 ;; text before eol. Macros are regarded as syntactically
1529 ;; significant text here.
1531 ;; Match eol (possibly inside a block comment or preceded
1532 ;; by a line continuation backslash), or the beginning of a
1533 ;; line comment. Note: This has to be modified for awk
1534 ;; where line comments start with '#'.
1548 \f
1549 ;;; Defun functions
1551 ;; The Emacs variables beginning-of-defun-function and
1552 ;; end-of-defun-function will be set so that commands like
1553 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1554 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1555 ;; functions, allowing optimization for large n.
1557 "Function to which beginning-of-defun-function will be set."
1558 t 'c-beginning-of-defun
1564 "Function to which end-of-defun-function will be set."
1565 t 'c-end-of-defun
1568 \f
1569 ;;; In-comment text handling.
1572 "Regexp to append to `paragraph-start'."
1573 t "$"
1579 "Regexp to append to `paragraph-separate'."
1580 t "$"
1584 \f
1585 ;;; Keyword lists.
1587 ;; Note: All and only all language constants containing keyword lists
1588 ;; should end with "-kwds"; they're automatically collected into the
1589 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1592 "Primitive type keywords. As opposed to the other keyword lists, the
1593 keywords listed here are fontified with the type face instead of the
1594 keyword face.
1596 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1597 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1598 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1599 will be handled.
1601 Do not try to modify this list for end user customizations; the
1602 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1603 the appropriate place for that."
1612 ;; Objective-C extends C, but probably not the new stuff in C99.
1619 ;; In CORBA PSDL:
1620 "ref"
1621 ;; The following can't really end a type, but we have to specify them
1622 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1623 ;; doesn't matter that much.
1626 ;; used as a builtin type.
1631 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1636 "Keywords that might act as prefixes for primitive types. Assumed to
1637 be a subset of `c-primitive-type-kwds'."
1638 t nil
1641 ;; In CORBA PSDL:
1646 of a variable declaration."
1651 ;; Adorned regexp matching `c-typedef-kwds'.
1656 "Keywords where the following name - if any - is a type name, and
1657 where the keyword together with the symbol works as a type in
1658 declarations.
1660 Note that an alternative if the second part doesn't hold is
1661 `c-type-list-kwds'. Keywords on this list are typically also present
1662 on one of the `*-decl-kwds' lists."
1663 t nil
1669 ;; Adorned regexp matching `c-type-prefix-kwds'.
1674 "Type modifier keywords. These can occur almost anywhere in types
1675 but they don't build a type of themselves. Unlike the keywords on
1676 `c-primitive-type-kwds', they are fontified with the keyword face and
1677 not the type face."
1678 t nil
1684 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1685 ;; languages without such keywords.
1691 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1692 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1702 ;; All keywords that can start a type (i.e. are either a type prefix
1703 ;; or a complete type).
1710 "Keywords introducing declarations where the following block (if any)
1711 contains another declaration level that should be considered a class.
1713 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1714 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1715 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1716 will be handled.
1718 Note that presence on this list does not automatically treat the
1719 following identifier as a type; the keyword must also be present on
1720 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1721 t nil
1729 ;; In CORBA PSDL:
1731 ;; In CORBA CIDL:
1736 ;; Regexp matching the start of a class.
1741 "Keywords introducing declarations where the following block (if
1742 any) is a brace list.
1744 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1745 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1746 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1747 will be handled."
1752 ;; Regexp matching the start of declarations where the following
1753 ;; block is a brace list.
1758 "Keywords where the following block (if any) contains another
1759 declaration level that should not be considered a class. For every
1760 keyword here, CC Mode will add a set of special syntactic symbols for
1762 `foo-open', `foo-close', and `infoo' symbols.
1764 The intention is that this category should be used for block
1765 constructs that aren't related to object orientation concepts like
1766 classes (which thus also include e.g. interfaces, templates,
1767 contracts, structs, etc). The more pragmatic distinction is that
1768 while most want some indentation inside classes, it's fairly common
1769 that they don't want it in some of these constructs, so it should be
1770 simple to configure that differently from classes. See also
1771 `c-class-decl-kwds'.
1773 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1774 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1775 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1776 will be handled."
1777 t nil
1781 ;; In CORBA CIDL:
1785 ;; Regexp matching the start of blocks besides classes that contain
1786 ;; another declaration level.
1795 'inextern-lang
1798 "Alist associating keywords in c-other-decl-block-decl-kwds with
1802 "Keywords introducing declarations where the identifier(s) being
1803 declared are types.
1805 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1806 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1807 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1808 will be handled."
1809 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1810 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1811 ;; {...}").
1814 ;; Languages that have a "typedef" construct.
1817 ;; Unlike most other languages, exception names are not handled as
1818 ;; types in IDL since they only can occur in "raises" specs.
1826 "Keywords introducing declarations where the \(first) identifier
1827 \(declarator) follows directly after the keyword, without any type.
1829 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1830 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1831 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1832 will be handled."
1833 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1834 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1835 ;; {...}").
1838 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1839 ;; `c-type-list-kwds' for IDL.
1842 ;; In CORBA PSDL:
1844 ;; In CORBA CIDL:
1850 "Keywords that can prefix normal declarations of identifiers
1851 \(and typically act as flags). Things like argument declarations
1852 inside function headers are also considered declarations in this
1853 sense.
1855 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1856 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1857 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1858 will be handled."
1859 t nil
1864 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1868 ;; In CORBA PSDL:
1870 ;; In CORBA CIDL:
1872 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1879 "Keywords that can start or prefix any declaration level construct,
1880 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1881 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1882 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1884 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1885 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1886 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1887 will be handled."
1888 t nil
1894 "Keywords that always start declarations, wherever they occur.
1895 This can be used for declarations that aren't recognized by the normal
1896 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1897 t nil
1898 ;; Classes can be declared anywhere in a Pike expression.
1902 "Keywords that can occur anywhere in a declaration level construct.
1903 This is used for self-contained things that can be tacked on anywhere
1904 on a declaration and that should be ignored to be able to recognize it
1905 correctly. Typical cases are compiler extensions like
1908 __declspec(noreturn) void foo();
1909 class __declspec(dllexport) classname {...};
1910 void foo() __attribute__((noreturn));
1912 Note that unrecognized plain symbols are skipped anyway if they occur
1913 before the type, so such things are not necessary to mention here.
1914 Mentioning them here is necessary only if they can occur in other
1915 places, or if they are followed by a construct that must be skipped
1917 examples above). In the last case, they alse need to be present on
1918 one of `c-type-list-kwds', `c-ref-list-kwds',
1919 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1920 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1921 ;; NB: These are currently not recognized in all parts of a
1922 ;; declaration. Specifically, they aren't recognized in the middle
1923 ;; of multi-token types, inside declarators, and between the
1924 ;; identifier and the arglist paren of a function declaration.
1925 ;;
1926 ;; FIXME: This ought to be user customizable since compiler stuff
1927 ;; like this usually is wrapped in project specific macros. (It'd
1928 ;; of course be even better if we could cope without knowing this.)
1929 t nil
1931 "__attribute__"
1932 ;; MSVC extension.
1936 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1941 ;; All keywords that can occur in the preamble of a declaration.
1942 ;; They typically occur before the type, but they are also matched
1943 ;; after presumptive types since we often can't be sure that
1944 ;; something is a type or just some sort of macro in front of the
1945 ;; declaration. They might be ambiguous with types or type
1946 ;; prefixes.
1959 ;; Adorned regexp of `c-prefix-spec-kwds'.
1965 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1966 ;; ambiguous with types or type prefixes. These are the keywords (like
1967 ;; extern, namespace, but NOT template) that can modify a declaration.
1976 ;; Keywords that can occur after argument list of a function header
1977 ;; declaration, i.e. in the "K&R region".
1982 ;; Adorned regexp matching all keywords that can't appear at the
1983 ;; start of a declaration.
1997 ;; The "more" for C++ is the QT keyword (as in "more slots:").
1998 ;; This variable is intended for use in c-beginning-of-statement-1.
2008 "Access protection label keywords in classes."
2009 t nil
2014 "Keywords introducing declarations that can contain a block which
2017 like that, it ends with the following ';' and not right away.
2019 The keywords on list are assumed to also be present on one of the
2020 `*-decl-kwds' lists."
2021 t nil
2026 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
2027 ;; languages without such constructs.
2034 "Keywords introducing extra declaration specifiers in the region
2036 declarations."
2037 t nil
2040 "supports"
2041 ;; In CORBA PSDL:
2045 ;; Regexp matching the keywords in `c-postfix-decl-spec-kwds'.
2051 "Keywords that may be followed by a nonsymbol sexp before whatever
2052 construct it's part of continues."
2053 t nil
2057 "Keywords that may be followed by a comma separated list of type
2058 identifiers, where each optionally can be prefixed by keywords. (Can
2059 also be used for the special case when the list can contain only one
2060 element.)
2062 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
2063 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
2064 There's also no reason to add keywords that prefixes a normal
2065 declaration consisting of a type followed by a declarator (list), so
2066 the keywords on `c-modifier-kwds' should normally not be listed here
2067 either.
2069 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2070 or variable identifier (that's being defined)."
2071 t nil
2076 ;; In CORBA PSDL:
2081 "Keywords that may be followed by a comma separated list of
2082 reference (i.e. namespace/scope/module) identifiers, where each
2083 optionally can be prefixed by keywords. (Can also be used for the
2084 special case when the list can contain only one element.) Assumed to
2085 be mutually exclusive with `c-type-list-kwds'.
2087 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
2088 or variable identifier (that's being defined)."
2089 t nil
2093 ;; In CORBA CIDL:
2098 "Keywords that may be followed (not necessarily directly) by a colon
2099 and then a comma separated list of type identifiers, where each
2100 optionally can be prefixed by keywords. (Can also be used for the
2101 special case when the list can contain only one element.)"
2102 t nil
2105 ;; In CORBA PSDL:
2109 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2110 forward to the colon. The end of the match is assumed to be directly
2112 regexp if `c-colon-type-list-kwds' isn't nil."
2114 ;; Disallow various common punctuation chars that can't come
2115 ;; before the ":" that starts the inherit list after "class"
2116 ;; or "struct" in C++. (Also used as default for other
2117 ;; languages.)
2122 "Keywords that may be followed by a parenthesis expression that doesn't
2123 contain type identifiers."
2124 t nil
2126 "__attribute__"
2127 ;; MSVC extension.
2131 "Keywords that may be followed by a parenthesis expression containing
2132 type identifiers separated by arbitrary tokens."
2133 t nil
2145 "Keywords that may be followed by an angle bracket expression
2147 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2148 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2149 if this isn't nil."
2150 t nil
2153 ;; In CORBA PSDL:
2157 "Keywords that can be followed by a C++ style template arglist; see
2158 `c-recognize-<>-arglists' for details. That language constant is
2159 assumed to be set if this isn't nil."
2160 t nil
2165 ;; All keywords that can be followed by an angle bracket sexp.
2171 ;; Adorned regexp matching keywords that can be followed by an angle
2172 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2177 "Keywords that may be followed by a brace block containing a comma
2178 separated list of identifier definitions, i.e. like the list of
2179 identifiers that follows the type in a normal declaration."
2183 "Statement keywords followed directly by a substatement."
2188 idl nil)
2191 ;; Regexp matching the start of any statement followed directly by a
2192 ;; substatement (doesn't match a bare block, however).
2197 "Statement keywords optionally followed by a paren sexp.
2198 Keywords here should also be in `c-block-stmt-1-kwds'."
2199 t nil
2203 ;; Regexp matching the start of a statement which may be followed by a
2204 ;; paren sexp and will then be followed by a substatement.
2209 "Statement keywords followed by a paren sexp and then by a substatement."
2214 idl nil
2219 ;; Regexp matching the start of any statement followed by a paren sexp
2220 ;; and then by a substatement.
2225 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2231 ;; Regexp matching the start of any statement that has a
2232 ;; substatement (except a bare block). Nil in languages that
2233 ;; don't have such constructs.
2242 "Statement keywords followed by an expression or nothing."
2245 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2247 idl nil
2254 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2259 "Statement keywords followed by a parenthesis expression that
2260 nevertheless contains a list separated with ';' and not ','."
2262 idl nil)
2265 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2270 "Statement keywords followed by an assembler expression."
2271 t nil
2275 ;; Regexp matching the start of an assembler statement. Nil in
2276 ;; languages that don't support that.
2285 awk nil)
2288 ;; Adorned regexp matching any "case"-like keyword.
2293 "Keywords introducing colon terminated labels in blocks."
2297 ;; Adorned regexp matching any keyword that introduces a label.
2302 "Keywords that might be followed by a label identifier."
2306 idl nil
2307 awk nil)
2310 "Keywords for constants."
2311 t nil
2320 "Keywords besides constants and operators that start primary expressions."
2321 t nil
2328 ;; Keywords that can occur anywhere in expressions. Built from
2329 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2333 t
2338 "Keywords that start lambda constructs, i.e. function definitions in
2339 expressions."
2340 t nil
2344 "Keywords that start constructs followed by statement blocks which can
2345 be used in expressions \(the gcc extension for this in C and C++ is
2346 handled separately by `c-recognize-paren-inexpr-blocks')."
2347 t nil
2351 "Keywords that can start classes inside expressions."
2352 t nil
2357 "Keywords that can start brace list blocks inside expressions.
2358 Note that Java specific rules are currently applied to tell this from
2359 `c-inexpr-class-kwds'."
2360 t nil
2364 ;; Regexp matching the start of a brace list in an expression, or
2365 ;; nil in languages that don't have such things. This should not
2366 ;; match brace lists recognized through `c-special-brace-lists'.
2373 ;; Regexp matching keywords in any construct that contain another
2374 ;; declaration level, i.e. that isn't followed by a function block
2375 ;; or brace list. When the first submatch matches, it's an
2376 ;; unambiguous construct, otherwise it's an ambiguous match that
2377 ;; might also be the return type of a function declaration.
2395 "Keywords that can introduce bitfields."
2396 t nil
2400 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2401 ;; languages without bitfield support.
2402 t nil
2407 "Keywords not accounted for by any other `*-kwds' language constant."
2408 t nil
2410 ;; In CORBA CIDL: (These are declaration keywords that never
2411 ;; can start a declaration.)
2414 \f
2415 ;;; Constants built from keywords.
2417 ;; Note: No `*-kwds' language constants may be defined below this point.
2421 ;; List of all the language constants that contain keyword lists.
2426 ;; Make the list of globally interned symbols
2427 ;; instead of ones interned in `c-lang-constants'.
2429 c-lang-constants)
2430 list)))
2433 ;; All keywords as a list.
2438 c-kwds-lang-consts)
2439 nil))
2443 ;; All keywords as an adorned regexp.
2448 ;; An alist with all the keywords in the cars. The cdr for each
2449 ;; keyword is a list of the symbols for the `*-kwds' lists that
2450 ;; contains it.
2456 c-kwds-lang-consts))))
2457 lang-const kwd-list kwd
2458 result-alist elem)
2470 result-alist))
2473 ;; An obarray containing all keywords as symbols. The property list
2474 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2475 ;; lists it's a member of.
2476 ;;
2477 ;; E.g. to see whether the string str contains a keyword on
2478 ;; `c-class-decl-kwds', one can do like this:
2479 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2480 ;; Which preferably is written using the associated functions in
2481 ;; cc-engine:
2482 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2484 ;; The obarray is not stored directly as a language constant since
2485 ;; the printed representation for obarrays used in .elc files isn't
2486 ;; complete.
2489 kwd lang-const-list
2496 ;; Emacs has an odd bug that causes `mapcan' to fail
2497 ;; with unintelligible errors. (XEmacs works.)
2498 ;;(mapcan (lambda (lang-const)
2499 ;; (list lang-const t))
2500 ;; lang-const-list)
2503 lang-const-list))))
2504 obarray))
2507 ;; Adorned regexp matching all keywords that should be fontified
2508 ;; with the keywords face. I.e. that aren't types or constants.
2518 ;; Regexp matching the start of any primary expression, i.e. any
2519 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2520 ;; exclude keywords; they are excluded afterwards unless the second
2521 ;; submatch matches. If the first but not the second submatch
2522 ;; matches then it is an ambiguous primary expression; it could also
2523 ;; be a match of e.g. an infix operator. (The case with ambiguous
2524 ;; keyword operators isn't handled.)
2530 ;; Filter out the special case prefix
2531 ;; operators that are close parens.
2536 t
2542 postfix-if-paren
2543 left-assoc
2544 right-assoc
2545 right-assoc-sequence)
2546 t))
2549 in-or-postfix-ops
2552 in-or-postfix-ops
2557 ;; Take out all symbol class operators from `prefix-ops' and make the
2558 ;; first submatch from them together with `c-primary-expr-kwds'.
2565 ;; Match all ambiguous operators.
2572 ;; Now match all other symbols.
2576 ;; The chars that can start integer and floating point
2577 ;; constants.
2581 ;; The unambiguous operators from `prefix-ops'.
2587 ;; Match string and character literals.
2594 \f
2595 ;;; Additional constants for parser-level constructs.
2598 "Regexp matching a keyword that is followed by a colon, where
2599 the whole construct can precede a declaration.
2607 "Regexp matching something that might precede a declaration, cast or
2608 label, such as the last token of a preceding statement or declaration.
2609 This is used in the common situation where a declaration or cast
2610 doesn't start with any specific token that can be searched for.
2612 The regexp should not match bob; that is done implicitly. It can't
2613 require a match longer than one token. The end of the token is taken
2614 to be at the end of the first submatch, which is assumed to always
2615 match. It's undefined whether identifier syntax (see
2616 `c-identifier-syntax-table') is in effect or not. This regexp is
2617 assumed to be a superset of `c-label-prefix-re' if
2618 `c-recognize-colon-labels' is set.
2620 Besides this, `c-decl-start-kwds' is used to find declarations.
2622 Note: This variable together with `c-decl-start-re' and
2624 declaration/cast/label starts. I.e. they might produce more matches
2625 but should not miss anything (or else it's necessary to use text
2626 properties - see the next note). Wherever they match, the following
2627 construct is analyzed to see if it indeed is a declaration, cast or
2628 label. That analysis is not cheap, so it's important that not too
2629 many false matches are triggered.
2631 Note: If a declaration/cast/label start can't be detected with this
2632 variable, it's necessary to use the `c-type' text property with the
2633 value `c-decl-end' on the last char of the last token preceding the
2634 declaration. See the comment blurb at the start of cc-engine.el for
2635 more info."
2637 ;; We match a sequence of characters to skip over things like \"};\"
2638 ;; more quickly. We match ")" in C for K&R region declarations, and
2639 ;; in all languages except Java for when a cpp macro definition
2640 ;; begins with a declaration.
2643 ;; Match "<" in C++ to get the first argument in a template arglist.
2644 ;; In that case there's an additional check in `c-find-decl-spots'
2645 ;; that it got open paren syntax. Match ":" to aid in picking up
2646 ;; "public:", etc. This involves additional checks in
2647 ;; `c-find-decl-prefix-search' to prevent a match of identifiers
2648 ;; or labels.
2650 ;; Additionally match the protection directives in Objective-C.
2651 ;; Note that this doesn't cope with the longer directives, which we
2652 ;; would have to match from start to end since they don't end with
2653 ;; any easily recognized characters.
2657 ;; Pike is like C but we also match "[" for multiple value
2658 ;; assignments and type casts.
2664 "Regexp matching the start of any declaration, cast or label.
2665 It's used on the token after the one `c-decl-prefix-re' matched. This
2666 regexp should not try to match those constructs accurately as it's
2667 only used as a sieve to avoid spending more time checking other
2668 constructs."
2673 ;; Regexp matching something that might precede or start a
2674 ;; declaration, cast or label.
2675 ;;
2676 ;; If the first submatch matches, it's taken to match the end of a
2677 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2678 ;; It's built from `c-decl-prefix-re'.
2679 ;;
2680 ;; If the first submatch did not match, the match of the whole
2681 ;; regexp is taken to be at the first token in the declaration.
2682 ;; `c-decl-start-re' is not checked in this case.
2683 ;;
2684 ;; Design note: The reason the same regexp is used to match both
2685 ;; tokens that precede declarations and start them is to avoid an
2686 ;; extra regexp search from the previous declaration spot in
2687 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2688 ;; that it finds all declaration/cast/label starts in approximately
2689 ;; linear order, so we can't do the searches in two separate passes.
2700 ;; List containing the paren characters that can open a cast, or nil in
2701 ;; languages without casts.
2709 "List of syntactically relevant characters that never can occur before
2710 the open brace in any construct that contains a brace block, e.g. in
2713 class Foo: public Bar {int x();} a, *b;
2715 If parens can occur, the chars inside those aren't filtered with this
2716 list.
2718 '<' and '>' should be disallowed even if angle bracket arglists can
2719 occur. That since the search function needs to stop at them anyway to
2720 ensure they are given paren syntax.
2722 This is used to skip backward from the open brace to find the region
2725 possible for good performance."
2727 ;; Default to all chars that only occurs in nonsymbol tokens outside
2728 ;; identifiers.
2734 t
2735 t
2739 op pos)
2742 res))))
2744 ;; Allow cpp operations (where applicable).
2750 ;; Allow ':' for inherit list starters.
2754 ;; Allow ',' for multiple inherits.
2758 ;; Allow parentheses for anonymous inner classes in Java and class
2759 ;; initializer lists in Pike.
2763 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2768 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2769 ;; for `c-syntactic-skip-backward'.
2774 "Regexp matching the declarator operators that might precede the
2777 The end of the first submatch is taken as the end of the operator.
2778 Identifier syntax is in effect when this is matched \(see
2779 `c-identifier-syntax-table')."
2782 ;; Default to a regexp that never matches.
2784 ;; Check that there's no "=" afterwards to avoid matching tokens
2785 ;; like "*=".
2787 "[*\(]"
2793 "[*\(&]"
2798 ;; If this matches there's special treatment in
2799 ;; `c-font-lock-declarators' and
2800 ;; `c-font-lock-declarations' that check for a
2801 ;; complete name followed by ":: *".
2811 "Regexp matching the declarator operators that might follow after the
2814 it matches an open paren of some kind, the type declaration check
2815 continues at the corresponding close paren, otherwise the end of the
2816 first submatch is taken as the end of the operator. Identifier syntax
2817 is in effect when this is matched (see `c-identifier-syntax-table')."
2818 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2819 ;; function argument list parenthesis.
2827 "[\)\[\(]"
2831 ;; "throw" in `c-type-modifier-kwds' is followed
2832 ;; by a parenthesis list, but no extra measures
2833 ;; are necessary to handle that.
2844 "This regexp is matched after a declarator expression where
2845 `c-type-decl-suffix-key' has matched. If it matches then the
2846 construct is taken as a declaration. It's typically used to match the
2847 beginning of a function body or whatever might occur after the
2848 function header in a function declaration or definition. It's
2849 undefined whether identifier syntax (see `c-identifier-syntax-table')
2850 is in effect or not.
2855 t "{"
2856 ;; If K&R style declarations should be recognized then one could
2857 ;; consider to match the start of any symbol since we want to match
2858 ;; the start of the first declaration in the "K&R region". That
2859 ;; could however produce false matches on code like "FOO(bar) x"
2860 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2861 ;; on the other heuristics in that case.
2863 ;; Add on the keywords in `c-postfix-spec-kwds'.
2868 ;; Also match the colon that starts a base class initializer list in
2869 ;; C++. That can be confused with a function call before the colon
2870 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2871 ;; match before such a thing (as a declaration-level construct;
2872 ;; matches inside arglist contexts are already excluded).
2879 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2880 ;; matches ";" and ",".
2889 end of the operator. nil in languages without such operators. It's
2890 undefined whether identifier syntax (see `c-identifier-syntax-table')
2891 is in effect or not."
2892 t nil
2898 "Regexp matching operators that might follow after a type, or nil in
2899 languages that don't have such operators. The end of the first
2900 submatch is taken as the end of the operator. This should not match
2901 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2902 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2903 is in effect or not."
2904 t nil
2910 ;; Regexp matching the known type identifiers. This is initialized
2911 ;; from the type keywords and `*-font-lock-extra-types'. The first
2912 ;; submatch is the one that matches the type. Note that this regexp
2913 ;; assumes that symbol constituents like '_' and '$' have word
2914 ;; syntax.
2923 extra-types)))
2929 extra-types))))
2934 plain-strings)))
2935 regexp-strings)
2940 "List of open- and close-chars that makes up a pike-style brace list,
2942 list."
2943 t nil
2948 "Non-nil means K&R style argument declarations are valid."
2949 t nil
2950 c t)
2954 "Non-nil means function declarations without return type should be
2955 recognized. That can introduce an ambiguity with parenthesized macro
2956 calls before a brace block. This setting does not affect declarations
2957 that are preceded by a declaration starting keyword, so
2958 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2959 t nil
2965 "Non-nil means C++ style template arglists should be handled. More
2966 specifically, this means a comma separated list of types or
2968 identifier or one of the keywords on `c-<>-type-kwds' or
2969 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2970 expression is considered to be a type."
2973 java t)
2977 "Non-nil means that an enum structure can contain declarations."
2978 t nil
2979 java t)
2983 "Non-nil means that parenthesis style initializers exist,
2984 i.e. constructs like
2986 Foo bar (gnu);
2988 in addition to the more classic
2990 Foo bar = gnu;"
2991 t nil
2996 "Non-nil to recognize gcc style in-expression blocks,
2997 i.e. compound statements surrounded by parentheses inside expressions."
2998 t nil
3004 ;; Regexp matching the start of angle bracket arglists in languages
3005 ;; where `c-recognize-<>-arglists' is set. Does not exclude
3006 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
3007 ;; assumed to surround the preceding symbol. The whole match is
3008 ;; assumed to end directly after the opening "<".
3018 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
3019 ;; parens. The first submatch is assumed to surround
3020 ;; `c-opt-<>-arglist-start'.
3029 ;; Regexp matching the beginning of a declaration specifier in the
3030 ;; region between the header and the body of a declaration.
3031 ;;
3032 ;; TODO: This is currently not used uniformly; c++-mode and
3033 ;; java-mode each have their own ways of using it.
3034 t nil
3047 That includes labels in code and access keys in classes. This does
3048 not apply to labels recognized by `c-label-kwds' and
3049 `c-opt-extra-label-key'."
3050 t nil
3056 "Regexp like `c-decl-prefix-re' that matches any token that can precede
3057 a generic colon label. Not used if `c-recognize-colon-labels' is
3058 nil."
3064 "Regexp matching things that can't occur in generic colon labels,
3065 neither in a statement nor in a declaration context. The regexp is
3066 tested at the beginning of every sexp in a suspected label,
3069 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
3075 ;; Don't allow string literals, except in AWK. Character constants are OK.
3078 ;; Also check for open parens in C++, to catch member init lists in
3079 ;; constructors. We normally allow it so that macros with arguments
3080 ;; work in labels.
3085 "Regexp matching things that can't occur two symbols before a colon in
3093 "Optional regexp matching labels.
3094 Normally, labels are detected according to `c-nonlabel-token-key',
3095 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
3096 be used if there are additional labels that aren't recognized that
3097 way."
3098 t nil
3103 ;; Regexp describing friend declarations classes, or nil in
3104 ;; languages that don't have such things.
3105 ;;
3106 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
3107 ;; template skipping isn't done properly. This will disappear soon.
3108 t nil
3113 "<.+>"
3115 "friend"
3120 ;; Special regexp to match the start of Objective-C methods. The
3121 ;; first submatch is assumed to end after the + or - key.
3122 t nil
3124 ;; TODO: Ought to use a better method than anchoring on bol.
3129 "([^\)]*)"
3136 ;; Must be set in buffers where the `c-type' text property might be
3137 ;; used with the value `c-decl-end'.
3138 ;;
3139 ;; `c-decl-end' is used to mark the ends of labels and access keys
3140 ;; to make interactive refontification work better.
3143 ;; `c-decl-end' is used to mark the end of the @-style directives in
3144 ;; Objective-C.
3145 objc t)
3148 \f
3149 ;;; Wrap up the `c-lang-defvar' system.
3151 ;; Compile in the list of language variables that has been collected
3152 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3153 ;; first element of each is nil.
3157 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3158 ;; These are typically standard emacs variables such as `comment-start'.
3166 "Create a function that initializes all the language dependent variables
3167 for the given mode.
3169 This function should be evaluated at compile time, so that the
3170 function it returns is byte compiled with all the evaluated results
3171 from the language constants. Use the `c-init-language-vars' macro to
3172 accomplish that conveniently."
3178 ;; No need to byte compile this lambda since the byte compiler is
3179 ;; smart enough to detect the `funcall' construct in the
3180 ;; `c-init-language-vars' macro below and compile it all straight
3181 ;; into the function that contains `c-init-language-vars'.
3184 ;; This let sets up the context for `c-mode-var' and similar
3185 ;; that could be in the result from `c--macroexpand-all'.
3187 current-var source-eval)
3194 ;; `c-lang-const' will expand to the evaluated
3195 ;; constant immediately in `c--macroexpand-all'
3196 ;; below.
3202 ;; Note: The following `append' copies the
3203 ;; first argument. That list is small, so
3204 ;; this doesn't matter too much.
3208 ;; This diagnostic message isn't useful for end
3209 ;; users, so it's disabled.
3210 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3211 ;; (message ,(concat "%s compiled with CC Mode %s "
3212 ;; "but loaded with %s - evaluating "
3213 ;; "language constants from source")
3214 ;; ',mode ,c-version c-version)
3215 ;; (put ',mode 'c-has-warned-lang-consts t))
3228 current-var
3231 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3234 err)
3237 ;; Being evaluated from source. Always use the dynamic method to
3238 ;; work well when `c-lang-defvar's in this file are reevaluated
3239 ;; interactively.
3245 current-var)
3257 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3258 current-var err)
3260 ))
3263 "Initialize all the language dependent variables for the given mode.
3264 This macro is expanded at compile time to a form tailored for the mode
3265 in question, so MODE must be a constant. Therefore MODE is not
3266 evaluated and should not be quoted."
3269 \f
3272 ;;; cc-langs.el ends here