| blob | d29e75e92f0b1193a98fce90dc4165c13594ea50 |
1 ;;; cc-langs.el --- language specific settings for CC Mode
3 ;; Copyright (C) 1985,1987,1992-2003, 2004, 2005, 2006 Free Software
4 ;; Foundation, Inc.
6 ;; Authors: 1998- Martin Stjernholm
7 ;; 1992-1999 Barry A. Warsaw
8 ;; 1987 Dave Detlefs and Stewart Clamen
9 ;; 1985 Richard M. Stallman
10 ;; Maintainer: bug-cc-mode@gnu.org
11 ;; Created: 22-Apr-1997 (split from cc-mode.el)
12 ;; Version: See cc-mode.el
13 ;; Keywords: c languages oop
15 ;; This file is part of GNU Emacs.
17 ;; GNU Emacs is free software; you can redistribute it and/or modify
18 ;; it under the terms of the GNU General Public License as published by
19 ;; the Free Software Foundation; either version 2, or (at your option)
20 ;; any later version.
22 ;; GNU Emacs is distributed in the hope that it will be useful,
23 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
24 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
25 ;; GNU General Public License for more details.
27 ;; You should have received a copy of the GNU General Public License
28 ;; along with this program; see the file COPYING. If not, write to
29 ;; the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
30 ;; Boston, MA 02110-1301, USA.
32 ;;; Commentary:
34 ;; HACKERS NOTE: There's heavy macro magic here. If you need to make
35 ;; changes in this or other files containing `c-lang-defconst' but
36 ;; don't want to read through the longer discussion below then read
37 ;; this:
38 ;;
39 ;; o A change in a `c-lang-defconst' or `c-lang-defvar' will not take
40 ;; effect if the file containing the mode init function (typically
41 ;; cc-mode.el) is byte compiled.
42 ;; o To make changes show in font locking you need to reevaluate the
43 ;; `*-font-lock-keywords-*' constants, which normally is easiest to
44 ;; do with M-x eval-buffer in cc-fonts.el.
45 ;; o In either case it's necessary to reinitialize the mode to make
46 ;; the changes show in an existing buffer.
48 ;;; Introduction to the language dependent variable system:
49 ;;
50 ;; This file contains all the language dependent variables, except
51 ;; those specific for font locking which reside in cc-fonts.el. As
52 ;; far as possible, all the differences between the languages that CC
53 ;; Mode supports are described with these variables only, so that the
54 ;; code can be shared.
55 ;;
56 ;; The language constant system (see cc-defs.el) is used to specify
57 ;; various language dependent info at a high level, such as lists of
58 ;; keywords, and then from them generate - at compile time - the
59 ;; various regexps and other low-level structures actually employed in
60 ;; the code at runtime.
61 ;;
62 ;; This system is also designed to make it easy for developers of
63 ;; derived modes to customize the source constants for new language
64 ;; variants, without having to keep up with the exact regexps etc that
65 ;; are used in each CC Mode version. It's possible from an external
66 ;; package to add a new language by inheriting an existing one, and
67 ;; then change specific constants as necessary for the new language.
68 ;; The old values for those constants (and the values of all the other
69 ;; high-level constants) may be used to build the new ones, and those
70 ;; new values will in turn be used by the low-level definitions here
71 ;; to build the runtime constants appropriately for the new language
72 ;; in the current version of CC Mode.
73 ;;
74 ;; Like elsewhere in CC Mode, the existence of a doc string signifies
75 ;; that a language constant is part of the external API, and that it
76 ;; therefore can be used with a high confidence that it will continue
77 ;; to work with future versions of CC Mode. Even so, it's not
78 ;; unlikely that such constants will change meaning slightly as this
79 ;; system is refined further; a certain degree of dependence on the CC
80 ;; Mode version is unavoidable when hooking in at this level. Also
81 ;; note that there's still work to be done to actually use these
82 ;; constants everywhere inside CC Mode; there are still hardcoded
83 ;; values in many places in the code.
84 ;;
85 ;; Separate packages will also benefit from the compile time
86 ;; evaluation; the byte compiled file(s) for them will contain the
87 ;; compiled runtime constants ready for use by (the byte compiled) CC
88 ;; Mode, and the source definitions in this file don't have to be
89 ;; loaded then. However, if a byte compiled package is loaded that
90 ;; has been compiled with a different version of CC Mode than the one
91 ;; currently loaded, then the compiled-in values will be discarded and
92 ;; new ones will be built when the mode is initialized. That will
93 ;; automatically trig a load of the file(s) containing the source
94 ;; definitions (i.e. this file and/or cc-fonts.el) if necessary.
95 ;;
96 ;; A small example of a derived mode is available at
97 ;; <http://cc-mode.sourceforge.net/derived-mode-ex.el>. It also
98 ;; contains some useful hints for derived mode developers.
100 ;;; Using language variables:
101 ;;
102 ;; The `c-lang-defvar' forms in this file comprise the language
103 ;; variables that CC Mode uses. It does not work to use
104 ;; `c-lang-defvar' anywhere else (which isn't much of a limitation
105 ;; since these variables sole purpose is to interface with the CC Mode
106 ;; core functions). The values in these `c-lang-defvar's are not
107 ;; evaluated right away but instead collected to a single large `setq'
108 ;; that can be inserted for a particular language with the
109 ;; `c-init-language-vars' macro.
111 ;; This file is only required at compile time, or when not running
112 ;; from byte compiled files, or when the source definitions for the
113 ;; language constants are requested.
115 ;;; Code:
122 load-path)))
129 ;; This file is not always loaded. See note above.
132 \f
133 ;;; Setup for the `c-lang-defvar' system.
136 ;; These are used to collect the init forms from the subsequent
137 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
138 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
139 ;; and `make-variable-buffer-local's in cc-engine and
140 ;; `make-local-variable's in `c-init-language-vars-for'.
144 c-lang-variable-inits-tail c-lang-variable-inits)
148 c-emacs-variable-inits-tail c-emacs-variable-inits))
151 "Declares the buffer local variable VAR to get the value VAL. VAL is
152 evaluated and assigned at mode initialization. More precisely, VAL is
153 evaluated and bound to VAR when the result from the macro
154 `c-init-language-vars' is evaluated.
156 `c-lang-const' is typically used in VAL to get the right value for the
157 language being initialized, and such calls will be macro expanded to
158 the evaluated constant value at compile time."
164 ;; Special case: If there's no docstring and the value is a
165 ;; simple (c-lang-const foo) where foo is the same name as VAR
166 ;; then take the docstring from the language constant foo.
178 ;; Return the symbol, like the other def* forms.
182 "Causes the variable VAR to be made buffer local and to get set to the
183 value VAL. VAL is evaluated and assigned at mode initialization. More
184 precisely, VAL is evaluated and bound to VAR when the result from the
185 macro `c-init-language-vars' is evaluated. VAR is typically a standard
186 Emacs variable like `comment-start'.
188 `c-lang-const' is typically used in VAL to get the right value for the
189 language being initialized, and such calls will be macro expanded to
190 the evaluated constant value at compile time."
197 ;; Return the symbol, like the other def* forms.
201 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
202 ; '
207 ;; Some helper functions used when building the language constants.
210 ;; Used to filter operators from the list OPS in a DWIM:ey way:
211 ;; OPS either has the structure of `c-operators', as a single
212 ;; group in `c-operators', or is a plain list of operators.
213 ;; OPGROUP-FILTER is used filter out the operator groups. It can
214 ;; be t to choose all groups, a list of the group type symbols to
215 ;; accept, or a function which will be called with the group
216 ;; symbol for each group and should return non-nil for those to
217 ;; include. OP-FILTER filters the individual operators in each
218 ;; group. It can be t to choose all operators, a regexp to test
219 ;; against each operator, or a function which will be called for
220 ;; each operator and should return non-nil for those to include.
221 ;; If XLATE is given, it's a function which is called for each
222 ;; matching operator and its return value is collected instead.
223 ;; If it returns a list, the elements are spliced directly into
224 ;; the final result, which is returned as a list with duplicates
225 ;; removed using `equal'. `c-mode-syntax-table' for the current
226 ;; mode is in effect during the whole procedure.
247 t)
248 t)
253 opgroup)))
254 ops)
257 \f
258 ;;; Various mode specific values that aren't language related.
261 ;; The definition for the mode menu. The menu title is prepended to
262 ;; this before it's fed to `easy-menu-define'.
272 "----"
276 ;; Only applicable if there's a cpp preprocessor.
280 "----"
285 "----"
297 c-subword-mode)])))
299 \f
300 ;;; Syntax tables.
303 "Populate the given syntax table as necessary for a C-like language.
321 ;; Set up block and line oriented comments. The new C
322 ;; standard mandates both comment styles even in C, so since
323 ;; all languages now require dual comments, we make this the
324 ;; default.
326 ;; XEmacs
330 ;; Emacs
334 ;; incompatible
338 ;; Give CR the same syntax as newline, for selective-display
342 "Functions that generates the mode specific syntax tables.
343 The syntax tables aren't stored directly since they're quite large."
347 ;; Mode specific syntaxes.
349 ;; Let '@' be part of symbols in ObjC to cope with
350 ;; its compiler directives as single keyword tokens.
351 ;; This is then necessary since it's assumed that
352 ;; every keyword is a single symbol.
356 table)))
359 ;; The syntax tables in evaluated form. Only used temporarily when
360 ;; the constants in this file are evaluated.
364 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
365 ;; parenthesis characters. Used temporarily when template argument
366 ;; lists are parsed. Note that this encourages incorrect parsing of
367 ;; templates since they might contain normal operators that uses the
368 ;; '<' and '>' characters. Therefore this syntax table might go
369 ;; away when CC Mode handles templates correctly everywhere.
370 t nil
375 table)))
381 "A list that describes the modifications that should be done to the
382 mode syntax table to get a syntax table that matches all identifiers
383 and keywords as words.
385 The list is just like the one used in `font-lock-defaults': Each
386 element is a cons where the car is the character to modify and the cdr
387 the new syntax, as accepted by `modify-syntax-entry'."
388 ;; The $ character is not allowed in most languages (one exception
389 ;; is Java which allows it for legacy reasons) but we still classify
390 ;; it as an indentifier character since it's often used in various
391 ;; machine generated identifiers.
402 mod)
407 table)
408 "Syntax table built on the mode syntax table but additionally
409 classifies symbol constituents like '_' and '$' as word constituents,
412 \f
413 ;;; Lexer-level syntax (identifiers, tokens etc).
416 "Regexp that matches the start of a symbol, i.e. any identifier or
418 operator at the top level."
425 "Set of characters that can be part of a symbol.
426 This is on the form that fits inside [ ] in a regexp."
427 ;; Pike note: With the backquote identifiers this would include most
428 ;; operator chars too, but they are handled with other means instead.
433 "Regexp matching identifiers and keywords (with submatch 0). Assumed
434 to match if `c-symbol-start' matches on the same position."
438 ;; Use the value from C here since the operator backquote is
439 ;; covered by the other alternative.
447 ;; Number of regexp grouping parens in `c-symbol-key'.
451 "This is the set of chars that can't be part of a symbol, i.e. the
452 negation of `c-symbol-chars'."
457 "Regexp that matches any character that can't be part of a symbol.
458 It's usually appended to other regexps to avoid matching a prefix.
459 It's assumed to not contain any submatchers."
460 ;; The same thing regarding Unicode identifiers applies here as to
461 ;; `c-symbol-key'.
465 "The operators that make up fully qualified identifiers. nil in
466 languages that don't have such things. See `c-operators' for a
467 description of the format. Binary operators can concatenate symbols,
471 This value is by default merged into `c-operators'."
472 t nil
476 ;; Java has "." to concatenate identifiers but it's also used for
477 ;; normal indexing. There's special code in the Java font lock
478 ;; rules to fontify qualified identifiers based on the standard
479 ;; naming conventions. We still define "." here to make
480 ;; `c-forward-name' move over as long names as possible which is
481 ;; necessary to e.g. handle throws clauses correctly.
490 ;; Appendable adorned regexp matching the operators that join
491 ;; symbols to fully qualified identifiers, or nil in languages that
492 ;; don't have such things.
493 ;;
494 ;; This was a docstring constant in 5.30. It still works but is now
495 ;; considered internal - change `c-identifier-ops' instead.
498 t)))
506 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
510 ;; Appendable adorned regexp matching operators that might precede
511 ;; an identifier and that are part of the identifier in that case.
512 ;; nil in languages without such things.
515 t)))
520 "Operators that can occur after a binary operator on `c-identifier-ops'
521 in identifiers. nil in languages that don't have such things.
523 Operators here should also have appropriate entries in `c-operators' -
524 it's not taken care of by default."
525 t nil
526 ;; '~' for destructors in C++, '*' for member pointers.
528 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
529 ;; in import declarations. (This will also match bogus things like
530 ;; "foo.*bar" but we don't bother.)
534 ;; Regexp that must match the token after
535 ;; `c-opt-identifier-concat-key' for it to be considered an
536 ;; identifier concatenation operator (which e.g. causes the
537 ;; preceding identifier to be fontified as a reference). Assumed to
538 ;; be a string if `c-opt-identifier-concat-key' is.
539 ;;
540 ;; This was a docstring constant in 5.30. It still works but is now
541 ;; considered internal - change `c-after-id-concat-ops' instead.
549 "Regexp that matches the start of an (optionally qualified) identifier.
550 It should also match all keywords. It's unspecified how far it
551 matches."
561 C++. It does not recognize the full range of syntactic whitespace
562 between the tokens; `c-forward-name' has to be used for that. It
563 should also not match identifiers containing parenthesis groupings,
565 ;; This regexp is more complex than strictly necessary to ensure
566 ;; that it can be matched with a minimum of backtracking.
587 ;; For flexibility, consider the symbol match
588 ;; optional if we've hit a
589 ;; `c-after-id-concat-ops' operator. This is
590 ;; also necessary to handle the "*" that can
591 ;; end import declaration identifiers in Java.
605 ;; This was a docstring constant in 5.30 but it's no longer used.
606 ;; It's only kept to avoid breaking third party code.
607 ;;
608 ;; Used to identify the submatch in `c-identifier-key' that
609 ;; surrounds the last symbol in the qualified identifier. It's a
610 ;; list of submatch numbers, of which the first that has a match is
611 ;; taken. It's assumed that at least one does when the regexp has
612 ;; matched.
613 t nil)
616 "Set if the language support backslash escaped newlines inside string
617 literals."
618 t nil
624 "Set if the language supports multiline string literals without escaped
625 newlines. If t, all string literals are multiline. If a character,
626 only literals where the open quote is immediately preceded by that
627 literal are multiline."
628 t nil
629 pike ?#)
634 "Regexp matching the prefix of a cpp directive in the languages that
635 normally use that macro preprocessor. Tested at bol or at boi.
637 ;; TODO (ACM, 2005-04-01). Amend the following to recognise escaped NLs;
638 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
644 "Regexp matching the prefix of a cpp directive including the directive
645 name, or nil in languages without preprocessor support. The first
646 submatch surrounds the directive name."
650 ;; Pike, being a scripting language, recognizes hash-bangs too.
656 "List of cpp directives (without the prefix) that are followed by a
657 string message."
663 "List of cpp directives (without the prefix) that are followed by a
664 file name in angle brackets or quotes."
670 "Cpp directive (without the prefix) that is followed by a macro
671 definition, or nil if the language doesn't have any."
676 ;; Regexp matching everything up to the macro body of a cpp define,
677 ;; or the end of the logical line if there is none. Set if
678 ;; c-opt-cpp-macro-define is.
688 "List if cpp directives (without the prefix) that are followed by an
689 expression."
694 "List of functions in cpp expressions."
700 "List of all assignment operators."
706 idl nil)
709 "List describing all operators, along with their precedence and
710 associativity. The order in the list corresponds to the precedence of
711 the operators: The operators in each element is a group with the same
712 precedence, and the group has higher precedence than the groups in all
713 following elements. The car of each element describes the type of of
714 the operator group, and the cdr is a list of the operator tokens in
715 it. The operator group types are:
717 'prefix Unary prefix operators.
718 'postfix Unary postfix operators.
719 'postfix-if-paren
720 Unary postfix operators if and only if the chars have
721 parenthesis syntax.
722 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
723 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
724 'right-assoc-sequence
725 Right associative operator that constitutes of a
726 sequence of tokens that separate expressions. All the
727 tokens in the group are in this case taken as
728 describing the sequence in one such operator, and the
729 order between them is therefore significant.
731 Operators containing a character with paren syntax are taken to match
732 with a corresponding open/close paren somewhere else. A postfix
733 operator with close paren syntax is taken to end a postfix expression
734 started somewhere earlier, rather than start a new one at point. Vice
735 versa for prefix operators with open paren syntax.
738 often are described as postfix operators are considered binary here,
739 since CC Mode treats every identifier as an expression."
741 ;; There's currently no code in CC Mode that exploit all the info
742 ;; in this variable; precedence, associativity etc are present as a
743 ;; preparation for future work.
754 ;; Primary.
763 ;; Postfix.
765 ;; The following need special treatment.
775 ;; Unary.
782 ;; The following need special treatment.
793 ;; Member selection.
797 ;; Multiplicative.
800 ;; Additive.
803 ;; Shift.
808 ;; Relational.
813 ;; Equality.
817 ;; Bitwise and.
821 ;; Bitwise exclusive or.
827 ;; Bitwise or.
833 ;; Logical and.
837 ;; Logical or.
843 ;; Conditional.
846 ;; Assignment.
849 ;; Exception.
853 ;; Sequence.
856 ;; IDL got its own definition since it has a much smaller operator
857 ;; set than the other languages.
861 ;; Primary.
863 ;; Unary.
865 ;; Multiplicative.
867 ;; Additive.
869 ;; Shift.
871 ;; And.
873 ;; Xor.
875 ;; Or.
879 ;; The operators as a flat list (without duplicates).
885 t nil
894 ;; These work like identifiers in Pike.
901 ;; Regexp tested after an "operator" token in C++.
902 t nil
908 "Regexp matching the token before the ones in
909 `c-overloadable-operators' when operators are specified in their
912 languages without operator functions or where the complete operator
913 identifier is listed in `c-overloadable-operators'.
915 This regexp is assumed to not match any non-operator identifier."
916 t nil
922 "List of the tokens made up of characters in the punctuation or
923 parenthesis syntax classes that have uses other than as expression
924 operators."
942 ;; List of all tokens in the punctuation and parenthesis syntax
943 ;; classes.
949 ;; List containing all chars not in the word, symbol or
950 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
951 ;; parenthesis and string delimiter chars.
953 ;; Only go through the chars in the printable ASCII range. No
954 ;; language so far has 8-bit or widestring operators.
960 list)))
963 ;; Regexp matching all tokens in the punctuation and parenthesis
964 ;; syntax classes. Note that this also matches ".", which can start
965 ;; a float.
968 t
974 ;; Regexp matching all assignment operators and only them. The
975 ;; beginning of the first submatch is used to detect the end of the
976 ;; token, along with the end of the whole match.
979 ;; Need special case for "=" since it's a prefix of "==".
991 ;; Regexp matching all tokens containing "<" or ">" which are longer
992 ;; than one char.
995 t
1001 ;; Regexp matching the second and subsequent characters of all
1002 ;; multicharacter tokens that begin with "<".
1005 t
1011 ;; Regexp matching the second and subsequent characters of all
1012 ;; multicharacter tokens that begin with ">".
1015 t
1021 ;; The characters that should be considered to bound statements. To
1022 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1023 ;; begin with "^" to negate the set. If ? : operators should be
1024 ;; detected then the string must end with "?:".
1025 t "^;{}?:"
1030 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1031 t "^;,{}?:"
1036 \f
1037 ;;; Syntactic whitespace.
1040 "Regexp matching an ordinary whitespace character.
1042 ;; "\\s " is not enough since it doesn't match line breaks.
1046 ;; Number of regexp grouping parens in `c-simple-ws'.
1050 "String that starts line comments, or nil if such don't exist.
1051 Line comments are always terminated by newlines. At least one of
1052 `c-block-comment-starter' and this one is assumed to be set.
1054 Note that it's currently not enough to set this to support a new
1055 comment style. Other stuff like the syntax table must also be set up
1056 properly."
1057 t "//"
1062 "String that starts block comments, or nil if such don't exist.
1063 Block comments are ended by `c-block-comment-ender', which is assumed
1064 to be set if this is. At least one of `c-line-comment-starter' and
1065 this one is assumed to be set.
1067 Note that it's currently not enough to set this to support a new
1068 comment style. Other stuff like the syntax table must also be set up
1069 properly."
1070 t "/*"
1071 awk nil)
1074 "String that ends block comments, or nil if such don't exist.
1076 Note that it's currently not enough to set this to support a new
1077 comment style. Other stuff like the syntax table must also be set up
1078 properly."
1079 t "*/"
1080 awk nil)
1083 ;; Regexp to match the start of any type of comment.
1089 re)))
1092 ;;;; Added by ACM, 2003/9/18.
1094 ;; Regexp which matches the start of a block comment (if such exists in the
1095 ;; language)
1103 ;; Regexp to match the start of comments and string literals.
1112 "Regexp to match the start of documentation comments."
1114 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1122 "String that starts comments inserted with M-; etc.
1123 `comment-start' is initialized from this."
1124 ;; Default: Prefer line comments to block comments, and pad with a space.
1128 ;; In C we still default to the block comment style since line
1129 ;; comments aren't entirely portable.
1134 "String that ends comments inserted with M-; etc.
1135 `comment-end' is initialized from this."
1136 ;; Default: Use block comment style if comment-start uses block
1137 ;; comments, and pad with a space in that case.
1147 "Regexp to match the start of a comment plus everything up to its body.
1148 `comment-start-skip' is initialized from this."
1149 ;; Default: Allow the last char of the comment starter(s) to be
1150 ;; repeated, then allow any amount of horizontal whitespace.
1163 ;; Regexp matching any sequence that can start syntactic whitespace.
1164 ;; The only uncertain case is '#' when there are cpp directives.
1178 ;; Regexp matching any single character that might end syntactic whitespace.
1193 ;; Regexp matching an unterminated block comment that doesn't
1194 ;; contain line breaks, or nil in languages without block comments.
1195 ;; Does not contain a \| operator at the top level.
1199 ;; It's messy to cook together a regexp that matches anything
1200 ;; but c-block-comment-ender.
1208 "[^"
1209 ;; The quoting rules inside char classes are silly. :P
1218 "]"
1226 ;; Regexp matching a block comment that doesn't contain line breaks,
1227 ;; or nil in languages without block comments. The reason we don't
1228 ;; allow line breaks is to avoid going very far and risk running out
1229 ;; of regexp stack; this regexp is intended to handle only short
1230 ;; comments that might be put in the middle of limited constructs
1231 ;; like declarations. Does not contain a \| operator at the top
1232 ;; level.
1247 ;; Regexp matching a piece of syntactic whitespace that isn't a
1248 ;; sequence of simple whitespace characters. As opposed to
1249 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1250 ;; directives as syntactic whitespace.
1262 ;; Regexp matching syntactic whitespace, including possibly the
1263 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1264 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1265 ;; not contain a \| operator at the top level.
1273 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1277 ;; Regexp matching syntactic whitespace, which is at least one
1278 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1279 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1280 ;; not contain a \| operator at the top level.
1288 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1292 ;; Regexp matching syntactic whitespace without any line breaks. As
1293 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1294 ;; regard cpp directives as syntactic whitespace. Does not contain
1295 ;; a \| operator at the top level.
1303 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1307 ;; Regexp that matches when there is no syntactically significant
1308 ;; text before eol. Macros are regarded as syntactically
1309 ;; significant text here.
1311 ;; Match eol (possibly inside a block comment or preceded
1312 ;; by a line continuation backslash), or the beginning of a
1313 ;; line comment. Note: This has to be modified for awk
1314 ;; where line comments start with '#'.
1328 \f
1329 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
1332 Such a function takes one optional parameter, a buffer position (defaults to
1333 point), and returns NIL or t. This variable contains NIL for languages which
1334 don't have EOL terminated statements. "
1335 t nil
1341 The (admittedly kludgey) purpose of such a function is to prevent an infinite
1342 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
1343 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
1344 even indirectly. This variable contains NIL for languages which don't have
1345 EOL terminated statements."
1346 t nil
1351 \f
1352 ;;; In-comment text handling.
1355 "Regexp to append to `paragraph-start'."
1356 t "$"
1362 "Regexp to append to `paragraph-separate'."
1363 t "$"
1367 \f
1368 ;;; Keyword lists.
1370 ;; Note: All and only all language constants containing keyword lists
1371 ;; should end with "-kwds"; they're automatically collected into the
1372 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1375 "Primitive type keywords. As opposed to the other keyword lists, the
1376 keywords listed here are fontified with the type face instead of the
1377 keyword face.
1379 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1380 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1381 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1382 will be handled.
1384 Do not try to modify this list for end user customizations; the
1385 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1386 the appropriate place for that."
1395 ;; Objective-C extends C, but probably not the new stuff in C99.
1402 ;; In CORBA PSDL:
1403 "ref"
1404 ;; The following can't really end a type, but we have to specify them
1405 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1406 ;; doesn't matter that much.
1409 ;; used as a builtin type.
1414 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1419 "Keywords that might act as prefixes for primitive types. Assumed to
1420 be a subset of `c-primitive-type-kwds'."
1421 t nil
1424 ;; In CORBA PSDL:
1428 "Keywords where the following name - if any - is a type name, and
1429 where the keyword together with the symbol works as a type in
1430 declarations.
1432 Note that an alternative if the second part doesn't hold is
1433 `c-type-list-kwds'. Keywords on this list are typically also present
1434 on one of the `*-decl-kwds' lists."
1435 t nil
1441 ;; Adorned regexp matching `c-type-prefix-kwds'.
1446 "Type modifier keywords. These can occur almost anywhere in types
1447 but they don't build a type of themselves. Unlike the keywords on
1448 `c-primitive-type-kwds', they are fontified with the keyword face and
1449 not the type face."
1450 t nil
1456 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1457 ;; languages without such keywords.
1463 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1464 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1474 ;; All keywords that can start a type (i.e. are either a type prefix
1475 ;; or a complete type).
1482 "Keywords introducing declarations where the following block (if any)
1483 contains another declaration level that should be considered a class.
1485 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1486 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1487 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1488 will be handled.
1490 Note that presence on this list does not automatically treat the
1491 following identifier as a type; the keyword must also be present on
1492 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1493 t nil
1501 ;; In CORBA PSDL:
1503 ;; In CORBA CIDL:
1508 ;; Regexp matching the start of a class.
1513 "Keywords introducing declarations where the following block (if
1514 any) is a brace list.
1516 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1517 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1518 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1519 will be handled."
1524 ;; Regexp matching the start of declarations where the following
1525 ;; block is a brace list.
1530 "Keywords where the following block (if any) contains another
1531 declaration level that should not be considered a class. For every
1532 keyword here, CC Mode will add a set of special syntactic symbols for
1534 `foo-open', `foo-close', and `infoo' symbols.
1536 The intention is that this category should be used for block
1537 constructs that aren't related to object orientation concepts like
1538 classes (which thus also include e.g. interfaces, templates,
1539 contracts, structs, etc). The more pragmatic distinction is that
1540 while most want some indentation inside classes, it's fairly common
1541 that they don't want it in some of these constructs, so it should be
1542 simple to configure that differently from classes. See also
1543 `c-class-decl-kwds'.
1545 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1546 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1547 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1548 will be handled."
1549 t nil
1553 ;; In CORBA CIDL:
1557 ;; Regexp matching the start of blocks besides classes that contain
1558 ;; another declaration level.
1563 "Keywords introducing declarations where the identifier(s) being
1564 declared are types.
1566 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1567 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1568 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1569 will be handled."
1570 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1571 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1572 ;; {...}").
1575 ;; Languages that have a "typedef" construct.
1578 ;; Unlike most other languages, exception names are not handled as
1579 ;; types in IDL since they only can occur in "raises" specs.
1583 "Keywords introducing declarations where the \(first) identifier
1584 \(declarator) follows directly after the keyword, without any type.
1586 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1587 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1588 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1589 will be handled."
1590 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1591 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1592 ;; {...}").
1595 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1596 ;; `c-type-list-kwds' for IDL.
1599 ;; In CORBA PSDL:
1601 ;; In CORBA CIDL:
1607 "Keywords that can prefix normal declarations of identifiers
1608 \(and typically act as flags). Things like argument declarations
1609 inside function headers are also considered declarations in this
1610 sense.
1612 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1613 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1614 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1615 will be handled."
1616 t nil
1621 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1625 ;; In CORBA PSDL:
1627 ;; In CORBA CIDL:
1629 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1636 "Keywords that can start or prefix any declaration level construct,
1637 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1638 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1639 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1641 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1642 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1643 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1644 will be handled."
1645 t nil
1651 "Keywords that always start declarations, wherever they occur.
1652 This can be used for declarations that aren't recognized by the normal
1653 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1654 t nil
1655 ;; Classes can be declared anywhere in a Pike expression.
1659 "Keywords that can occur anywhere in a declaration level construct.
1660 This is used for self-contained things that can be tacked on anywhere
1661 on a declaration and that should be ignored to be able to recognize it
1662 correctly. Typical cases are compiler extensions like
1665 __declspec(noreturn) void foo();
1666 class __declspec(dllexport) classname {...};
1667 void foo() __attribute__((noreturn));
1669 Note that unrecognized plain symbols are skipped anyway if they occur
1670 before the type, so such things are not necessary to mention here.
1671 Mentioning them here is necessary only if they can occur in other
1672 places, or if they are followed by a construct that must be skipped
1674 examples above). In the last case, they alse need to be present on
1675 one of `c-type-list-kwds', `c-ref-list-kwds',
1676 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1677 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1678 ;; NB: These are currently not recognized in all parts of a
1679 ;; declaration. Specifically, they aren't recognized in the middle
1680 ;; of multi-token types, inside declarators, and between the
1681 ;; identifier and the arglist paren of a function declaration.
1682 ;;
1683 ;; FIXME: This ought to be user customizable since compiler stuff
1684 ;; like this usually is wrapped in project specific macros. (It'd
1685 ;; of course be even better if we could cope without knowing this.)
1686 t nil
1688 "__attribute__"
1689 ;; MSVC extension.
1693 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1698 ;; All keywords that can occur in the preamble of a declaration.
1699 ;; They typically occur before the type, but they are also matched
1700 ;; after presumptive types since we often can't be sure that
1701 ;; something is a type or just some sort of macro in front of the
1702 ;; declaration. They might be ambiguous with types or type
1703 ;; prefixes.
1716 ;; Adorned regexp of `c-prefix-spec-kwds'.
1721 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that
1722 ;; aren't ambiguous with types or type prefixes.
1730 ;; Keywords that can occur after argument list of a function header
1731 ;; declaration, i.e. in the "K&R region".
1736 ;; Adorned regexp matching all keywords that can't appear at the
1737 ;; start of a declaration.
1747 "Access protection label keywords in classes."
1748 t nil
1753 "Keywords introducing declarations that can contain a block which
1756 like that, it ends with the following ';' and not right away.
1758 The keywords on list are assumed to also be present on one of the
1759 `*-decl-kwds' lists."
1760 t nil
1765 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
1766 ;; languages without such constructs.
1773 "Keywords introducing extra declaration specifiers in the region
1775 declarations."
1776 t nil
1779 "supports"
1780 ;; In CORBA PSDL:
1784 "Keywords that may be followed by a nonsymbol sexp before whatever
1785 construct it's part of continues."
1786 t nil
1790 "Keywords that may be followed by a comma separated list of type
1791 identifiers, where each optionally can be prefixed by keywords. (Can
1792 also be used for the special case when the list can contain only one
1793 element.)
1795 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
1796 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
1797 There's also no reason to add keywords that prefixes a normal
1798 declaration consisting of a type followed by a declarator (list), so
1799 the keywords on `c-modifier-kwds' should normally not be listed here
1800 either.
1802 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1803 or variable identifier (that's being defined)."
1804 t nil
1809 ;; In CORBA PSDL:
1814 "Keywords that may be followed by a comma separated list of
1815 reference (i.e. namespace/scope/module) identifiers, where each
1816 optionally can be prefixed by keywords. (Can also be used for the
1817 special case when the list can contain only one element.) Assumed to
1818 be mutually exclusive with `c-type-list-kwds'.
1820 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1821 or variable identifier (that's being defined)."
1822 t nil
1826 ;; In CORBA CIDL:
1831 "Keywords that may be followed (not necessarily directly) by a colon
1832 and then a comma separated list of type identifiers, where each
1833 optionally can be prefixed by keywords. (Can also be used for the
1834 special case when the list can contain only one element.)"
1835 t nil
1838 ;; In CORBA PSDL:
1842 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
1843 forward to the colon. The end of the match is assumed to be directly
1845 regexp if `c-colon-type-list-kwds' isn't nil."
1847 ;; Disallow various common punctuation chars that can't come
1848 ;; before the ":" that starts the inherit list after "class"
1849 ;; or "struct" in C++. (Also used as default for other
1850 ;; languages.)
1855 "Keywords that may be followed by a parenthesis expression that doesn't
1856 contain type identifiers."
1857 t nil
1859 "__attribute__"
1860 ;; MSVC extension.
1864 "Keywords that may be followed by a parenthesis expression containing
1865 type identifiers separated by arbitrary tokens."
1866 t nil
1878 "Keywords that may be followed by an angle bracket expression
1880 `c-<>-arglist-kwds' is that unknown names are taken to be types and
1881 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
1882 if this isn't nil."
1883 t nil
1886 ;; In CORBA PSDL:
1890 "Keywords that can be followed by a C++ style template arglist; see
1891 `c-recognize-<>-arglists' for details. That language constant is
1892 assumed to be set if this isn't nil."
1893 t nil
1898 ;; All keywords that can be followed by an angle bracket sexp.
1904 ;; Adorned regexp matching keywords that can be followed by an angle
1905 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
1911 "Keywords that may be followed by a brace block containing a comma
1912 separated list of identifier definitions, i.e. like the list of
1913 identifiers that follows the type in a normal declaration."
1917 "Statement keywords followed directly by a substatement."
1921 idl nil)
1924 ;; Regexp matching the start of any statement followed directly by a
1925 ;; substatement (doesn't match a bare block, however).
1930 "Statement keywords followed by a paren sexp and then by a substatement."
1934 idl nil
1939 ;; Regexp matching the start of any statement followed by a paren sexp
1940 ;; and then by a substatement.
1945 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
1951 ;; Regexp matching the start of any statement that has a
1952 ;; substatement (except a bare block). Nil in languages that
1953 ;; don't have such constructs.
1962 "Statement keywords followed by an expression or nothing."
1964 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
1966 idl nil
1973 ;; Adorned regexp matching `c-simple-stmt-kwds'.
1978 "Statement keywords followed by a parenthesis expression that
1979 nevertheless contains a list separated with ';' and not ','."
1981 idl nil)
1984 ;; Adorned regexp matching `c-paren-stmt-kwds'.
1989 "Statement keywords followed by an assembler expression."
1990 t nil
1994 ;; Regexp matching the start of an assembler statement. Nil in
1995 ;; languages that don't support that.
2001 "Keywords introducing colon terminated labels in blocks."
2003 awk nil)
2006 ;; Adorned regexp matching any keyword that introduces a label.
2011 "Keywords that might be followed by a label identifier."
2015 idl nil
2016 awk nil)
2019 "Keywords for constants."
2020 t nil
2028 "Keywords besides constants and operators that start primary expressions."
2029 t nil
2036 ;; Keywords that can occur anywhere in expressions. Built from
2037 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2041 t
2046 "Keywords that start lambda constructs, i.e. function definitions in
2047 expressions."
2048 t nil
2052 "Keywords that start constructs followed by statement blocks which can
2053 be used in expressions \(the gcc extension for this in C and C++ is
2054 handled separately by `c-recognize-paren-inexpr-blocks')."
2055 t nil
2059 "Keywords that can start classes inside expressions."
2060 t nil
2065 "Keywords that can start brace list blocks inside expressions.
2066 Note that Java specific rules are currently applied to tell this from
2067 `c-inexpr-class-kwds'."
2068 t nil
2072 ;; Regexp matching the start of a brace list in an expression, or
2073 ;; nil in languages that don't have such things. This should not
2074 ;; match brace lists recognized through `c-special-brace-lists'.
2081 ;; Regexp matching keywords in any construct that contain another
2082 ;; declaration level, i.e. that isn't followed by a function block
2083 ;; or brace list. When the first submatch matches, it's an
2084 ;; unambiguous construct, otherwise it's an ambiguous match that
2085 ;; might also be the return type of a function declaration.
2103 "Keywords that can introduce bitfields."
2104 t nil
2108 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2109 ;; languages without bitfield support.
2110 t nil
2115 "Keywords not accounted for by any other `*-kwds' language constant."
2116 t nil
2118 ;; In CORBA CIDL: (These are declaration keywords that never
2119 ;; can start a declaration.)
2122 \f
2123 ;;; Constants built from keywords.
2125 ;; Note: No `*-kwds' language constants may be defined below this point.
2129 ;; List of all the language constants that contain keyword lists.
2134 ;; Make the list of globally interned symbols
2135 ;; instead of ones interned in `c-lang-constants'.
2137 c-lang-constants)
2138 list)))
2141 ;; All keywords as a list.
2146 c-kwds-lang-consts)
2147 nil))
2151 ;; All keywords as an adorned regexp.
2156 ;; An alist with all the keywords in the cars. The cdr for each
2157 ;; keyword is a list of the symbols for the `*-kwds' lists that
2158 ;; contains it.
2164 c-kwds-lang-consts))))
2165 lang-const kwd-list kwd
2166 result-alist elem)
2178 result-alist))
2181 ;; An obarray containing all keywords as symbols. The property list
2182 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2183 ;; lists it's a member of.
2184 ;;
2185 ;; E.g. to see whether the string str contains a keyword on
2186 ;; `c-class-decl-kwds', one can do like this:
2187 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2188 ;; Which preferably is written using the associated functions in
2189 ;; cc-engine:
2190 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2192 ;; The obarray is not stored directly as a language constant since
2193 ;; the printed representation for obarrays used in .elc files isn't
2194 ;; complete.
2197 kwd lang-const-list
2204 ;; Emacs has an odd bug that causes `mapcan' to fail
2205 ;; with unintelligible errors. (XEmacs works.)
2206 ;;(mapcan (lambda (lang-const)
2207 ;; (list lang-const t))
2208 ;; lang-const-list)
2211 lang-const-list))))
2212 obarray))
2215 ;; Adorned regexp matching all keywords that should be fontified
2216 ;; with the keywords face. I.e. that aren't types or constants.
2226 ;; Regexp matching the start of any primary expression, i.e. any
2227 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2228 ;; exclude keywords; they are excluded afterwards unless the second
2229 ;; submatch matches. If the first but not the second submatch
2230 ;; matches then it is an ambiguous primary expression; it could also
2231 ;; be a match of e.g. an infix operator. (The case with ambiguous
2232 ;; keyword operators isn't handled.)
2238 ;; Filter out the special case prefix
2239 ;; operators that are close parens.
2244 t
2250 postfix-if-paren
2251 left-assoc
2252 right-assoc
2253 right-assoc-sequence)
2254 t))
2257 in-or-postfix-ops
2260 in-or-postfix-ops
2265 ;; Take out all symbol class operators from `prefix-ops' and make the
2266 ;; first submatch from them together with `c-primary-expr-kwds'.
2273 ;; Match all ambiguous operators.
2280 ;; Now match all other symbols.
2284 ;; The chars that can start integer and floating point
2285 ;; constants.
2289 ;; The nonambiguous operators from `prefix-ops'.
2295 ;; Match string and character literals.
2302 \f
2303 ;;; Additional constants for parser-level constructs.
2306 "Regexp matching something that might precede a declaration, cast or
2307 label, such as the last token of a preceding statement or declaration.
2308 This is used in the common situation where a declaration or cast
2309 doesn't start with any specific token that can be searched for.
2311 The regexp should not match bob; that is done implicitly. It can't
2312 require a match longer than one token. The end of the token is taken
2313 to be at the end of the first submatch, which is assumed to always
2314 match. It's undefined whether identifier syntax (see
2315 `c-identifier-syntax-table') is in effect or not. This regexp is
2316 assumed to be a superset of `c-label-prefix-re' if
2317 `c-recognize-colon-labels' is set.
2319 Besides this, `c-decl-start-kwds' is used to find declarations.
2321 Note: This variable together with `c-decl-start-re' and
2323 declaration/cast/label starts. I.e. they might produce more matches
2324 but should not miss anything (or else it's necessary to use text
2325 properties - see the next note). Wherever they match, the following
2326 construct is analyzed to see if it indeed is a declaration, cast or
2327 label. That analysis is not cheap, so it's important that not too
2328 many false matches are triggered.
2330 Note: If a declaration/cast/label start can't be detected with this
2331 variable, it's necessary to use the `c-type' text property with the
2332 value `c-decl-end' on the last char of the last token preceding the
2333 declaration. See the comment blurb at the start of cc-engine.el for
2334 more info."
2336 ;; We match a sequence of characters to skip over things like \"};\"
2337 ;; more quickly. We match ")" in C for K&R region declarations, and
2338 ;; in all languages except Java for when a cpp macro definition
2339 ;; begins with a declaration.
2342 ;; Match "<" in C++ to get the first argument in a template arglist.
2343 ;; In that case there's an additional check in `c-find-decl-spots'
2344 ;; that it got open paren syntax.
2346 ;; Additionally match the protection directives in Objective-C.
2347 ;; Note that this doesn't cope with the longer directives, which we
2348 ;; would have to match from start to end since they don't end with
2349 ;; any easily recognized characters.
2353 ;; Pike is like C but we also match "[" for multiple value
2354 ;; assignments and type casts.
2360 "Regexp matching the start of any declaration, cast or label.
2361 It's used on the token after the one `c-decl-prefix-re' matched. This
2362 regexp should not try to match those constructs accurately as it's
2363 only used as a sieve to avoid spending more time checking other
2364 constructs."
2369 ;; Regexp matching something that might precede or start a
2370 ;; declaration, cast or label.
2371 ;;
2372 ;; If the first submatch matches, it's taken to match the end of a
2373 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2374 ;; It's built from `c-decl-prefix-re'.
2375 ;;
2376 ;; If the first submatch did not match, the match of the whole
2377 ;; regexp is taken to be at the first token in the declaration.
2378 ;; `c-decl-start-re' is not checked in this case.
2379 ;;
2380 ;; Design note: The reason the same regexp is used to match both
2381 ;; tokens that precede declarations and start them is to avoid an
2382 ;; extra regexp search from the previous declaration spot in
2383 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2384 ;; that it finds all declaration/cast/label starts in approximately
2385 ;; linear order, so we can't do the searches in two separate passes.
2396 ;; List containing the paren characters that can open a cast, or nil in
2397 ;; languages without casts.
2405 "List of syntactically relevant characters that never can occur before
2406 the open brace in any construct that contains a brace block, e.g. in
2409 class Foo: public Bar {int x();} a, *b;
2411 If parens can occur, the chars inside those aren't filtered with this
2412 list.
2414 '<' and '>' should be disallowed even if angle bracket arglists can
2415 occur. That since the search function needs to stop at them anyway to
2416 ensure they are given paren syntax.
2418 This is used to skip backward from the open brace to find the region
2421 possible for good performance."
2423 ;; Default to all chars that only occurs in nonsymbol tokens outside
2424 ;; identifiers.
2430 t
2431 t
2435 op pos)
2438 res))))
2440 ;; Allow cpp operatios (where applicable).
2446 ;; Allow ':' for inherit list starters.
2450 ;; Allow ',' for multiple inherits.
2454 ;; Allow parentheses for anonymous inner classes in Java and class
2455 ;; initializer lists in Pike.
2459 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2464 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2465 ;; for `c-syntactic-skip-backward'.
2470 "Regexp matching the declarator operators that might precede the
2473 The end of the first submatch is taken as the end of the operator.
2474 Identifier syntax is in effect when this is matched \(see
2475 `c-identifier-syntax-table')."
2478 ;; Default to a regexp that never matches.
2480 ;; Check that there's no "=" afterwards to avoid matching tokens
2481 ;; like "*=".
2483 "[*\(]"
2489 "[*\(&]"
2492 ;; If this matches there's special treatment in
2493 ;; `c-font-lock-declarators' and
2494 ;; `c-font-lock-declarations' that check for a
2495 ;; complete name followed by ":: *".
2507 "Regexp matching the declarator operators that might follow after the
2510 it matches an open paren of some kind, the type declaration check
2511 continues at the corresponding close paren, otherwise the end of the
2512 first submatch is taken as the end of the operator. Identifier syntax
2513 is in effect when this is matched (see `c-identifier-syntax-table')."
2514 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2515 ;; function argument list parenthesis.
2523 "[\)\[\(]"
2527 ;; "throw" in `c-type-modifier-kwds' is followed
2528 ;; by a parenthesis list, but no extra measures
2529 ;; are necessary to handle that.
2539 "This regexp is matched after a declarator expression where
2540 `c-type-decl-suffix-key' has matched. If it matches then the
2541 construct is taken as a declaration. It's typically used to match the
2542 beginning of a function body or whatever might occur after the
2543 function header in a function declaration or definition. It's
2544 undefined whether identifier syntax (see `c-identifier-syntax-table')
2545 is in effect or not.
2550 t "{"
2551 ;; If K&R style declarations should be recognized then one could
2552 ;; consider to match the start of any symbol since we want to match
2553 ;; the start of the first declaration in the "K&R region". That
2554 ;; could however produce false matches on code like "FOO(bar) x"
2555 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2556 ;; on the other heuristics in that case.
2558 ;; Add on the keywords in `c-postfix-spec-kwds'.
2563 ;; Also match the colon that starts a base class initializer list in
2564 ;; C++. That can be confused with a function call before the colon
2565 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2566 ;; match before such a thing (as a declaration-level construct;
2567 ;; matches inside arglist contexts are already excluded).
2574 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2575 ;; matches ";" and ",".
2584 end of the operator. nil in languages without such operators. It's
2585 undefined whether identifier syntax (see `c-identifier-syntax-table')
2586 is in effect or not."
2587 t nil
2593 "Regexp matching operators that might follow after a type, or nil in
2594 languages that don't have such operators. The end of the first
2595 submatch is taken as the end of the operator. This should not match
2596 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2597 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2598 is in effect or not."
2599 t nil
2605 ;; Regexp matching the known type identifiers. This is initialized
2606 ;; from the type keywords and `*-font-lock-extra-types'. The first
2607 ;; submatch is the one that matches the type. Note that this regexp
2608 ;; assumes that symbol constituents like '_' and '$' have word
2609 ;; syntax.
2618 extra-types)))
2624 extra-types))))
2629 plain-strings)))
2630 regexp-strings)
2635 "List of open- and close-chars that makes up a pike-style brace list,
2637 list."
2638 t nil
2643 "Non-nil means K&R style argument declarations are valid."
2644 t nil
2645 c t)
2649 "Non-nil means function declarations without return type should be
2650 recognized. That can introduce an ambiguity with parenthesized macro
2651 calls before a brace block. This setting does not affect declarations
2652 that are preceded by a declaration starting keyword, so
2653 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2654 t nil
2660 "Non-nil means C++ style template arglists should be handled. More
2661 specifically, this means a comma separated list of types or
2663 identifier or one of the keywords on `c-<>-type-kwds' or
2664 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2665 expression is considered to be a type."
2671 "Non-nil means that parenthesis style initializers exist,
2672 i.e. constructs like
2674 Foo bar (gnu);
2676 in addition to the more classic
2678 Foo bar = gnu;"
2679 t nil
2684 "Non-nil to recognize gcc style in-expression blocks,
2685 i.e. compound statements surrounded by parentheses inside expressions."
2686 t nil
2692 ;; Regexp matching the start of angle bracket arglists in languages
2693 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2694 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2695 ;; assumed to surround the preceding symbol. The whole match is
2696 ;; assumed to end directly after the opening "<".
2706 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2707 ;; parens. The first submatch is assumed to surround
2708 ;; `c-opt-<>-arglist-start'.
2717 ;; Regexp matching the beginning of a declaration specifier in the
2718 ;; region between the header and the body of a declaration.
2719 ;;
2720 ;; TODO: This is currently not used uniformly; c++-mode and
2721 ;; java-mode each have their own ways of using it.
2722 t nil
2735 That includes labels in code and access keys in classes. This does
2736 not apply to labels recognized by `c-label-kwds' and
2737 `c-opt-extra-label-key'."
2738 t nil
2744 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2745 a generic colon label. Not used if `c-recognize-colon-labels' is
2746 nil."
2752 "Regexp matching things that can't occur in generic colon labels,
2753 neither in a statement nor in a declaration context. The regexp is
2754 tested at the beginning of every sexp in a suspected label,
2757 ;; Don't allow string literals.
2759 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
2765 ;; Also check for open parens in C++, to catch member init lists in
2766 ;; constructors. We normally allow it so that macros with arguments
2767 ;; work in labels.
2772 "Optional regexp matching labels.
2773 Normally, labels are detected according to `c-nonlabel-token-key',
2774 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
2775 be used if there are additional labels that aren't recognized that
2776 way."
2777 t nil
2782 ;; Regexp describing friend declarations classes, or nil in
2783 ;; languages that don't have such things.
2784 ;;
2785 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
2786 ;; template skipping isn't done properly. This will disappear soon.
2787 t nil
2792 "<.+>"
2794 "friend"
2799 ;; Special regexp to match the start of Objective-C methods. The
2800 ;; first submatch is assumed to end after the + or - key.
2801 t nil
2803 ;; TODO: Ought to use a better method than anchoring on bol.
2808 "([^\)]*)"
2815 ;; Must be set in buffers where the `c-type' text property might be
2816 ;; used with the value `c-decl-end'.
2817 ;;
2818 ;; `c-decl-end' is used to mark the ends of labels and access keys
2819 ;; to make interactive refontification work better.
2822 ;; `c-decl-end' is used to mark the end of the @-style directives in
2823 ;; Objective-C.
2824 objc t)
2827 \f
2828 ;;; Wrap up the `c-lang-defvar' system.
2830 ;; Compile in the list of language variables that has been collected
2831 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
2832 ;; first element of each is nil.
2837 "Create a function that initializes all the language dependent variables
2838 for the given mode.
2840 This function should be evaluated at compile time, so that the
2841 function it returns is byte compiled with all the evaluated results
2842 from the language constants. Use the `c-init-language-vars' macro to
2843 accomplish that conveniently."
2849 ;; No need to byte compile this lambda since the byte compiler is
2850 ;; smart enough to detect the `funcall' construct in the
2851 ;; `c-init-language-vars' macro below and compile it all straight
2852 ;; into the function that contains `c-init-language-vars'.
2855 ;; This let sets up the context for `c-mode-var' and similar
2856 ;; that could be in the result from `cl-macroexpand-all'.
2858 current-var source-eval)
2864 ;; `c-lang-const' will expand to the evaluated
2865 ;; constant immediately in `cl-macroexpand-all'
2866 ;; below.
2872 ;; Note: The following `append' copies the
2873 ;; first argument. That list is small, so
2874 ;; this doesn't matter too much.
2878 ;; This diagnostic message isn't useful for end
2879 ;; users, so it's disabled.
2880 ;;(unless (get ',mode 'c-has-warned-lang-consts)
2881 ;; (message ,(concat "%s compiled with CC Mode %s "
2882 ;; "but loaded with %s - evaluating "
2883 ;; "language constants from source")
2884 ;; ',mode ,c-version c-version)
2885 ;; (put ',mode 'c-has-warned-lang-consts t))
2899 current-var
2902 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
2905 err)
2908 ;; Being evaluated from source. Always use the dynamic method to
2909 ;; work well when `c-lang-defvar's in this file are reevaluated
2910 ;; interactively.
2916 current-var)
2927 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
2928 current-var err)
2930 ))
2933 "Initialize all the language dependent variables for the given mode.
2934 This macro is expanded at compile time to a form tailored for the mode
2935 in question, so MODE must be a constant. Therefore MODE is not
2936 evaluated and should not be quoted."
2939 \f
2942 ;;; arch-tag: 1ab57482-cfc2-4c5b-b628-3539c3098822
2943 ;;; cc-langs.el ends here