| blob | d0beab1d48555e6696a2fc05f32fe579e51b77b7 |
1 ;;; cc-defs.el --- compile time definitions for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2015 Free Software Foundation, Inc.
5 ;; Authors: 2003- Alan Mackenzie
6 ;; 1998- Martin Stjernholm
7 ;; 1992-1999 Barry A. Warsaw
8 ;; 1987 Dave Detlefs
9 ;; 1987 Stewart Clamen
10 ;; 1985 Richard M. Stallman
11 ;; Maintainer: bug-cc-mode@gnu.org
12 ;; Created: 22-Apr-1997 (split from cc-mode.el)
13 ;; Keywords: c languages
14 ;; Package: cc-mode
16 ;; This file is part of GNU Emacs.
18 ;; GNU Emacs is free software: you can redistribute it and/or modify
19 ;; it under the terms of the GNU General Public License as published by
20 ;; the Free Software Foundation, either version 3 of the License, or
21 ;; (at your option) any later version.
23 ;; GNU Emacs is distributed in the hope that it will be useful,
24 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
25 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
26 ;; GNU General Public License for more details.
28 ;; You should have received a copy of the GNU General Public License
29 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
31 ;;; Commentary:
33 ;; This file contains macros, defsubsts, and various other things that
34 ;; must be loaded early both during compilation and at runtime.
36 ;;; Code:
43 load-path)))
49 ;; Silence the compiler.
59 \f
60 ;; cc-fix.el contains compatibility macros that should be used if
61 ;; needed.
68 ; to make the call to f-l-c-k throw an error.
76 ;; The above takes care of the delayed loading, but this is necessary
77 ;; to ensure correct byte compilation.
85 font-lock-keywords)))
88 ;; XEmacs 21.4 doesn't have `delete-dups'.
93 \f
94 ;;; Variables also used at compile time.
100 ;; A little more compact and faster in comparisons.
103 "Non-nil for all buffers with a major mode derived from CC Mode.
104 Otherwise, this variable is nil. I.e. this variable is non-nil for
105 `c-mode', `c++-mode', `objc-mode', `java-mode', `idl-mode',
106 `pike-mode', `awk-mode', and any other non-CC Mode mode that calls
107 `c-initialize-cc-mode'. The value is the mode symbol itself
108 \(i.e. `c-mode' etc) of the original CC Mode mode, or just t if it's
112 ;; Have to make `c-buffer-is-cc-mode' permanently local so that it
113 ;; survives the initialization of the derived mode.
116 \f
117 ;; The following is used below during compilation.
122 "Like `progn', but evaluates the body at compile time.
123 The result of the body appears to the compiler as a quoted constant.
125 This variant works around bugs in `eval-when-compile' in various
126 \(X)Emacs versions. See cc-defs.el for details."
129 ;; XEmacs 21.4.6 has a bug in `eval-when-compile' in that it
130 ;; evaluates its body at macro expansion time if it's nested
131 ;; inside another `eval-when-compile'. So we use a dynamically
132 ;; bound variable to avoid nesting them.
136 ;; In all (X)Emacsen so far, `eval-when-compile' byte compiles
137 ;; its contents before evaluating it. That can cause forms to
138 ;; be compiled in situations they aren't intended to be
139 ;; compiled.
140 ;;
141 ;; Example: It's not possible to defsubst a primitive, e.g. the
142 ;; following will produce an error (in any emacs flavor), since
143 ;; `nthcdr' is a primitive function that's handled specially by
144 ;; the byte compiler and thus can't be redefined:
145 ;;
146 ;; (defsubst nthcdr (val) val)
147 ;;
148 ;; `defsubst', like `defmacro', needs to be evaluated at
149 ;; compile time, so this will produce an error during byte
150 ;; compilation.
151 ;;
152 ;; CC Mode occasionally needs to do things like this for
153 ;; cross-emacs compatibility. It therefore uses the following
154 ;; to conditionally do a `defsubst':
155 ;;
156 ;; (eval-when-compile
157 ;; (if (not (fboundp 'foo))
158 ;; (defsubst foo ...)))
159 ;;
160 ;; But `eval-when-compile' byte compiles its contents and
161 ;; _then_ evaluates it (in all current emacs versions, up to
162 ;; and including Emacs 20.6 and XEmacs 21.1 as of this
163 ;; writing). So this will still produce an error, since the
164 ;; byte compiler will get to the defsubst anyway. That's
165 ;; arguably a bug because the point with `eval-when-compile' is
166 ;; that it should evaluate rather than compile its contents.
167 ;;
168 ;; We get around it by expanding the body to a quoted
169 ;; constant that we eval. That otoh introduce a problem in
170 ;; that a returned lambda expression doesn't get byte
171 ;; compiled (even if `function' is used).
180 \f
181 ;;; Macros.
184 "Return the value of certain commonly referenced POSITIONs relative to POINT.
185 The current point is used if POINT isn't specified. POSITION can be
186 one of the following symbols:
188 `bol' -- beginning of line
189 `eol' -- end of line
190 `bod' -- beginning of defun
191 `eod' -- end of defun
192 `boi' -- beginning of indentation
193 `ionl' -- indentation of next line
194 `iopl' -- indentation of previous line
195 `bonl' -- beginning of next line
196 `eonl' -- end of next line
197 `bopl' -- beginning of previous line
198 `eopl' -- end of previous line
199 `bosws' -- beginning of syntactic whitespace
200 `eosws' -- end of syntactic whitespace
202 If the referenced position doesn't exist, the closest accessible point
203 to it is returned. This function does not modify the point or the mark."
305 ;; The bulk of this should perhaps be in a function to avoid large
306 ;; expansions, but this case is not used anywhere in CC Mode (and
307 ;; probably not anywhere else either) so we only have it to be on
308 ;; the safe side.
339 ;; Constant to decide at compilation time whether to use category
340 ;; properties. Currently (2010-03) they're available only on GNU Emacs.
358 ;; See the doc string for either of the defuns expanded to.
361 ;; XEmacs >= 2005-01-25
363 ;; Emacs and earlier XEmacs
367 ;; Return t when the region is active. The determination of region
368 ;; activeness is different in both Emacs and XEmacs.
370 ;; XEmacs.
372 ;; Old Emacs.
376 ;; Activate the region if ACTIVE is non-nil, deactivate it
377 ;; otherwise. Covers the differences between Emacs and XEmacs.
379 ;; XEmacs.
383 ;; Emacs.
387 "Delete the text between START and END and return it."
389 ;; Emacs 21.1 and later
391 ;; XEmacs and Emacs 20.x
397 ;; safely execute BODY, return nil if an error occurred
404 ;; In Emacs, a character is an integer. In XEmacs, a character is a
405 ;; type distinct from an integer. Sometimes we need to convert integers to
406 ;; characters. `c-int-to-char' makes this conversion, if necessary.
409 integer))
412 ;; The last character just typed. Note that `last-command-event' exists in
413 ;; both Emacs and XEmacs, but with confusingly different meanings.
415 'last-command-char
419 ;; Get the regular expression `sentence-end'.
421 ;; Emacs 22:
423 ;; Emacs <22 + XEmacs
427 ;; Get the default value of the variable sentence end.
429 ;; Emacs 22:
431 ;; Emacs <22 + XEmacs
434 ;; The following is essentially `save-buffer-state' from lazy-lock.el.
435 ;; It ought to be a standard macro.
437 "Bind variables according to VARLIST (in `let*' style) and eval BODY,
438 then restore the buffer state under the assumption that no significant
439 modification has been made in BODY. A change is considered
440 significant if it affects the buffer text in any way that isn't
441 completely restored again. Changes in text properties like `face' or
442 `syntax-table' are considered insignificant. This macro allows text
443 properties to be changed, even in a read-only buffer.
445 This macro should be placed around all calculations which set
447 known to be writable. That way, these text properties remain set
448 even if the user undoes the command which set them.
451 changes \(like adding a newline to calculate a text-property then
452 deleting it again\), so that the user never sees them on his
453 `buffer-undo-list'. See also `c-tentative-buffer-changes'.
455 However, any user-visible changes to the buffer \(like auto-newlines\)
456 must not be within a `c-save-buffer-state', since the user then
457 wouldn't be able to undo them.
459 The return value is the value of the last form in BODY."
462 before-change-functions after-change-functions
463 deactivate-mark
464 buffer-file-name buffer-file-truename ; Prevent primitives checking
465 ; for file modification
475 "Eval BODY and optionally restore the buffer contents to the state it
476 was in before BODY. Any changes are kept if the last form in BODY
477 returns non-nil. Otherwise it's undone using the undo facility, and
478 various other buffer state that might be affected by the changes is
479 restored. That includes the current buffer, point, mark, mark
480 activation \(similar to `save-excursion'), and the modified state.
481 The state is also restored if BODY exits nonlocally.
483 If BODY makes a change that unconditionally is undone then wrap this
484 macro inside `c-save-buffer-state'. That way the change can be done
485 even when the buffer is read-only, and without interference from
486 various buffer change hooks."
488 -tnt-chng-state)
490 ;; Insert an undo boundary for use with `undo-more'. We
491 ;; don't use `undo-boundary' since it doesn't insert one
492 ;; unconditionally.
500 ;; Used internally in `c-tentative-buffer-changes'.
503 ;; No need to use markers for the point and mark; if the
504 ;; undo got out of synch we're hosed anyway.
511 ;; Used internally in `c-tentative-buffer-changes'.
515 ;; No change was done after all.
519 ;; Find and remove the undo boundary.
525 ;; `primitive-undo' will remove the boundary.
530 saved-undo-list))))
542 "Forward skip over syntactic whitespace.
543 Syntactic whitespace is defined as whitespace characters, comments,
544 and preprocessor directives. However if point starts inside a comment
545 or preprocessor directive, the content of it is not treated as
546 whitespace.
548 LIMIT sets an upper limit of the forward movement, if specified. If
549 LIMIT or the end of the buffer is reached inside a comment or
550 preprocessor directive, the point will be left there.
552 Note that this function might do hidden buffer changes. See the
553 comment at the start of cc-engine.el for more info."
561 "Backward skip over syntactic whitespace.
562 Syntactic whitespace is defined as whitespace characters, comments,
563 and preprocessor directives. However if point starts inside a comment
564 or preprocessor directive, the content of it is not treated as
565 whitespace.
567 LIMIT sets a lower limit of the backward movement, if specified. If
568 LIMIT is reached inside a line comment or preprocessor directive then
569 the point is moved into it past the whitespace at the end.
571 Note that this function might do hidden buffer changes. See the
572 comment at the start of cc-engine.el for more info."
580 "Move forward across COUNT balanced expressions.
581 A negative COUNT means move backward. Signal an error if the move
582 fails for any reason.
584 This is like `forward-sexp' except that it isn't interactive and does
585 not do any user friendly adjustments of the point and that it isn't
586 susceptible to user configurations such as disabling of signals in
587 certain situations."
592 "See `c-forward-sexp' and reverse directions."
597 "Like `scan-lists' but returns nil instead of signaling errors
598 for unbalanced parens.
600 A limit for the search may be given. FROM is assumed to be on the
601 right side of it."
615 res)))
617 \f
618 ;; Wrappers for common scan-lists cases, mainly because it's almost
619 ;; impossible to get a feel for how that function works.
622 "Move backward across one balanced group of parentheses.
624 Return POINT when we succeed, NIL when we fail. In the latter case, leave
625 point unmoved."
628 endpos)))
631 "Move backward across one balanced group of parentheses.
633 Return POINT when we succeed, NIL when we fail. In the latter case, leave
634 point unmoved."
637 endpos)))
640 "Return the first position after the list sexp containing POS,
641 or nil if no such position exists. The point is used if POS is left out.
643 A limit for the search may be given. The start position is assumed to
644 be before it."
648 "Return the position of the start of the list sexp containing POS,
649 or nil if no such position exists. The point is used if POS is left out.
651 A limit for the search may be given. The start position is assumed to
652 be after it."
656 "Return the first position inside the first list sexp after POS,
657 or nil if no such position exists. The point is used if POS is left out.
659 A limit for the search may be given. The start position is assumed to
660 be before it."
664 "Return the last position inside the last list sexp before POS,
665 or nil if no such position exists. The point is used if POS is left out.
667 A limit for the search may be given. The start position is assumed to
668 be after it."
672 "Move the point to the first position after the list sexp containing POS,
673 or containing the point if POS is left out. Return t if such a
674 position exists, otherwise nil is returned and the point isn't moved.
676 A limit for the search may be given. The start position is assumed to
677 be before it."
683 res)))
686 "Move the point to the position of the start of the list sexp containing POS,
687 or containing the point if POS is left out. Return t if such a
688 position exists, otherwise nil is returned and the point isn't moved.
690 A limit for the search may be given. The start position is assumed to
691 be after it."
697 res)))
700 "Move the point to the first position inside the first list sexp after POS,
701 or before the point if POS is left out. Return t if such a position
702 exists, otherwise nil is returned and the point isn't moved.
704 A limit for the search may be given. The start position is assumed to
705 be before it."
711 res)))
714 "Move the point to the last position inside the last list sexp before POS,
715 or before the point if POS is left out. Return t if such a position
716 exists, otherwise nil is returned and the point isn't moved.
718 A limit for the search may be given. The start position is assumed to
719 be after it."
725 res)))
727 \f
729 ;; Wrapper around beginning-of-defun.
730 ;;
731 ;; NOTE: This function should contain the only explicit use of
732 ;; beginning-of-defun in CC Mode. Eventually something better than
733 ;; b-o-d will be available and this should be the only place the
734 ;; code needs to change. Everything else should use
735 ;; (c-beginning-of-defun-1)
736 ;;
737 ;; This is really a bit too large to be a macro but that isn't a
738 ;; problem as long as it only is used in one place in
739 ;; `c-parse-state'.
743 c-enable-xemacs-performance-kludge-p)
745 ;; XEmacs only. This can improve the performance of
746 ;; c-parse-state to between 3 and 60 times faster when
747 ;; braces are hung. It can also degrade performance by
748 ;; about as much when braces are not hung.
750 pos)
760 ;; unbalanced parenthesis, while invalid C code,
761 ;; shouldn't cause an infloop! See unbal.c
763 ;; Punt!
770 ))
772 ;; Emacs, which doesn't have buffer-syntactic-context-depth
775 ;; if defun-prompt-regexp is non-nil, b-o-d won't leave us at the
776 ;; open brace.
781 \f
782 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
783 ;; V i r t u a l S e m i c o l o n s
784 ;;
785 ;; In most CC Mode languages, statements are terminated explicitly by
786 ;; semicolons or closing braces. In some of the CC modes (currently AWK Mode
787 ;; and certain user-specified #define macros in C, C++, etc. (November 2008)),
788 ;; statements are (or can be) terminated by EOLs. Such a statement is said to
789 ;; be terminated by a "virtual semicolon" (VS). A statement terminated by an
790 ;; actual semicolon or brace is never considered to have a VS.
791 ;;
792 ;; The indentation engine (or whatever) tests for a VS at a specific position
793 ;; by invoking the macro `c-at-vsemi-p', which in its turn calls the mode
794 ;; specific function (if any) which is the value of the language variable
795 ;; `c-at-vsemi-p-fn'. This function should only use "low-level" features of
796 ;; CC Mode, i.e. features which won't trigger infinite recursion. ;-) The
797 ;; actual details of what constitutes a VS in a language are thus encapsulated
798 ;; in code specific to that language (e.g. cc-awk.el). `c-at-vsemi-p' returns
799 ;; non-nil if point (or the optional parameter POS) is at a VS, nil otherwise.
800 ;;
801 ;; The language specific function might well do extensive analysis of the
802 ;; source text, and may use a caching scheme to speed up repeated calls.
803 ;;
804 ;; The "virtual semicolon" lies just after the last non-ws token on the line.
805 ;; Like POINT, it is considered to lie between two characters. For example,
806 ;; at the place shown in the following AWK source line:
807 ;;
808 ;; kbyte = 1024 # 1000 if you're not picky
809 ;; ^
810 ;; |
811 ;; Virtual Semicolon
812 ;;
813 ;; In addition to `c-at-vsemi-p-fn', a mode may need to supply a function for
814 ;; `c-vsemi-status-unknown-p-fn'. The macro `c-vsemi-status-unknown-p' is a
815 ;; rather recondite kludge. It exists because the function
816 ;; `c-beginning-of-statement-1' sometimes tests for VSs as an optimization,
817 ;; but `c-at-vsemi-p' might well need to call `c-beginning-of-statement-1' in
818 ;; its calculations, thus potentially leading to infinite recursion.
819 ;;
820 ;; The macro `c-vsemi-status-unknown-p' resolves this problem; it may return
821 ;; non-nil at any time; returning nil is a guarantee that an immediate
822 ;; invocation of `c-at-vsemi-p' at point will NOT call
823 ;; `c-beginning-of-statement-1'. `c-vsemi-status-unknown-p' may not itself
824 ;; call `c-beginning-of-statement-1'.
825 ;;
826 ;; The macro `c-vsemi-status-unknown-p' will typically check the caching
827 ;; scheme used by the `c-at-vsemi-p-fn', hence the name - the status is
828 ;; "unknown" if there is no cache entry current for the line.
829 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
832 ;; Is there a virtual semicolon (not a real one or a }) at POS (defaults to
833 ;; point)? Always returns nil for languages which don't have Virtual
834 ;; semicolons.
835 ;; This macro might do hidden buffer changes.
840 ;; Return NIL only if it can be guaranteed that an immediate
841 ;; (c-at-vsemi-p) will NOT call c-beginning-of-statement-1. Otherwise,
842 ;; return non-nil. (See comments above). The function invoked by this
843 ;; macro MUST NOT UNDER ANY CIRCUMSTANCES itself call
844 ;; c-beginning-of-statement-1.
845 ;; Languages which don't have EOL terminated statements always return NIL
846 ;; (they _know_ there's no vsemi ;-).
849 \f
851 ;; Formats an error message for the echo area and dings, i.e. like
852 ;; `error' but doesn't abort.
858 ;; Temporarily switches to the specified syntax table in a failsafe
859 ;; way to execute code.
860 ;; Maintainers' note: If TABLE is `c++-template-syntax-table', DON'T call
861 ;; any forms inside this that call `c-parse-state'. !!!!
871 "Skip over any whitespace following point.
872 This function skips over horizontal and vertical whitespace and line
873 continuations."
877 ;; skip-syntax-* doesn't count \n as whitespace..
892 "Skip over any whitespace preceding point.
893 This function skips over horizontal and vertical whitespace and line
894 continuations."
898 ;; skip-syntax-* doesn't count \n as whitespace..
914 "Return non-nil if the current CC Mode major mode is MODE.
915 MODE is either a mode symbol or a list of mode symbols."
918 ;; Inside a `c-lang-defconst'.
932 \f
933 ;; Macros/functions to handle so-called "char properties", which are
934 ;; properties set on a single character and that never spread to any
935 ;; other characters.
938 ;; Constant used at compile time to decide whether or not to use
939 ;; XEmacs extents. Check all the extent functions we'll use since
940 ;; some packages might add compatibility aliases for some of them in
941 ;; Emacs.
956 ;; `c-put-char-property' is complex enough in XEmacs and Emacs < 21 to
957 ;; make it a function.
961 ;; XEmacs.
971 end-open t)))))))))
974 ;; In Emacs < 21 we have to mess with the `rear-nonsticky' property.
981 'rear-nonsticky
983 ;; This won't be used for anything.
988 ;; Put the given property with the given value on the character at
989 ;; POS and make it front and rear nonsticky, or start and end open
990 ;; in XEmacs vocabulary. If the character already has the given
991 ;; property then the value is replaced, and the behavior is
992 ;; undefined if that property has been put by some other function.
993 ;; PROPERTY is assumed to be constant.
994 ;;
995 ;; If there's a `text-property-default-nonsticky' variable (Emacs
996 ;; 21) then it's assumed that the property is present on it.
997 ;;
998 ;; This macro does a hidden buffer change.
1002 ;; XEmacs and Emacs < 21.
1004 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1005 ;; by `text-property-default-nonsticky'.
1010 ;; Get the value of the given property on the character at POS if
1011 ;; it's been put there by `c-put-char-property'. PROPERTY is
1012 ;; assumed to be constant.
1015 ;; XEmacs.
1018 ;; Emacs.
1021 ;; `c-clear-char-property' is complex enough in Emacs < 21 to make it
1022 ;; a function, since we have to mess with the `rear-nonsticky' property.
1032 'rear-nonsticky
1038 ;; Remove the given property on the character at POS if it's been put
1039 ;; there by `c-put-char-property'. PROPERTY is assumed to be
1040 ;; constant.
1041 ;;
1042 ;; This macro does a hidden buffer change.
1045 ;; XEmacs.
1049 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1050 ;; by `text-property-default-nonsticky'.
1055 ;; Emacs < 21.
1059 ;; Remove all the occurrences of the given property in the given
1060 ;; region that has been put with `c-put-char-property'. PROPERTY is
1061 ;; assumed to be constant.
1062 ;;
1063 ;; Note that this function does not clean up the property from the
1064 ;; lists of the `rear-nonsticky' properties in the region, if such
1065 ;; are used. Thus it should not be used for common properties like
1066 ;; `syntax-table'.
1067 ;;
1068 ;; This macro does hidden buffer changes.
1071 ;; XEmacs.
1075 ;; Emacs.
1079 "Search forward for a text-property PROPERTY having value VALUE.
1080 LIMIT bounds the search. The comparison is done with `equal'.
1082 Leave point just after the character, and set the match data on
1083 this character, and return point. If VALUE isn't found, Return
1084 nil; point is then left undefined."
1098 "Search backward for a text-property PROPERTY having value VALUE.
1099 LIMIT bounds the search. The comparison is done with `equal'.
1101 Leave point just before the character, set the match data on this
1102 character, and return point. If VALUE isn't found, Return nil;
1103 point is then left undefined."
1111 ;; XEmacs > 2005-01-25.
1112 'previous-single-char-property-change
1113 ;; Emacs and earlier XEmacs.
1122 "Remove all text-properties PROPERTY from the region (FROM, TO)
1123 which have the value VALUE, as tested by `equal'. These
1124 properties are assumed to be over individual characters, having
1125 been put there by c-put-char-property. POINT remains unchanged."
1137 ;; Do we have to do anything with stickiness here?
1141 "Remove all text-properties PROPERTY from the region [FROM, TO)
1142 which have the value VALUE, as tested by `equal'. These
1143 properties are assumed to be over individual characters, having
1144 been put there by c-put-char-property. POINT remains unchanged."
1146 ;; XEmacs
1152 ;; GNU Emacs
1154 \f
1155 ;; Macros to put overlays (Emacs) or extents (XEmacs) on buffer text.
1156 ;; For our purposes, these are characterized by being possible to
1157 ;; remove again without affecting the other text properties in the
1158 ;; buffer that got overridden when they were put.
1161 ;; Put an overlay/extent covering the given range in the current
1162 ;; buffer. It's currently undefined whether it's front/end sticky
1163 ;; or not. The overlay/extent object is returned.
1165 ;; Emacs.
1168 ol)
1169 ;; XEmacs.
1172 ext)))
1175 ;; Deletes an overlay/extent object previously retrieved using
1176 ;; `c-put-overlay'.
1178 ;; Emacs.
1180 ;; XEmacs.
1183 \f
1184 ;; Make edebug understand the macros.
1185 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1186 ; '(progn
1215 \f
1216 ;;; Functions.
1218 ;; Note: All these after the macros, to be on safe side in avoiding
1219 ;; bugs where macros are defined too late. These bugs often only show
1220 ;; when the files are compiled in a certain order within the same
1221 ;; session.
1224 ;; Replacement for end-of-defun that use c-beginning-of-defun-1.
1226 ;; Skip forward into the next defun block. Don't bother to avoid
1227 ;; comments, literals etc, since beginning-of-defun doesn't do that
1228 ;; anyway.
1237 ;; Mark the "<" character at POS as a template opener using the
1238 ;; `syntax-table' property either directly (XEmacs) or via a `category'
1239 ;; property (GNU Emacs).
1240 ;;
1241 ;; This function does a hidden buffer change. Note that we use
1242 ;; indirection through the `category' text property. This allows us to
1243 ;; toggle the property in all template brackets simultaneously and
1244 ;; cheaply. We use this, for instance, in `c-parse-state'.
1251 ;; Mark the ">" character at POS as an sexp list closer using the
1252 ;; `syntax-table' property either directly (XEmacs) or via a `category'
1253 ;; property (GNU Emacs).
1254 ;;
1255 ;; This function does a hidden buffer change. Note that we use
1256 ;; indirection through the `category' text property. This allows us to
1257 ;; toggle the property in all template brackets simultaneously and
1258 ;; cheaply. We use this, for instance, in `c-parse-state'.
1264 ;; Unmark the "<" or "<" character at POS as an sexp list opener using the
1265 ;; `syntax-table' property either directly or indirectly through a
1266 ;; `category' text property.
1267 ;;
1268 ;; This function does a hidden buffer change. Note that we try to use
1269 ;; indirection through the `category' text property. This allows us to
1270 ;; toggle the property in all template brackets simultaneously and
1271 ;; cheaply. We use this, for instance, in `c-parse-state'.
1275 ;; Suppress the syntactic effect of all marked < and > as parens. Note
1276 ;; that this effect is NOT buffer local. You should probably not use
1277 ;; this directly, but only through the macro
1278 ;; `c-with-<->-as-parens-suppressed'
1283 ;; Restore the syntactic effect of all marked <s and >s as parens. This
1284 ;; has no effect on unmarked <s and >s
1289 ;; Like progn, except that the paren property is suppressed on all
1290 ;; template brackets whilst they are running. This macro does a hidden
1291 ;; buffer change.
1298 ;;;;;;;;;;;;;;;
1301 ;; This is the value of the `category' text property placed on every #
1302 ;; which introduces a CPP construct and every EOL (or EOB, or character
1303 ;; preceding //, etc.) which terminates it. We can instantly "comment
1304 ;; out" all CPP constructs by giving `c-cpp-delimiter' a syntax-table
1305 ;; property '(14) (generic comment delimiter).
1307 ;; This macro does a hidden buffer change.
1313 ;; This macro does a hidden buffer change.
1320 ;; Render all preprocessor constructs syntactically commented out.
1323 ;; Restore the syntactic visibility of preprocessor constructs.
1327 ;; Execute FORMS... whilst the syntactic effect of all characters in
1328 ;; all CPP regions is suppressed. In particular, this is to suppress
1329 ;; the syntactic significance of parens/braces/brackets to functions
1330 ;; such as `scan-lists' and `parse-partial-sexp'.
1339 ;; Execute FORMS... whilst the syntactic effect of all characters in
1340 ;; every CPP region APART FROM THE ONE BETWEEN BEG and END is
1341 ;; suppressed.
1352 \f
1353 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1354 ;; The following macros are to be used only in `c-parse-state' and its
1355 ;; subroutines. Their main purpose is to simplify the handling of C++/Java
1356 ;; template delimiters and CPP macros. In GNU Emacs, this is done slickly by
1357 ;; the judicious use of 'category properties. These don't exist in XEmacs.
1358 ;;
1359 ;; Note: in the following macros, there is no special handling for parentheses
1360 ;; inside CPP constructs. That is because CPPs are always syntactically
1361 ;; balanced, thanks to `c-neutralize-CPP-line' in cc-mode.el.
1363 ;; Do a (scan-lists FROM 1 1). Any finishing position which either (i) is
1364 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1365 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1370 pos))
1373 ;; Do a (scan-lists FROM 1 -1). Any finishing position which either (i) is
1374 ;; determined by an angle bracket; or (ii) is inside a macro whose start
1375 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1381 pos))
1384 ;; Do a (scan-lists FROM -1 1). Any finishing position which either (i) is
1385 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1386 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1391 pos))
1394 ;; Do a (scan-lists FROM -1 -1). Any finishing position which either (i) is
1395 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1396 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1402 pos))
1420 oldstate)
1421 ;; Do a parse-partial-sexp using the supplied arguments, disregarding
1422 ;; template/generic delimiters < > and disregarding macros other than the
1423 ;; one at POINT-MACRO-START.
1424 ;;
1425 ;; NOTE that STOPBEFORE must be nil. TARGETDEPTH should be one less than
1426 ;; the depth in OLDSTATE. This function is thus a SPECIAL PURPOSE variation
1427 ;; on parse-partial-sexp, designed for calling from
1428 ;; `c-remove-stale-state-cache'.
1429 ;;
1430 ;; Any finishing position which is determined by an angle bracket delimiter
1431 ;; doesn't count as a finishing position.
1432 ;;
1433 ;; Note there is no special handling of CPP constructs here, since these are
1434 ;; always syntactically balanced (thanks to `c-neutralize-CPP-line').
1439 ;; We must have hit targetdepth.
1448 state))
1451 oldstate)
1457 \f
1461 "Are we looking at a character which isn't alphanumeric or space?"
1470 \f
1472 ;; return the element of ALIST that matches the first element found
1473 ;; in LIST. Uses assq.
1478 match))
1481 ;; first, find the first entry from LIST that is present in ALIST1,
1482 ;; then find the entry in ALIST2 for that entry.
1486 "Return the syntactic symbol in LANGELEM.
1490 form as used in `c-syntactic-element'."
1494 "Return the anchor position in LANGELEM, or nil if there is none.
1498 form as used in `c-syntactic-element'."
1504 "Return the column of the anchor position in LANGELEM.
1505 Also move the point to that position unless PRESERVE-POINT is non-nil.
1509 form as used in `c-syntactic-element'."
1521 "Return the secondary position in LANGELEM, or nil if there is none.
1524 in `c-syntactic-element'. It may also be a cons cell as passed in the
1525 first argument to lineup functions, but then the returned value always
1526 will be nil."
1530 ;; Do whatever is necessary to keep the region active in XEmacs.
1531 ;; This is not needed for Emacs.
1545 the corresponding symbol."
1551 c-buffer-is-cc-mode))
1556 the value of the variable with that name."
1560 "Return non-nil if position POS in the current buffer has any of the
1561 faces in the list FACES."
1568 pos-faces)
1572 ;; Return t if FACENAME is the name of a face. This method is
1573 ;; necessary since facep in XEmacs only returns t for the actual
1574 ;; face objects (while it's only their names that are used just
1575 ;; about anywhere else) without providing a predicate that tests
1576 ;; face names.
1580 "Like `concat' on LIST, but separate each element with SEPARATOR.
1581 Notably, null elements in LIST are ignored."
1585 "Make a regexp that matches all the strings the list.
1586 Duplicates and nil elements in the list are removed. The
1587 resulting regexp may contain zero or more submatch expressions.
1589 If ADORN is t there will be at least one submatch and the first
1590 surrounds the matched alternative, and the regexp will also not match
1591 a prefix of any identifier. Adorned regexps cannot be appended. The
1592 language variable `c-nonsymbol-key' is used to make the adornment.
1594 A value 'appendable for ADORN is like above, but all alternatives in
1596 instead, so that the regexp remains appendable. Note that this
1597 variant doesn't always guarantee that an identifier prefix isn't
1598 matched since the symbol constituent '_' is normally considered a
1601 The optional MODE specifies the language to get `c-nonsymbol-key' from
1602 when it's needed. The default is the current language taken from
1603 `c-buffer-is-cc-mode'."
1610 ;; This is kludgy but it works: Search for a string that
1611 ;; doesn't occur in any word in LIST. Append it to all
1612 ;; the alternatives where we want to add \>. Run through
1613 ;; `regexp-opt' and then replace it with \>.
1617 pos list)
1621 nil)
1622 t))
1624 found))
1638 ;; Emacs 20 and XEmacs (all versions so far) has a buggy
1639 ;; regexp-opt that doesn't always cope with strings containing
1640 ;; newlines. This kludge doesn't handle shy parens correctly
1641 ;; so we can't advice regexp-opt directly with it.
1665 ;; Add our own grouping parenthesis around re instead of
1666 ;; passing adorn to `regexp-opt', since in XEmacs it makes the
1667 ;; top level grouping "shy".
1676 re)))
1678 ;; Produce a regexp that matches nothing.
1686 "Make a character alternative string from the list of characters CHARS.
1687 The returned string is of the type that can be used with
1688 `skip-chars-forward' and `skip-chars-backward'. If INVERTED is
1689 non-nil, a caret is prepended to invert the set."
1690 ;; This function ought to be in the elisp core somewhere.
1696 ;; Quoting necessary (this method only works in the skip
1697 ;; functions).
1700 ;; Check for range.
1708 str))
1710 ;; Leftovers from (X)Emacs 19 compatibility.
1714 \f
1715 ;; Figure out what features this Emacs has
1725 ;; I've no idea what this actually is, but it's legacy. /mast
1728 ;; XEmacs uses 8-bit modify-syntax-entry flags.
1729 ;; Emacs uses a 1-bit flag. We will have to set up our
1730 ;; syntax tables differently to handle this.
1732 entry)
1735 ;; Emacs
1738 ;; In Emacs, table entries are cons cells
1740 ;; XEmacs
1743 ;; incompatible
1748 list)))
1750 ;; Check whether beginning/end-of-defun call
1751 ;; beginning/end-of-defun-function nicely, passing through the
1752 ;; argument and respecting the return code.
1772 ;; Record whether the `category' text property works.
1776 parse-sexp-lookup-properties
1777 parse-sexp-ignore-comments
1782 ;; For some reason we have to set some of these after the
1783 ;; buffer has been made current. (Specifically,
1784 ;; `parse-sexp-ignore-comments' in Emacs 21.)
1786 parse-sexp-ignore-comments t
1787 lookup-syntax-properties t)
1789 ;; Find out if the `syntax-table' text property works.
1800 "CC Mode is incompatible with this version of Emacs - "
1801 "support for the `syntax-table' text property "
1804 ;; Find out if "\\s!" (generic comment delimiters) work.
1810 ;; Find out if "\\s|" (generic string delimiters) work.
1816 ;; See if POSIX char classes work.
1818 ;; All versions of Emacs 21 so far haven't fixed
1819 ;; char classes in `skip-chars-forward' and
1820 ;; `skip-chars-backward'.
1829 ;; See if `open-paren-in-column-0-is-defun-start' exists and
1830 ;; isn't buggy (Emacs >= 21.4).
1838 ;; XEmacs. Afaik this is currently an Emacs-only
1839 ;; feature, but it's good to be prepared.
1843 ;; Emacs
1856 ;; See if `parse-partial-sexp' returns the eighth element.
1862 "CC Mode is incompatible with this version of Emacs - "
1865 ;;(message "c-emacs-features: %S" list)
1866 list)
1867 "A list of certain features in the (X)Emacs you are using.
1868 There are many flavors of Emacs out there, each with different
1869 features supporting those needed by CC Mode. The following values
1870 might be present:
1872 '8-bit 8 bit syntax entry flags (XEmacs style).
1873 '1-bit 1 bit syntax entry flags (Emacs style).
1874 'argumentative-bod-function beginning-of-defun and end-of-defun pass
1875 ARG through to beginning/end-of-defun-function.
1876 'syntax-properties It works to override the syntax for specific characters
1877 in the buffer with the 'syntax-table property. It's
1878 always set - CC Mode no longer works in emacsen without
1879 this feature.
1880 'category-properties Syntax routines can add a level of indirection to text
1881 properties using the 'category property.
1882 'gen-comment-delim Generic comment delimiters work
1883 (i.e. the syntax class `!').
1884 'gen-string-delim Generic string delimiters work
1885 (i.e. the syntax class `|').
1886 'pps-extended-state `parse-partial-sexp' returns a list with at least 10
1887 elements, i.e. it contains the position of the start of
1888 the last comment or string. It's always set - CC Mode
1889 no longer works in emacsen without this feature.
1890 'posix-char-classes The regexp engine understands POSIX character classes.
1891 'col-0-paren It's possible to turn off the ad-hoc rule that a paren
1892 in column zero is the start of a defun.
1893 'infodock This is Infodock (based on XEmacs).
1897 \f
1898 ;;; Some helper constants.
1900 ;; If the regexp engine supports POSIX char classes then we can use
1901 ;; them to handle extended charsets correctly.
1915 \f
1916 ;;; System for handling language dependent constants.
1918 ;; This is used to set various language dependent data in a flexible
1919 ;; way: Language constants can be built from the values of other
1920 ;; language constants, also those for other languages. They can also
1921 ;; process the values of other language constants uniformly across all
1922 ;; the languages. E.g. one language constant can list all the type
1923 ;; keywords in each language, and another can build a regexp for each
1924 ;; language from those lists without code duplication.
1925 ;;
1926 ;; Language constants are defined with `c-lang-defconst', and their
1927 ;; value forms (referred to as source definitions) are evaluated only
1928 ;; on demand when requested for a particular language with
1929 ;; `c-lang-const'. It's therefore possible to refer to the values of
1930 ;; constants defined later in the file, or in another file, just as
1931 ;; long as all the relevant `c-lang-defconst' have been loaded when
1932 ;; `c-lang-const' is actually evaluated from somewhere else.
1933 ;;
1934 ;; `c-lang-const' forms are also evaluated at compile time and
1935 ;; replaced with the values they produce. Thus there's no overhead
1936 ;; for this system when compiled code is used - only the values
1937 ;; actually used in the code are present, and the file(s) containing
1938 ;; the `c-lang-defconst' forms don't need to be loaded at all then.
1939 ;; There are however safeguards to make sure that they can be loaded
1940 ;; to get the source definitions for the values if there's a mismatch
1941 ;; in compiled versions, or if `c-lang-const' is used uncompiled.
1942 ;;
1943 ;; Note that the source definitions in a `c-lang-defconst' form are
1944 ;; compiled into the .elc file where it stands; there's no need to
1945 ;; load the source file to get it.
1946 ;;
1947 ;; See cc-langs.el for more details about how this system is deployed
1948 ;; in CC Mode, and how the associated language variable system
1949 ;; (`c-lang-defvar') works. That file also contains a lot of
1950 ;; examples.
1953 "Declare a new language in the language dependent variable system.
1954 This is intended to be used by modes that inherit CC Mode to add new
1955 languages. It should be used at the top level before any calls to
1956 `c-lang-defconst'. MODE is the mode name symbol for the new language,
1957 and BASE-MODE is the mode name symbol for the language in CC Mode that
1958 is to be the template for the new mode.
1960 The exact effect of BASE-MODE is to make all language constants that
1961 haven't got a setting in the new language fall back to their values in
1962 BASE-MODE. It does not have any effect outside the language constant
1963 system."
1972 ;; Obarray used as a cache to keep track of the language constants.
1973 ;; The constants stored are those defined by `c-lang-defconst' and the values
1974 ;; computed by `c-lang-const'. It's mostly used at compile time but it's not
1975 ;; stored in compiled files.
1977 ;; The obarray contains all the language constants as symbols. The
1978 ;; value cells hold the evaluated values as alists where each car is
1979 ;; the mode name symbol and the corresponding cdr is the evaluated
1980 ;; value in that mode. The property lists hold the source definitions
1981 ;; and other miscellaneous data. The obarray might also contain
1982 ;; various other symbols, but those don't have any variable bindings.
1986 ;; Ugly hack to pull in the definition of `cc-bytecomp-compiling-or-loading`
1987 ;; from cc-bytecomp to make it available at loadtime. This is the same
1988 ;; mechanism used in cc-mode.el for `c-populate-syntax-table'.
1995 ;; Return the base name of the current file.
2007 "Can be used inside a VAL in `c-lang-defconst' to evaluate FORM
2008 immediately, i.e. at the same time as the `c-lang-defconst' form
2009 itself is evaluated."
2010 ;; Evaluate at macro expansion time, i.e. in the
2011 ;; `c--macroexpand-all' inside `c-lang-defconst'.
2015 "Set the language specific values of the language constant NAME.
2016 The second argument can optionally be a docstring. The rest of the
2017 arguments are one or more repetitions of LANG VAL where LANG specifies
2018 the language(s) that VAL applies to. LANG is the name of the
2020 of such language names, or `t' for all languages. VAL is a form to
2021 evaluate to get the value.
2023 If LANG isn't `t' or one of the core languages in CC Mode, it must
2024 have been declared with `c-add-language'.
2026 Neither NAME, LANG nor VAL are evaluated directly - they should not be
2027 quoted. `c-lang-defconst-eval-immediately' can however be used inside
2028 VAL to evaluate parts of it directly.
2030 When VAL is evaluated for some language, that language is temporarily
2031 made current so that `c-lang-const' without an explicit language can
2032 be used inside VAL to refer to the value of a language constant in the
2033 same language. That is particularly useful if LANG is `t'.
2035 VAL is not evaluated right away but rather when the value is requested
2036 with `c-lang-const'. Thus it's possible to use `c-lang-const' inside
2037 VAL to refer to language constants that haven't been defined yet.
2038 However, if the definition of a language constant is in another file
2039 then that file must be loaded \(at compile time) before it's safe to
2040 reference the constant.
2042 The assignments in ARGS are processed in sequence like `setq', so
2043 \(c-lang-const NAME) may be used inside a VAL to refer to the last
2044 assigned value to this language constant, or a value that it has
2045 gotten in another earlier loaded file.
2047 To work well with repeated loads and interactive reevaluation, only
2048 one `c-lang-defconst' for each NAME is permitted per file. If there
2049 already is one it will be completely replaced; the value in the
2050 earlier definition will not affect `c-lang-const' on the same
2051 constant. A file is identified by its base name."
2054 ;; Make `c-lang-const' expand to a straightforward call to
2055 ;; `c-get-lang-constant' in `c--macroexpand-all' below.
2056 ;;
2057 ;; (The default behavior, i.e. to expand to a call inside
2058 ;; `eval-when-compile' should be equivalent, since that macro
2059 ;; should only expand to its content if it's used inside a
2060 ;; form that's already evaluated at compile time. It's
2061 ;; however necessary to use our cover macro
2062 ;; `cc-eval-when-compile' due to bugs in `eval-when-compile',
2063 ;; and it expands to a bulkier form that in this case only is
2064 ;; unnecessary garbage that we don't want to store in the
2065 ;; language constant source definitions.)
2071 bindings
2072 pre-files)
2078 ;; The docstring is hardly used anywhere since there's no normal
2079 ;; symbol to attach it to. It's primarily for getting the right
2080 ;; format in the source.
2087 ;; Rework ARGS to an association list to make it easier to handle.
2088 ;; It's reversed at the same time to make it easier to implement
2089 ;; the demand-driven (i.e. reversed) evaluation in `c-lang-const'.
2106 val)
2113 ;; Emacs has a weird bug where it seems to fail to read
2114 ;; backquote lists from byte compiled files correctly (,@
2115 ;; forms, to be specific), so make sure the bindings in the
2116 ;; expansion below don't contain any backquote stuff.
2117 ;; (XEmacs handles it correctly and doesn't need this for that
2118 ;; reason, but we also use this expansion handle
2119 ;; `c-lang-defconst-eval-immediately' and to register
2120 ;; dependencies on the `c-lang-const's in VAL.)
2126 ;; Compile in the other files that have provided source
2127 ;; definitions for this symbol, to make sure the order in the
2128 ;; `source' property is correct even when files are loaded out of
2129 ;; order.
2132 ;; This can happen when the source file (e.g. cc-langs.el) is first
2133 ;; loaded as source, setting a 'source property entry, and then itself
2134 ;; being compiled.
2136 ;; Reverse to get the right load order.
2144 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
2145 ; '
2150 ;; Used by `c-lang-defconst'.
2159 ;;(when (cdr-safe elem)
2160 ;; (message "Language constant %s redefined in %S" name file))
2162 ;; Note that the order in the source alist is relevant. Like how
2163 ;; `c-lang-defconst' reverses the bindings, this reverses the
2164 ;; order between files so that the last to evaluate comes first.
2174 ;; Bind the symbol as a variable, or clear any earlier evaluated
2175 ;; value it has.
2178 ;; Clear the evaluated values that depend on this source.
2181 ptr)
2194 name))
2197 "Get the mode specific value of the language constant NAME in language LANG.
2198 LANG is the name of the language, i.e. the mode name without the
2200 `c-lang-defvar', LANG may be left out to refer to the current
2201 language. NAME and LANG are not evaluated so they should not be
2202 quoted."
2214 lang))
2217 ;; No need to find out the source file(s) when we evaluate
2218 ;; immediately since all the info is already there in the
2219 ;; `source' property.
2225 ;; Get the source file(s) that must be loaded to get the value
2226 ;; of the constant. If the symbol isn't defined yet we assume
2227 ;; that its definition will come later in this file, and thus
2228 ;; are no file dependencies needed.
2230 ;; Reverse to get the right load order.
2234 nil ; Exclude our own file.
2237 ;; Make some effort to do a compact call to
2238 ;; `c-get-lang-constant' since it will be compiled in.
2248 ;; Either a straight call is requested in the context, or
2249 ;; we're in an "uncontrolled" context and got no language,
2250 ;; or we're not being byte compiled so the compile time
2251 ;; stuff below is unnecessary.
2254 ;; Being compiled. If the loading and compiling version is
2255 ;; the same we use a value that is evaluated at compile time,
2256 ;; otherwise it's evaluated at runtime.
2263 "Alist of constants in the process of being evaluated.
2264 The `cdr' of each entry indicates how far we've looked in the list
2265 of definitions, so that the def for var FOO in c-mode can be defined in
2266 terms of the def for that same var FOO (which will then rely on the
2272 ;; Used by `c-lang-const'.
2280 elem
2284 ;; Record the dependencies between this symbol and the one we're
2285 ;; being evaluated in.
2290 ;; Make sure the source files have entries on the `source'
2291 ;; property so that loading will take place when necessary.
2296 ;; Might pull in more definitions which affect the value. The
2297 ;; clearing of dependent values etc is done when the
2298 ;; definition is encountered during the load; this is just to
2299 ;; jump past the check for a cached value below.
2307 ;; Check if an evaluation of this symbol is already underway.
2308 ;; In that case we just continue with the "assignment" before
2309 ;; the one currently being evaluated, thereby creating the
2310 ;; illusion if a `setq'-like sequence of assignments.
2315 ;; Append `c-lang-constants-under-evaluation' even if an
2316 ;; earlier entry is found. It's only necessary to get
2317 ;; the recording of dependencies above correct.
2321 value
2322 ;; Make sure the recursion limits aren't very low
2323 ;; since the `c-lang-const' dependencies can go deep.
2330 ;; First try the original mode but don't accept an
2331 ;; entry matching all languages since the fallback
2332 ;; mode might have an explicit entry before that.
2335 c-lang--novalue)
2336 ;; Try again with the fallback mode from the
2337 ;; original position. Note that
2338 ;; `c-buffer-is-cc-mode' still is the real mode if
2339 ;; language parameterization takes place.
2342 fallback t name))
2343 c-lang--novalue)))
2344 ;; A simple lookup with no fallback mode.
2347 c-lang--novalue))
2349 "`%s' got no (prior) value in %S (might be a cyclic reference)"
2350 name mode))
2355 ;; Print a message to aid in locating the error. We don't
2356 ;; print the error itself since that will be done later by
2357 ;; some caller higher up.
2359 sym mode)
2364 value))))
2367 ;; Find the first assignment entry that applies to MODE at or after
2368 ;; SOURCE-POS. If MATCH-ANY-LANG is non-nil, entries with `t' as
2369 ;; the language list are considered to match, otherwise they don't.
2370 ;; On return SOURCE-POS is updated to point to the next assignment
2371 ;; after the returned one. If no assignment is found,
2372 ;; `c-lang--novalue' is returned as a magic value.
2373 ;;
2374 ;; SOURCE-POS is a vector that points out a specific assignment in
2375 ;; the double alist that's used in the `source' property. The first
2376 ;; element is the position in the top alist which is indexed with
2377 ;; the source files, and the second element is the position in the
2378 ;; nested bindings alist.
2379 ;;
2380 ;; NAME is only used for error messages.
2385 assignment)
2388 t
2389 ;; Handled the last assignment from one file, begin on the
2390 ;; next. Due to the check in `c-lang-defconst', we know
2391 ;; there's at least one.
2396 ;; The file containing the source definitions has not
2397 ;; been loaded.
2400 ;;(message (concat "Loading %s to get the source "
2401 ;; "value for language constant %s")
2402 ;; file name)
2406 ;; The load didn't fill in the source for the
2407 ;; constant as expected. The situation is
2408 ;; probably that a derived mode was written for
2409 ;; and compiled with another version of CC Mode,
2410 ;; and the requested constant isn't in the
2411 ;; currently loaded one. Put in a dummy
2412 ;; assignment that matches no language.
2417 t))
2425 match-any-lang)
2428 c-lang--novalue)))
2431 ;; `c-major-mode-is' expands to a call to this function inside
2432 ;; `c-lang-defconst'. Here we also match the mode(s) against any
2433 ;; fallback modes for the one in `c-buffer-is-cc-mode', so that
2434 ;; e.g. (c-major-mode-is 'c++-mode) is true in a derived language
2435 ;; that has c++-mode as base mode.
2442 nil)
2444 match))
2446 \f
2449 ;;; Local Variables:
2450 ;;; indent-tabs-mode: t
2451 ;;; tab-width: 8
2452 ;;; End:
2453 ;;; cc-defs.el ends here