| blob | 86a963bcf558b2f26496a4fb56364cc6fbdddcef |
1 ;;; cc-langs.el --- language specific settings for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2011 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 "----"
309 subword-mode)])))
311 \f
312 ;;; Syntax tables.
315 "Populate the given syntax table as necessary for a C-like language.
333 ;; Set up block and line oriented comments. The new C
334 ;; standard mandates both comment styles even in C, so since
335 ;; all languages now require dual comments, we make this the
336 ;; default.
338 ;; XEmacs
342 ;; Emacs
346 ;; incompatible
350 ;; Give CR the same syntax as newline, for selective-display
354 "Functions that generates the mode specific syntax tables.
355 The syntax tables aren't stored directly since they're quite large."
359 ;; Mode specific syntaxes.
361 ;; Let '@' be part of symbols in ObjC to cope with
362 ;; its compiler directives as single keyword tokens.
363 ;; This is then necessary since it's assumed that
364 ;; every keyword is a single symbol.
368 table)))
371 ;; The syntax tables in evaluated form. Only used temporarily when
372 ;; the constants in this file are evaluated.
376 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
377 ;; parenthesis characters. Used temporarily when template argument
378 ;; lists are parsed. Note that this encourages incorrect parsing of
379 ;; templates since they might contain normal operators that uses the
380 ;; '<' and '>' characters. Therefore this syntax table might go
381 ;; away when CC Mode handles templates correctly everywhere.
382 t nil
387 table)))
393 ;; A variant of the standard syntax table which is used to find matching
394 ;; "<"s and ">"s which have been marked as parens using syntax table
395 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
396 ;; non-paren syntax here. so that the list commands will work on "< ... >"
397 ;; even when there's unbalanced other parens inside them.
398 ;;
399 ;; This variable is nil for languages which don't have template stuff.
409 table))))
414 "A list that describes the modifications that should be done to the
415 mode syntax table to get a syntax table that matches all identifiers
416 and keywords as words.
418 The list is just like the one used in `font-lock-defaults': Each
419 element is a cons where the car is the character to modify and the cdr
420 the new syntax, as accepted by `modify-syntax-entry'."
421 ;; The $ character is not allowed in most languages (one exception
422 ;; is Java which allows it for legacy reasons) but we still classify
423 ;; it as an indentifier character since it's often used in various
424 ;; machine generated identifiers.
435 mod)
440 table)
441 "Syntax table built on the mode syntax table but additionally
442 classifies symbol constituents like '_' and '$' as word constituents,
446 ;; For documentation see the following c-lang-defvar of the same name.
447 ;; The value here may be a list of functions or a single function.
448 t nil
451 ;; java 'c-before-change-check-<>-operators
456 fs
458 "If non-nil, a list of functions called from c-before-change-hook.
459 Typically these will record enough state to allow
460 `c-before-font-lock-function' to extend the region to fontify,
461 and may do such things as removing text-properties which must be
462 recalculated.
464 These functions will be run in the order given. Each of them
465 takes 2 parameters, the BEG and END supplied to every
466 before-change function; on entry, the buffer will have been
467 widened and match-data will have been saved; point is undefined
468 on both entry and exit; the return value is ignored.
470 The functions are called even when font locking isn't enabled.
472 When the mode is initialized, the functions are called with
476 "If non-nil, a function called just before font locking.
477 Typically it will extend the region about to be fontified \(see
478 below) and will set `syntax-table' text properties on the region.
480 It takes 3 parameters, the BEG, END, and OLD-LEN supplied to
481 every after-change function; point is undefined on both entry and
482 exit; on entry, the buffer will have been widened and match-data
483 will have been saved; the return value is ignored.
485 The function may extend the region to be fontified by setting the
486 buffer local variables c-new-BEG and c-new-END.
488 The function is called even when font locking is disabled.
490 When the mode is initialized, this function is called with
491 parameters \(point-min), \(point-max) and <buffer size>."
492 t nil
498 \f
499 ;;; Lexer-level syntax (identifiers, tokens etc).
502 "Regexp that matches the start of a symbol, i.e. any identifier or
504 operator at the top level."
512 "Set of characters that can be part of a symbol.
513 This is on the form that fits inside [ ] in a regexp."
514 ;; Pike note: With the backquote identifiers this would include most
515 ;; operator chars too, but they are handled with other means instead.
520 "Regexp matching identifiers and keywords (with submatch 0). Assumed
521 to match if `c-symbol-start' matches on the same position."
525 ;; Use the value from C here since the operator backquote is
526 ;; covered by the other alternative.
534 ;; Number of regexp grouping parens in `c-symbol-key'.
538 "This is the set of chars that can't be part of a symbol, i.e. the
539 negation of `c-symbol-chars'."
544 "Regexp that matches any character that can't be part of a symbol.
545 It's usually appended to other regexps to avoid matching a prefix.
546 It's assumed to not contain any submatchers."
547 ;; The same thing regarding Unicode identifiers applies here as to
548 ;; `c-symbol-key'.
552 "The operators that make up fully qualified identifiers. nil in
553 languages that don't have such things. See `c-operators' for a
554 description of the format. Binary operators can concatenate symbols,
558 This value is by default merged into `c-operators'."
559 t nil
563 ;; Java has "." to concatenate identifiers but it's also used for
564 ;; normal indexing. There's special code in the Java font lock
565 ;; rules to fontify qualified identifiers based on the standard
566 ;; naming conventions. We still define "." here to make
567 ;; `c-forward-name' move over as long names as possible which is
568 ;; necessary to e.g. handle throws clauses correctly.
577 ;; Appendable adorned regexp matching the operators that join
578 ;; symbols to fully qualified identifiers, or nil in languages that
579 ;; don't have such things.
580 ;;
581 ;; This was a docstring constant in 5.30. It still works but is now
582 ;; considered internal - change `c-identifier-ops' instead.
585 t)))
593 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
597 ;; Appendable adorned regexp matching operators that might precede
598 ;; an identifier and that are part of the identifier in that case.
599 ;; nil in languages without such things.
602 t)))
607 "Operators that can occur after a binary operator on `c-identifier-ops'
608 in identifiers. nil in languages that don't have such things.
610 Operators here should also have appropriate entries in `c-operators' -
611 it's not taken care of by default."
612 t nil
613 ;; '~' for destructors in C++, '*' for member pointers.
615 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
616 ;; in import declarations. (This will also match bogus things like
617 ;; "foo.*bar" but we don't bother.)
621 ;; Regexp that must match the token after
622 ;; `c-opt-identifier-concat-key' for it to be considered an
623 ;; identifier concatenation operator (which e.g. causes the
624 ;; preceding identifier to be fontified as a reference). Assumed to
625 ;; be a string if `c-opt-identifier-concat-key' is.
626 ;;
627 ;; This was a docstring constant in 5.30. It still works but is now
628 ;; considered internal - change `c-after-id-concat-ops' instead.
636 "Regexp that matches the start of an (optionally qualified) identifier.
637 It should also match all keywords. It's unspecified how far it
638 matches."
648 C++. It does not recognize the full range of syntactic whitespace
649 between the tokens; `c-forward-name' has to be used for that. It
650 should also not match identifiers containing parenthesis groupings,
652 ;; This regexp is more complex than strictly necessary to ensure
653 ;; that it can be matched with a minimum of backtracking.
674 ;; For flexibility, consider the symbol match
675 ;; optional if we've hit a
676 ;; `c-after-id-concat-ops' operator. This is
677 ;; also necessary to handle the "*" that can
678 ;; end import declaration identifiers in Java.
692 ;; This was a docstring constant in 5.30 but it's no longer used.
693 ;; It's only kept to avoid breaking third party code.
694 ;;
695 ;; Used to identify the submatch in `c-identifier-key' that
696 ;; surrounds the last symbol in the qualified identifier. It's a
697 ;; list of submatch numbers, of which the first that has a match is
698 ;; taken. It's assumed that at least one does when the regexp has
699 ;; matched.
700 t nil)
703 "Set if the language support backslash escaped newlines inside string
704 literals."
705 t nil
711 "Set if the language supports multiline string literals without escaped
712 newlines. If t, all string literals are multiline. If a character,
713 only literals where the open quote is immediately preceded by that
714 literal are multiline."
715 t nil
716 pike ?#)
721 "Regexp matching the prefix of a cpp directive in the languages that
722 normally use that macro preprocessor. Tested at bol or at boi.
724 ;; TODO (ACM, 2005-04-01). Amend the following to recognise escaped NLs;
725 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
731 "Regexp matching the prefix of a cpp directive anchored to BOL,
732 in the languages that have a macro preprocessor."
738 "Regexp matching the prefix of a cpp directive including the directive
739 name, or nil in languages without preprocessor support. The first
740 submatch surrounds the directive name."
744 ;; Pike, being a scripting language, recognizes hash-bangs too.
750 "List of cpp directives (without the prefix) that are followed by a
751 string message."
757 "List of cpp directives (without the prefix) that are followed by a
758 file name in angle brackets or quotes."
764 "Cpp directive (without the prefix) that is followed by a macro
765 definition, or nil if the language doesn't have any."
770 ;; Regexp matching everything up to the macro body of a cpp define, or the
771 ;; end of the logical line if there is none. Submatch 1 is the name of the
772 ;; macro. Set if c-opt-cpp-macro-define is.
777 ;; ^ ^ #defined name
783 ;; Regexp matching everything up to the end of the identifier defined
784 ;; by a cpp define.
793 "List of cpp directives (without the prefix) that are followed by an
794 expression."
799 "List of functions in cpp expressions."
805 "List of all assignment operators."
811 idl nil)
814 "List describing all operators, along with their precedence and
815 associativity. The order in the list corresponds to the precedence of
816 the operators: The operators in each element are a group with the same
817 precedence, and the group has higher precedence than the groups in all
818 following elements. The car of each element describes the type of the
819 operator group, and the cdr is a list of the operator tokens in it.
820 The operator group types are:
822 'prefix Unary prefix operators.
823 'postfix Unary postfix operators.
824 'postfix-if-paren
825 Unary postfix operators if and only if the chars have
826 parenthesis syntax.
827 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
828 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
829 'right-assoc-sequence
830 Right associative operator that constitutes of a
831 sequence of tokens that separate expressions. All the
832 tokens in the group are in this case taken as
833 describing the sequence in one such operator, and the
834 order between them is therefore significant.
836 Operators containing a character with paren syntax are taken to match
837 with a corresponding open/close paren somewhere else. A postfix
838 operator with close paren syntax is taken to end a postfix expression
839 started somewhere earlier, rather than start a new one at point. Vice
840 versa for prefix operators with open paren syntax.
843 often are described as postfix operators are considered binary here,
844 since CC Mode treats every identifier as an expression."
846 ;; There's currently no code in CC Mode that exploit all the info
847 ;; in this variable; precedence, associativity etc are present as a
848 ;; preparation for future work.
859 ;; Primary.
868 ;; Postfix.
870 ;; The following need special treatment.
880 ;; Unary.
887 ;; The following need special treatment.
898 ;; Member selection.
902 ;; Multiplicative.
905 ;; Additive.
908 ;; Shift.
913 ;; Relational.
918 ;; Equality.
922 ;; Bitwise and.
926 ;; Bitwise exclusive or.
932 ;; Bitwise or.
938 ;; Logical and.
942 ;; Logical or.
948 ;; Conditional.
951 ;; Assignment.
954 ;; Exception.
958 ;; Sequence.
961 ;; IDL got its own definition since it has a much smaller operator
962 ;; set than the other languages.
966 ;; Primary.
968 ;; Unary.
970 ;; Multiplicative.
972 ;; Additive.
974 ;; Shift.
976 ;; And.
978 ;; Xor.
980 ;; Or.
984 ;; The operators as a flat list (without duplicates).
990 t nil
999 ;; These work like identifiers in Pike.
1006 ;; Regexp tested after an "operator" token in C++.
1007 t nil
1013 "Regexp matching the token before the ones in
1014 `c-overloadable-operators' when operators are specified in their
1017 languages without operator functions or where the complete operator
1018 identifier is listed in `c-overloadable-operators'.
1020 This regexp is assumed to not match any non-operator identifier."
1021 t nil
1026 ;; Note: the following alias is an old name which was a mis-spelling. It has
1027 ;; been corrected above and throughout cc-engine.el. It will be removed at
1028 ;; some release very shortly in the future. ACM, 2006-04-14.
1034 "List of the tokens made up of characters in the punctuation or
1035 parenthesis syntax classes that have uses other than as expression
1036 operators."
1054 ;; List of all tokens in the punctuation and parenthesis syntax
1055 ;; classes.
1061 ;; List containing all chars not in the word, symbol or
1062 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1063 ;; parenthesis and string delimiter chars.
1065 ;; Only go through the chars in the printable ASCII range. No
1066 ;; language so far has 8-bit or widestring operators.
1072 list)))
1075 ;; Regexp matching all tokens in the punctuation and parenthesis
1076 ;; syntax classes. Note that this also matches ".", which can start
1077 ;; a float.
1080 t
1086 ;; Regexp matching all assignment operators and only them. The
1087 ;; beginning of the first submatch is used to detect the end of the
1088 ;; token, along with the end of the whole match.
1091 ;; Need special case for "=" since it's a prefix of "==".
1103 ;; Regexp matching all tokens containing "<" or ">" which are longer
1104 ;; than one char.
1107 t
1113 ;; Regexp matching the second and subsequent characters of all
1114 ;; multicharacter tokens that begin with "<".
1117 t
1124 ;; Regexp matching the second and subsequent characters of all
1125 ;; multicharacter tokens that begin with ">".
1128 t
1133 t
1140 ;; The characters that should be considered to bound statements. To
1141 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1142 ;; begin with "^" to negate the set. If ? : operators should be
1143 ;; detected then the string must end with "?:".
1144 t "^;{}?:"
1149 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1150 t "^;,{}?:"
1155 \f
1156 ;;; Syntactic whitespace.
1159 "Regexp matching an ordinary whitespace character.
1161 ;; "\\s " is not enough since it doesn't match line breaks.
1165 ;; Number of regexp grouping parens in `c-simple-ws'.
1169 "String that starts line comments, or nil if such don't exist.
1170 Line comments are always terminated by newlines. At least one of
1171 `c-block-comment-starter' and this one is assumed to be set.
1173 Note that it's currently not enough to set this to support a new
1174 comment style. Other stuff like the syntax table must also be set up
1175 properly."
1176 t "//"
1181 "String that starts block comments, or nil if such don't exist.
1182 Block comments are ended by `c-block-comment-ender', which is assumed
1183 to be set if this is. At least one of `c-line-comment-starter' and
1184 this one is assumed to be set.
1186 Note that it's currently not enough to set this to support a new
1187 comment style. Other stuff like the syntax table must also be set up
1188 properly."
1189 t "/*"
1190 awk nil)
1193 "String that ends block comments, or nil if such don't exist.
1195 Note that it's currently not enough to set this to support a new
1196 comment style. Other stuff like the syntax table must also be set up
1197 properly."
1198 t "*/"
1199 awk nil)
1202 ;; Regexp to match the start of any type of comment.
1208 re)))
1211 ;;;; Added by ACM, 2003/9/18.
1213 ;; Regexp which matches the start of a block comment (if such exists in the
1214 ;; language)
1222 ;; Regexp to match the start of comments and string literals.
1231 "Regexp to match the start of documentation comments."
1233 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1241 "String that starts comments inserted with M-; etc.
1242 `comment-start' is initialized from this."
1243 ;; Default: Prefer line comments to block comments, and pad with a space.
1247 ;; In C we still default to the block comment style since line
1248 ;; comments aren't entirely portable.
1253 "String that ends comments inserted with M-; etc.
1254 `comment-end' is initialized from this."
1255 ;; Default: Use block comment style if comment-start uses block
1256 ;; comments, and pad with a space in that case.
1266 "Regexp to match the start of a comment plus everything up to its body.
1267 `comment-start-skip' is initialized from this."
1268 ;; Default: Allow the last char of the comment starter(s) to be
1269 ;; repeated, then allow any amount of horizontal whitespace.
1282 ;; Regexp matching any sequence that can start syntactic whitespace.
1283 ;; The only uncertain case is '#' when there are cpp directives.
1297 ;; Regexp matching any single character that might end syntactic whitespace.
1312 ;; Regexp matching an unterminated block comment that doesn't
1313 ;; contain line breaks, or nil in languages without block comments.
1314 ;; Does not contain a \| operator at the top level.
1318 ;; It's messy to cook together a regexp that matches anything
1319 ;; but c-block-comment-ender.
1327 "[^"
1328 ;; The quoting rules inside char classes are silly. :P
1337 "]"
1345 ;; Regexp matching a block comment that doesn't contain line breaks,
1346 ;; or nil in languages without block comments. The reason we don't
1347 ;; allow line breaks is to avoid going very far and risk running out
1348 ;; of regexp stack; this regexp is intended to handle only short
1349 ;; comments that might be put in the middle of limited constructs
1350 ;; like declarations. Does not contain a \| operator at the top
1351 ;; level.
1366 ;; Regexp matching a piece of syntactic whitespace that isn't a
1367 ;; sequence of simple whitespace characters. As opposed to
1368 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1369 ;; directives as syntactic whitespace.
1381 ;; Regexp matching syntactic whitespace, including possibly the
1382 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1383 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1384 ;; not contain a \| operator at the top level.
1392 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1396 ;; Regexp matching syntactic whitespace, which is at least one
1397 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1398 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1399 ;; not contain a \| operator at the top level.
1407 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1411 ;; Regexp matching syntactic whitespace without any line breaks. As
1412 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1413 ;; regard cpp directives as syntactic whitespace. Does not contain
1414 ;; a \| operator at the top level.
1422 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1426 ;; Regexp that matches when there is no syntactically significant
1427 ;; text before eol. Macros are regarded as syntactically
1428 ;; significant text here.
1430 ;; Match eol (possibly inside a block comment or preceded
1431 ;; by a line continuation backslash), or the beginning of a
1432 ;; line comment. Note: This has to be modified for awk
1433 ;; where line comments start with '#'.
1447 \f
1448 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
1451 Such a function takes one optional parameter, a buffer position (defaults to
1452 point), and returns nil or t. This variable contains nil for languages which
1453 don't have EOL terminated statements. "
1454 t nil
1460 The (admittedly kludgey) purpose of such a function is to prevent an infinite
1461 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
1462 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
1463 even indirectly. This variable contains nil for languages which don't have
1464 EOL terminated statements."
1465 t nil
1470 \f
1471 ;;; Defun functions
1473 ;; The Emacs variables beginning-of-defun-function and
1474 ;; end-of-defun-function will be set so that commands like
1475 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1476 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1477 ;; functions, allowing optimisation for large n.
1479 "Function to which beginning-of-defun-function will be set."
1480 t 'c-beginning-of-defun
1486 "Function to which end-of-defun-function will be set."
1487 t 'c-end-of-defun
1490 \f
1491 ;;; In-comment text handling.
1494 "Regexp to append to `paragraph-start'."
1495 t "$"
1501 "Regexp to append to `paragraph-separate'."
1502 t "$"
1506 \f
1507 ;;; Keyword lists.
1509 ;; Note: All and only all language constants containing keyword lists
1510 ;; should end with "-kwds"; they're automatically collected into the
1511 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1514 "Primitive type keywords. As opposed to the other keyword lists, the
1515 keywords listed here are fontified with the type face instead of the
1516 keyword face.
1518 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1519 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1520 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1521 will be handled.
1523 Do not try to modify this list for end user customizations; the
1524 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1525 the appropriate place for that."
1534 ;; Objective-C extends C, but probably not the new stuff in C99.
1541 ;; In CORBA PSDL:
1542 "ref"
1543 ;; The following can't really end a type, but we have to specify them
1544 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1545 ;; doesn't matter that much.
1548 ;; used as a builtin type.
1553 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1558 "Keywords that might act as prefixes for primitive types. Assumed to
1559 be a subset of `c-primitive-type-kwds'."
1560 t nil
1563 ;; In CORBA PSDL:
1568 of a variable declaration."
1573 ;; Adorned regexp matching `c-typedef-kwds'.
1578 "Keywords where the following name - if any - is a type name, and
1579 where the keyword together with the symbol works as a type in
1580 declarations.
1582 Note that an alternative if the second part doesn't hold is
1583 `c-type-list-kwds'. Keywords on this list are typically also present
1584 on one of the `*-decl-kwds' lists."
1585 t nil
1591 ;; Adorned regexp matching `c-type-prefix-kwds'.
1596 "Type modifier keywords. These can occur almost anywhere in types
1597 but they don't build a type of themselves. Unlike the keywords on
1598 `c-primitive-type-kwds', they are fontified with the keyword face and
1599 not the type face."
1600 t nil
1606 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1607 ;; languages without such keywords.
1613 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1614 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1624 ;; All keywords that can start a type (i.e. are either a type prefix
1625 ;; or a complete type).
1632 "Keywords introducing declarations where the following block (if any)
1633 contains another declaration level that should be considered a class.
1635 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1636 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1637 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1638 will be handled.
1640 Note that presence on this list does not automatically treat the
1641 following identifier as a type; the keyword must also be present on
1642 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1643 t nil
1651 ;; In CORBA PSDL:
1653 ;; In CORBA CIDL:
1658 ;; Regexp matching the start of a class.
1663 "Keywords introducing declarations where the following block (if
1664 any) is a brace list.
1666 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1667 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1668 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1669 will be handled."
1674 ;; Regexp matching the start of declarations where the following
1675 ;; block is a brace list.
1680 "Keywords where the following block (if any) contains another
1681 declaration level that should not be considered a class. For every
1682 keyword here, CC Mode will add a set of special syntactic symbols for
1684 `foo-open', `foo-close', and `infoo' symbols.
1686 The intention is that this category should be used for block
1687 constructs that aren't related to object orientation concepts like
1688 classes (which thus also include e.g. interfaces, templates,
1689 contracts, structs, etc). The more pragmatic distinction is that
1690 while most want some indentation inside classes, it's fairly common
1691 that they don't want it in some of these constructs, so it should be
1692 simple to configure that differently from classes. See also
1693 `c-class-decl-kwds'.
1695 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1696 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1697 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1698 will be handled."
1699 t nil
1703 ;; In CORBA CIDL:
1707 ;; Regexp matching the start of blocks besides classes that contain
1708 ;; another declaration level.
1717 'inextern-lang
1720 "Alist associating keywords in c-other-decl-block-decl-kwds with
1724 "Keywords introducing declarations where the identifier(s) being
1725 declared are types.
1727 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1728 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1729 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1730 will be handled."
1731 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1732 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1733 ;; {...}").
1736 ;; Languages that have a "typedef" construct.
1739 ;; Unlike most other languages, exception names are not handled as
1740 ;; types in IDL since they only can occur in "raises" specs.
1748 "Keywords introducing declarations where the \(first) identifier
1749 \(declarator) follows directly after the keyword, without any type.
1751 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1752 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1753 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1754 will be handled."
1755 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1756 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1757 ;; {...}").
1760 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1761 ;; `c-type-list-kwds' for IDL.
1764 ;; In CORBA PSDL:
1766 ;; In CORBA CIDL:
1772 "Keywords that can prefix normal declarations of identifiers
1773 \(and typically act as flags). Things like argument declarations
1774 inside function headers are also considered declarations in this
1775 sense.
1777 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1778 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1779 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1780 will be handled."
1781 t nil
1786 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1790 ;; In CORBA PSDL:
1792 ;; In CORBA CIDL:
1794 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1801 "Keywords that can start or prefix any declaration level construct,
1802 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1803 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1804 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1806 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1807 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1808 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1809 will be handled."
1810 t nil
1816 "Keywords that always start declarations, wherever they occur.
1817 This can be used for declarations that aren't recognized by the normal
1818 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1819 t nil
1820 ;; Classes can be declared anywhere in a Pike expression.
1824 "Keywords that can occur anywhere in a declaration level construct.
1825 This is used for self-contained things that can be tacked on anywhere
1826 on a declaration and that should be ignored to be able to recognize it
1827 correctly. Typical cases are compiler extensions like
1830 __declspec(noreturn) void foo();
1831 class __declspec(dllexport) classname {...};
1832 void foo() __attribute__((noreturn));
1834 Note that unrecognized plain symbols are skipped anyway if they occur
1835 before the type, so such things are not necessary to mention here.
1836 Mentioning them here is necessary only if they can occur in other
1837 places, or if they are followed by a construct that must be skipped
1839 examples above). In the last case, they alse need to be present on
1840 one of `c-type-list-kwds', `c-ref-list-kwds',
1841 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1842 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1843 ;; NB: These are currently not recognized in all parts of a
1844 ;; declaration. Specifically, they aren't recognized in the middle
1845 ;; of multi-token types, inside declarators, and between the
1846 ;; identifier and the arglist paren of a function declaration.
1847 ;;
1848 ;; FIXME: This ought to be user customizable since compiler stuff
1849 ;; like this usually is wrapped in project specific macros. (It'd
1850 ;; of course be even better if we could cope without knowing this.)
1851 t nil
1853 "__attribute__"
1854 ;; MSVC extension.
1858 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1863 ;; All keywords that can occur in the preamble of a declaration.
1864 ;; They typically occur before the type, but they are also matched
1865 ;; after presumptive types since we often can't be sure that
1866 ;; something is a type or just some sort of macro in front of the
1867 ;; declaration. They might be ambiguous with types or type
1868 ;; prefixes.
1881 ;; Adorned regexp of `c-prefix-spec-kwds'.
1885 (replace-regexp-in-string "\\\\\\+" "+" (c-make-keywords-re t (c-lang-const c-prefix-spec-kwds)))))
1890 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1891 ;; ambiguous with types or type prefixes. These are the keywords (like
1892 ;; extern, namespace, but NOT template) that can modify a declaration.
1901 ;; Keywords that can occur after argument list of a function header
1902 ;; declaration, i.e. in the "K&R region".
1907 ;; Adorned regexp matching all keywords that can't appear at the
1908 ;; start of a declaration.
1918 "Access protection label keywords in classes."
1919 t nil
1924 "Keywords introducing declarations that can contain a block which
1927 like that, it ends with the following ';' and not right away.
1929 The keywords on list are assumed to also be present on one of the
1930 `*-decl-kwds' lists."
1931 t nil
1936 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
1937 ;; languages without such constructs.
1944 "Keywords introducing extra declaration specifiers in the region
1946 declarations."
1947 t nil
1950 "supports"
1951 ;; In CORBA PSDL:
1955 "Keywords that may be followed by a nonsymbol sexp before whatever
1956 construct it's part of continues."
1957 t nil
1961 "Keywords that may be followed by a comma separated list of type
1962 identifiers, where each optionally can be prefixed by keywords. (Can
1963 also be used for the special case when the list can contain only one
1964 element.)
1966 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
1967 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
1968 There's also no reason to add keywords that prefixes a normal
1969 declaration consisting of a type followed by a declarator (list), so
1970 the keywords on `c-modifier-kwds' should normally not be listed here
1971 either.
1973 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1974 or variable identifier (that's being defined)."
1975 t nil
1980 ;; In CORBA PSDL:
1985 "Keywords that may be followed by a comma separated list of
1986 reference (i.e. namespace/scope/module) identifiers, where each
1987 optionally can be prefixed by keywords. (Can also be used for the
1988 special case when the list can contain only one element.) Assumed to
1989 be mutually exclusive with `c-type-list-kwds'.
1991 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1992 or variable identifier (that's being defined)."
1993 t nil
1997 ;; In CORBA CIDL:
2002 "Keywords that may be followed (not necessarily directly) by a colon
2003 and then a comma separated list of type identifiers, where each
2004 optionally can be prefixed by keywords. (Can also be used for the
2005 special case when the list can contain only one element.)"
2006 t nil
2009 ;; In CORBA PSDL:
2013 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2014 forward to the colon. The end of the match is assumed to be directly
2016 regexp if `c-colon-type-list-kwds' isn't nil."
2018 ;; Disallow various common punctuation chars that can't come
2019 ;; before the ":" that starts the inherit list after "class"
2020 ;; or "struct" in C++. (Also used as default for other
2021 ;; languages.)
2026 "Keywords that may be followed by a parenthesis expression that doesn't
2027 contain type identifiers."
2028 t nil
2030 "__attribute__"
2031 ;; MSVC extension.
2035 "Keywords that may be followed by a parenthesis expression containing
2036 type identifiers separated by arbitrary tokens."
2037 t nil
2049 "Keywords that may be followed by an angle bracket expression
2051 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2052 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2053 if this isn't nil."
2054 t nil
2057 ;; In CORBA PSDL:
2061 "Keywords that can be followed by a C++ style template arglist; see
2062 `c-recognize-<>-arglists' for details. That language constant is
2063 assumed to be set if this isn't nil."
2064 t nil
2069 ;; All keywords that can be followed by an angle bracket sexp.
2075 ;; Adorned regexp matching keywords that can be followed by an angle
2076 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2082 "Keywords that may be followed by a brace block containing a comma
2083 separated list of identifier definitions, i.e. like the list of
2084 identifiers that follows the type in a normal declaration."
2088 "Statement keywords followed directly by a substatement."
2093 idl nil)
2096 ;; Regexp matching the start of any statement followed directly by a
2097 ;; substatement (doesn't match a bare block, however).
2102 "Statement keywords followed by a paren sexp and then by a substatement."
2107 idl nil
2112 ;; Regexp matching the start of any statement followed by a paren sexp
2113 ;; and then by a substatement.
2118 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2124 ;; Regexp matching the start of any statement that has a
2125 ;; substatement (except a bare block). Nil in languages that
2126 ;; don't have such constructs.
2135 "Statement keywords followed by an expression or nothing."
2138 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2140 idl nil
2147 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2152 "Statement keywords followed by a parenthesis expression that
2153 nevertheless contains a list separated with ';' and not ','."
2155 idl nil)
2158 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2163 "Statement keywords followed by an assembler expression."
2164 t nil
2168 ;; Regexp matching the start of an assembler statement. Nil in
2169 ;; languages that don't support that.
2178 awk nil)
2181 ;; Adorned regexp matching any "case"-like keyword.
2186 "Keywords introducing colon terminated labels in blocks."
2188 awk nil)
2191 ;; Adorned regexp matching any keyword that introduces a label.
2196 "Keywords that might be followed by a label identifier."
2200 idl nil
2201 awk nil)
2204 "Keywords for constants."
2205 t nil
2214 "Keywords besides constants and operators that start primary expressions."
2215 t nil
2222 ;; Keywords that can occur anywhere in expressions. Built from
2223 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2227 t
2232 "Keywords that start lambda constructs, i.e. function definitions in
2233 expressions."
2234 t nil
2238 "Keywords that start constructs followed by statement blocks which can
2239 be used in expressions \(the gcc extension for this in C and C++ is
2240 handled separately by `c-recognize-paren-inexpr-blocks')."
2241 t nil
2245 "Keywords that can start classes inside expressions."
2246 t nil
2251 "Keywords that can start brace list blocks inside expressions.
2252 Note that Java specific rules are currently applied to tell this from
2253 `c-inexpr-class-kwds'."
2254 t nil
2258 ;; Regexp matching the start of a brace list in an expression, or
2259 ;; nil in languages that don't have such things. This should not
2260 ;; match brace lists recognized through `c-special-brace-lists'.
2267 ;; Regexp matching keywords in any construct that contain another
2268 ;; declaration level, i.e. that isn't followed by a function block
2269 ;; or brace list. When the first submatch matches, it's an
2270 ;; unambiguous construct, otherwise it's an ambiguous match that
2271 ;; might also be the return type of a function declaration.
2289 "Keywords that can introduce bitfields."
2290 t nil
2294 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2295 ;; languages without bitfield support.
2296 t nil
2301 "Keywords not accounted for by any other `*-kwds' language constant."
2302 t nil
2304 ;; In CORBA CIDL: (These are declaration keywords that never
2305 ;; can start a declaration.)
2308 \f
2309 ;;; Constants built from keywords.
2311 ;; Note: No `*-kwds' language constants may be defined below this point.
2315 ;; List of all the language constants that contain keyword lists.
2320 ;; Make the list of globally interned symbols
2321 ;; instead of ones interned in `c-lang-constants'.
2323 c-lang-constants)
2324 list)))
2327 ;; All keywords as a list.
2332 c-kwds-lang-consts)
2333 nil))
2337 ;; All keywords as an adorned regexp.
2342 ;; An alist with all the keywords in the cars. The cdr for each
2343 ;; keyword is a list of the symbols for the `*-kwds' lists that
2344 ;; contains it.
2350 c-kwds-lang-consts))))
2351 lang-const kwd-list kwd
2352 result-alist elem)
2364 result-alist))
2367 ;; An obarray containing all keywords as symbols. The property list
2368 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2369 ;; lists it's a member of.
2370 ;;
2371 ;; E.g. to see whether the string str contains a keyword on
2372 ;; `c-class-decl-kwds', one can do like this:
2373 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2374 ;; Which preferably is written using the associated functions in
2375 ;; cc-engine:
2376 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2378 ;; The obarray is not stored directly as a language constant since
2379 ;; the printed representation for obarrays used in .elc files isn't
2380 ;; complete.
2383 kwd lang-const-list
2390 ;; Emacs has an odd bug that causes `mapcan' to fail
2391 ;; with unintelligible errors. (XEmacs works.)
2392 ;;(mapcan (lambda (lang-const)
2393 ;; (list lang-const t))
2394 ;; lang-const-list)
2397 lang-const-list))))
2398 obarray))
2401 ;; Adorned regexp matching all keywords that should be fontified
2402 ;; with the keywords face. I.e. that aren't types or constants.
2412 ;; Regexp matching the start of any primary expression, i.e. any
2413 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2414 ;; exclude keywords; they are excluded afterwards unless the second
2415 ;; submatch matches. If the first but not the second submatch
2416 ;; matches then it is an ambiguous primary expression; it could also
2417 ;; be a match of e.g. an infix operator. (The case with ambiguous
2418 ;; keyword operators isn't handled.)
2424 ;; Filter out the special case prefix
2425 ;; operators that are close parens.
2430 t
2436 postfix-if-paren
2437 left-assoc
2438 right-assoc
2439 right-assoc-sequence)
2440 t))
2443 in-or-postfix-ops
2446 in-or-postfix-ops
2451 ;; Take out all symbol class operators from `prefix-ops' and make the
2452 ;; first submatch from them together with `c-primary-expr-kwds'.
2459 ;; Match all ambiguous operators.
2466 ;; Now match all other symbols.
2470 ;; The chars that can start integer and floating point
2471 ;; constants.
2475 ;; The nonambiguous operators from `prefix-ops'.
2481 ;; Match string and character literals.
2488 \f
2489 ;;; Additional constants for parser-level constructs.
2492 "Regexp matching something that might precede a declaration, cast or
2493 label, such as the last token of a preceding statement or declaration.
2494 This is used in the common situation where a declaration or cast
2495 doesn't start with any specific token that can be searched for.
2497 The regexp should not match bob; that is done implicitly. It can't
2498 require a match longer than one token. The end of the token is taken
2499 to be at the end of the first submatch, which is assumed to always
2500 match. It's undefined whether identifier syntax (see
2501 `c-identifier-syntax-table') is in effect or not. This regexp is
2502 assumed to be a superset of `c-label-prefix-re' if
2503 `c-recognize-colon-labels' is set.
2505 Besides this, `c-decl-start-kwds' is used to find declarations.
2507 Note: This variable together with `c-decl-start-re' and
2509 declaration/cast/label starts. I.e. they might produce more matches
2510 but should not miss anything (or else it's necessary to use text
2511 properties - see the next note). Wherever they match, the following
2512 construct is analyzed to see if it indeed is a declaration, cast or
2513 label. That analysis is not cheap, so it's important that not too
2514 many false matches are triggered.
2516 Note: If a declaration/cast/label start can't be detected with this
2517 variable, it's necessary to use the `c-type' text property with the
2518 value `c-decl-end' on the last char of the last token preceding the
2519 declaration. See the comment blurb at the start of cc-engine.el for
2520 more info."
2522 ;; We match a sequence of characters to skip over things like \"};\"
2523 ;; more quickly. We match ")" in C for K&R region declarations, and
2524 ;; in all languages except Java for when a cpp macro definition
2525 ;; begins with a declaration.
2528 ;; Match "<" in C++ to get the first argument in a template arglist.
2529 ;; In that case there's an additional check in `c-find-decl-spots'
2530 ;; that it got open paren syntax.
2532 ;; Additionally match the protection directives in Objective-C.
2533 ;; Note that this doesn't cope with the longer directives, which we
2534 ;; would have to match from start to end since they don't end with
2535 ;; any easily recognized characters.
2539 ;; Pike is like C but we also match "[" for multiple value
2540 ;; assignments and type casts.
2546 "Regexp matching the start of any declaration, cast or label.
2547 It's used on the token after the one `c-decl-prefix-re' matched. This
2548 regexp should not try to match those constructs accurately as it's
2549 only used as a sieve to avoid spending more time checking other
2550 constructs."
2555 ;; Regexp matching something that might precede or start a
2556 ;; declaration, cast or label.
2557 ;;
2558 ;; If the first submatch matches, it's taken to match the end of a
2559 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2560 ;; It's built from `c-decl-prefix-re'.
2561 ;;
2562 ;; If the first submatch did not match, the match of the whole
2563 ;; regexp is taken to be at the first token in the declaration.
2564 ;; `c-decl-start-re' is not checked in this case.
2565 ;;
2566 ;; Design note: The reason the same regexp is used to match both
2567 ;; tokens that precede declarations and start them is to avoid an
2568 ;; extra regexp search from the previous declaration spot in
2569 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2570 ;; that it finds all declaration/cast/label starts in approximately
2571 ;; linear order, so we can't do the searches in two separate passes.
2582 ;; List containing the paren characters that can open a cast, or nil in
2583 ;; languages without casts.
2591 "List of syntactically relevant characters that never can occur before
2592 the open brace in any construct that contains a brace block, e.g. in
2595 class Foo: public Bar {int x();} a, *b;
2597 If parens can occur, the chars inside those aren't filtered with this
2598 list.
2600 '<' and '>' should be disallowed even if angle bracket arglists can
2601 occur. That since the search function needs to stop at them anyway to
2602 ensure they are given paren syntax.
2604 This is used to skip backward from the open brace to find the region
2607 possible for good performance."
2609 ;; Default to all chars that only occurs in nonsymbol tokens outside
2610 ;; identifiers.
2616 t
2617 t
2621 op pos)
2624 res))))
2626 ;; Allow cpp operatios (where applicable).
2632 ;; Allow ':' for inherit list starters.
2636 ;; Allow ',' for multiple inherits.
2640 ;; Allow parentheses for anonymous inner classes in Java and class
2641 ;; initializer lists in Pike.
2645 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2650 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2651 ;; for `c-syntactic-skip-backward'.
2656 "Regexp matching the declarator operators that might precede the
2659 The end of the first submatch is taken as the end of the operator.
2660 Identifier syntax is in effect when this is matched \(see
2661 `c-identifier-syntax-table')."
2664 ;; Default to a regexp that never matches.
2666 ;; Check that there's no "=" afterwards to avoid matching tokens
2667 ;; like "*=".
2669 "[*\(]"
2675 "[*\(&]"
2680 ;; If this matches there's special treatment in
2681 ;; `c-font-lock-declarators' and
2682 ;; `c-font-lock-declarations' that check for a
2683 ;; complete name followed by ":: *".
2693 "Regexp matching the declarator operators that might follow after the
2696 it matches an open paren of some kind, the type declaration check
2697 continues at the corresponding close paren, otherwise the end of the
2698 first submatch is taken as the end of the operator. Identifier syntax
2699 is in effect when this is matched (see `c-identifier-syntax-table')."
2700 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2701 ;; function argument list parenthesis.
2709 "[\)\[\(]"
2713 ;; "throw" in `c-type-modifier-kwds' is followed
2714 ;; by a parenthesis list, but no extra measures
2715 ;; are necessary to handle that.
2725 "This regexp is matched after a declarator expression where
2726 `c-type-decl-suffix-key' has matched. If it matches then the
2727 construct is taken as a declaration. It's typically used to match the
2728 beginning of a function body or whatever might occur after the
2729 function header in a function declaration or definition. It's
2730 undefined whether identifier syntax (see `c-identifier-syntax-table')
2731 is in effect or not.
2736 t "{"
2737 ;; If K&R style declarations should be recognized then one could
2738 ;; consider to match the start of any symbol since we want to match
2739 ;; the start of the first declaration in the "K&R region". That
2740 ;; could however produce false matches on code like "FOO(bar) x"
2741 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2742 ;; on the other heuristics in that case.
2744 ;; Add on the keywords in `c-postfix-spec-kwds'.
2749 ;; Also match the colon that starts a base class initializer list in
2750 ;; C++. That can be confused with a function call before the colon
2751 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2752 ;; match before such a thing (as a declaration-level construct;
2753 ;; matches inside arglist contexts are already excluded).
2760 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2761 ;; matches ";" and ",".
2770 end of the operator. nil in languages without such operators. It's
2771 undefined whether identifier syntax (see `c-identifier-syntax-table')
2772 is in effect or not."
2773 t nil
2779 "Regexp matching operators that might follow after a type, or nil in
2780 languages that don't have such operators. The end of the first
2781 submatch is taken as the end of the operator. This should not match
2782 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2783 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2784 is in effect or not."
2785 t nil
2791 ;; Regexp matching the known type identifiers. This is initialized
2792 ;; from the type keywords and `*-font-lock-extra-types'. The first
2793 ;; submatch is the one that matches the type. Note that this regexp
2794 ;; assumes that symbol constituents like '_' and '$' have word
2795 ;; syntax.
2804 extra-types)))
2810 extra-types))))
2815 plain-strings)))
2816 regexp-strings)
2821 "List of open- and close-chars that makes up a pike-style brace list,
2823 list."
2824 t nil
2829 "Non-nil means K&R style argument declarations are valid."
2830 t nil
2831 c t)
2835 "Non-nil means function declarations without return type should be
2836 recognized. That can introduce an ambiguity with parenthesized macro
2837 calls before a brace block. This setting does not affect declarations
2838 that are preceded by a declaration starting keyword, so
2839 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2840 t nil
2846 "Non-nil means C++ style template arglists should be handled. More
2847 specifically, this means a comma separated list of types or
2849 identifier or one of the keywords on `c-<>-type-kwds' or
2850 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2851 expression is considered to be a type."
2857 "Non-nil means that parenthesis style initializers exist,
2858 i.e. constructs like
2860 Foo bar (gnu);
2862 in addition to the more classic
2864 Foo bar = gnu;"
2865 t nil
2870 "Non-nil to recognize gcc style in-expression blocks,
2871 i.e. compound statements surrounded by parentheses inside expressions."
2872 t nil
2878 ;; Regexp matching the start of angle bracket arglists in languages
2879 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2880 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2881 ;; assumed to surround the preceding symbol. The whole match is
2882 ;; assumed to end directly after the opening "<".
2892 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2893 ;; parens. The first submatch is assumed to surround
2894 ;; `c-opt-<>-arglist-start'.
2903 ;; Regexp matching the beginning of a declaration specifier in the
2904 ;; region between the header and the body of a declaration.
2905 ;;
2906 ;; TODO: This is currently not used uniformly; c++-mode and
2907 ;; java-mode each have their own ways of using it.
2908 t nil
2921 That includes labels in code and access keys in classes. This does
2922 not apply to labels recognized by `c-label-kwds' and
2923 `c-opt-extra-label-key'."
2924 t nil
2930 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2931 a generic colon label. Not used if `c-recognize-colon-labels' is
2932 nil."
2938 "Regexp matching things that can't occur in generic colon labels,
2939 neither in a statement nor in a declaration context. The regexp is
2940 tested at the beginning of every sexp in a suspected label,
2943 ;; Don't allow string literals.
2945 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
2951 ;; Also check for open parens in C++, to catch member init lists in
2952 ;; constructors. We normally allow it so that macros with arguments
2953 ;; work in labels.
2958 "Optional regexp matching labels.
2959 Normally, labels are detected according to `c-nonlabel-token-key',
2960 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
2961 be used if there are additional labels that aren't recognized that
2962 way."
2963 t nil
2968 ;; Regexp describing friend declarations classes, or nil in
2969 ;; languages that don't have such things.
2970 ;;
2971 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
2972 ;; template skipping isn't done properly. This will disappear soon.
2973 t nil
2978 "<.+>"
2980 "friend"
2985 ;; Special regexp to match the start of Objective-C methods. The
2986 ;; first submatch is assumed to end after the + or - key.
2987 t nil
2989 ;; TODO: Ought to use a better method than anchoring on bol.
2994 "([^\)]*)"
3001 ;; Must be set in buffers where the `c-type' text property might be
3002 ;; used with the value `c-decl-end'.
3003 ;;
3004 ;; `c-decl-end' is used to mark the ends of labels and access keys
3005 ;; to make interactive refontification work better.
3008 ;; `c-decl-end' is used to mark the end of the @-style directives in
3009 ;; Objective-C.
3010 objc t)
3013 \f
3014 ;;; Wrap up the `c-lang-defvar' system.
3016 ;; Compile in the list of language variables that has been collected
3017 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3018 ;; first element of each is nil.
3022 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3023 ;; These are typically standard emacs variables such as `comment-start'.
3031 "Create a function that initializes all the language dependent variables
3032 for the given mode.
3034 This function should be evaluated at compile time, so that the
3035 function it returns is byte compiled with all the evaluated results
3036 from the language constants. Use the `c-init-language-vars' macro to
3037 accomplish that conveniently."
3043 ;; No need to byte compile this lambda since the byte compiler is
3044 ;; smart enough to detect the `funcall' construct in the
3045 ;; `c-init-language-vars' macro below and compile it all straight
3046 ;; into the function that contains `c-init-language-vars'.
3049 ;; This let sets up the context for `c-mode-var' and similar
3050 ;; that could be in the result from `cl-macroexpand-all'.
3052 current-var source-eval)
3059 ;; `c-lang-const' will expand to the evaluated
3060 ;; constant immediately in `cl-macroexpand-all'
3061 ;; below.
3067 ;; Note: The following `append' copies the
3068 ;; first argument. That list is small, so
3069 ;; this doesn't matter too much.
3073 ;; This diagnostic message isn't useful for end
3074 ;; users, so it's disabled.
3075 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3076 ;; (message ,(concat "%s compiled with CC Mode %s "
3077 ;; "but loaded with %s - evaluating "
3078 ;; "language constants from source")
3079 ;; ',mode ,c-version c-version)
3080 ;; (put ',mode 'c-has-warned-lang-consts t))
3094 current-var
3097 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3100 err)
3103 ;; Being evaluated from source. Always use the dynamic method to
3104 ;; work well when `c-lang-defvar's in this file are reevaluated
3105 ;; interactively.
3111 current-var)
3123 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3124 current-var err)
3126 ))
3129 "Initialize all the language dependent variables for the given mode.
3130 This macro is expanded at compile time to a form tailored for the mode
3131 in question, so MODE must be a constant. Therefore MODE is not
3132 evaluated and should not be quoted."
3135 \f
3138 ;;; cc-langs.el ends here