| blob | b02df16b4f5cb6d70c6b59452487149117b13b47 |
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'. They are used to build the lambda in
138 ;; `c-make-init-lang-vars-fun' below.
142 c-lang-variable-inits-tail c-lang-variable-inits))
145 "Declares the buffer local variable VAR to get the value VAL. VAL is
146 evaluated and assigned at mode initialization. More precisely, VAL is
147 evaluated and bound to VAR when the result from the macro
148 `c-init-language-vars' is evaluated.
150 `c-lang-const' is typically used in VAL to get the right value for the
151 language being initialized, and such calls will be macro expanded to
152 the evaluated constant value at compile time."
158 ;; Special case: If there's no docstring and the value is a
159 ;; simple (c-lang-const foo) where foo is the same name as VAR
160 ;; then take the docstring from the language constant foo.
172 ;; Return the symbol, like the other def* forms.
181 ;; Some helper functions used when building the language constants.
184 ;; Used to filter operators from the list OPS in a DWIM:ey way:
185 ;; OPS either has the structure of `c-operators', as a single
186 ;; group in `c-operators', or is a plain list of operators.
187 ;; OPGROUP-FILTER is used filter out the operator groups. It can
188 ;; be t to choose all groups, a list of the group type symbols to
189 ;; accept, or a function which will be called with the group
190 ;; symbol for each group and should return non-nil for those to
191 ;; include. OP-FILTER filters the individual operators in each
192 ;; group. It can be t to choose all operators, a regexp to test
193 ;; against each operator, or a function which will be called for
194 ;; each operator and should return non-nil for those to include.
195 ;; If XLATE is given, it's a function which is called for each
196 ;; matching operator and its return value is collected instead.
197 ;; If it returns a list, the elements are spliced directly into
198 ;; the final result, which is returned as a list with duplicates
199 ;; removed using `equal'. `c-mode-syntax-table' for the current
200 ;; mode is in effect during the whole procedure.
221 t)
222 t)
227 opgroup)))
228 ops)
231 \f
232 ;;; Various mode specific values that aren't language related.
235 ;; The definition for the mode menu. The menu title is prepended to
236 ;; this before it's fed to `easy-menu-define'.
246 "----"
250 ;; Only applicable if there's a cpp preprocessor.
254 "----"
259 "----"
272 \f
273 ;;; Syntax tables.
276 "Populate the given syntax table as necessary for a C-like language.
294 ;; Set up block and line oriented comments. The new C
295 ;; standard mandates both comment styles even in C, so since
296 ;; all languages now require dual comments, we make this the
297 ;; default.
299 ;; XEmacs
303 ;; Emacs
307 ;; incompatible
311 ;; Give CR the same syntax as newline, for selective-display
315 "Functions that generates the mode specific syntax tables.
316 The syntax tables aren't stored directly since they're quite large."
320 ;; Mode specific syntaxes.
322 ;; Let '@' be part of symbols in ObjC to cope with
323 ;; its compiler directives as single keyword tokens.
324 ;; This is then necessary since it's assumed that
325 ;; every keyword is a single symbol.
329 table)))
332 ;; The syntax tables in evaluated form. Only used temporarily when
333 ;; the constants in this file are evaluated.
337 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
338 ;; parenthesis characters. Used temporarily when template argument
339 ;; lists are parsed. Note that this encourages incorrect parsing of
340 ;; templates since they might contain normal operators that uses the
341 ;; '<' and '>' characters. Therefore this syntax table might go
342 ;; away when CC Mode handles templates correctly everywhere.
343 t nil
348 table)))
354 "A list that describes the modifications that should be done to the
355 mode syntax table to get a syntax table that matches all identifiers
356 and keywords as words.
358 The list is just like the one used in `font-lock-defaults': Each
359 element is a cons where the car is the character to modify and the cdr
360 the new syntax, as accepted by `modify-syntax-entry'."
361 ;; The $ character is not allowed in most languages (one exception
362 ;; is Java which allows it for legacy reasons) but we still classify
363 ;; it as an indentifier character since it's often used in various
364 ;; machine generated identifiers.
375 mod)
380 table)
381 "Syntax table built on the mode syntax table but additionally
382 classifies symbol constituents like '_' and '$' as word constituents,
385 \f
386 ;;; Lexer-level syntax (identifiers, tokens etc).
389 "Regexp that matches the start of a symbol, i.e. any identifier or
391 operator at the top level."
398 "Set of characters that can be part of a symbol.
399 This is on the form that fits inside [ ] in a regexp."
400 ;; Pike note: With the backquote identifiers this would include most
401 ;; operator chars too, but they are handled with other means instead.
406 "Regexp matching identifiers and keywords (with submatch 0). Assumed
407 to match if `c-symbol-start' matches on the same position."
411 ;; Use the value from C here since the operator backquote is
412 ;; covered by the other alternative.
420 ;; Number of regexp grouping parens in `c-symbol-key'.
424 "This is the set of chars that can't be part of a symbol, i.e. the
425 negation of `c-symbol-chars'."
430 "Regexp that matches any character that can't be part of a symbol.
431 It's usually appended to other regexps to avoid matching a prefix.
432 It's assumed to not contain any submatchers."
433 ;; The same thing regarding Unicode identifiers applies here as to
434 ;; `c-symbol-key'.
438 "The operators that make up fully qualified identifiers. nil in
439 languages that don't have such things. See `c-operators' for a
440 description of the format. Binary operators can concatenate symbols,
444 This value is by default merged into `c-operators'."
445 t nil
449 ;; Java has "." to concatenate identifiers but it's also used for
450 ;; normal indexing. There's special code in the Java font lock
451 ;; rules to fontify qualified identifiers based on the standard
452 ;; naming conventions. We still define "." here to make
453 ;; `c-forward-name' move over as long names as possible which is
454 ;; necessary to e.g. handle throws clauses correctly.
463 ;; Appendable adorned regexp matching the operators that join
464 ;; symbols to fully qualified identifiers, or nil in languages that
465 ;; don't have such things.
466 ;;
467 ;; This was a docstring constant in 5.30. It still works but is now
468 ;; considered internal - change `c-identifier-ops' instead.
471 t)))
479 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
483 ;; Appendable adorned regexp matching operators that might precede
484 ;; an identifier and that are part of the identifier in that case.
485 ;; nil in languages without such things.
488 t)))
493 "Operators that can occur after a binary operator on `c-identifier-ops'
494 in identifiers. nil in languages that don't have such things.
496 Operators here should also have appropriate entries in `c-operators' -
497 it's not taken care of by default."
498 t nil
499 ;; '~' for destructors in C++, '*' for member pointers.
501 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
502 ;; in import declarations. (This will also match bogus things like
503 ;; "foo.*bar" but we don't bother.)
507 ;; Regexp that must match the token after
508 ;; `c-opt-identifier-concat-key' for it to be considered an
509 ;; identifier concatenation operator (which e.g. causes the
510 ;; preceding identifier to be fontified as a reference). Assumed to
511 ;; be a string if `c-opt-identifier-concat-key' is.
512 ;;
513 ;; This was a docstring constant in 5.30. It still works but is now
514 ;; considered internal - change `c-after-id-concat-ops' instead.
522 "Regexp that matches the start of an (optionally qualified) identifier.
523 It should also match all keywords. It's unspecified how far it
524 matches."
534 C++. It does not recognize the full range of syntactic whitespace
535 between the tokens; `c-forward-name' has to be used for that. It
536 should also not match identifiers containing parenthesis groupings,
538 ;; This regexp is more complex than strictly necessary to ensure
539 ;; that it can be matched with a minimum of backtracking.
560 ;; For flexibility, consider the symbol match
561 ;; optional if we've hit a
562 ;; `c-after-id-concat-ops' operator. This is
563 ;; also necessary to handle the "*" that can
564 ;; end import declaration identifiers in Java.
578 ;; This was a docstring constant in 5.30 but it's no longer used.
579 ;; It's only kept to avoid breaking third party code.
580 ;;
581 ;; Used to identify the submatch in `c-identifier-key' that
582 ;; surrounds the last symbol in the qualified identifier. It's a
583 ;; list of submatch numbers, of which the first that has a match is
584 ;; taken. It's assumed that at least one does when the regexp has
585 ;; matched.
586 t nil)
589 "Set if the language support backslash escaped newlines inside string
590 literals."
591 t nil
597 "Set if the language supports multiline string literals without escaped
598 newlines. If t, all string literals are multiline. If a character,
599 only literals where the open quote is immediately preceded by that
600 literal are multiline."
601 t nil
602 pike ?#)
607 "Regexp matching the prefix of a cpp directive in the languages that
608 normally use that macro preprocessor. Tested at bol or at boi.
610 ;; TODO (ACM, 2005-04-01). Amend the following to recognise escaped NLs;
611 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
617 "Regexp matching the prefix of a cpp directive including the directive
618 name, or nil in languages without preprocessor support. The first
619 submatch surrounds the directive name."
623 ;; Pike, being a scripting language, recognizes hash-bangs too.
629 "List of cpp directives (without the prefix) that are followed by a
630 string message."
636 "List of cpp directives (without the prefix) that are followed by a
637 file name in angle brackets or quotes."
643 "Cpp directive (without the prefix) that is followed by a macro
644 definition, or nil if the language doesn't have any."
649 ;; Regexp matching everything up to the macro body of a cpp define,
650 ;; or the end of the logical line if there is none. Set if
651 ;; c-opt-cpp-macro-define is.
661 "List if cpp directives (without the prefix) that are followed by an
662 expression."
667 "List of functions in cpp expressions."
673 "List of all assignment operators."
679 idl nil)
682 "List describing all operators, along with their precedence and
683 associativity. The order in the list corresponds to the precedence of
684 the operators: The operators in each element is a group with the same
685 precedence, and the group has higher precedence than the groups in all
686 following elements. The car of each element describes the type of of
687 the operator group, and the cdr is a list of the operator tokens in
688 it. The operator group types are:
690 'prefix Unary prefix operators.
691 'postfix Unary postfix operators.
692 'postfix-if-paren
693 Unary postfix operators if and only if the chars have
694 parenthesis syntax.
695 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
696 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
697 'right-assoc-sequence
698 Right associative operator that constitutes of a
699 sequence of tokens that separate expressions. All the
700 tokens in the group are in this case taken as
701 describing the sequence in one such operator, and the
702 order between them is therefore significant.
704 Operators containing a character with paren syntax are taken to match
705 with a corresponding open/close paren somewhere else. A postfix
706 operator with close paren syntax is taken to end a postfix expression
707 started somewhere earlier, rather than start a new one at point. Vice
708 versa for prefix operators with open paren syntax.
711 often are described as postfix operators are considered binary here,
712 since CC Mode treats every identifier as an expression."
714 ;; There's currently no code in CC Mode that exploit all the info
715 ;; in this variable; precedence, associativity etc are present as a
716 ;; preparation for future work.
727 ;; Primary.
736 ;; Postfix.
738 ;; The following need special treatment.
748 ;; Unary.
755 ;; The following need special treatment.
766 ;; Member selection.
770 ;; Multiplicative.
773 ;; Additive.
776 ;; Shift.
781 ;; Relational.
786 ;; Equality.
790 ;; Bitwise and.
794 ;; Bitwise exclusive or.
800 ;; Bitwise or.
806 ;; Logical and.
810 ;; Logical or.
816 ;; Conditional.
819 ;; Assignment.
822 ;; Exception.
826 ;; Sequence.
829 ;; IDL got its own definition since it has a much smaller operator
830 ;; set than the other languages.
834 ;; Primary.
836 ;; Unary.
838 ;; Multiplicative.
840 ;; Additive.
842 ;; Shift.
844 ;; And.
846 ;; Xor.
848 ;; Or.
852 ;; The operators as a flat list (without duplicates).
858 t nil
867 ;; These work like identifiers in Pike.
874 ;; Regexp tested after an "operator" token in C++.
875 t nil
881 "Regexp matching the token before the ones in
882 `c-overloadable-operators' when operators are specified in their
885 languages without operator functions or where the complete operator
886 identifier is listed in `c-overloadable-operators'.
888 This regexp is assumed to not match any non-operator identifier."
889 t nil
895 "List of the tokens made up of characters in the punctuation or
896 parenthesis syntax classes that have uses other than as expression
897 operators."
915 ;; List of all tokens in the punctuation and parenthesis syntax
916 ;; classes.
922 ;; List containing all chars not in the word, symbol or
923 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
924 ;; parenthesis and string delimiter chars.
926 ;; Only go through the chars in the printable ASCII range. No
927 ;; language so far has 8-bit or widestring operators.
933 list)))
936 ;; Regexp matching all tokens in the punctuation and parenthesis
937 ;; syntax classes. Note that this also matches ".", which can start
938 ;; a float.
941 t
947 ;; Regexp matching all assignment operators and only them. The
948 ;; beginning of the first submatch is used to detect the end of the
949 ;; token, along with the end of the whole match.
952 ;; Need special case for "=" since it's a prefix of "==".
964 ;; Regexp matching all tokens containing "<" or ">" which are longer
965 ;; than one char.
968 t
974 ;; Regexp matching the second and subsequent characters of all
975 ;; multicharacter tokens that begin with "<".
978 t
984 ;; Regexp matching the second and subsequent characters of all
985 ;; multicharacter tokens that begin with ">".
988 t
994 ;; The characters that should be considered to bound statements. To
995 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
996 ;; begin with "^" to negate the set. If ? : operators should be
997 ;; detected then the string must end with "?:".
998 t "^;{}?:"
1003 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1004 t "^;,{}?:"
1009 \f
1010 ;;; Syntactic whitespace.
1013 "Regexp matching an ordinary whitespace character.
1015 ;; "\\s " is not enough since it doesn't match line breaks.
1019 ;; Number of regexp grouping parens in `c-simple-ws'.
1023 "String that starts line comments, or nil if such don't exist.
1024 Line comments are always terminated by newlines. At least one of
1025 `c-block-comment-starter' and this one is assumed to be set.
1027 Note that it's currently not enough to set this to support a new
1028 comment style. Other stuff like the syntax table must also be set up
1029 properly."
1030 t "//"
1035 "String that starts block comments, or nil if such don't exist.
1036 Block comments are ended by `c-block-comment-ender', which is assumed
1037 to be set if this is. At least one of `c-line-comment-starter' and
1038 this one is assumed to be set.
1040 Note that it's currently not enough to set this to support a new
1041 comment style. Other stuff like the syntax table must also be set up
1042 properly."
1043 t "/*"
1044 awk nil)
1047 "String that ends block comments, or nil if such don't exist.
1049 Note that it's currently not enough to set this to support a new
1050 comment style. Other stuff like the syntax table must also be set up
1051 properly."
1052 t "*/"
1053 awk nil)
1056 ;; Regexp to match the start of any type of comment.
1062 re)))
1065 ;;;; Added by ACM, 2003/9/18.
1067 ;; Regexp which matches the start of a block comment (if such exists in the
1068 ;; language)
1076 ;; Regexp to match the start of comments and string literals.
1085 "Regexp to match the start of documentation comments."
1087 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1095 "String that starts comments inserted with M-; etc.
1096 `comment-start' is initialized from this."
1097 ;; Default: Prefer line comments to block comments, and pad with a space.
1101 ;; In C we still default to the block comment style since line
1102 ;; comments aren't entirely portable.
1108 "String that ends comments inserted with M-; etc.
1109 `comment-end' is initialized from this."
1110 ;; Default: Use block comment style if comment-start uses block
1111 ;; comments, and pad with a space in that case.
1122 "Regexp to match the start of a comment plus everything up to its body.
1123 `comment-start-skip' is initialized from this."
1124 ;; Default: Allow the last char of the comment starter(s) to be
1125 ;; repeated, then allow any amount of horizontal whitespace.
1139 ;; Regexp matching any sequence that can start syntactic whitespace.
1140 ;; The only uncertain case is '#' when there are cpp directives.
1154 ;; Regexp matching any single character that might end syntactic whitespace.
1169 ;; Regexp matching an unterminated block comment that doesn't
1170 ;; contain line breaks, or nil in languages without block comments.
1171 ;; Does not contain a \| operator at the top level.
1175 ;; It's messy to cook together a regexp that matches anything
1176 ;; but c-block-comment-ender.
1184 "[^"
1185 ;; The quoting rules inside char classes are silly. :P
1194 "]"
1202 ;; Regexp matching a block comment that doesn't contain line breaks,
1203 ;; or nil in languages without block comments. The reason we don't
1204 ;; allow line breaks is to avoid going very far and risk running out
1205 ;; of regexp stack; this regexp is intended to handle only short
1206 ;; comments that might be put in the middle of limited constructs
1207 ;; like declarations. Does not contain a \| operator at the top
1208 ;; level.
1223 ;; Regexp matching a piece of syntactic whitespace that isn't a
1224 ;; sequence of simple whitespace characters. As opposed to
1225 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1226 ;; directives as syntactic whitespace.
1238 ;; Regexp matching syntactic whitespace, including possibly the
1239 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1240 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1241 ;; not contain a \| operator at the top level.
1249 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1253 ;; Regexp matching syntactic whitespace, which is at least one
1254 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1255 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1256 ;; not contain a \| operator at the top level.
1264 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1268 ;; Regexp matching syntactic whitespace without any line breaks. As
1269 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1270 ;; regard cpp directives as syntactic whitespace. Does not contain
1271 ;; a \| operator at the top level.
1279 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1283 ;; Regexp that matches when there is no syntactically significant
1284 ;; text before eol. Macros are regarded as syntactically
1285 ;; significant text here.
1287 ;; Match eol (possibly inside a block comment or preceded
1288 ;; by a line continuation backslash), or the beginning of a
1289 ;; line comment. Note: This has to be modified for awk
1290 ;; where line comments start with '#'.
1304 \f
1305 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
1308 Such a function takes one optional parameter, a buffer position (defaults to
1309 point), and returns NIL or t. This variable contains NIL for languages which
1310 don't have EOL terminated statements. "
1311 t nil
1317 The (admittedly kludgey) purpose of such a function is to prevent an infinite
1318 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
1319 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
1320 even indirectly. This variable contains NIL for languages which don't have
1321 EOL terminated statements."
1322 t nil
1327 \f
1328 ;;; In-comment text handling.
1331 "Regexp to append to `paragraph-start'."
1332 t "$"
1338 "Regexp to append to `paragraph-separate'."
1339 t "$"
1343 \f
1344 ;;; Keyword lists.
1346 ;; Note: All and only all language constants containing keyword lists
1347 ;; should end with "-kwds"; they're automatically collected into the
1348 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1351 "Primitive type keywords. As opposed to the other keyword lists, the
1352 keywords listed here are fontified with the type face instead of the
1353 keyword face.
1355 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1356 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1357 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1358 will be handled.
1360 Do not try to modify this list for end user customizations; the
1361 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1362 the appropriate place for that."
1371 ;; Objective-C extends C, but probably not the new stuff in C99.
1378 ;; In CORBA PSDL:
1379 "ref"
1380 ;; The following can't really end a type, but we have to specify them
1381 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1382 ;; doesn't matter that much.
1385 ;; used as a builtin type.
1390 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1395 "Keywords that might act as prefixes for primitive types. Assumed to
1396 be a subset of `c-primitive-type-kwds'."
1397 t nil
1400 ;; In CORBA PSDL:
1404 "Keywords where the following name - if any - is a type name, and
1405 where the keyword together with the symbol works as a type in
1406 declarations.
1408 Note that an alternative if the second part doesn't hold is
1409 `c-type-list-kwds'. Keywords on this list are typically also present
1410 on one of the `*-decl-kwds' lists."
1411 t nil
1417 ;; Adorned regexp matching `c-type-prefix-kwds'.
1422 "Type modifier keywords. These can occur almost anywhere in types
1423 but they don't build a type of themselves. Unlike the keywords on
1424 `c-primitive-type-kwds', they are fontified with the keyword face and
1425 not the type face."
1426 t nil
1432 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1433 ;; languages without such keywords.
1439 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1440 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1450 ;; All keywords that can start a type (i.e. are either a type prefix
1451 ;; or a complete type).
1458 "Keywords introducing declarations where the following block (if any)
1459 contains another declaration level that should be considered a class.
1461 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1462 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1463 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1464 will be handled.
1466 Note that presence on this list does not automatically treat the
1467 following identifier as a type; the keyword must also be present on
1468 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1469 t nil
1477 ;; In CORBA PSDL:
1479 ;; In CORBA CIDL:
1484 ;; Regexp matching the start of a class.
1489 "Keywords introducing declarations where the following block (if
1490 any) is a brace list.
1492 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1493 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1494 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1495 will be handled."
1500 ;; Regexp matching the start of declarations where the following
1501 ;; block is a brace list.
1506 "Keywords where the following block (if any) contains another
1507 declaration level that should not be considered a class. For every
1508 keyword here, CC Mode will add a set of special syntactic symbols for
1510 `foo-open', `foo-close', and `infoo' symbols.
1512 The intention is that this category should be used for block
1513 constructs that aren't related to object orientation concepts like
1514 classes (which thus also include e.g. interfaces, templates,
1515 contracts, structs, etc). The more pragmatic distinction is that
1516 while most want some indentation inside classes, it's fairly common
1517 that they don't want it in some of these constructs, so it should be
1518 simple to configure that differently from classes. See also
1519 `c-class-decl-kwds'.
1521 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1522 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1523 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1524 will be handled."
1525 t nil
1529 ;; In CORBA CIDL:
1533 ;; Regexp matching the start of blocks besides classes that contain
1534 ;; another declaration level.
1539 "Keywords introducing declarations where the identifier(s) being
1540 declared are types.
1542 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1543 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1544 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1545 will be handled."
1546 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1547 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1548 ;; {...}").
1551 ;; Languages that have a "typedef" construct.
1554 ;; Unlike most other languages, exception names are not handled as
1555 ;; types in IDL since they only can occur in "raises" specs.
1559 "Keywords introducing declarations where the \(first) identifier
1560 \(declarator) follows directly after the keyword, without any type.
1562 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1563 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1564 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1565 will be handled."
1566 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1567 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1568 ;; {...}").
1571 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1572 ;; `c-type-list-kwds' for IDL.
1575 ;; In CORBA PSDL:
1577 ;; In CORBA CIDL:
1583 "Keywords that can prefix normal declarations of identifiers
1584 \(and typically act as flags). Things like argument declarations
1585 inside function headers are also considered declarations in this
1586 sense.
1588 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1589 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1590 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1591 will be handled."
1592 t nil
1597 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1601 ;; In CORBA PSDL:
1603 ;; In CORBA CIDL:
1605 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1612 "Keywords that can start or prefix any declaration level construct,
1613 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1614 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1615 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1617 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1618 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1619 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1620 will be handled."
1621 t nil
1627 "Keywords that always start declarations, wherever they occur.
1628 This can be used for declarations that aren't recognized by the normal
1629 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1630 t nil
1631 ;; Classes can be declared anywhere in a Pike expression.
1635 "Keywords that can occur anywhere in a declaration level construct.
1636 This is used for self-contained things that can be tacked on anywhere
1637 on a declaration and that should be ignored to be able to recognize it
1638 correctly. Typical cases are compiler extensions like
1641 __declspec(noreturn) void foo();
1642 class __declspec(dllexport) classname {...};
1643 void foo() __attribute__((noreturn));
1645 Note that unrecognized plain symbols are skipped anyway if they occur
1646 before the type, so such things are not necessary to mention here.
1647 Mentioning them here is necessary only if they can occur in other
1648 places, or if they are followed by a construct that must be skipped
1650 examples above). In the last case, they alse need to be present on
1651 one of `c-type-list-kwds', `c-ref-list-kwds',
1652 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1653 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1654 ;; NB: These are currently not recognized in all parts of a
1655 ;; declaration. Specifically, they aren't recognized in the middle
1656 ;; of multi-token types, inside declarators, and between the
1657 ;; identifier and the arglist paren of a function declaration.
1658 ;;
1659 ;; FIXME: This ought to be user customizable since compiler stuff
1660 ;; like this usually is wrapped in project specific macros. (It'd
1661 ;; of course be even better if we could cope without knowing this.)
1662 t nil
1664 "__attribute__"
1665 ;; MSVC extension.
1669 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1674 ;; All keywords that can occur in the preamble of a declaration.
1675 ;; They typically occur before the type, but they are also matched
1676 ;; after presumptive types since we often can't be sure that
1677 ;; something is a type or just some sort of macro in front of the
1678 ;; declaration. They might be ambiguous with types or type
1679 ;; prefixes.
1692 ;; Adorned regexp of `c-prefix-spec-kwds'.
1697 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that
1698 ;; aren't ambiguous with types or type prefixes.
1706 ;; Keywords that can occur after argument list of a function header
1707 ;; declaration, i.e. in the "K&R region".
1712 ;; Adorned regexp matching all keywords that can't appear at the
1713 ;; start of a declaration.
1723 "Access protection label keywords in classes."
1724 t nil
1729 "Keywords introducing declarations that can contain a block which
1732 like that, it ends with the following ';' and not right away.
1734 The keywords on list are assumed to also be present on one of the
1735 `*-decl-kwds' lists."
1736 t nil
1741 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
1742 ;; languages without such constructs.
1749 "Keywords introducing extra declaration specifiers in the region
1751 declarations."
1752 t nil
1755 "supports"
1756 ;; In CORBA PSDL:
1760 "Keywords that may be followed by a nonsymbol sexp before whatever
1761 construct it's part of continues."
1762 t nil
1766 "Keywords that may be followed by a comma separated list of type
1767 identifiers, where each optionally can be prefixed by keywords. (Can
1768 also be used for the special case when the list can contain only one
1769 element.)
1771 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
1772 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
1773 There's also no reason to add keywords that prefixes a normal
1774 declaration consisting of a type followed by a declarator (list), so
1775 the keywords on `c-modifier-kwds' should normally not be listed here
1776 either.
1778 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1779 or variable identifier (that's being defined)."
1780 t nil
1785 ;; In CORBA PSDL:
1790 "Keywords that may be followed by a comma separated list of
1791 reference (i.e. namespace/scope/module) identifiers, where each
1792 optionally can be prefixed by keywords. (Can also be used for the
1793 special case when the list can contain only one element.) Assumed to
1794 be mutually exclusive with `c-type-list-kwds'.
1796 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1797 or variable identifier (that's being defined)."
1798 t nil
1802 ;; In CORBA CIDL:
1807 "Keywords that may be followed (not necessarily directly) by a colon
1808 and then a comma separated list of type identifiers, where each
1809 optionally can be prefixed by keywords. (Can also be used for the
1810 special case when the list can contain only one element.)"
1811 t nil
1814 ;; In CORBA PSDL:
1818 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
1819 forward to the colon. The end of the match is assumed to be directly
1821 regexp if `c-colon-type-list-kwds' isn't nil."
1823 ;; Disallow various common punctuation chars that can't come
1824 ;; before the ":" that starts the inherit list after "class"
1825 ;; or "struct" in C++. (Also used as default for other
1826 ;; languages.)
1831 "Keywords that may be followed by a parenthesis expression that doesn't
1832 contain type identifiers."
1833 t nil
1835 "__attribute__"
1836 ;; MSVC extension.
1840 "Keywords that may be followed by a parenthesis expression containing
1841 type identifiers separated by arbitrary tokens."
1842 t nil
1854 "Keywords that may be followed by an angle bracket expression
1856 `c-<>-arglist-kwds' is that unknown names are taken to be types and
1857 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
1858 if this isn't nil."
1859 t nil
1862 ;; In CORBA PSDL:
1866 "Keywords that can be followed by a C++ style template arglist; see
1867 `c-recognize-<>-arglists' for details. That language constant is
1868 assumed to be set if this isn't nil."
1869 t nil
1874 ;; All keywords that can be followed by an angle bracket sexp.
1880 ;; Adorned regexp matching keywords that can be followed by an angle
1881 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
1887 "Keywords that may be followed by a brace block containing a comma
1888 separated list of identifier definitions, i.e. like the list of
1889 identifiers that follows the type in a normal declaration."
1893 "Statement keywords followed directly by a substatement."
1897 idl nil)
1900 ;; Regexp matching the start of any statement followed directly by a
1901 ;; substatement (doesn't match a bare block, however).
1906 "Statement keywords followed by a paren sexp and then by a substatement."
1910 idl nil
1915 ;; Regexp matching the start of any statement followed by a paren sexp
1916 ;; and then by a substatement.
1921 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
1927 ;; Regexp matching the start of any statement that has a
1928 ;; substatement (except a bare block). Nil in languages that
1929 ;; don't have such constructs.
1938 "Statement keywords followed by an expression or nothing."
1940 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
1942 idl nil
1949 ;; Adorned regexp matching `c-simple-stmt-kwds'.
1954 "Statement keywords followed by a parenthesis expression that
1955 nevertheless contains a list separated with ';' and not ','."
1957 idl nil)
1960 ;; Adorned regexp matching `c-paren-stmt-kwds'.
1965 "Statement keywords followed by an assembler expression."
1966 t nil
1970 ;; Regexp matching the start of an assembler statement. Nil in
1971 ;; languages that don't support that.
1977 "Keywords introducing colon terminated labels in blocks."
1979 awk nil)
1982 ;; Adorned regexp matching any keyword that introduces a label.
1987 "Keywords that might be followed by a label identifier."
1991 idl nil
1992 awk nil)
1995 "Keywords for constants."
1996 t nil
2004 "Keywords besides constants and operators that start primary expressions."
2005 t nil
2012 ;; Keywords that can occur anywhere in expressions. Built from
2013 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2017 t
2022 "Keywords that start lambda constructs, i.e. function definitions in
2023 expressions."
2024 t nil
2028 "Keywords that start constructs followed by statement blocks which can
2029 be used in expressions \(the gcc extension for this in C and C++ is
2030 handled separately by `c-recognize-paren-inexpr-blocks')."
2031 t nil
2035 "Keywords that can start classes inside expressions."
2036 t nil
2041 "Keywords that can start brace list blocks inside expressions.
2042 Note that Java specific rules are currently applied to tell this from
2043 `c-inexpr-class-kwds'."
2044 t nil
2048 ;; Regexp matching the start of a brace list in an expression, or
2049 ;; nil in languages that don't have such things. This should not
2050 ;; match brace lists recognized through `c-special-brace-lists'.
2057 ;; Regexp matching keywords in any construct that contain another
2058 ;; declaration level, i.e. that isn't followed by a function block
2059 ;; or brace list. When the first submatch matches, it's an
2060 ;; unambiguous construct, otherwise it's an ambiguous match that
2061 ;; might also be the return type of a function declaration.
2079 "Keywords that can introduce bitfields."
2080 t nil
2084 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2085 ;; languages without bitfield support.
2086 t nil
2091 "Keywords not accounted for by any other `*-kwds' language constant."
2092 t nil
2094 ;; In CORBA CIDL: (These are declaration keywords that never
2095 ;; can start a declaration.)
2098 \f
2099 ;;; Constants built from keywords.
2101 ;; Note: No `*-kwds' language constants may be defined below this point.
2105 ;; List of all the language constants that contain keyword lists.
2110 ;; Make the list of globally interned symbols
2111 ;; instead of ones interned in `c-lang-constants'.
2113 c-lang-constants)
2114 list)))
2117 ;; All keywords as a list.
2122 c-kwds-lang-consts)
2123 nil))
2127 ;; All keywords as an adorned regexp.
2132 ;; An alist with all the keywords in the cars. The cdr for each
2133 ;; keyword is a list of the symbols for the `*-kwds' lists that
2134 ;; contains it.
2140 c-kwds-lang-consts))))
2141 lang-const kwd-list kwd
2142 result-alist elem)
2154 result-alist))
2157 ;; An obarray containing all keywords as symbols. The property list
2158 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2159 ;; lists it's a member of.
2160 ;;
2161 ;; E.g. to see whether the string str contains a keyword on
2162 ;; `c-class-decl-kwds', one can do like this:
2163 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2164 ;; Which preferably is written using the associated functions in
2165 ;; cc-engine:
2166 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2168 ;; The obarray is not stored directly as a language constant since
2169 ;; the printed representation for obarrays used in .elc files isn't
2170 ;; complete.
2173 kwd lang-const-list
2180 ;; Emacs has an odd bug that causes `mapcan' to fail
2181 ;; with unintelligible errors. (XEmacs works.)
2182 ;;(mapcan (lambda (lang-const)
2183 ;; (list lang-const t))
2184 ;; lang-const-list)
2187 lang-const-list))))
2188 obarray))
2191 ;; Adorned regexp matching all keywords that should be fontified
2192 ;; with the keywords face. I.e. that aren't types or constants.
2202 ;; Regexp matching the start of any primary expression, i.e. any
2203 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2204 ;; exclude keywords; they are excluded afterwards unless the second
2205 ;; submatch matches. If the first but not the second submatch
2206 ;; matches then it is an ambiguous primary expression; it could also
2207 ;; be a match of e.g. an infix operator. (The case with ambiguous
2208 ;; keyword operators isn't handled.)
2214 ;; Filter out the special case prefix
2215 ;; operators that are close parens.
2220 t
2226 postfix-if-paren
2227 left-assoc
2228 right-assoc
2229 right-assoc-sequence)
2230 t))
2233 in-or-postfix-ops
2236 in-or-postfix-ops
2241 ;; Take out all symbol class operators from `prefix-ops' and make the
2242 ;; first submatch from them together with `c-primary-expr-kwds'.
2249 ;; Match all ambiguous operators.
2256 ;; Now match all other symbols.
2260 ;; The chars that can start integer and floating point
2261 ;; constants.
2265 ;; The nonambiguous operators from `prefix-ops'.
2271 ;; Match string and character literals.
2278 \f
2279 ;;; Additional constants for parser-level constructs.
2282 "Regexp matching something that might precede a declaration, cast or
2283 label, such as the last token of a preceding statement or declaration.
2284 This is used in the common situation where a declaration or cast
2285 doesn't start with any specific token that can be searched for.
2287 The regexp should not match bob; that is done implicitly. It can't
2288 require a match longer than one token. The end of the token is taken
2289 to be at the end of the first submatch, which is assumed to always
2290 match. It's undefined whether identifier syntax (see
2291 `c-identifier-syntax-table') is in effect or not. This regexp is
2292 assumed to be a superset of `c-label-prefix-re' if
2293 `c-recognize-colon-labels' is set.
2295 Besides this, `c-decl-start-kwds' is used to find declarations.
2297 Note: This variable together with `c-decl-start-re' and
2299 declaration/cast/label starts. I.e. they might produce more matches
2300 but should not miss anything (or else it's necessary to use text
2301 properties - see the next note). Wherever they match, the following
2302 construct is analyzed to see if it indeed is a declaration, cast or
2303 label. That analysis is not cheap, so it's important that not too
2304 many false matches are triggered.
2306 Note: If a declaration/cast/label start can't be detected with this
2307 variable, it's necessary to use the `c-type' text property with the
2308 value `c-decl-end' on the last char of the last token preceding the
2309 declaration. See the comment blurb at the start of cc-engine.el for
2310 more info."
2312 ;; We match a sequence of characters to skip over things like \"};\"
2313 ;; more quickly. We match ")" in C for K&R region declarations, and
2314 ;; in all languages except Java for when a cpp macro definition
2315 ;; begins with a declaration.
2318 ;; Match "<" in C++ to get the first argument in a template arglist.
2319 ;; In that case there's an additional check in `c-find-decl-spots'
2320 ;; that it got open paren syntax.
2322 ;; Additionally match the protection directives in Objective-C.
2323 ;; Note that this doesn't cope with the longer directives, which we
2324 ;; would have to match from start to end since they don't end with
2325 ;; any easily recognized characters.
2329 ;; Pike is like C but we also match "[" for multiple value
2330 ;; assignments and type casts.
2336 "Regexp matching the start of any declaration, cast or label.
2337 It's used on the token after the one `c-decl-prefix-re' matched. This
2338 regexp should not try to match those constructs accurately as it's
2339 only used as a sieve to avoid spending more time checking other
2340 constructs."
2345 ;; Regexp matching something that might precede or start a
2346 ;; declaration, cast or label.
2347 ;;
2348 ;; If the first submatch matches, it's taken to match the end of a
2349 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2350 ;; It's built from `c-decl-prefix-re'.
2351 ;;
2352 ;; If the first submatch did not match, the match of the whole
2353 ;; regexp is taken to be at the first token in the declaration.
2354 ;; `c-decl-start-re' is not checked in this case.
2355 ;;
2356 ;; Design note: The reason the same regexp is used to match both
2357 ;; tokens that precede declarations and start them is to avoid an
2358 ;; extra regexp search from the previous declaration spot in
2359 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2360 ;; that it finds all declaration/cast/label starts in approximately
2361 ;; linear order, so we can't do the searches in two separate passes.
2372 ;; List containing the paren characters that can open a cast, or nil in
2373 ;; languages without casts.
2381 "List of syntactically relevant characters that never can occur before
2382 the open brace in any construct that contains a brace block, e.g. in
2385 class Foo: public Bar {int x();} a, *b;
2387 If parens can occur, the chars inside those aren't filtered with this
2388 list.
2390 '<' and '>' should be disallowed even if angle bracket arglists can
2391 occur. That since the search function needs to stop at them anyway to
2392 ensure they are given paren syntax.
2394 This is used to skip backward from the open brace to find the region
2397 possible for good performance."
2399 ;; Default to all chars that only occurs in nonsymbol tokens outside
2400 ;; identifiers.
2406 t
2407 t
2411 op pos)
2414 res))))
2416 ;; Allow cpp operatios (where applicable).
2422 ;; Allow ':' for inherit list starters.
2426 ;; Allow ',' for multiple inherits.
2430 ;; Allow parentheses for anonymous inner classes in Java and class
2431 ;; initializer lists in Pike.
2435 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2440 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2441 ;; for `c-syntactic-skip-backward'.
2446 "Regexp matching the declarator operators that might precede the
2449 The end of the first submatch is taken as the end of the operator.
2450 Identifier syntax is in effect when this is matched \(see
2451 `c-identifier-syntax-table')."
2454 ;; Default to a regexp that never matches.
2456 ;; Check that there's no "=" afterwards to avoid matching tokens
2457 ;; like "*=".
2459 "[*\(]"
2465 "[*\(&]"
2468 ;; If this matches there's special treatment in
2469 ;; `c-font-lock-declarators' and
2470 ;; `c-font-lock-declarations' that check for a
2471 ;; complete name followed by ":: *".
2483 "Regexp matching the declarator operators that might follow after the
2486 it matches an open paren of some kind, the type declaration check
2487 continues at the corresponding close paren, otherwise the end of the
2488 first submatch is taken as the end of the operator. Identifier syntax
2489 is in effect when this is matched (see `c-identifier-syntax-table')."
2490 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2491 ;; function argument list parenthesis.
2499 "[\)\[\(]"
2503 ;; "throw" in `c-type-modifier-kwds' is followed
2504 ;; by a parenthesis list, but no extra measures
2505 ;; are necessary to handle that.
2515 "This regexp is matched after a declarator expression where
2516 `c-type-decl-suffix-key' has matched. If it matches then the
2517 construct is taken as a declaration. It's typically used to match the
2518 beginning of a function body or whatever might occur after the
2519 function header in a function declaration or definition. It's
2520 undefined whether identifier syntax (see `c-identifier-syntax-table')
2521 is in effect or not.
2526 t "{"
2527 ;; If K&R style declarations should be recognized then one could
2528 ;; consider to match the start of any symbol since we want to match
2529 ;; the start of the first declaration in the "K&R region". That
2530 ;; could however produce false matches on code like "FOO(bar) x"
2531 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2532 ;; on the other heuristics in that case.
2534 ;; Add on the keywords in `c-postfix-spec-kwds'.
2539 ;; Also match the colon that starts a base class initializer list in
2540 ;; C++. That can be confused with a function call before the colon
2541 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2542 ;; match before such a thing (as a declaration-level construct;
2543 ;; matches inside arglist contexts are already excluded).
2550 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2551 ;; matches ";" and ",".
2560 end of the operator. nil in languages without such operators. It's
2561 undefined whether identifier syntax (see `c-identifier-syntax-table')
2562 is in effect or not."
2563 t nil
2569 "Regexp matching operators that might follow after a type, or nil in
2570 languages that don't have such operators. The end of the first
2571 submatch is taken as the end of the operator. This should not match
2572 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2573 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2574 is in effect or not."
2575 t nil
2581 ;; Regexp matching the known type identifiers. This is initialized
2582 ;; from the type keywords and `*-font-lock-extra-types'. The first
2583 ;; submatch is the one that matches the type. Note that this regexp
2584 ;; assumes that symbol constituents like '_' and '$' have word
2585 ;; syntax.
2594 extra-types)))
2600 extra-types))))
2605 plain-strings)))
2606 regexp-strings)
2611 "List of open- and close-chars that makes up a pike-style brace list,
2613 list."
2614 t nil
2619 "Non-nil means K&R style argument declarations are valid."
2620 t nil
2621 c t)
2625 "Non-nil means function declarations without return type should be
2626 recognized. That can introduce an ambiguity with parenthesized macro
2627 calls before a brace block. This setting does not affect declarations
2628 that are preceded by a declaration starting keyword, so
2629 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2630 t nil
2636 "Non-nil means C++ style template arglists should be handled. More
2637 specifically, this means a comma separated list of types or
2639 identifier or one of the keywords on `c-<>-type-kwds' or
2640 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2641 expression is considered to be a type."
2647 "Non-nil means that parenthesis style initializers exist,
2648 i.e. constructs like
2650 Foo bar (gnu);
2652 in addition to the more classic
2654 Foo bar = gnu;"
2655 t nil
2660 "Non-nil to recognize gcc style in-expression blocks,
2661 i.e. compound statements surrounded by parentheses inside expressions."
2662 t nil
2668 ;; Regexp matching the start of angle bracket arglists in languages
2669 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2670 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2671 ;; assumed to surround the preceding symbol. The whole match is
2672 ;; assumed to end directly after the opening "<".
2682 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2683 ;; parens. The first submatch is assumed to surround
2684 ;; `c-opt-<>-arglist-start'.
2693 ;; Regexp matching the beginning of a declaration specifier in the
2694 ;; region between the header and the body of a declaration.
2695 ;;
2696 ;; TODO: This is currently not used uniformly; c++-mode and
2697 ;; java-mode each have their own ways of using it.
2698 t nil
2711 That includes labels in code and access keys in classes. This does
2712 not apply to labels recognized by `c-label-kwds' and
2713 `c-opt-extra-label-key'."
2714 t nil
2720 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2721 a generic colon label. Not used if `c-recognize-colon-labels' is
2722 nil."
2728 "Regexp matching things that can't occur in generic colon labels,
2729 neither in a statement nor in a declaration context. The regexp is
2730 tested at the beginning of every sexp in a suspected label,
2733 ;; Don't allow string literals.
2735 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
2741 ;; Also check for open parens in C++, to catch member init lists in
2742 ;; constructors. We normally allow it so that macros with arguments
2743 ;; work in labels.
2748 "Optional regexp matching labels.
2749 Normally, labels are detected according to `c-nonlabel-token-key',
2750 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
2751 be used if there are additional labels that aren't recognized that
2752 way."
2753 t nil
2758 ;; Regexp describing friend declarations classes, or nil in
2759 ;; languages that don't have such things.
2760 ;;
2761 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
2762 ;; template skipping isn't done properly. This will disappear soon.
2763 t nil
2768 "<.+>"
2770 "friend"
2775 ;; Special regexp to match the start of Objective-C methods. The
2776 ;; first submatch is assumed to end after the + or - key.
2777 t nil
2779 ;; TODO: Ought to use a better method than anchoring on bol.
2784 "([^\)]*)"
2791 ;; Must be set in buffers where the `c-type' text property might be
2792 ;; used with the value `c-decl-end'.
2793 ;;
2794 ;; `c-decl-end' is used to mark the ends of labels and access keys
2795 ;; to make interactive refontification work better.
2798 ;; `c-decl-end' is used to mark the end of the @-style directives in
2799 ;; Objective-C.
2800 objc t)
2803 \f
2804 ;;; Wrap up the `c-lang-defvar' system.
2806 ;; Compile in the list of language variables that has been collected
2807 ;; with the `c-lang-defvar' macro. Note that the first element is
2808 ;; nil.
2812 "Create a function that initializes all the language dependent variables
2813 for the given mode.
2815 This function should be evaluated at compile time, so that the
2816 function it returns is byte compiled with all the evaluated results
2817 from the language constants. Use the `c-init-language-vars' macro to
2818 accomplish that conveniently."
2824 ;; No need to byte compile this lambda since the byte compiler is
2825 ;; smart enough to detect the `funcall' construct in the
2826 ;; `c-init-language-vars' macro below and compile it all straight
2827 ;; into the function that contains `c-init-language-vars'.
2830 ;; This let sets up the context for `c-mode-var' and similar
2831 ;; that could be in the result from `cl-macroexpand-all'.
2833 current-var source-eval)
2839 ;; `c-lang-const' will expand to the evaluated
2840 ;; constant immediately in `cl-macroexpand-all'
2841 ;; below.
2849 ;; This diagnostic message isn't useful for end
2850 ;; users, so it's disabled.
2851 ;;(unless (get ',mode 'c-has-warned-lang-consts)
2852 ;; (message ,(concat "%s compiled with CC Mode %s "
2853 ;; "but loaded with %s - evaluating "
2854 ;; "language constants from source")
2855 ;; ',mode ,c-version c-version)
2856 ;; (put ',mode 'c-has-warned-lang-consts t))
2869 current-var
2872 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
2875 err)
2878 ;; Being evaluated from source. Always use the dynamic method to
2879 ;; work well when `c-lang-defvar's in this file are reevaluated
2880 ;; interactively.
2885 current-var)
2896 "Eval error in the `c-lang-defvar' for `%s' (source eval): %S"
2897 current-var err)
2899 ))
2902 "Initialize all the language dependent variables for the given mode.
2903 This macro is expanded at compile time to a form tailored for the mode
2904 in question, so MODE must be a constant. Therefore MODE is not
2905 evaluated and should not be quoted."
2908 \f
2911 ;;; arch-tag: 1ab57482-cfc2-4c5b-b628-3539c3098822
2912 ;;; cc-langs.el ends here