| blob | bd9af00d9c6d0c6920806fe98fbffd4ff1033ef6 |
1 ;;; cc-langs.el --- language specific settings for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
4 ;; 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software
5 ;; Foundation, Inc.
7 ;; Authors: 1998- Martin Stjernholm
8 ;; 1992-1999 Barry A. Warsaw
9 ;; 1987 Dave Detlefs and Stewart Clamen
10 ;; 1985 Richard M. Stallman
11 ;; Maintainer: bug-cc-mode@gnu.org
12 ;; Created: 22-Apr-1997 (split from cc-mode.el)
13 ;; Version: See cc-mode.el
14 ;; Keywords: c languages oop
16 ;; This file is part of GNU Emacs.
18 ;; GNU Emacs is free software; you can redistribute it and/or modify
19 ;; it under the terms of the GNU General Public License as published by
20 ;; the Free Software Foundation; either version 2, or (at your option)
21 ;; any later version.
23 ;; GNU Emacs is distributed in the hope that it will be useful,
24 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
25 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
26 ;; GNU General Public License for more details.
28 ;; You should have received a copy of the GNU General Public License
29 ;; along with this program; see the file COPYING. If not, write to
30 ;; the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
31 ;; Boston, MA 02110-1301, USA.
33 ;;; Commentary:
35 ;; HACKERS NOTE: There's heavy macro magic here. If you need to make
36 ;; changes in this or other files containing `c-lang-defconst' but
37 ;; don't want to read through the longer discussion below then read
38 ;; this:
39 ;;
40 ;; o A change in a `c-lang-defconst' or `c-lang-defvar' will not take
41 ;; effect if the file containing the mode init function (typically
42 ;; cc-mode.el) is byte compiled.
43 ;; o To make changes show in font locking you need to reevaluate the
44 ;; `*-font-lock-keywords-*' constants, which normally is easiest to
45 ;; do with M-x eval-buffer in cc-fonts.el.
46 ;; o In either case it's necessary to reinitialize the mode to make
47 ;; the changes show in an existing buffer.
49 ;;; Introduction to the language dependent variable system:
50 ;;
51 ;; This file contains all the language dependent variables, except
52 ;; those specific for font locking which reside in cc-fonts.el. As
53 ;; far as possible, all the differences between the languages that CC
54 ;; Mode supports are described with these variables only, so that the
55 ;; code can be shared.
56 ;;
57 ;; The language constant system (see cc-defs.el) is used to specify
58 ;; various language dependent info at a high level, such as lists of
59 ;; keywords, and then from them generate - at compile time - the
60 ;; various regexps and other low-level structures actually employed in
61 ;; the code at runtime.
62 ;;
63 ;; This system is also designed to make it easy for developers of
64 ;; derived modes to customize the source constants for new language
65 ;; variants, without having to keep up with the exact regexps etc that
66 ;; are used in each CC Mode version. It's possible from an external
67 ;; package to add a new language by inheriting an existing one, and
68 ;; then change specific constants as necessary for the new language.
69 ;; The old values for those constants (and the values of all the other
70 ;; high-level constants) may be used to build the new ones, and those
71 ;; new values will in turn be used by the low-level definitions here
72 ;; to build the runtime constants appropriately for the new language
73 ;; in the current version of CC Mode.
74 ;;
75 ;; Like elsewhere in CC Mode, the existence of a doc string signifies
76 ;; that a language constant is part of the external API, and that it
77 ;; therefore can be used with a high confidence that it will continue
78 ;; to work with future versions of CC Mode. Even so, it's not
79 ;; unlikely that such constants will change meaning slightly as this
80 ;; system is refined further; a certain degree of dependence on the CC
81 ;; Mode version is unavoidable when hooking in at this level. Also
82 ;; note that there's still work to be done to actually use these
83 ;; constants everywhere inside CC Mode; there are still hardcoded
84 ;; values in many places in the code.
85 ;;
86 ;; Separate packages will also benefit from the compile time
87 ;; evaluation; the byte compiled file(s) for them will contain the
88 ;; compiled runtime constants ready for use by (the byte compiled) CC
89 ;; Mode, and the source definitions in this file don't have to be
90 ;; loaded then. However, if a byte compiled package is loaded that
91 ;; has been compiled with a different version of CC Mode than the one
92 ;; currently loaded, then the compiled-in values will be discarded and
93 ;; new ones will be built when the mode is initialized. That will
94 ;; automatically trig a load of the file(s) containing the source
95 ;; definitions (i.e. this file and/or cc-fonts.el) if necessary.
96 ;;
97 ;; A small example of a derived mode is available at
98 ;; <http://cc-mode.sourceforge.net/derived-mode-ex.el>. It also
99 ;; contains some useful hints for derived mode developers.
101 ;;; Using language variables:
102 ;;
103 ;; The `c-lang-defvar' forms in this file comprise the language
104 ;; variables that CC Mode uses. It does not work to use
105 ;; `c-lang-defvar' anywhere else (which isn't much of a limitation
106 ;; since these variables sole purpose is to interface with the CC Mode
107 ;; core functions). The values in these `c-lang-defvar's are not
108 ;; evaluated right away but instead collected to a single large `setq'
109 ;; that can be inserted for a particular language with the
110 ;; `c-init-language-vars' macro.
112 ;; This file is only required at compile time, or when not running
113 ;; from byte compiled files, or when the source definitions for the
114 ;; language constants are requested.
116 ;;; Code:
123 load-path)))
130 ;; This file is not always loaded. See note above.
133 \f
134 ;;; Setup for the `c-lang-defvar' system.
137 ;; These are used to collect the init forms from the subsequent
138 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
139 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
140 ;; and `make-variable-buffer-local's in cc-engine and
141 ;; `make-local-variable's in `c-init-language-vars-for'.
145 c-lang-variable-inits-tail c-lang-variable-inits)
149 c-emacs-variable-inits-tail c-emacs-variable-inits))
152 "Declares the buffer local variable VAR to get the value VAL. VAL is
153 evaluated and assigned at mode initialization. More precisely, VAL is
154 evaluated and bound to VAR when the result from the macro
155 `c-init-language-vars' is evaluated.
157 `c-lang-const' is typically used in VAL to get the right value for the
158 language being initialized, and such calls will be macro expanded to
159 the evaluated constant value at compile time."
165 ;; Special case: If there's no docstring and the value is a
166 ;; simple (c-lang-const foo) where foo is the same name as VAR
167 ;; then take the docstring from the language constant foo.
179 ;; Return the symbol, like the other def* forms.
183 "Causes the variable VAR to be made buffer local and to get set to the
184 value VAL. VAL is evaluated and assigned at mode initialization. More
185 precisely, VAL is evaluated and bound to VAR when the result from the
186 macro `c-init-language-vars' is evaluated. VAR is typically a standard
187 Emacs variable like `comment-start'.
189 `c-lang-const' is typically used in VAL to get the right value for the
190 language being initialized, and such calls will be macro expanded to
191 the evaluated constant value at compile time."
198 ;; Return the symbol, like the other def* forms.
202 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
203 ; '
208 ;; Some helper functions used when building the language constants.
211 ;; Used to filter operators from the list OPS in a DWIM:ey way:
212 ;; OPS either has the structure of `c-operators', as a single
213 ;; group in `c-operators', or is a plain list of operators.
214 ;; OPGROUP-FILTER is used filter out the operator groups. It can
215 ;; be t to choose all groups, a list of the group type symbols to
216 ;; accept, or a function which will be called with the group
217 ;; symbol for each group and should return non-nil for those to
218 ;; include. OP-FILTER filters the individual operators in each
219 ;; group. It can be t to choose all operators, a regexp to test
220 ;; against each operator, or a function which will be called for
221 ;; each operator and should return non-nil for those to include.
222 ;; If XLATE is given, it's a function which is called for each
223 ;; matching operator and its return value is collected instead.
224 ;; If it returns a list, the elements are spliced directly into
225 ;; the final result, which is returned as a list with duplicates
226 ;; removed using `equal'. `c-mode-syntax-table' for the current
227 ;; mode is in effect during the whole procedure.
248 t)
249 t)
254 opgroup)))
255 ops)
258 \f
259 ;;; Various mode specific values that aren't language related.
262 ;; The definition for the mode menu. The menu title is prepended to
263 ;; this before it's fed to `easy-menu-define'.
273 "----"
277 ;; Only applicable if there's a cpp preprocessor.
281 "----"
286 "----"
298 c-subword-mode)])))
300 \f
301 ;;; Syntax tables.
304 "Populate the given syntax table as necessary for a C-like language.
322 ;; Set up block and line oriented comments. The new C
323 ;; standard mandates both comment styles even in C, so since
324 ;; all languages now require dual comments, we make this the
325 ;; default.
327 ;; XEmacs
331 ;; Emacs
335 ;; incompatible
339 ;; Give CR the same syntax as newline, for selective-display
343 "Functions that generates the mode specific syntax tables.
344 The syntax tables aren't stored directly since they're quite large."
348 ;; Mode specific syntaxes.
350 ;; Let '@' be part of symbols in ObjC to cope with
351 ;; its compiler directives as single keyword tokens.
352 ;; This is then necessary since it's assumed that
353 ;; every keyword is a single symbol.
357 table)))
360 ;; The syntax tables in evaluated form. Only used temporarily when
361 ;; the constants in this file are evaluated.
365 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
366 ;; parenthesis characters. Used temporarily when template argument
367 ;; lists are parsed. Note that this encourages incorrect parsing of
368 ;; templates since they might contain normal operators that uses the
369 ;; '<' and '>' characters. Therefore this syntax table might go
370 ;; away when CC Mode handles templates correctly everywhere.
371 t nil
376 table)))
382 "A list that describes the modifications that should be done to the
383 mode syntax table to get a syntax table that matches all identifiers
384 and keywords as words.
386 The list is just like the one used in `font-lock-defaults': Each
387 element is a cons where the car is the character to modify and the cdr
388 the new syntax, as accepted by `modify-syntax-entry'."
389 ;; The $ character is not allowed in most languages (one exception
390 ;; is Java which allows it for legacy reasons) but we still classify
391 ;; it as an indentifier character since it's often used in various
392 ;; machine generated identifiers.
403 mod)
408 table)
409 "Syntax table built on the mode syntax table but additionally
410 classifies symbol constituents like '_' and '$' as word constituents,
413 \f
414 ;;; Lexer-level syntax (identifiers, tokens etc).
417 "Regexp that matches the start of a symbol, i.e. any identifier or
419 operator at the top level."
426 "Set of characters that can be part of a symbol.
427 This is on the form that fits inside [ ] in a regexp."
428 ;; Pike note: With the backquote identifiers this would include most
429 ;; operator chars too, but they are handled with other means instead.
434 "Regexp matching identifiers and keywords (with submatch 0). Assumed
435 to match if `c-symbol-start' matches on the same position."
439 ;; Use the value from C here since the operator backquote is
440 ;; covered by the other alternative.
448 ;; Number of regexp grouping parens in `c-symbol-key'.
452 "This is the set of chars that can't be part of a symbol, i.e. the
453 negation of `c-symbol-chars'."
458 "Regexp that matches any character that can't be part of a symbol.
459 It's usually appended to other regexps to avoid matching a prefix.
460 It's assumed to not contain any submatchers."
461 ;; The same thing regarding Unicode identifiers applies here as to
462 ;; `c-symbol-key'.
466 "The operators that make up fully qualified identifiers. nil in
467 languages that don't have such things. See `c-operators' for a
468 description of the format. Binary operators can concatenate symbols,
472 This value is by default merged into `c-operators'."
473 t nil
477 ;; Java has "." to concatenate identifiers but it's also used for
478 ;; normal indexing. There's special code in the Java font lock
479 ;; rules to fontify qualified identifiers based on the standard
480 ;; naming conventions. We still define "." here to make
481 ;; `c-forward-name' move over as long names as possible which is
482 ;; necessary to e.g. handle throws clauses correctly.
491 ;; Appendable adorned regexp matching the operators that join
492 ;; symbols to fully qualified identifiers, or nil in languages that
493 ;; don't have such things.
494 ;;
495 ;; This was a docstring constant in 5.30. It still works but is now
496 ;; considered internal - change `c-identifier-ops' instead.
499 t)))
507 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
511 ;; Appendable adorned regexp matching operators that might precede
512 ;; an identifier and that are part of the identifier in that case.
513 ;; nil in languages without such things.
516 t)))
521 "Operators that can occur after a binary operator on `c-identifier-ops'
522 in identifiers. nil in languages that don't have such things.
524 Operators here should also have appropriate entries in `c-operators' -
525 it's not taken care of by default."
526 t nil
527 ;; '~' for destructors in C++, '*' for member pointers.
529 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
530 ;; in import declarations. (This will also match bogus things like
531 ;; "foo.*bar" but we don't bother.)
535 ;; Regexp that must match the token after
536 ;; `c-opt-identifier-concat-key' for it to be considered an
537 ;; identifier concatenation operator (which e.g. causes the
538 ;; preceding identifier to be fontified as a reference). Assumed to
539 ;; be a string if `c-opt-identifier-concat-key' is.
540 ;;
541 ;; This was a docstring constant in 5.30. It still works but is now
542 ;; considered internal - change `c-after-id-concat-ops' instead.
550 "Regexp that matches the start of an (optionally qualified) identifier.
551 It should also match all keywords. It's unspecified how far it
552 matches."
562 C++. It does not recognize the full range of syntactic whitespace
563 between the tokens; `c-forward-name' has to be used for that. It
564 should also not match identifiers containing parenthesis groupings,
566 ;; This regexp is more complex than strictly necessary to ensure
567 ;; that it can be matched with a minimum of backtracking.
588 ;; For flexibility, consider the symbol match
589 ;; optional if we've hit a
590 ;; `c-after-id-concat-ops' operator. This is
591 ;; also necessary to handle the "*" that can
592 ;; end import declaration identifiers in Java.
606 ;; This was a docstring constant in 5.30 but it's no longer used.
607 ;; It's only kept to avoid breaking third party code.
608 ;;
609 ;; Used to identify the submatch in `c-identifier-key' that
610 ;; surrounds the last symbol in the qualified identifier. It's a
611 ;; list of submatch numbers, of which the first that has a match is
612 ;; taken. It's assumed that at least one does when the regexp has
613 ;; matched.
614 t nil)
617 "Set if the language support backslash escaped newlines inside string
618 literals."
619 t nil
625 "Set if the language supports multiline string literals without escaped
626 newlines. If t, all string literals are multiline. If a character,
627 only literals where the open quote is immediately preceded by that
628 literal are multiline."
629 t nil
630 pike ?#)
635 "Regexp matching the prefix of a cpp directive in the languages that
636 normally use that macro preprocessor. Tested at bol or at boi.
638 ;; TODO (ACM, 2005-04-01). Amend the following to recognise escaped NLs;
639 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
645 "Regexp matching the prefix of a cpp directive including the directive
646 name, or nil in languages without preprocessor support. The first
647 submatch surrounds the directive name."
651 ;; Pike, being a scripting language, recognizes hash-bangs too.
657 "List of cpp directives (without the prefix) that are followed by a
658 string message."
664 "List of cpp directives (without the prefix) that are followed by a
665 file name in angle brackets or quotes."
671 "Cpp directive (without the prefix) that is followed by a macro
672 definition, or nil if the language doesn't have any."
677 ;; Regexp matching everything up to the macro body of a cpp define,
678 ;; or the end of the logical line if there is none. Set if
679 ;; c-opt-cpp-macro-define is.
689 "List if cpp directives (without the prefix) that are followed by an
690 expression."
695 "List of functions in cpp expressions."
701 "List of all assignment operators."
707 idl nil)
710 "List describing all operators, along with their precedence and
711 associativity. The order in the list corresponds to the precedence of
712 the operators: The operators in each element is a group with the same
713 precedence, and the group has higher precedence than the groups in all
714 following elements. The car of each element describes the type of of
715 the operator group, and the cdr is a list of the operator tokens in
716 it. The operator group types are:
718 'prefix Unary prefix operators.
719 'postfix Unary postfix operators.
720 'postfix-if-paren
721 Unary postfix operators if and only if the chars have
722 parenthesis syntax.
723 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
724 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
725 'right-assoc-sequence
726 Right associative operator that constitutes of a
727 sequence of tokens that separate expressions. All the
728 tokens in the group are in this case taken as
729 describing the sequence in one such operator, and the
730 order between them is therefore significant.
732 Operators containing a character with paren syntax are taken to match
733 with a corresponding open/close paren somewhere else. A postfix
734 operator with close paren syntax is taken to end a postfix expression
735 started somewhere earlier, rather than start a new one at point. Vice
736 versa for prefix operators with open paren syntax.
739 often are described as postfix operators are considered binary here,
740 since CC Mode treats every identifier as an expression."
742 ;; There's currently no code in CC Mode that exploit all the info
743 ;; in this variable; precedence, associativity etc are present as a
744 ;; preparation for future work.
755 ;; Primary.
764 ;; Postfix.
766 ;; The following need special treatment.
776 ;; Unary.
783 ;; The following need special treatment.
794 ;; Member selection.
798 ;; Multiplicative.
801 ;; Additive.
804 ;; Shift.
809 ;; Relational.
814 ;; Equality.
818 ;; Bitwise and.
822 ;; Bitwise exclusive or.
828 ;; Bitwise or.
834 ;; Logical and.
838 ;; Logical or.
844 ;; Conditional.
847 ;; Assignment.
850 ;; Exception.
854 ;; Sequence.
857 ;; IDL got its own definition since it has a much smaller operator
858 ;; set than the other languages.
862 ;; Primary.
864 ;; Unary.
866 ;; Multiplicative.
868 ;; Additive.
870 ;; Shift.
872 ;; And.
874 ;; Xor.
876 ;; Or.
880 ;; The operators as a flat list (without duplicates).
886 t nil
895 ;; These work like identifiers in Pike.
902 ;; Regexp tested after an "operator" token in C++.
903 t nil
909 "Regexp matching the token before the ones in
910 `c-overloadable-operators' when operators are specified in their
913 languages without operator functions or where the complete operator
914 identifier is listed in `c-overloadable-operators'.
916 This regexp is assumed to not match any non-operator identifier."
917 t nil
923 "List of the tokens made up of characters in the punctuation or
924 parenthesis syntax classes that have uses other than as expression
925 operators."
943 ;; List of all tokens in the punctuation and parenthesis syntax
944 ;; classes.
950 ;; List containing all chars not in the word, symbol or
951 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
952 ;; parenthesis and string delimiter chars.
954 ;; Only go through the chars in the printable ASCII range. No
955 ;; language so far has 8-bit or widestring operators.
961 list)))
964 ;; Regexp matching all tokens in the punctuation and parenthesis
965 ;; syntax classes. Note that this also matches ".", which can start
966 ;; a float.
969 t
975 ;; Regexp matching all assignment operators and only them. The
976 ;; beginning of the first submatch is used to detect the end of the
977 ;; token, along with the end of the whole match.
980 ;; Need special case for "=" since it's a prefix of "==".
992 ;; Regexp matching all tokens containing "<" or ">" which are longer
993 ;; than one char.
996 t
1002 ;; Regexp matching the second and subsequent characters of all
1003 ;; multicharacter tokens that begin with "<".
1006 t
1012 ;; Regexp matching the second and subsequent characters of all
1013 ;; multicharacter tokens that begin with ">".
1016 t
1022 ;; The characters that should be considered to bound statements. To
1023 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1024 ;; begin with "^" to negate the set. If ? : operators should be
1025 ;; detected then the string must end with "?:".
1026 t "^;{}?:"
1031 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1032 t "^;,{}?:"
1037 \f
1038 ;;; Syntactic whitespace.
1041 "Regexp matching an ordinary whitespace character.
1043 ;; "\\s " is not enough since it doesn't match line breaks.
1047 ;; Number of regexp grouping parens in `c-simple-ws'.
1051 "String that starts line comments, or nil if such don't exist.
1052 Line comments are always terminated by newlines. At least one of
1053 `c-block-comment-starter' and this one is assumed to be set.
1055 Note that it's currently not enough to set this to support a new
1056 comment style. Other stuff like the syntax table must also be set up
1057 properly."
1058 t "//"
1063 "String that starts block comments, or nil if such don't exist.
1064 Block comments are ended by `c-block-comment-ender', which is assumed
1065 to be set if this is. At least one of `c-line-comment-starter' and
1066 this one is assumed to be set.
1068 Note that it's currently not enough to set this to support a new
1069 comment style. Other stuff like the syntax table must also be set up
1070 properly."
1071 t "/*"
1072 awk nil)
1075 "String that ends block comments, or nil if such don't exist.
1077 Note that it's currently not enough to set this to support a new
1078 comment style. Other stuff like the syntax table must also be set up
1079 properly."
1080 t "*/"
1081 awk nil)
1084 ;; Regexp to match the start of any type of comment.
1090 re)))
1093 ;;;; Added by ACM, 2003/9/18.
1095 ;; Regexp which matches the start of a block comment (if such exists in the
1096 ;; language)
1104 ;; Regexp to match the start of comments and string literals.
1113 "Regexp to match the start of documentation comments."
1115 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1123 "String that starts comments inserted with M-; etc.
1124 `comment-start' is initialized from this."
1125 ;; Default: Prefer line comments to block comments, and pad with a space.
1129 ;; In C we still default to the block comment style since line
1130 ;; comments aren't entirely portable.
1135 "String that ends comments inserted with M-; etc.
1136 `comment-end' is initialized from this."
1137 ;; Default: Use block comment style if comment-start uses block
1138 ;; comments, and pad with a space in that case.
1148 "Regexp to match the start of a comment plus everything up to its body.
1149 `comment-start-skip' is initialized from this."
1150 ;; Default: Allow the last char of the comment starter(s) to be
1151 ;; repeated, then allow any amount of horizontal whitespace.
1164 ;; Regexp matching any sequence that can start syntactic whitespace.
1165 ;; The only uncertain case is '#' when there are cpp directives.
1179 ;; Regexp matching any single character that might end syntactic whitespace.
1194 ;; Regexp matching an unterminated block comment that doesn't
1195 ;; contain line breaks, or nil in languages without block comments.
1196 ;; Does not contain a \| operator at the top level.
1200 ;; It's messy to cook together a regexp that matches anything
1201 ;; but c-block-comment-ender.
1209 "[^"
1210 ;; The quoting rules inside char classes are silly. :P
1219 "]"
1227 ;; Regexp matching a block comment that doesn't contain line breaks,
1228 ;; or nil in languages without block comments. The reason we don't
1229 ;; allow line breaks is to avoid going very far and risk running out
1230 ;; of regexp stack; this regexp is intended to handle only short
1231 ;; comments that might be put in the middle of limited constructs
1232 ;; like declarations. Does not contain a \| operator at the top
1233 ;; level.
1248 ;; Regexp matching a piece of syntactic whitespace that isn't a
1249 ;; sequence of simple whitespace characters. As opposed to
1250 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1251 ;; directives as syntactic whitespace.
1263 ;; Regexp matching syntactic whitespace, including possibly the
1264 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1265 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1266 ;; not contain a \| operator at the top level.
1274 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1278 ;; Regexp matching syntactic whitespace, which is at least one
1279 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1280 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1281 ;; not contain a \| operator at the top level.
1289 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1293 ;; Regexp matching syntactic whitespace without any line breaks. As
1294 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1295 ;; regard cpp directives as syntactic whitespace. Does not contain
1296 ;; a \| operator at the top level.
1304 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1308 ;; Regexp that matches when there is no syntactically significant
1309 ;; text before eol. Macros are regarded as syntactically
1310 ;; significant text here.
1312 ;; Match eol (possibly inside a block comment or preceded
1313 ;; by a line continuation backslash), or the beginning of a
1314 ;; line comment. Note: This has to be modified for awk
1315 ;; where line comments start with '#'.
1329 \f
1330 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
1333 Such a function takes one optional parameter, a buffer position (defaults to
1334 point), and returns nil or t. This variable contains nil for languages which
1335 don't have EOL terminated statements. "
1336 t nil
1342 The (admittedly kludgey) purpose of such a function is to prevent an infinite
1343 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
1344 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
1345 even indirectly. This variable contains nil for languages which don't have
1346 EOL terminated statements."
1347 t nil
1352 \f
1353 ;;; In-comment text handling.
1356 "Regexp to append to `paragraph-start'."
1357 t "$"
1363 "Regexp to append to `paragraph-separate'."
1364 t "$"
1368 \f
1369 ;;; Keyword lists.
1371 ;; Note: All and only all language constants containing keyword lists
1372 ;; should end with "-kwds"; they're automatically collected into the
1373 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1376 "Primitive type keywords. As opposed to the other keyword lists, the
1377 keywords listed here are fontified with the type face instead of the
1378 keyword face.
1380 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1381 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1382 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1383 will be handled.
1385 Do not try to modify this list for end user customizations; the
1386 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1387 the appropriate place for that."
1396 ;; Objective-C extends C, but probably not the new stuff in C99.
1403 ;; In CORBA PSDL:
1404 "ref"
1405 ;; The following can't really end a type, but we have to specify them
1406 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1407 ;; doesn't matter that much.
1410 ;; used as a builtin type.
1415 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1420 "Keywords that might act as prefixes for primitive types. Assumed to
1421 be a subset of `c-primitive-type-kwds'."
1422 t nil
1425 ;; In CORBA PSDL:
1429 "Keywords where the following name - if any - is a type name, and
1430 where the keyword together with the symbol works as a type in
1431 declarations.
1433 Note that an alternative if the second part doesn't hold is
1434 `c-type-list-kwds'. Keywords on this list are typically also present
1435 on one of the `*-decl-kwds' lists."
1436 t nil
1442 ;; Adorned regexp matching `c-type-prefix-kwds'.
1447 "Type modifier keywords. These can occur almost anywhere in types
1448 but they don't build a type of themselves. Unlike the keywords on
1449 `c-primitive-type-kwds', they are fontified with the keyword face and
1450 not the type face."
1451 t nil
1457 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1458 ;; languages without such keywords.
1464 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1465 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1475 ;; All keywords that can start a type (i.e. are either a type prefix
1476 ;; or a complete type).
1483 "Keywords introducing declarations where the following block (if any)
1484 contains another declaration level that should be considered a class.
1486 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1487 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1488 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1489 will be handled.
1491 Note that presence on this list does not automatically treat the
1492 following identifier as a type; the keyword must also be present on
1493 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1494 t nil
1502 ;; In CORBA PSDL:
1504 ;; In CORBA CIDL:
1509 ;; Regexp matching the start of a class.
1514 "Keywords introducing declarations where the following block (if
1515 any) is a brace list.
1517 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1518 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1519 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1520 will be handled."
1525 ;; Regexp matching the start of declarations where the following
1526 ;; block is a brace list.
1531 "Keywords where the following block (if any) contains another
1532 declaration level that should not be considered a class. For every
1533 keyword here, CC Mode will add a set of special syntactic symbols for
1535 `foo-open', `foo-close', and `infoo' symbols.
1537 The intention is that this category should be used for block
1538 constructs that aren't related to object orientation concepts like
1539 classes (which thus also include e.g. interfaces, templates,
1540 contracts, structs, etc). The more pragmatic distinction is that
1541 while most want some indentation inside classes, it's fairly common
1542 that they don't want it in some of these constructs, so it should be
1543 simple to configure that differently from classes. See also
1544 `c-class-decl-kwds'.
1546 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1547 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1548 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1549 will be handled."
1550 t nil
1554 ;; In CORBA CIDL:
1558 ;; Regexp matching the start of blocks besides classes that contain
1559 ;; another declaration level.
1564 "Keywords introducing declarations where the identifier(s) being
1565 declared are types.
1567 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1568 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1569 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1570 will be handled."
1571 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1572 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1573 ;; {...}").
1576 ;; Languages that have a "typedef" construct.
1579 ;; Unlike most other languages, exception names are not handled as
1580 ;; types in IDL since they only can occur in "raises" specs.
1584 "Keywords introducing declarations where the \(first) identifier
1585 \(declarator) follows directly after the keyword, without any type.
1587 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1588 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1589 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1590 will be handled."
1591 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1592 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1593 ;; {...}").
1596 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1597 ;; `c-type-list-kwds' for IDL.
1600 ;; In CORBA PSDL:
1602 ;; In CORBA CIDL:
1608 "Keywords that can prefix normal declarations of identifiers
1609 \(and typically act as flags). Things like argument declarations
1610 inside function headers are also considered declarations in this
1611 sense.
1613 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1614 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1615 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1616 will be handled."
1617 t nil
1622 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1626 ;; In CORBA PSDL:
1628 ;; In CORBA CIDL:
1630 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1637 "Keywords that can start or prefix any declaration level construct,
1638 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1639 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1640 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1642 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1643 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1644 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1645 will be handled."
1646 t nil
1652 "Keywords that always start declarations, wherever they occur.
1653 This can be used for declarations that aren't recognized by the normal
1654 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1655 t nil
1656 ;; Classes can be declared anywhere in a Pike expression.
1660 "Keywords that can occur anywhere in a declaration level construct.
1661 This is used for self-contained things that can be tacked on anywhere
1662 on a declaration and that should be ignored to be able to recognize it
1663 correctly. Typical cases are compiler extensions like
1666 __declspec(noreturn) void foo();
1667 class __declspec(dllexport) classname {...};
1668 void foo() __attribute__((noreturn));
1670 Note that unrecognized plain symbols are skipped anyway if they occur
1671 before the type, so such things are not necessary to mention here.
1672 Mentioning them here is necessary only if they can occur in other
1673 places, or if they are followed by a construct that must be skipped
1675 examples above). In the last case, they alse need to be present on
1676 one of `c-type-list-kwds', `c-ref-list-kwds',
1677 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1678 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1679 ;; NB: These are currently not recognized in all parts of a
1680 ;; declaration. Specifically, they aren't recognized in the middle
1681 ;; of multi-token types, inside declarators, and between the
1682 ;; identifier and the arglist paren of a function declaration.
1683 ;;
1684 ;; FIXME: This ought to be user customizable since compiler stuff
1685 ;; like this usually is wrapped in project specific macros. (It'd
1686 ;; of course be even better if we could cope without knowing this.)
1687 t nil
1689 "__attribute__"
1690 ;; MSVC extension.
1694 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1699 ;; All keywords that can occur in the preamble of a declaration.
1700 ;; They typically occur before the type, but they are also matched
1701 ;; after presumptive types since we often can't be sure that
1702 ;; something is a type or just some sort of macro in front of the
1703 ;; declaration. They might be ambiguous with types or type
1704 ;; prefixes.
1717 ;; Adorned regexp of `c-prefix-spec-kwds'.
1722 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that
1723 ;; aren't ambiguous with types or type prefixes.
1731 ;; Keywords that can occur after argument list of a function header
1732 ;; declaration, i.e. in the "K&R region".
1737 ;; Adorned regexp matching all keywords that can't appear at the
1738 ;; start of a declaration.
1748 "Access protection label keywords in classes."
1749 t nil
1754 "Keywords introducing declarations that can contain a block which
1757 like that, it ends with the following ';' and not right away.
1759 The keywords on list are assumed to also be present on one of the
1760 `*-decl-kwds' lists."
1761 t nil
1766 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
1767 ;; languages without such constructs.
1774 "Keywords introducing extra declaration specifiers in the region
1776 declarations."
1777 t nil
1780 "supports"
1781 ;; In CORBA PSDL:
1785 "Keywords that may be followed by a nonsymbol sexp before whatever
1786 construct it's part of continues."
1787 t nil
1791 "Keywords that may be followed by a comma separated list of type
1792 identifiers, where each optionally can be prefixed by keywords. (Can
1793 also be used for the special case when the list can contain only one
1794 element.)
1796 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
1797 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
1798 There's also no reason to add keywords that prefixes a normal
1799 declaration consisting of a type followed by a declarator (list), so
1800 the keywords on `c-modifier-kwds' should normally not be listed here
1801 either.
1803 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1804 or variable identifier (that's being defined)."
1805 t nil
1810 ;; In CORBA PSDL:
1815 "Keywords that may be followed by a comma separated list of
1816 reference (i.e. namespace/scope/module) identifiers, where each
1817 optionally can be prefixed by keywords. (Can also be used for the
1818 special case when the list can contain only one element.) Assumed to
1819 be mutually exclusive with `c-type-list-kwds'.
1821 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1822 or variable identifier (that's being defined)."
1823 t nil
1827 ;; In CORBA CIDL:
1832 "Keywords that may be followed (not necessarily directly) by a colon
1833 and then a comma separated list of type identifiers, where each
1834 optionally can be prefixed by keywords. (Can also be used for the
1835 special case when the list can contain only one element.)"
1836 t nil
1839 ;; In CORBA PSDL:
1843 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
1844 forward to the colon. The end of the match is assumed to be directly
1846 regexp if `c-colon-type-list-kwds' isn't nil."
1848 ;; Disallow various common punctuation chars that can't come
1849 ;; before the ":" that starts the inherit list after "class"
1850 ;; or "struct" in C++. (Also used as default for other
1851 ;; languages.)
1856 "Keywords that may be followed by a parenthesis expression that doesn't
1857 contain type identifiers."
1858 t nil
1860 "__attribute__"
1861 ;; MSVC extension.
1865 "Keywords that may be followed by a parenthesis expression containing
1866 type identifiers separated by arbitrary tokens."
1867 t nil
1879 "Keywords that may be followed by an angle bracket expression
1881 `c-<>-arglist-kwds' is that unknown names are taken to be types and
1882 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
1883 if this isn't nil."
1884 t nil
1887 ;; In CORBA PSDL:
1891 "Keywords that can be followed by a C++ style template arglist; see
1892 `c-recognize-<>-arglists' for details. That language constant is
1893 assumed to be set if this isn't nil."
1894 t nil
1899 ;; All keywords that can be followed by an angle bracket sexp.
1905 ;; Adorned regexp matching keywords that can be followed by an angle
1906 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
1912 "Keywords that may be followed by a brace block containing a comma
1913 separated list of identifier definitions, i.e. like the list of
1914 identifiers that follows the type in a normal declaration."
1918 "Statement keywords followed directly by a substatement."
1922 idl nil)
1925 ;; Regexp matching the start of any statement followed directly by a
1926 ;; substatement (doesn't match a bare block, however).
1931 "Statement keywords followed by a paren sexp and then by a substatement."
1935 idl nil
1940 ;; Regexp matching the start of any statement followed by a paren sexp
1941 ;; and then by a substatement.
1946 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
1952 ;; Regexp matching the start of any statement that has a
1953 ;; substatement (except a bare block). Nil in languages that
1954 ;; don't have such constructs.
1963 "Statement keywords followed by an expression or nothing."
1965 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
1967 idl nil
1974 ;; Adorned regexp matching `c-simple-stmt-kwds'.
1979 "Statement keywords followed by a parenthesis expression that
1980 nevertheless contains a list separated with ';' and not ','."
1982 idl nil)
1985 ;; Adorned regexp matching `c-paren-stmt-kwds'.
1990 "Statement keywords followed by an assembler expression."
1991 t nil
1995 ;; Regexp matching the start of an assembler statement. Nil in
1996 ;; languages that don't support that.
2002 "Keywords introducing colon terminated labels in blocks."
2004 awk nil)
2007 ;; Adorned regexp matching any keyword that introduces a label.
2012 "Keywords that might be followed by a label identifier."
2016 idl nil
2017 awk nil)
2020 "Keywords for constants."
2021 t nil
2029 "Keywords besides constants and operators that start primary expressions."
2030 t nil
2037 ;; Keywords that can occur anywhere in expressions. Built from
2038 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2042 t
2047 "Keywords that start lambda constructs, i.e. function definitions in
2048 expressions."
2049 t nil
2053 "Keywords that start constructs followed by statement blocks which can
2054 be used in expressions \(the gcc extension for this in C and C++ is
2055 handled separately by `c-recognize-paren-inexpr-blocks')."
2056 t nil
2060 "Keywords that can start classes inside expressions."
2061 t nil
2066 "Keywords that can start brace list blocks inside expressions.
2067 Note that Java specific rules are currently applied to tell this from
2068 `c-inexpr-class-kwds'."
2069 t nil
2073 ;; Regexp matching the start of a brace list in an expression, or
2074 ;; nil in languages that don't have such things. This should not
2075 ;; match brace lists recognized through `c-special-brace-lists'.
2082 ;; Regexp matching keywords in any construct that contain another
2083 ;; declaration level, i.e. that isn't followed by a function block
2084 ;; or brace list. When the first submatch matches, it's an
2085 ;; unambiguous construct, otherwise it's an ambiguous match that
2086 ;; might also be the return type of a function declaration.
2104 "Keywords that can introduce bitfields."
2105 t nil
2109 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2110 ;; languages without bitfield support.
2111 t nil
2116 "Keywords not accounted for by any other `*-kwds' language constant."
2117 t nil
2119 ;; In CORBA CIDL: (These are declaration keywords that never
2120 ;; can start a declaration.)
2123 \f
2124 ;;; Constants built from keywords.
2126 ;; Note: No `*-kwds' language constants may be defined below this point.
2130 ;; List of all the language constants that contain keyword lists.
2135 ;; Make the list of globally interned symbols
2136 ;; instead of ones interned in `c-lang-constants'.
2138 c-lang-constants)
2139 list)))
2142 ;; All keywords as a list.
2147 c-kwds-lang-consts)
2148 nil))
2152 ;; All keywords as an adorned regexp.
2157 ;; An alist with all the keywords in the cars. The cdr for each
2158 ;; keyword is a list of the symbols for the `*-kwds' lists that
2159 ;; contains it.
2165 c-kwds-lang-consts))))
2166 lang-const kwd-list kwd
2167 result-alist elem)
2179 result-alist))
2182 ;; An obarray containing all keywords as symbols. The property list
2183 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2184 ;; lists it's a member of.
2185 ;;
2186 ;; E.g. to see whether the string str contains a keyword on
2187 ;; `c-class-decl-kwds', one can do like this:
2188 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2189 ;; Which preferably is written using the associated functions in
2190 ;; cc-engine:
2191 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2193 ;; The obarray is not stored directly as a language constant since
2194 ;; the printed representation for obarrays used in .elc files isn't
2195 ;; complete.
2198 kwd lang-const-list
2205 ;; Emacs has an odd bug that causes `mapcan' to fail
2206 ;; with unintelligible errors. (XEmacs works.)
2207 ;;(mapcan (lambda (lang-const)
2208 ;; (list lang-const t))
2209 ;; lang-const-list)
2212 lang-const-list))))
2213 obarray))
2216 ;; Adorned regexp matching all keywords that should be fontified
2217 ;; with the keywords face. I.e. that aren't types or constants.
2227 ;; Regexp matching the start of any primary expression, i.e. any
2228 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2229 ;; exclude keywords; they are excluded afterwards unless the second
2230 ;; submatch matches. If the first but not the second submatch
2231 ;; matches then it is an ambiguous primary expression; it could also
2232 ;; be a match of e.g. an infix operator. (The case with ambiguous
2233 ;; keyword operators isn't handled.)
2239 ;; Filter out the special case prefix
2240 ;; operators that are close parens.
2245 t
2251 postfix-if-paren
2252 left-assoc
2253 right-assoc
2254 right-assoc-sequence)
2255 t))
2258 in-or-postfix-ops
2261 in-or-postfix-ops
2266 ;; Take out all symbol class operators from `prefix-ops' and make the
2267 ;; first submatch from them together with `c-primary-expr-kwds'.
2274 ;; Match all ambiguous operators.
2281 ;; Now match all other symbols.
2285 ;; The chars that can start integer and floating point
2286 ;; constants.
2290 ;; The nonambiguous operators from `prefix-ops'.
2296 ;; Match string and character literals.
2303 \f
2304 ;;; Additional constants for parser-level constructs.
2307 "Regexp matching something that might precede a declaration, cast or
2308 label, such as the last token of a preceding statement or declaration.
2309 This is used in the common situation where a declaration or cast
2310 doesn't start with any specific token that can be searched for.
2312 The regexp should not match bob; that is done implicitly. It can't
2313 require a match longer than one token. The end of the token is taken
2314 to be at the end of the first submatch, which is assumed to always
2315 match. It's undefined whether identifier syntax (see
2316 `c-identifier-syntax-table') is in effect or not. This regexp is
2317 assumed to be a superset of `c-label-prefix-re' if
2318 `c-recognize-colon-labels' is set.
2320 Besides this, `c-decl-start-kwds' is used to find declarations.
2322 Note: This variable together with `c-decl-start-re' and
2324 declaration/cast/label starts. I.e. they might produce more matches
2325 but should not miss anything (or else it's necessary to use text
2326 properties - see the next note). Wherever they match, the following
2327 construct is analyzed to see if it indeed is a declaration, cast or
2328 label. That analysis is not cheap, so it's important that not too
2329 many false matches are triggered.
2331 Note: If a declaration/cast/label start can't be detected with this
2332 variable, it's necessary to use the `c-type' text property with the
2333 value `c-decl-end' on the last char of the last token preceding the
2334 declaration. See the comment blurb at the start of cc-engine.el for
2335 more info."
2337 ;; We match a sequence of characters to skip over things like \"};\"
2338 ;; more quickly. We match ")" in C for K&R region declarations, and
2339 ;; in all languages except Java for when a cpp macro definition
2340 ;; begins with a declaration.
2343 ;; Match "<" in C++ to get the first argument in a template arglist.
2344 ;; In that case there's an additional check in `c-find-decl-spots'
2345 ;; that it got open paren syntax.
2347 ;; Additionally match the protection directives in Objective-C.
2348 ;; Note that this doesn't cope with the longer directives, which we
2349 ;; would have to match from start to end since they don't end with
2350 ;; any easily recognized characters.
2354 ;; Pike is like C but we also match "[" for multiple value
2355 ;; assignments and type casts.
2361 "Regexp matching the start of any declaration, cast or label.
2362 It's used on the token after the one `c-decl-prefix-re' matched. This
2363 regexp should not try to match those constructs accurately as it's
2364 only used as a sieve to avoid spending more time checking other
2365 constructs."
2370 ;; Regexp matching something that might precede or start a
2371 ;; declaration, cast or label.
2372 ;;
2373 ;; If the first submatch matches, it's taken to match the end of a
2374 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2375 ;; It's built from `c-decl-prefix-re'.
2376 ;;
2377 ;; If the first submatch did not match, the match of the whole
2378 ;; regexp is taken to be at the first token in the declaration.
2379 ;; `c-decl-start-re' is not checked in this case.
2380 ;;
2381 ;; Design note: The reason the same regexp is used to match both
2382 ;; tokens that precede declarations and start them is to avoid an
2383 ;; extra regexp search from the previous declaration spot in
2384 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2385 ;; that it finds all declaration/cast/label starts in approximately
2386 ;; linear order, so we can't do the searches in two separate passes.
2397 ;; List containing the paren characters that can open a cast, or nil in
2398 ;; languages without casts.
2406 "List of syntactically relevant characters that never can occur before
2407 the open brace in any construct that contains a brace block, e.g. in
2410 class Foo: public Bar {int x();} a, *b;
2412 If parens can occur, the chars inside those aren't filtered with this
2413 list.
2415 '<' and '>' should be disallowed even if angle bracket arglists can
2416 occur. That since the search function needs to stop at them anyway to
2417 ensure they are given paren syntax.
2419 This is used to skip backward from the open brace to find the region
2422 possible for good performance."
2424 ;; Default to all chars that only occurs in nonsymbol tokens outside
2425 ;; identifiers.
2431 t
2432 t
2436 op pos)
2439 res))))
2441 ;; Allow cpp operatios (where applicable).
2447 ;; Allow ':' for inherit list starters.
2451 ;; Allow ',' for multiple inherits.
2455 ;; Allow parentheses for anonymous inner classes in Java and class
2456 ;; initializer lists in Pike.
2460 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2465 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2466 ;; for `c-syntactic-skip-backward'.
2471 "Regexp matching the declarator operators that might precede the
2474 The end of the first submatch is taken as the end of the operator.
2475 Identifier syntax is in effect when this is matched \(see
2476 `c-identifier-syntax-table')."
2479 ;; Default to a regexp that never matches.
2481 ;; Check that there's no "=" afterwards to avoid matching tokens
2482 ;; like "*=".
2484 "[*\(]"
2490 "[*\(&]"
2493 ;; If this matches there's special treatment in
2494 ;; `c-font-lock-declarators' and
2495 ;; `c-font-lock-declarations' that check for a
2496 ;; complete name followed by ":: *".
2508 "Regexp matching the declarator operators that might follow after the
2511 it matches an open paren of some kind, the type declaration check
2512 continues at the corresponding close paren, otherwise the end of the
2513 first submatch is taken as the end of the operator. Identifier syntax
2514 is in effect when this is matched (see `c-identifier-syntax-table')."
2515 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2516 ;; function argument list parenthesis.
2524 "[\)\[\(]"
2528 ;; "throw" in `c-type-modifier-kwds' is followed
2529 ;; by a parenthesis list, but no extra measures
2530 ;; are necessary to handle that.
2540 "This regexp is matched after a declarator expression where
2541 `c-type-decl-suffix-key' has matched. If it matches then the
2542 construct is taken as a declaration. It's typically used to match the
2543 beginning of a function body or whatever might occur after the
2544 function header in a function declaration or definition. It's
2545 undefined whether identifier syntax (see `c-identifier-syntax-table')
2546 is in effect or not.
2551 t "{"
2552 ;; If K&R style declarations should be recognized then one could
2553 ;; consider to match the start of any symbol since we want to match
2554 ;; the start of the first declaration in the "K&R region". That
2555 ;; could however produce false matches on code like "FOO(bar) x"
2556 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2557 ;; on the other heuristics in that case.
2559 ;; Add on the keywords in `c-postfix-spec-kwds'.
2564 ;; Also match the colon that starts a base class initializer list in
2565 ;; C++. That can be confused with a function call before the colon
2566 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2567 ;; match before such a thing (as a declaration-level construct;
2568 ;; matches inside arglist contexts are already excluded).
2575 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2576 ;; matches ";" and ",".
2585 end of the operator. nil in languages without such operators. It's
2586 undefined whether identifier syntax (see `c-identifier-syntax-table')
2587 is in effect or not."
2588 t nil
2594 "Regexp matching operators that might follow after a type, or nil in
2595 languages that don't have such operators. The end of the first
2596 submatch is taken as the end of the operator. This should not match
2597 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2598 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2599 is in effect or not."
2600 t nil
2606 ;; Regexp matching the known type identifiers. This is initialized
2607 ;; from the type keywords and `*-font-lock-extra-types'. The first
2608 ;; submatch is the one that matches the type. Note that this regexp
2609 ;; assumes that symbol constituents like '_' and '$' have word
2610 ;; syntax.
2619 extra-types)))
2625 extra-types))))
2630 plain-strings)))
2631 regexp-strings)
2636 "List of open- and close-chars that makes up a pike-style brace list,
2638 list."
2639 t nil
2644 "Non-nil means K&R style argument declarations are valid."
2645 t nil
2646 c t)
2650 "Non-nil means function declarations without return type should be
2651 recognized. That can introduce an ambiguity with parenthesized macro
2652 calls before a brace block. This setting does not affect declarations
2653 that are preceded by a declaration starting keyword, so
2654 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2655 t nil
2661 "Non-nil means C++ style template arglists should be handled. More
2662 specifically, this means a comma separated list of types or
2664 identifier or one of the keywords on `c-<>-type-kwds' or
2665 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2666 expression is considered to be a type."
2672 "Non-nil means that parenthesis style initializers exist,
2673 i.e. constructs like
2675 Foo bar (gnu);
2677 in addition to the more classic
2679 Foo bar = gnu;"
2680 t nil
2685 "Non-nil to recognize gcc style in-expression blocks,
2686 i.e. compound statements surrounded by parentheses inside expressions."
2687 t nil
2693 ;; Regexp matching the start of angle bracket arglists in languages
2694 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2695 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2696 ;; assumed to surround the preceding symbol. The whole match is
2697 ;; assumed to end directly after the opening "<".
2707 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2708 ;; parens. The first submatch is assumed to surround
2709 ;; `c-opt-<>-arglist-start'.
2718 ;; Regexp matching the beginning of a declaration specifier in the
2719 ;; region between the header and the body of a declaration.
2720 ;;
2721 ;; TODO: This is currently not used uniformly; c++-mode and
2722 ;; java-mode each have their own ways of using it.
2723 t nil
2736 That includes labels in code and access keys in classes. This does
2737 not apply to labels recognized by `c-label-kwds' and
2738 `c-opt-extra-label-key'."
2739 t nil
2745 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2746 a generic colon label. Not used if `c-recognize-colon-labels' is
2747 nil."
2753 "Regexp matching things that can't occur in generic colon labels,
2754 neither in a statement nor in a declaration context. The regexp is
2755 tested at the beginning of every sexp in a suspected label,
2758 ;; Don't allow string literals.
2760 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
2766 ;; Also check for open parens in C++, to catch member init lists in
2767 ;; constructors. We normally allow it so that macros with arguments
2768 ;; work in labels.
2773 "Optional regexp matching labels.
2774 Normally, labels are detected according to `c-nonlabel-token-key',
2775 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
2776 be used if there are additional labels that aren't recognized that
2777 way."
2778 t nil
2783 ;; Regexp describing friend declarations classes, or nil in
2784 ;; languages that don't have such things.
2785 ;;
2786 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
2787 ;; template skipping isn't done properly. This will disappear soon.
2788 t nil
2793 "<.+>"
2795 "friend"
2800 ;; Special regexp to match the start of Objective-C methods. The
2801 ;; first submatch is assumed to end after the + or - key.
2802 t nil
2804 ;; TODO: Ought to use a better method than anchoring on bol.
2809 "([^\)]*)"
2816 ;; Must be set in buffers where the `c-type' text property might be
2817 ;; used with the value `c-decl-end'.
2818 ;;
2819 ;; `c-decl-end' is used to mark the ends of labels and access keys
2820 ;; to make interactive refontification work better.
2823 ;; `c-decl-end' is used to mark the end of the @-style directives in
2824 ;; Objective-C.
2825 objc t)
2828 \f
2829 ;;; Wrap up the `c-lang-defvar' system.
2831 ;; Compile in the list of language variables that has been collected
2832 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
2833 ;; first element of each is nil.
2838 "Create a function that initializes all the language dependent variables
2839 for the given mode.
2841 This function should be evaluated at compile time, so that the
2842 function it returns is byte compiled with all the evaluated results
2843 from the language constants. Use the `c-init-language-vars' macro to
2844 accomplish that conveniently."
2850 ;; No need to byte compile this lambda since the byte compiler is
2851 ;; smart enough to detect the `funcall' construct in the
2852 ;; `c-init-language-vars' macro below and compile it all straight
2853 ;; into the function that contains `c-init-language-vars'.
2856 ;; This let sets up the context for `c-mode-var' and similar
2857 ;; that could be in the result from `cl-macroexpand-all'.
2859 current-var source-eval)
2865 ;; `c-lang-const' will expand to the evaluated
2866 ;; constant immediately in `cl-macroexpand-all'
2867 ;; below.
2873 ;; Note: The following `append' copies the
2874 ;; first argument. That list is small, so
2875 ;; this doesn't matter too much.
2879 ;; This diagnostic message isn't useful for end
2880 ;; users, so it's disabled.
2881 ;;(unless (get ',mode 'c-has-warned-lang-consts)
2882 ;; (message ,(concat "%s compiled with CC Mode %s "
2883 ;; "but loaded with %s - evaluating "
2884 ;; "language constants from source")
2885 ;; ',mode ,c-version c-version)
2886 ;; (put ',mode 'c-has-warned-lang-consts t))
2900 current-var
2903 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
2906 err)
2909 ;; Being evaluated from source. Always use the dynamic method to
2910 ;; work well when `c-lang-defvar's in this file are reevaluated
2911 ;; interactively.
2917 current-var)
2928 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
2929 current-var err)
2931 ))
2934 "Initialize all the language dependent variables for the given mode.
2935 This macro is expanded at compile time to a form tailored for the mode
2936 in question, so MODE must be a constant. Therefore MODE is not
2937 evaluated and should not be quoted."
2940 \f
2943 ;;; arch-tag: 1ab57482-cfc2-4c5b-b628-3539c3098822
2944 ;;; cc-langs.el ends here