| blob | ad6b6787652426e42d6bb8628ef69cc0a50396da |
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, 2007, 2008, 2009, 2010
5 ;; Free Software Foundation, Inc.
7 ;; Authors: 2002- Alan Mackenzie
8 ;; 1998- Martin Stjernholm
9 ;; 1992-1999 Barry A. Warsaw
10 ;; 1987 Dave Detlefs
11 ;; 1987 Stewart Clamen
12 ;; 1985 Richard M. Stallman
13 ;; Maintainer: bug-cc-mode@gnu.org
14 ;; Created: 22-Apr-1997 (split from cc-mode.el)
15 ;; Keywords: c languages
16 ;; Package: cc-mode
18 ;; This file is part of GNU Emacs.
20 ;; GNU Emacs is free software: you can redistribute it and/or modify
21 ;; it under the terms of the GNU General Public License as published by
22 ;; the Free Software Foundation, either version 3 of the License, or
23 ;; (at your option) any later version.
25 ;; GNU Emacs is distributed in the hope that it will be useful,
26 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
27 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
28 ;; GNU General Public License for more details.
30 ;; You should have received a copy of the GNU General Public License
31 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
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:
118 ;; For Emacs < 22.2.
127 load-path)))
134 ;; This file is not always loaded. See note above.
137 \f
138 ;;; Setup for the `c-lang-defvar' system.
141 ;; These are used to collect the init forms from the subsequent
142 ;; `c-lang-defvar' and `c-lang-setvar'. They are used to build the
143 ;; lambda in `c-make-init-lang-vars-fun' below, and to build `defvar's
144 ;; and `make-variable-buffer-local's in cc-engine and
145 ;; `make-local-variable's in `c-init-language-vars-for'.
149 c-lang-variable-inits-tail c-lang-variable-inits)
153 c-emacs-variable-inits-tail c-emacs-variable-inits))
156 "Declares the buffer local variable VAR to get the value VAL. VAL is
157 evaluated and assigned at mode initialization. More precisely, VAL is
158 evaluated and bound to VAR when the result from the macro
159 `c-init-language-vars' is evaluated.
161 `c-lang-const' is typically used in VAL to get the right value for the
162 language being initialized, and such calls will be macro expanded to
163 the evaluated constant value at compile time."
169 ;; Special case: If there's no docstring and the value is a
170 ;; simple (c-lang-const foo) where foo is the same name as VAR
171 ;; then take the docstring from the language constant foo.
183 ;; Return the symbol, like the other def* forms.
187 "Causes the variable VAR to be made buffer local and to get set to the
188 value VAL. VAL is evaluated and assigned at mode initialization. More
189 precisely, VAL is evaluated and bound to VAR when the result from the
190 macro `c-init-language-vars' is evaluated. VAR is typically a standard
191 Emacs variable like `comment-start'.
193 `c-lang-const' is typically used in VAL to get the right value for the
194 language being initialized, and such calls will be macro expanded to
195 the evaluated constant value at compile time."
202 ;; Return the symbol, like the other def* forms.
206 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
207 ; '
211 ;; Suppress "might not be defined at runtime" warning.
212 ;; This file is only used when compiling other cc files.
218 ;; Some helper functions used when building the language constants.
221 ;; Extract a subset of the operators in the list OPS in a DWIM:ey
222 ;; way. The return value is a plain list of operators:
223 ;;
224 ;; OPS either has the structure of `c-operators', is a single
225 ;; group in `c-operators', or is a plain list of operators.
226 ;;
227 ;; OPGROUP-FILTER specifies how to select the operator groups. It
228 ;; can be t to choose all groups, a list of group type symbols
229 ;; (such as 'prefix) to accept, or a function which will be called
230 ;; with the group symbol for each group and should return non-nil
231 ;; if that group is to be included.
232 ;;
233 ;; If XLATE is given, it's a function which is called for each
234 ;; matching operator and its return value is collected instead.
235 ;; If it returns a list, the elements are spliced directly into
236 ;; the final result, which is returned as a list with duplicates
237 ;; removed using `equal'.
238 ;;
239 ;; `c-mode-syntax-table' for the current mode is in effect during
240 ;; the whole procedure.
261 t)
262 t)
267 opgroup)))
268 ops)
271 \f
272 ;;; Various mode specific values that aren't language related.
275 ;; The definition for the mode menu. The menu title is prepended to
276 ;; this before it's fed to `easy-menu-define'.
286 "----"
290 ;; Only applicable if there's a cpp preprocessor.
294 "----"
299 "----"
311 subword-mode)])))
313 \f
314 ;;; Syntax tables.
317 "Populate the given syntax table as necessary for a C-like language.
335 ;; Set up block and line oriented comments. The new C
336 ;; standard mandates both comment styles even in C, so since
337 ;; all languages now require dual comments, we make this the
338 ;; default.
340 ;; XEmacs
344 ;; Emacs
348 ;; incompatible
352 ;; Give CR the same syntax as newline, for selective-display
356 "Functions that generates the mode specific syntax tables.
357 The syntax tables aren't stored directly since they're quite large."
361 ;; Mode specific syntaxes.
363 ;; Let '@' be part of symbols in ObjC to cope with
364 ;; its compiler directives as single keyword tokens.
365 ;; This is then necessary since it's assumed that
366 ;; every keyword is a single symbol.
370 table)))
373 ;; The syntax tables in evaluated form. Only used temporarily when
374 ;; the constants in this file are evaluated.
378 ;; A variant of `c++-mode-syntax-table' that defines `<' and `>' as
379 ;; parenthesis characters. Used temporarily when template argument
380 ;; lists are parsed. Note that this encourages incorrect parsing of
381 ;; templates since they might contain normal operators that uses the
382 ;; '<' and '>' characters. Therefore this syntax table might go
383 ;; away when CC Mode handles templates correctly everywhere.
384 t nil
389 table)))
395 ;; A variant of the standard syntax table which is used to find matching
396 ;; "<"s and ">"s which have been marked as parens using syntax table
397 ;; properties. The other paren characters (e.g. "{", ")" "]") are given a
398 ;; non-paren syntax here. so that the list commands will work on "< ... >"
399 ;; even when there's unbalanced other parens inside them.
400 ;;
401 ;; This variable is nil for languages which don't have template stuff.
411 table))))
416 "A list that describes the modifications that should be done to the
417 mode syntax table to get a syntax table that matches all identifiers
418 and keywords as words.
420 The list is just like the one used in `font-lock-defaults': Each
421 element is a cons where the car is the character to modify and the cdr
422 the new syntax, as accepted by `modify-syntax-entry'."
423 ;; The $ character is not allowed in most languages (one exception
424 ;; is Java which allows it for legacy reasons) but we still classify
425 ;; it as an indentifier character since it's often used in various
426 ;; machine generated identifiers.
437 mod)
442 table)
443 "Syntax table built on the mode syntax table but additionally
444 classifies symbol constituents like '_' and '$' as word constituents,
448 ;; For documentation see the following c-lang-defvar of the same name.
449 ;; The value here may be a list of functions or a single function.
450 t nil
453 ;; java 'c-before-change-check-<>-operators
458 fs
460 "If non-nil, a list of functions called from c-before-change-hook.
461 Typically these will record enough state to allow
462 `c-before-font-lock-function' to extend the region to fontify,
463 and may do such things as removing text-properties which must be
464 recalculated.
466 These functions will be run in the order given. Each of them
467 takes 2 parameters, the BEG and END supplied to every
468 before-change function; on entry, the buffer will have been
469 widened and match-data will have been saved; point is undefined
470 on both entry and exit; the return value is ignored.
472 The functions are called even when font locking isn't enabled.
474 When the mode is initialized, the functions are called with
478 "If non-nil, a function called just before font locking.
479 Typically it will extend the region about to be fontified \(see
480 below) and will set `syntax-table' text properties on the region.
482 It takes 3 parameters, the BEG, END, and OLD-LEN supplied to
483 every after-change function; point is undefined on both entry and
484 exit; on entry, the buffer will have been widened and match-data
485 will have been saved; the return value is ignored.
487 The function may extend the region to be fontified by setting the
488 buffer local variables c-new-BEG and c-new-END.
490 The function is called even when font locking is disabled.
492 When the mode is initialized, this function is called with
493 parameters \(point-min), \(point-max) and <buffer size>."
494 t nil
500 \f
501 ;;; Lexer-level syntax (identifiers, tokens etc).
504 "Regexp that matches the start of a symbol, i.e. any identifier or
506 operator at the top level."
514 "Set of characters that can be part of a symbol.
515 This is on the form that fits inside [ ] in a regexp."
516 ;; Pike note: With the backquote identifiers this would include most
517 ;; operator chars too, but they are handled with other means instead.
522 "Regexp matching identifiers and keywords (with submatch 0). Assumed
523 to match if `c-symbol-start' matches on the same position."
527 ;; Use the value from C here since the operator backquote is
528 ;; covered by the other alternative.
536 ;; Number of regexp grouping parens in `c-symbol-key'.
540 "This is the set of chars that can't be part of a symbol, i.e. the
541 negation of `c-symbol-chars'."
546 "Regexp that matches any character that can't be part of a symbol.
547 It's usually appended to other regexps to avoid matching a prefix.
548 It's assumed to not contain any submatchers."
549 ;; The same thing regarding Unicode identifiers applies here as to
550 ;; `c-symbol-key'.
554 "The operators that make up fully qualified identifiers. nil in
555 languages that don't have such things. See `c-operators' for a
556 description of the format. Binary operators can concatenate symbols,
560 This value is by default merged into `c-operators'."
561 t nil
565 ;; Java has "." to concatenate identifiers but it's also used for
566 ;; normal indexing. There's special code in the Java font lock
567 ;; rules to fontify qualified identifiers based on the standard
568 ;; naming conventions. We still define "." here to make
569 ;; `c-forward-name' move over as long names as possible which is
570 ;; necessary to e.g. handle throws clauses correctly.
579 ;; Appendable adorned regexp matching the operators that join
580 ;; symbols to fully qualified identifiers, or nil in languages that
581 ;; don't have such things.
582 ;;
583 ;; This was a docstring constant in 5.30. It still works but is now
584 ;; considered internal - change `c-identifier-ops' instead.
587 t)))
595 ;; Number of regexp grouping parens in `c-opt-identifier-concat-key'.
599 ;; Appendable adorned regexp matching operators that might precede
600 ;; an identifier and that are part of the identifier in that case.
601 ;; nil in languages without such things.
604 t)))
609 "Operators that can occur after a binary operator on `c-identifier-ops'
610 in identifiers. nil in languages that don't have such things.
612 Operators here should also have appropriate entries in `c-operators' -
613 it's not taken care of by default."
614 t nil
615 ;; '~' for destructors in C++, '*' for member pointers.
617 ;; In Java we recognize '*' to deal with "foo.bar.*" that can occur
618 ;; in import declarations. (This will also match bogus things like
619 ;; "foo.*bar" but we don't bother.)
623 ;; Regexp that must match the token after
624 ;; `c-opt-identifier-concat-key' for it to be considered an
625 ;; identifier concatenation operator (which e.g. causes the
626 ;; preceding identifier to be fontified as a reference). Assumed to
627 ;; be a string if `c-opt-identifier-concat-key' is.
628 ;;
629 ;; This was a docstring constant in 5.30. It still works but is now
630 ;; considered internal - change `c-after-id-concat-ops' instead.
638 "Regexp that matches the start of an (optionally qualified) identifier.
639 It should also match all keywords. It's unspecified how far it
640 matches."
650 C++. It does not recognize the full range of syntactic whitespace
651 between the tokens; `c-forward-name' has to be used for that. It
652 should also not match identifiers containing parenthesis groupings,
654 ;; This regexp is more complex than strictly necessary to ensure
655 ;; that it can be matched with a minimum of backtracking.
676 ;; For flexibility, consider the symbol match
677 ;; optional if we've hit a
678 ;; `c-after-id-concat-ops' operator. This is
679 ;; also necessary to handle the "*" that can
680 ;; end import declaration identifiers in Java.
694 ;; This was a docstring constant in 5.30 but it's no longer used.
695 ;; It's only kept to avoid breaking third party code.
696 ;;
697 ;; Used to identify the submatch in `c-identifier-key' that
698 ;; surrounds the last symbol in the qualified identifier. It's a
699 ;; list of submatch numbers, of which the first that has a match is
700 ;; taken. It's assumed that at least one does when the regexp has
701 ;; matched.
702 t nil)
705 "Set if the language support backslash escaped newlines inside string
706 literals."
707 t nil
713 "Set if the language supports multiline string literals without escaped
714 newlines. If t, all string literals are multiline. If a character,
715 only literals where the open quote is immediately preceded by that
716 literal are multiline."
717 t nil
718 pike ?#)
723 "Regexp matching the prefix of a cpp directive in the languages that
724 normally use that macro preprocessor. Tested at bol or at boi.
726 ;; TODO (ACM, 2005-04-01). Amend the following to recognise escaped NLs;
727 ;; amend all uses of c-opt-cpp-prefix which count regexp-depth.
733 "Regexp matching the prefix of a cpp directive anchored to BOL,
734 in the languages that have a macro preprocessor."
740 "Regexp matching the prefix of a cpp directive including the directive
741 name, or nil in languages without preprocessor support. The first
742 submatch surrounds the directive name."
746 ;; Pike, being a scripting language, recognizes hash-bangs too.
752 "List of cpp directives (without the prefix) that are followed by a
753 string message."
759 "List of cpp directives (without the prefix) that are followed by a
760 file name in angle brackets or quotes."
766 "Cpp directive (without the prefix) that is followed by a macro
767 definition, or nil if the language doesn't have any."
772 ;; Regexp matching everything up to the macro body of a cpp define, or the
773 ;; end of the logical line if there is none. Submatch 1 is the name of the
774 ;; macro. Set if c-opt-cpp-macro-define is.
779 ;; ^ ^ #defined name
785 ;; Regexp matching everything up to the end of the identifier defined
786 ;; by a cpp define.
795 "List of cpp directives (without the prefix) that are followed by an
796 expression."
801 "List of functions in cpp expressions."
807 "List of all assignment operators."
813 idl nil)
816 "List describing all operators, along with their precedence and
817 associativity. The order in the list corresponds to the precedence of
818 the operators: The operators in each element are a group with the same
819 precedence, and the group has higher precedence than the groups in all
820 following elements. The car of each element describes the type of the
821 operator group, and the cdr is a list of the operator tokens in it.
822 The operator group types are:
824 'prefix Unary prefix operators.
825 'postfix Unary postfix operators.
826 'postfix-if-paren
827 Unary postfix operators if and only if the chars have
828 parenthesis syntax.
829 'left-assoc Binary left associative operators (i.e. a+b+c means (a+b)+c).
830 'right-assoc Binary right associative operators (i.e. a=b=c means a=(b=c)).
831 'right-assoc-sequence
832 Right associative operator that constitutes of a
833 sequence of tokens that separate expressions. All the
834 tokens in the group are in this case taken as
835 describing the sequence in one such operator, and the
836 order between them is therefore significant.
838 Operators containing a character with paren syntax are taken to match
839 with a corresponding open/close paren somewhere else. A postfix
840 operator with close paren syntax is taken to end a postfix expression
841 started somewhere earlier, rather than start a new one at point. Vice
842 versa for prefix operators with open paren syntax.
845 often are described as postfix operators are considered binary here,
846 since CC Mode treats every identifier as an expression."
848 ;; There's currently no code in CC Mode that exploit all the info
849 ;; in this variable; precedence, associativity etc are present as a
850 ;; preparation for future work.
861 ;; Primary.
870 ;; Postfix.
872 ;; The following need special treatment.
882 ;; Unary.
889 ;; The following need special treatment.
900 ;; Member selection.
904 ;; Multiplicative.
907 ;; Additive.
910 ;; Shift.
915 ;; Relational.
920 ;; Equality.
924 ;; Bitwise and.
928 ;; Bitwise exclusive or.
934 ;; Bitwise or.
940 ;; Logical and.
944 ;; Logical or.
950 ;; Conditional.
953 ;; Assignment.
956 ;; Exception.
960 ;; Sequence.
963 ;; IDL got its own definition since it has a much smaller operator
964 ;; set than the other languages.
968 ;; Primary.
970 ;; Unary.
972 ;; Multiplicative.
974 ;; Additive.
976 ;; Shift.
978 ;; And.
980 ;; Xor.
982 ;; Or.
986 ;; The operators as a flat list (without duplicates).
992 t nil
1001 ;; These work like identifiers in Pike.
1008 ;; Regexp tested after an "operator" token in C++.
1009 t nil
1015 "Regexp matching the token before the ones in
1016 `c-overloadable-operators' when operators are specified in their
1019 languages without operator functions or where the complete operator
1020 identifier is listed in `c-overloadable-operators'.
1022 This regexp is assumed to not match any non-operator identifier."
1023 t nil
1028 ;; Note: the following alias is an old name which was a mis-spelling. It has
1029 ;; been corrected above and throughout cc-engine.el. It will be removed at
1030 ;; some release very shortly in the future. ACM, 2006-04-14.
1036 "List of the tokens made up of characters in the punctuation or
1037 parenthesis syntax classes that have uses other than as expression
1038 operators."
1056 ;; List of all tokens in the punctuation and parenthesis syntax
1057 ;; classes.
1063 ;; List containing all chars not in the word, symbol or
1064 ;; syntactically irrelevant syntax classes, i.e. all punctuation,
1065 ;; parenthesis and string delimiter chars.
1067 ;; Only go through the chars in the printable ASCII range. No
1068 ;; language so far has 8-bit or widestring operators.
1074 list)))
1077 ;; Regexp matching all tokens in the punctuation and parenthesis
1078 ;; syntax classes. Note that this also matches ".", which can start
1079 ;; a float.
1082 t
1088 ;; Regexp matching all assignment operators and only them. The
1089 ;; beginning of the first submatch is used to detect the end of the
1090 ;; token, along with the end of the whole match.
1093 ;; Need special case for "=" since it's a prefix of "==".
1105 ;; Regexp matching all tokens containing "<" or ">" which are longer
1106 ;; than one char.
1109 t
1115 ;; Regexp matching the second and subsequent characters of all
1116 ;; multicharacter tokens that begin with "<".
1119 t
1126 ;; Regexp matching the second and subsequent characters of all
1127 ;; multicharacter tokens that begin with ">".
1130 t
1135 t
1142 ;; The characters that should be considered to bound statements. To
1143 ;; optimize `c-crosses-statement-barrier-p' somewhat, it's assumed to
1144 ;; begin with "^" to negate the set. If ? : operators should be
1145 ;; detected then the string must end with "?:".
1146 t "^;{}?:"
1151 ;; Variant of `c-stmt-delim-chars' that additionally contains ','.
1152 t "^;,{}?:"
1157 \f
1158 ;;; Syntactic whitespace.
1161 "Regexp matching an ordinary whitespace character.
1163 ;; "\\s " is not enough since it doesn't match line breaks.
1167 ;; Number of regexp grouping parens in `c-simple-ws'.
1171 "String that starts line comments, or nil if such don't exist.
1172 Line comments are always terminated by newlines. At least one of
1173 `c-block-comment-starter' and this one is assumed to be set.
1175 Note that it's currently not enough to set this to support a new
1176 comment style. Other stuff like the syntax table must also be set up
1177 properly."
1178 t "//"
1183 "String that starts block comments, or nil if such don't exist.
1184 Block comments are ended by `c-block-comment-ender', which is assumed
1185 to be set if this is. At least one of `c-line-comment-starter' and
1186 this one is assumed to be set.
1188 Note that it's currently not enough to set this to support a new
1189 comment style. Other stuff like the syntax table must also be set up
1190 properly."
1191 t "/*"
1192 awk nil)
1195 "String that ends block comments, or nil if such don't exist.
1197 Note that it's currently not enough to set this to support a new
1198 comment style. Other stuff like the syntax table must also be set up
1199 properly."
1200 t "*/"
1201 awk nil)
1204 ;; Regexp to match the start of any type of comment.
1210 re)))
1213 ;;;; Added by ACM, 2003/9/18.
1215 ;; Regexp which matches the start of a block comment (if such exists in the
1216 ;; language)
1224 ;; Regexp to match the start of comments and string literals.
1233 "Regexp to match the start of documentation comments."
1235 ;; From font-lock.el: `doxygen' uses /*! while others use /**.
1243 "String that starts comments inserted with M-; etc.
1244 `comment-start' is initialized from this."
1245 ;; Default: Prefer line comments to block comments, and pad with a space.
1249 ;; In C we still default to the block comment style since line
1250 ;; comments aren't entirely portable.
1255 "String that ends comments inserted with M-; etc.
1256 `comment-end' is initialized from this."
1257 ;; Default: Use block comment style if comment-start uses block
1258 ;; comments, and pad with a space in that case.
1268 "Regexp to match the start of a comment plus everything up to its body.
1269 `comment-start-skip' is initialized from this."
1270 ;; Default: Allow the last char of the comment starter(s) to be
1271 ;; repeated, then allow any amount of horizontal whitespace.
1284 ;; Regexp matching any sequence that can start syntactic whitespace.
1285 ;; The only uncertain case is '#' when there are cpp directives.
1299 ;; Regexp matching any single character that might end syntactic whitespace.
1314 ;; Regexp matching an unterminated block comment that doesn't
1315 ;; contain line breaks, or nil in languages without block comments.
1316 ;; Does not contain a \| operator at the top level.
1320 ;; It's messy to cook together a regexp that matches anything
1321 ;; but c-block-comment-ender.
1329 "[^"
1330 ;; The quoting rules inside char classes are silly. :P
1339 "]"
1347 ;; Regexp matching a block comment that doesn't contain line breaks,
1348 ;; or nil in languages without block comments. The reason we don't
1349 ;; allow line breaks is to avoid going very far and risk running out
1350 ;; of regexp stack; this regexp is intended to handle only short
1351 ;; comments that might be put in the middle of limited constructs
1352 ;; like declarations. Does not contain a \| operator at the top
1353 ;; level.
1368 ;; Regexp matching a piece of syntactic whitespace that isn't a
1369 ;; sequence of simple whitespace characters. As opposed to
1370 ;; `c-(forward|backward)-syntactic-ws', this doesn't regard cpp
1371 ;; directives as syntactic whitespace.
1383 ;; Regexp matching syntactic whitespace, including possibly the
1384 ;; empty string. As opposed to `c-(forward|backward)-syntactic-ws',
1385 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1386 ;; not contain a \| operator at the top level.
1394 ;; Number of regexp grouping parens in `c-syntactic-ws'.
1398 ;; Regexp matching syntactic whitespace, which is at least one
1399 ;; character long. As opposed to `c-(forward|backward)-syntactic-ws',
1400 ;; this doesn't regard cpp directives as syntactic whitespace. Does
1401 ;; not contain a \| operator at the top level.
1409 ;; Number of regexp grouping parens in `c-nonempty-syntactic-ws'.
1413 ;; Regexp matching syntactic whitespace without any line breaks. As
1414 ;; opposed to `c-(forward|backward)-syntactic-ws', this doesn't
1415 ;; regard cpp directives as syntactic whitespace. Does not contain
1416 ;; a \| operator at the top level.
1424 ;; Number of regexp grouping parens in `c-single-line-syntactic-ws'.
1428 ;; Regexp that matches when there is no syntactically significant
1429 ;; text before eol. Macros are regarded as syntactically
1430 ;; significant text here.
1432 ;; Match eol (possibly inside a block comment or preceded
1433 ;; by a line continuation backslash), or the beginning of a
1434 ;; line comment. Note: This has to be modified for awk
1435 ;; where line comments start with '#'.
1449 \f
1450 ;;; Syntactic analysis ("virtual semicolons") for line-oriented languages (AWK).
1453 Such a function takes one optional parameter, a buffer position (defaults to
1454 point), and returns nil or t. This variable contains nil for languages which
1455 don't have EOL terminated statements. "
1456 t nil
1462 The (admittedly kludgey) purpose of such a function is to prevent an infinite
1463 recursion in c-beginning-of-statement-1 when point starts at a `while' token.
1464 The function MUST NOT UNDER ANY CIRCUMSTANCES call c-beginning-of-statement-1,
1465 even indirectly. This variable contains nil for languages which don't have
1466 EOL terminated statements."
1467 t nil
1472 \f
1473 ;;; Defun functions
1475 ;; The Emacs variables beginning-of-defun-function and
1476 ;; end-of-defun-function will be set so that commands like
1477 ;; `mark-defun' and `narrow-to-defun' work right. The key sequences
1478 ;; C-M-a and C-M-e are, however, bound directly to the CC Mode
1479 ;; functions, allowing optimisation for large n.
1481 "Function to which beginning-of-defun-function will be set."
1482 t 'c-beginning-of-defun
1488 "Function to which end-of-defun-function will be set."
1489 t 'c-end-of-defun
1492 \f
1493 ;;; In-comment text handling.
1496 "Regexp to append to `paragraph-start'."
1497 t "$"
1503 "Regexp to append to `paragraph-separate'."
1504 t "$"
1508 \f
1509 ;;; Keyword lists.
1511 ;; Note: All and only all language constants containing keyword lists
1512 ;; should end with "-kwds"; they're automatically collected into the
1513 ;; `c-kwds-lang-consts' list below and used to build `c-keywords' etc.
1516 "Primitive type keywords. As opposed to the other keyword lists, the
1517 keywords listed here are fontified with the type face instead of the
1518 keyword face.
1520 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1521 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1522 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1523 will be handled.
1525 Do not try to modify this list for end user customizations; the
1526 `*-font-lock-extra-types' variable, where `*' is the mode prefix, is
1527 the appropriate place for that."
1536 ;; Objective-C extends C, but probably not the new stuff in C99.
1543 ;; In CORBA PSDL:
1544 "ref"
1545 ;; The following can't really end a type, but we have to specify them
1546 ;; here due to the assumption in `c-primitive-type-prefix-kwds'. It
1547 ;; doesn't matter that much.
1550 ;; used as a builtin type.
1555 ;; An adorned regexp that matches `c-primitive-type-kwds'.
1560 "Keywords that might act as prefixes for primitive types. Assumed to
1561 be a subset of `c-primitive-type-kwds'."
1562 t nil
1565 ;; In CORBA PSDL:
1570 of a variable declaration."
1575 ;; Adorned regexp matching `c-typedef-kwds'.
1580 "Keywords where the following name - if any - is a type name, and
1581 where the keyword together with the symbol works as a type in
1582 declarations.
1584 Note that an alternative if the second part doesn't hold is
1585 `c-type-list-kwds'. Keywords on this list are typically also present
1586 on one of the `*-decl-kwds' lists."
1587 t nil
1593 ;; Adorned regexp matching `c-type-prefix-kwds'.
1598 "Type modifier keywords. These can occur almost anywhere in types
1599 but they don't build a type of themselves. Unlike the keywords on
1600 `c-primitive-type-kwds', they are fontified with the keyword face and
1601 not the type face."
1602 t nil
1608 ;; Adorned regexp matching `c-type-modifier-kwds', or nil in
1609 ;; languages without such keywords.
1615 ;; An adorned regexp that matches `c-primitive-type-prefix-kwds' and
1616 ;; `c-type-modifier-kwds', or nil in languages without any of them.
1626 ;; All keywords that can start a type (i.e. are either a type prefix
1627 ;; or a complete type).
1634 "Keywords introducing declarations where the following block (if any)
1635 contains another declaration level that should be considered a class.
1637 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1638 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1639 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1640 will be handled.
1642 Note that presence on this list does not automatically treat the
1643 following identifier as a type; the keyword must also be present on
1644 `c-type-prefix-kwds' or `c-type-list-kwds' to accomplish that."
1645 t nil
1653 ;; In CORBA PSDL:
1655 ;; In CORBA CIDL:
1660 ;; Regexp matching the start of a class.
1665 "Keywords introducing declarations where the following block (if
1666 any) is a brace list.
1668 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1669 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1670 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1671 will be handled."
1676 ;; Regexp matching the start of declarations where the following
1677 ;; block is a brace list.
1682 "Keywords where the following block (if any) contains another
1683 declaration level that should not be considered a class. For every
1684 keyword here, CC Mode will add a set of special syntactic symbols for
1686 `foo-open', `foo-close', and `infoo' symbols.
1688 The intention is that this category should be used for block
1689 constructs that aren't related to object orientation concepts like
1690 classes (which thus also include e.g. interfaces, templates,
1691 contracts, structs, etc). The more pragmatic distinction is that
1692 while most want some indentation inside classes, it's fairly common
1693 that they don't want it in some of these constructs, so it should be
1694 simple to configure that differently from classes. See also
1695 `c-class-decl-kwds'.
1697 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1698 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1699 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1700 will be handled."
1701 t nil
1705 ;; In CORBA CIDL:
1709 ;; Regexp matching the start of blocks besides classes that contain
1710 ;; another declaration level.
1719 'inextern-lang
1722 "Alist associating keywords in c-other-decl-block-decl-kwds with
1726 "Keywords introducing declarations where the identifier(s) being
1727 declared are types.
1729 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1730 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1731 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1732 will be handled."
1733 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1734 ;; (since e.g. "Foo" is a type that's being defined in "class Foo
1735 ;; {...}").
1738 ;; Languages that have a "typedef" construct.
1741 ;; Unlike most other languages, exception names are not handled as
1742 ;; types in IDL since they only can occur in "raises" specs.
1750 "Keywords introducing declarations where the \(first) identifier
1751 \(declarator) follows directly after the keyword, without any type.
1753 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1754 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1755 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1756 will be handled."
1757 ;; Default to `c-class-decl-kwds' and `c-brace-list-decl-kwds'
1758 ;; (since e.g. "Foo" is the identifier being defined in "class Foo
1759 ;; {...}").
1762 ;; Note: "manages" for CORBA CIDL clashes with its presence on
1763 ;; `c-type-list-kwds' for IDL.
1766 ;; In CORBA PSDL:
1768 ;; In CORBA CIDL:
1774 "Keywords that can prefix normal declarations of identifiers
1775 \(and typically act as flags). Things like argument declarations
1776 inside function headers are also considered declarations in this
1777 sense.
1779 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1780 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1781 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1782 will be handled."
1783 t nil
1788 ;; FIXME: Some of those below ought to be on `c-other-decl-kwds' instead.
1792 ;; In CORBA PSDL:
1794 ;; In CORBA CIDL:
1796 ;; Note: "const" is not used in Java, but it's still a reserved keyword.
1803 "Keywords that can start or prefix any declaration level construct,
1804 besides those on `c-class-decl-kwds', `c-brace-list-decl-kwds',
1805 `c-other-block-decl-kwds', `c-typedef-decl-kwds',
1806 `c-typeless-decl-kwds' and `c-modifier-kwds'.
1808 If any of these also are on `c-type-list-kwds', `c-ref-list-kwds',
1809 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1810 `c-<>-type-kwds', or `c-<>-arglist-kwds' then the associated clauses
1811 will be handled."
1812 t nil
1818 "Keywords that always start declarations, wherever they occur.
1819 This can be used for declarations that aren't recognized by the normal
1820 combination of `c-decl-prefix-re' and `c-decl-start-re'."
1821 t nil
1822 ;; Classes can be declared anywhere in a Pike expression.
1826 "Keywords that can occur anywhere in a declaration level construct.
1827 This is used for self-contained things that can be tacked on anywhere
1828 on a declaration and that should be ignored to be able to recognize it
1829 correctly. Typical cases are compiler extensions like
1832 __declspec(noreturn) void foo();
1833 class __declspec(dllexport) classname {...};
1834 void foo() __attribute__((noreturn));
1836 Note that unrecognized plain symbols are skipped anyway if they occur
1837 before the type, so such things are not necessary to mention here.
1838 Mentioning them here is necessary only if they can occur in other
1839 places, or if they are followed by a construct that must be skipped
1841 examples above). In the last case, they alse need to be present on
1842 one of `c-type-list-kwds', `c-ref-list-kwds',
1843 `c-colon-type-list-kwds', `c-paren-nontype-kwds', `c-paren-type-kwds',
1844 `c-<>-type-kwds', or `c-<>-arglist-kwds'."
1845 ;; NB: These are currently not recognized in all parts of a
1846 ;; declaration. Specifically, they aren't recognized in the middle
1847 ;; of multi-token types, inside declarators, and between the
1848 ;; identifier and the arglist paren of a function declaration.
1849 ;;
1850 ;; FIXME: This ought to be user customizable since compiler stuff
1851 ;; like this usually is wrapped in project specific macros. (It'd
1852 ;; of course be even better if we could cope without knowing this.)
1853 t nil
1855 "__attribute__"
1856 ;; MSVC extension.
1860 ;; Adorned regexp matching `c-decl-hangon-kwds'.
1865 ;; All keywords that can occur in the preamble of a declaration.
1866 ;; They typically occur before the type, but they are also matched
1867 ;; after presumptive types since we often can't be sure that
1868 ;; something is a type or just some sort of macro in front of the
1869 ;; declaration. They might be ambiguous with types or type
1870 ;; prefixes.
1883 ;; Adorned regexp of `c-prefix-spec-kwds'.
1887 (replace-regexp-in-string "\\\\\\+" "+" (c-make-keywords-re t (c-lang-const c-prefix-spec-kwds)))))
1892 ;; Adorned regexp of the keywords in `c-prefix-spec-kwds' that aren't
1893 ;; ambiguous with types or type prefixes. These are the keywords (like
1894 ;; extern, namespace, but NOT template) that can modify a declaration.
1903 ;; Keywords that can occur after argument list of a function header
1904 ;; declaration, i.e. in the "K&R region".
1909 ;; Adorned regexp matching all keywords that can't appear at the
1910 ;; start of a declaration.
1920 "Access protection label keywords in classes."
1921 t nil
1926 "Keywords introducing declarations that can contain a block which
1929 like that, it ends with the following ';' and not right away.
1931 The keywords on list are assumed to also be present on one of the
1932 `*-decl-kwds' lists."
1933 t nil
1938 ;; Regexp matching the `c-block-decls-with-vars' keywords, or nil in
1939 ;; languages without such constructs.
1946 "Keywords introducing extra declaration specifiers in the region
1948 declarations."
1949 t nil
1952 "supports"
1953 ;; In CORBA PSDL:
1957 "Keywords that may be followed by a nonsymbol sexp before whatever
1958 construct it's part of continues."
1959 t nil
1963 "Keywords that may be followed by a comma separated list of type
1964 identifiers, where each optionally can be prefixed by keywords. (Can
1965 also be used for the special case when the list can contain only one
1966 element.)
1968 Assumed to be mutually exclusive with `c-ref-list-kwds'. There's no
1969 reason to put keywords on this list if they are on `c-type-prefix-kwds'.
1970 There's also no reason to add keywords that prefixes a normal
1971 declaration consisting of a type followed by a declarator (list), so
1972 the keywords on `c-modifier-kwds' should normally not be listed here
1973 either.
1975 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1976 or variable identifier (that's being defined)."
1977 t nil
1982 ;; In CORBA PSDL:
1987 "Keywords that may be followed by a comma separated list of
1988 reference (i.e. namespace/scope/module) identifiers, where each
1989 optionally can be prefixed by keywords. (Can also be used for the
1990 special case when the list can contain only one element.) Assumed to
1991 be mutually exclusive with `c-type-list-kwds'.
1993 Note: Use `c-typeless-decl-kwds' for keywords followed by a function
1994 or variable identifier (that's being defined)."
1995 t nil
1999 ;; In CORBA CIDL:
2004 "Keywords that may be followed (not necessarily directly) by a colon
2005 and then a comma separated list of type identifiers, where each
2006 optionally can be prefixed by keywords. (Can also be used for the
2007 special case when the list can contain only one element.)"
2008 t nil
2011 ;; In CORBA PSDL:
2015 "Regexp matched after the keywords in `c-colon-type-list-kwds' to skip
2016 forward to the colon. The end of the match is assumed to be directly
2018 regexp if `c-colon-type-list-kwds' isn't nil."
2020 ;; Disallow various common punctuation chars that can't come
2021 ;; before the ":" that starts the inherit list after "class"
2022 ;; or "struct" in C++. (Also used as default for other
2023 ;; languages.)
2028 "Keywords that may be followed by a parenthesis expression that doesn't
2029 contain type identifiers."
2030 t nil
2032 "__attribute__"
2033 ;; MSVC extension.
2037 "Keywords that may be followed by a parenthesis expression containing
2038 type identifiers separated by arbitrary tokens."
2039 t nil
2051 "Keywords that may be followed by an angle bracket expression
2053 `c-<>-arglist-kwds' is that unknown names are taken to be types and
2054 not other identifiers. `c-recognize-<>-arglists' is assumed to be set
2055 if this isn't nil."
2056 t nil
2059 ;; In CORBA PSDL:
2063 "Keywords that can be followed by a C++ style template arglist; see
2064 `c-recognize-<>-arglists' for details. That language constant is
2065 assumed to be set if this isn't nil."
2066 t nil
2071 ;; All keywords that can be followed by an angle bracket sexp.
2077 ;; Adorned regexp matching keywords that can be followed by an angle
2078 ;; bracket sexp. Always set when `c-recognize-<>-arglists' is.
2084 "Keywords that may be followed by a brace block containing a comma
2085 separated list of identifier definitions, i.e. like the list of
2086 identifiers that follows the type in a normal declaration."
2090 "Statement keywords followed directly by a substatement."
2095 idl nil)
2098 ;; Regexp matching the start of any statement followed directly by a
2099 ;; substatement (doesn't match a bare block, however).
2104 "Statement keywords followed by a paren sexp and then by a substatement."
2109 idl nil
2114 ;; Regexp matching the start of any statement followed by a paren sexp
2115 ;; and then by a substatement.
2120 ;; Union of `c-block-stmt-1-kwds' and `c-block-stmt-2-kwds'.
2126 ;; Regexp matching the start of any statement that has a
2127 ;; substatement (except a bare block). Nil in languages that
2128 ;; don't have such constructs.
2137 "Statement keywords followed by an expression or nothing."
2140 ;; Note: `goto' is not valid in Java, but the keyword is still reserved.
2142 idl nil
2149 ;; Adorned regexp matching `c-simple-stmt-kwds'.
2154 "Statement keywords followed by a parenthesis expression that
2155 nevertheless contains a list separated with ';' and not ','."
2157 idl nil)
2160 ;; Adorned regexp matching `c-paren-stmt-kwds'.
2165 "Statement keywords followed by an assembler expression."
2166 t nil
2170 ;; Regexp matching the start of an assembler statement. Nil in
2171 ;; languages that don't support that.
2180 awk nil)
2183 ;; Adorned regexp matching any "case"-like keyword.
2188 "Keywords introducing colon terminated labels in blocks."
2190 awk nil)
2193 ;; Adorned regexp matching any keyword that introduces a label.
2198 "Keywords that might be followed by a label identifier."
2202 idl nil
2203 awk nil)
2206 "Keywords for constants."
2207 t nil
2216 "Keywords besides constants and operators that start primary expressions."
2217 t nil
2224 ;; Keywords that can occur anywhere in expressions. Built from
2225 ;; `c-primary-expr-kwds' and all keyword operators in `c-operators'.
2229 t
2234 "Keywords that start lambda constructs, i.e. function definitions in
2235 expressions."
2236 t nil
2240 "Keywords that start constructs followed by statement blocks which can
2241 be used in expressions \(the gcc extension for this in C and C++ is
2242 handled separately by `c-recognize-paren-inexpr-blocks')."
2243 t nil
2247 "Keywords that can start classes inside expressions."
2248 t nil
2253 "Keywords that can start brace list blocks inside expressions.
2254 Note that Java specific rules are currently applied to tell this from
2255 `c-inexpr-class-kwds'."
2256 t nil
2260 ;; Regexp matching the start of a brace list in an expression, or
2261 ;; nil in languages that don't have such things. This should not
2262 ;; match brace lists recognized through `c-special-brace-lists'.
2269 ;; Regexp matching keywords in any construct that contain another
2270 ;; declaration level, i.e. that isn't followed by a function block
2271 ;; or brace list. When the first submatch matches, it's an
2272 ;; unambiguous construct, otherwise it's an ambiguous match that
2273 ;; might also be the return type of a function declaration.
2291 "Keywords that can introduce bitfields."
2292 t nil
2296 ;; Regexp matching the start of a bitfield (not uniquely), or nil in
2297 ;; languages without bitfield support.
2298 t nil
2303 "Keywords not accounted for by any other `*-kwds' language constant."
2304 t nil
2306 ;; In CORBA CIDL: (These are declaration keywords that never
2307 ;; can start a declaration.)
2310 \f
2311 ;;; Constants built from keywords.
2313 ;; Note: No `*-kwds' language constants may be defined below this point.
2317 ;; List of all the language constants that contain keyword lists.
2322 ;; Make the list of globally interned symbols
2323 ;; instead of ones interned in `c-lang-constants'.
2325 c-lang-constants)
2326 list)))
2329 ;; All keywords as a list.
2334 c-kwds-lang-consts)
2335 nil))
2339 ;; All keywords as an adorned regexp.
2344 ;; An alist with all the keywords in the cars. The cdr for each
2345 ;; keyword is a list of the symbols for the `*-kwds' lists that
2346 ;; contains it.
2352 c-kwds-lang-consts))))
2353 lang-const kwd-list kwd
2354 result-alist elem)
2366 result-alist))
2369 ;; An obarray containing all keywords as symbols. The property list
2370 ;; of each symbol has a non-nil entry for the specific `*-kwds'
2371 ;; lists it's a member of.
2372 ;;
2373 ;; E.g. to see whether the string str contains a keyword on
2374 ;; `c-class-decl-kwds', one can do like this:
2375 ;; (get (intern-soft str c-keyword-obarray) 'c-class-decl-kwds)
2376 ;; Which preferably is written using the associated functions in
2377 ;; cc-engine:
2378 ;; (c-keyword-member (c-keyword-sym str) 'c-class-decl-kwds)
2380 ;; The obarray is not stored directly as a language constant since
2381 ;; the printed representation for obarrays used in .elc files isn't
2382 ;; complete.
2385 kwd lang-const-list
2392 ;; Emacs has an odd bug that causes `mapcan' to fail
2393 ;; with unintelligible errors. (XEmacs works.)
2394 ;;(mapcan (lambda (lang-const)
2395 ;; (list lang-const t))
2396 ;; lang-const-list)
2399 lang-const-list))))
2400 obarray))
2403 ;; Adorned regexp matching all keywords that should be fontified
2404 ;; with the keywords face. I.e. that aren't types or constants.
2414 ;; Regexp matching the start of any primary expression, i.e. any
2415 ;; literal, symbol, prefix operator, and '('. It doesn't need to
2416 ;; exclude keywords; they are excluded afterwards unless the second
2417 ;; submatch matches. If the first but not the second submatch
2418 ;; matches then it is an ambiguous primary expression; it could also
2419 ;; be a match of e.g. an infix operator. (The case with ambiguous
2420 ;; keyword operators isn't handled.)
2426 ;; Filter out the special case prefix
2427 ;; operators that are close parens.
2432 t
2438 postfix-if-paren
2439 left-assoc
2440 right-assoc
2441 right-assoc-sequence)
2442 t))
2445 in-or-postfix-ops
2448 in-or-postfix-ops
2453 ;; Take out all symbol class operators from `prefix-ops' and make the
2454 ;; first submatch from them together with `c-primary-expr-kwds'.
2461 ;; Match all ambiguous operators.
2468 ;; Now match all other symbols.
2472 ;; The chars that can start integer and floating point
2473 ;; constants.
2477 ;; The nonambiguous operators from `prefix-ops'.
2483 ;; Match string and character literals.
2490 \f
2491 ;;; Additional constants for parser-level constructs.
2494 "Regexp matching something that might precede a declaration, cast or
2495 label, such as the last token of a preceding statement or declaration.
2496 This is used in the common situation where a declaration or cast
2497 doesn't start with any specific token that can be searched for.
2499 The regexp should not match bob; that is done implicitly. It can't
2500 require a match longer than one token. The end of the token is taken
2501 to be at the end of the first submatch, which is assumed to always
2502 match. It's undefined whether identifier syntax (see
2503 `c-identifier-syntax-table') is in effect or not. This regexp is
2504 assumed to be a superset of `c-label-prefix-re' if
2505 `c-recognize-colon-labels' is set.
2507 Besides this, `c-decl-start-kwds' is used to find declarations.
2509 Note: This variable together with `c-decl-start-re' and
2511 declaration/cast/label starts. I.e. they might produce more matches
2512 but should not miss anything (or else it's necessary to use text
2513 properties - see the next note). Wherever they match, the following
2514 construct is analyzed to see if it indeed is a declaration, cast or
2515 label. That analysis is not cheap, so it's important that not too
2516 many false matches are triggered.
2518 Note: If a declaration/cast/label start can't be detected with this
2519 variable, it's necessary to use the `c-type' text property with the
2520 value `c-decl-end' on the last char of the last token preceding the
2521 declaration. See the comment blurb at the start of cc-engine.el for
2522 more info."
2524 ;; We match a sequence of characters to skip over things like \"};\"
2525 ;; more quickly. We match ")" in C for K&R region declarations, and
2526 ;; in all languages except Java for when a cpp macro definition
2527 ;; begins with a declaration.
2530 ;; Match "<" in C++ to get the first argument in a template arglist.
2531 ;; In that case there's an additional check in `c-find-decl-spots'
2532 ;; that it got open paren syntax.
2534 ;; Additionally match the protection directives in Objective-C.
2535 ;; Note that this doesn't cope with the longer directives, which we
2536 ;; would have to match from start to end since they don't end with
2537 ;; any easily recognized characters.
2541 ;; Pike is like C but we also match "[" for multiple value
2542 ;; assignments and type casts.
2548 "Regexp matching the start of any declaration, cast or label.
2549 It's used on the token after the one `c-decl-prefix-re' matched. This
2550 regexp should not try to match those constructs accurately as it's
2551 only used as a sieve to avoid spending more time checking other
2552 constructs."
2557 ;; Regexp matching something that might precede or start a
2558 ;; declaration, cast or label.
2559 ;;
2560 ;; If the first submatch matches, it's taken to match the end of a
2561 ;; token that might precede such a construct, e.g. ';', '}' or '{'.
2562 ;; It's built from `c-decl-prefix-re'.
2563 ;;
2564 ;; If the first submatch did not match, the match of the whole
2565 ;; regexp is taken to be at the first token in the declaration.
2566 ;; `c-decl-start-re' is not checked in this case.
2567 ;;
2568 ;; Design note: The reason the same regexp is used to match both
2569 ;; tokens that precede declarations and start them is to avoid an
2570 ;; extra regexp search from the previous declaration spot in
2571 ;; `c-find-decl-spots'. Users of `c-find-decl-spots' also count on
2572 ;; that it finds all declaration/cast/label starts in approximately
2573 ;; linear order, so we can't do the searches in two separate passes.
2584 ;; List containing the paren characters that can open a cast, or nil in
2585 ;; languages without casts.
2593 "List of syntactically relevant characters that never can occur before
2594 the open brace in any construct that contains a brace block, e.g. in
2597 class Foo: public Bar {int x();} a, *b;
2599 If parens can occur, the chars inside those aren't filtered with this
2600 list.
2602 '<' and '>' should be disallowed even if angle bracket arglists can
2603 occur. That since the search function needs to stop at them anyway to
2604 ensure they are given paren syntax.
2606 This is used to skip backward from the open brace to find the region
2609 possible for good performance."
2611 ;; Default to all chars that only occurs in nonsymbol tokens outside
2612 ;; identifiers.
2618 t
2619 t
2623 op pos)
2626 res))))
2628 ;; Allow cpp operatios (where applicable).
2634 ;; Allow ':' for inherit list starters.
2638 ;; Allow ',' for multiple inherits.
2642 ;; Allow parentheses for anonymous inner classes in Java and class
2643 ;; initializer lists in Pike.
2647 ;; Allow '"' for extern clauses (e.g. extern "C" {...}).
2652 ;; `c-block-prefix-disallowed-chars' as an inverted charset suitable
2653 ;; for `c-syntactic-skip-backward'.
2658 "Regexp matching the declarator operators that might precede the
2661 The end of the first submatch is taken as the end of the operator.
2662 Identifier syntax is in effect when this is matched \(see
2663 `c-identifier-syntax-table')."
2666 ;; Default to a regexp that never matches.
2668 ;; Check that there's no "=" afterwards to avoid matching tokens
2669 ;; like "*=".
2671 "[*\(]"
2677 "[*\(&]"
2682 ;; If this matches there's special treatment in
2683 ;; `c-font-lock-declarators' and
2684 ;; `c-font-lock-declarations' that check for a
2685 ;; complete name followed by ":: *".
2695 "Regexp matching the declarator operators that might follow after the
2698 it matches an open paren of some kind, the type declaration check
2699 continues at the corresponding close paren, otherwise the end of the
2700 first submatch is taken as the end of the operator. Identifier syntax
2701 is in effect when this is matched (see `c-identifier-syntax-table')."
2702 ;; Default to a regexp that matches `c-type-modifier-kwds' and a
2703 ;; function argument list parenthesis.
2711 "[\)\[\(]"
2715 ;; "throw" in `c-type-modifier-kwds' is followed
2716 ;; by a parenthesis list, but no extra measures
2717 ;; are necessary to handle that.
2727 "This regexp is matched after a declarator expression where
2728 `c-type-decl-suffix-key' has matched. If it matches then the
2729 construct is taken as a declaration. It's typically used to match the
2730 beginning of a function body or whatever might occur after the
2731 function header in a function declaration or definition. It's
2732 undefined whether identifier syntax (see `c-identifier-syntax-table')
2733 is in effect or not.
2738 t "{"
2739 ;; If K&R style declarations should be recognized then one could
2740 ;; consider to match the start of any symbol since we want to match
2741 ;; the start of the first declaration in the "K&R region". That
2742 ;; could however produce false matches on code like "FOO(bar) x"
2743 ;; where FOO is a cpp macro, so it's better to leave it out and rely
2744 ;; on the other heuristics in that case.
2746 ;; Add on the keywords in `c-postfix-spec-kwds'.
2751 ;; Also match the colon that starts a base class initializer list in
2752 ;; C++. That can be confused with a function call before the colon
2753 ;; in a ? : operator, but we count on that `c-decl-prefix-re' won't
2754 ;; match before such a thing (as a declaration-level construct;
2755 ;; matches inside arglist contexts are already excluded).
2762 ;; Regexp that in addition to `c-after-suffixed-type-decl-key'
2763 ;; matches ";" and ",".
2772 end of the operator. nil in languages without such operators. It's
2773 undefined whether identifier syntax (see `c-identifier-syntax-table')
2774 is in effect or not."
2775 t nil
2781 "Regexp matching operators that might follow after a type, or nil in
2782 languages that don't have such operators. The end of the first
2783 submatch is taken as the end of the operator. This should not match
2784 things like C++ template arglists if `c-recognize-<>-arglists' is set.
2785 It's undefined whether identifier syntax (see `c-identifier-syntax-table')
2786 is in effect or not."
2787 t nil
2793 ;; Regexp matching the known type identifiers. This is initialized
2794 ;; from the type keywords and `*-font-lock-extra-types'. The first
2795 ;; submatch is the one that matches the type. Note that this regexp
2796 ;; assumes that symbol constituents like '_' and '$' have word
2797 ;; syntax.
2806 extra-types)))
2812 extra-types))))
2817 plain-strings)))
2818 regexp-strings)
2823 "List of open- and close-chars that makes up a pike-style brace list,
2825 list."
2826 t nil
2831 "Non-nil means K&R style argument declarations are valid."
2832 t nil
2833 c t)
2837 "Non-nil means function declarations without return type should be
2838 recognized. That can introduce an ambiguity with parenthesized macro
2839 calls before a brace block. This setting does not affect declarations
2840 that are preceded by a declaration starting keyword, so
2841 e.g. `c-typeless-decl-kwds' may still be used when it's set to nil."
2842 t nil
2848 "Non-nil means C++ style template arglists should be handled. More
2849 specifically, this means a comma separated list of types or
2851 identifier or one of the keywords on `c-<>-type-kwds' or
2852 `c-<>-arglist-kwds'. If there's an identifier before then the whole
2853 expression is considered to be a type."
2859 "Non-nil means that parenthesis style initializers exist,
2860 i.e. constructs like
2862 Foo bar (gnu);
2864 in addition to the more classic
2866 Foo bar = gnu;"
2867 t nil
2872 "Non-nil to recognize gcc style in-expression blocks,
2873 i.e. compound statements surrounded by parentheses inside expressions."
2874 t nil
2880 ;; Regexp matching the start of angle bracket arglists in languages
2881 ;; where `c-recognize-<>-arglists' is set. Does not exclude
2882 ;; keywords outside `c-<>-arglist-kwds'. The first submatch is
2883 ;; assumed to surround the preceding symbol. The whole match is
2884 ;; assumed to end directly after the opening "<".
2894 ;; Regexp that in addition to `c-opt-<>-arglist-start' matches close
2895 ;; parens. The first submatch is assumed to surround
2896 ;; `c-opt-<>-arglist-start'.
2905 ;; Regexp matching the beginning of a declaration specifier in the
2906 ;; region between the header and the body of a declaration.
2907 ;;
2908 ;; TODO: This is currently not used uniformly; c++-mode and
2909 ;; java-mode each have their own ways of using it.
2910 t nil
2923 That includes labels in code and access keys in classes. This does
2924 not apply to labels recognized by `c-label-kwds' and
2925 `c-opt-extra-label-key'."
2926 t nil
2932 "Regexp like `c-decl-prefix-re' that matches any token that can precede
2933 a generic colon label. Not used if `c-recognize-colon-labels' is
2934 nil."
2940 "Regexp matching things that can't occur in generic colon labels,
2941 neither in a statement nor in a declaration context. The regexp is
2942 tested at the beginning of every sexp in a suspected label,
2945 ;; Don't allow string literals.
2947 ;; All keywords except `c-label-kwds' and `c-protection-kwds'.
2953 ;; Also check for open parens in C++, to catch member init lists in
2954 ;; constructors. We normally allow it so that macros with arguments
2955 ;; work in labels.
2960 "Optional regexp matching labels.
2961 Normally, labels are detected according to `c-nonlabel-token-key',
2962 `c-decl-prefix-re' and `c-nonlabel-decl-prefix-re'. This regexp can
2963 be used if there are additional labels that aren't recognized that
2964 way."
2965 t nil
2970 ;; Regexp describing friend declarations classes, or nil in
2971 ;; languages that don't have such things.
2972 ;;
2973 ;; TODO: Ought to use `c-prefix-spec-kwds-re' or similar, and the
2974 ;; template skipping isn't done properly. This will disappear soon.
2975 t nil
2980 "<.+>"
2982 "friend"
2987 ;; Special regexp to match the start of Objective-C methods. The
2988 ;; first submatch is assumed to end after the + or - key.
2989 t nil
2991 ;; TODO: Ought to use a better method than anchoring on bol.
2996 "([^\)]*)"
3003 ;; Must be set in buffers where the `c-type' text property might be
3004 ;; used with the value `c-decl-end'.
3005 ;;
3006 ;; `c-decl-end' is used to mark the ends of labels and access keys
3007 ;; to make interactive refontification work better.
3010 ;; `c-decl-end' is used to mark the end of the @-style directives in
3011 ;; Objective-C.
3012 objc t)
3015 \f
3016 ;;; Wrap up the `c-lang-defvar' system.
3018 ;; Compile in the list of language variables that has been collected
3019 ;; with the `c-lang-defvar' and `c-lang-setvar' macros. Note that the
3020 ;; first element of each is nil.
3024 ;; Make the `c-lang-setvar' variables buffer local in the current buffer.
3025 ;; These are typically standard emacs variables such as `comment-start'.
3033 "Create a function that initializes all the language dependent variables
3034 for the given mode.
3036 This function should be evaluated at compile time, so that the
3037 function it returns is byte compiled with all the evaluated results
3038 from the language constants. Use the `c-init-language-vars' macro to
3039 accomplish that conveniently."
3045 ;; No need to byte compile this lambda since the byte compiler is
3046 ;; smart enough to detect the `funcall' construct in the
3047 ;; `c-init-language-vars' macro below and compile it all straight
3048 ;; into the function that contains `c-init-language-vars'.
3051 ;; This let sets up the context for `c-mode-var' and similar
3052 ;; that could be in the result from `cl-macroexpand-all'.
3054 current-var source-eval)
3061 ;; `c-lang-const' will expand to the evaluated
3062 ;; constant immediately in `cl-macroexpand-all'
3063 ;; below.
3069 ;; Note: The following `append' copies the
3070 ;; first argument. That list is small, so
3071 ;; this doesn't matter too much.
3075 ;; This diagnostic message isn't useful for end
3076 ;; users, so it's disabled.
3077 ;;(unless (get ',mode 'c-has-warned-lang-consts)
3078 ;; (message ,(concat "%s compiled with CC Mode %s "
3079 ;; "but loaded with %s - evaluating "
3080 ;; "language constants from source")
3081 ;; ',mode ,c-version c-version)
3082 ;; (put ',mode 'c-has-warned-lang-consts t))
3096 current-var
3099 (fallback source eval - %s compiled with CC Mode %s but loaded with %s)"
3102 err)
3105 ;; Being evaluated from source. Always use the dynamic method to
3106 ;; work well when `c-lang-defvar's in this file are reevaluated
3107 ;; interactively.
3113 current-var)
3125 "Eval error in the `c-lang-defvar' or `c-lang-setver' for `%s' (source eval): %S"
3126 current-var err)
3128 ))
3131 "Initialize all the language dependent variables for the given mode.
3132 This macro is expanded at compile time to a form tailored for the mode
3133 in question, so MODE must be a constant. Therefore MODE is not
3134 evaluated and should not be quoted."
3137 \f
3140 ;; arch-tag: 1ab57482-cfc2-4c5b-b628-3539c3098822
3141 ;;; cc-langs.el ends here