| blob | 0422ca0b02896be72ec3721fc2c4931d419d3562 |
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)))
50 ;; XEmacs
53 ;; Emacs >= 24.3
56 ;; Emacs <= 24.2
57 nil))))
60 ; was (cc-external-require 'cl). ACM 2005/11/29.
61 ; Changed from (eval-when-compile (require 'cl)) back to
62 ; cc-external-require, 2015-08-12.
65 ;; Silence the compiler.
75 \f
76 ;; cc-fix.el contains compatibility macros that should be used if
77 ;; needed.
84 ; to make the call to f-l-c-k throw an error.
92 ;; The above takes care of the delayed loading, but this is necessary
93 ;; to ensure correct byte compilation.
101 font-lock-keywords)))
104 ;; XEmacs 21.4 doesn't have `delete-dups'.
109 \f
110 ;;; Variables also used at compile time.
116 ;; A little more compact and faster in comparisons.
119 "Non-nil for all buffers with a major mode derived from CC Mode.
120 Otherwise, this variable is nil. I.e. this variable is non-nil for
121 `c-mode', `c++-mode', `objc-mode', `java-mode', `idl-mode',
122 `pike-mode', `awk-mode', and any other non-CC Mode mode that calls
123 `c-initialize-cc-mode'. The value is the mode symbol itself
124 \(i.e. `c-mode' etc) of the original CC Mode mode, or just t if it's
128 ;; Have to make `c-buffer-is-cc-mode' permanently local so that it
129 ;; survives the initialization of the derived mode.
132 \f
133 ;; The following is used below during compilation.
138 "Like `progn', but evaluates the body at compile time.
139 The result of the body appears to the compiler as a quoted constant.
141 This variant works around bugs in `eval-when-compile' in various
142 \(X)Emacs versions. See cc-defs.el for details."
145 ;; XEmacs 21.4.6 has a bug in `eval-when-compile' in that it
146 ;; evaluates its body at macro expansion time if it's nested
147 ;; inside another `eval-when-compile'. So we use a dynamically
148 ;; bound variable to avoid nesting them.
152 ;; In all (X)Emacsen so far, `eval-when-compile' byte compiles
153 ;; its contents before evaluating it. That can cause forms to
154 ;; be compiled in situations they aren't intended to be
155 ;; compiled.
156 ;;
157 ;; Example: It's not possible to defsubst a primitive, e.g. the
158 ;; following will produce an error (in any emacs flavor), since
159 ;; `nthcdr' is a primitive function that's handled specially by
160 ;; the byte compiler and thus can't be redefined:
161 ;;
162 ;; (defsubst nthcdr (val) val)
163 ;;
164 ;; `defsubst', like `defmacro', needs to be evaluated at
165 ;; compile time, so this will produce an error during byte
166 ;; compilation.
167 ;;
168 ;; CC Mode occasionally needs to do things like this for
169 ;; cross-emacs compatibility. It therefore uses the following
170 ;; to conditionally do a `defsubst':
171 ;;
172 ;; (eval-when-compile
173 ;; (if (not (fboundp 'foo))
174 ;; (defsubst foo ...)))
175 ;;
176 ;; But `eval-when-compile' byte compiles its contents and
177 ;; _then_ evaluates it (in all current emacs versions, up to
178 ;; and including Emacs 20.6 and XEmacs 21.1 as of this
179 ;; writing). So this will still produce an error, since the
180 ;; byte compiler will get to the defsubst anyway. That's
181 ;; arguably a bug because the point with `eval-when-compile' is
182 ;; that it should evaluate rather than compile its contents.
183 ;;
184 ;; We get around it by expanding the body to a quoted
185 ;; constant that we eval. That otoh introduce a problem in
186 ;; that a returned lambda expression doesn't get byte
187 ;; compiled (even if `function' is used).
192 \f
193 ;;; Macros.
195 ;; CC Mode equivalent of `mapcan' which bridges the difference
196 ;; between the host [X]Emacsen."
197 ;; The motivation for this macro is to avoid the irritating message
198 ;; "function `mapcan' from cl package called at runtime" produced by Emacs.
205 ;; Emacs <= 24.2. It would be nice to be able to distinguish between
206 ;; compile-time and run-time use here.
210 ;; Macro to smooth out the renaming of `set-difference' in Emacs 24.3.
216 ;; Macro to smooth out the renaming of `intersection' in Emacs 24.3.
223 ;; Macro to smooth out the renaming of `cl-macroexpand-all' in Emacs 24.3.
229 ;; Macro to smooth out the renaming of `delete-duplicates' in Emacs 24.3.
235 "Return the value of certain commonly referenced POSITIONs relative to POINT.
236 The current point is used if POINT isn't specified. POSITION can be
237 one of the following symbols:
239 `bol' -- beginning of line
240 `eol' -- end of line
241 `bod' -- beginning of defun
242 `eod' -- end of defun
243 `boi' -- beginning of indentation
244 `ionl' -- indentation of next line
245 `iopl' -- indentation of previous line
246 `bonl' -- beginning of next line
247 `eonl' -- end of next line
248 `bopl' -- beginning of previous line
249 `eopl' -- end of previous line
250 `bosws' -- beginning of syntactic whitespace
251 `eosws' -- end of syntactic whitespace
253 If the referenced position doesn't exist, the closest accessible point
254 to it is returned. This function does not modify the point or the mark."
356 ;; The bulk of this should perhaps be in a function to avoid large
357 ;; expansions, but this case is not used anywhere in CC Mode (and
358 ;; probably not anywhere else either) so we only have it to be on
359 ;; the safe side.
390 ;; Constant to decide at compilation time whether to use category
391 ;; properties. Currently (2010-03) they're available only on GNU Emacs.
409 ;; See the doc string for either of the defuns expanded to.
412 ;; XEmacs >= 2005-01-25
414 ;; Emacs and earlier XEmacs
418 ;; Return t when the region is active. The determination of region
419 ;; activeness is different in both Emacs and XEmacs.
421 ;; XEmacs.
423 ;; Old Emacs.
427 ;; Activate the region if ACTIVE is non-nil, deactivate it
428 ;; otherwise. Covers the differences between Emacs and XEmacs.
430 ;; XEmacs.
434 ;; Emacs.
438 "Delete the text between START and END and return it."
440 ;; Emacs 21.1 and later
442 ;; XEmacs and Emacs 20.x
448 ;; safely execute BODY, return nil if an error occurred
455 ;; In Emacs, a character is an integer. In XEmacs, a character is a
456 ;; type distinct from an integer. Sometimes we need to convert integers to
457 ;; characters. `c-int-to-char' makes this conversion, if necessary.
460 integer))
463 ;; The last character just typed. Note that `last-command-event' exists in
464 ;; both Emacs and XEmacs, but with confusingly different meanings.
466 'last-command-char
470 ;; Get the regular expression `sentence-end'.
472 ;; Emacs 22:
474 ;; Emacs <22 + XEmacs
478 ;; Get the default value of the variable sentence end.
480 ;; Emacs 22:
482 ;; Emacs <22 + XEmacs
485 ;; The following is essentially `save-buffer-state' from lazy-lock.el.
486 ;; It ought to be a standard macro.
488 "Bind variables according to VARLIST (in `let*' style) and eval BODY,
489 then restore the buffer state under the assumption that no significant
490 modification has been made in BODY. A change is considered
491 significant if it affects the buffer text in any way that isn't
492 completely restored again. Changes in text properties like `face' or
493 `syntax-table' are considered insignificant. This macro allows text
494 properties to be changed, even in a read-only buffer.
496 This macro should be placed around all calculations which set
498 known to be writable. That way, these text properties remain set
499 even if the user undoes the command which set them.
502 changes \(like adding a newline to calculate a text-property then
503 deleting it again\), so that the user never sees them on his
504 `buffer-undo-list'. See also `c-tentative-buffer-changes'.
506 However, any user-visible changes to the buffer \(like auto-newlines\)
507 must not be within a `c-save-buffer-state', since the user then
508 wouldn't be able to undo them.
510 The return value is the value of the last form in BODY."
513 before-change-functions after-change-functions
514 deactivate-mark
515 buffer-file-name buffer-file-truename ; Prevent primitives checking
516 ; for file modification
526 "Eval BODY and optionally restore the buffer contents to the state it
527 was in before BODY. Any changes are kept if the last form in BODY
528 returns non-nil. Otherwise it's undone using the undo facility, and
529 various other buffer state that might be affected by the changes is
530 restored. That includes the current buffer, point, mark, mark
531 activation \(similar to `save-excursion'), and the modified state.
532 The state is also restored if BODY exits nonlocally.
534 If BODY makes a change that unconditionally is undone then wrap this
535 macro inside `c-save-buffer-state'. That way the change can be done
536 even when the buffer is read-only, and without interference from
537 various buffer change hooks."
539 -tnt-chng-state)
541 ;; Insert an undo boundary for use with `undo-more'. We
542 ;; don't use `undo-boundary' since it doesn't insert one
543 ;; unconditionally.
551 ;; Used internally in `c-tentative-buffer-changes'.
554 ;; No need to use markers for the point and mark; if the
555 ;; undo got out of synch we're hosed anyway.
562 ;; Used internally in `c-tentative-buffer-changes'.
566 ;; No change was done after all.
570 ;; Find and remove the undo boundary.
576 ;; `primitive-undo' will remove the boundary.
581 saved-undo-list))))
593 "Forward skip over syntactic whitespace.
594 Syntactic whitespace is defined as whitespace characters, comments,
595 and preprocessor directives. However if point starts inside a comment
596 or preprocessor directive, the content of it is not treated as
597 whitespace.
599 LIMIT sets an upper limit of the forward movement, if specified. If
600 LIMIT or the end of the buffer is reached inside a comment or
601 preprocessor directive, the point will be left there.
603 Note that this function might do hidden buffer changes. See the
604 comment at the start of cc-engine.el for more info."
612 "Backward skip over syntactic whitespace.
613 Syntactic whitespace is defined as whitespace characters, comments,
614 and preprocessor directives. However if point starts inside a comment
615 or preprocessor directive, the content of it is not treated as
616 whitespace.
618 LIMIT sets a lower limit of the backward movement, if specified. If
619 LIMIT is reached inside a line comment or preprocessor directive then
620 the point is moved into it past the whitespace at the end.
622 Note that this function might do hidden buffer changes. See the
623 comment at the start of cc-engine.el for more info."
631 "Move forward across COUNT balanced expressions.
632 A negative COUNT means move backward. Signal an error if the move
633 fails for any reason.
635 This is like `forward-sexp' except that it isn't interactive and does
636 not do any user friendly adjustments of the point and that it isn't
637 susceptible to user configurations such as disabling of signals in
638 certain situations."
643 "See `c-forward-sexp' and reverse directions."
648 "Like `scan-lists' but returns nil instead of signaling errors
649 for unbalanced parens.
651 A limit for the search may be given. FROM is assumed to be on the
652 right side of it."
666 res)))
668 \f
669 ;; Wrappers for common scan-lists cases, mainly because it's almost
670 ;; impossible to get a feel for how that function works.
673 "Move backward across one balanced group of parentheses.
675 Return POINT when we succeed, NIL when we fail. In the latter case, leave
676 point unmoved."
679 endpos)))
682 "Move backward across one balanced group of parentheses.
684 Return POINT when we succeed, NIL when we fail. In the latter case, leave
685 point unmoved."
688 endpos)))
691 "Return the first position after the list sexp containing POS,
692 or nil if no such position exists. The point is used if POS is left out.
694 A limit for the search may be given. The start position is assumed to
695 be before it."
699 "Return the position of the start of the list sexp containing POS,
700 or nil if no such position exists. The point is used if POS is left out.
702 A limit for the search may be given. The start position is assumed to
703 be after it."
707 "Return the first position inside the first list sexp after POS,
708 or nil if no such position exists. The point is used if POS is left out.
710 A limit for the search may be given. The start position is assumed to
711 be before it."
715 "Return the last position inside the last list sexp before POS,
716 or nil if no such position exists. The point is used if POS is left out.
718 A limit for the search may be given. The start position is assumed to
719 be after it."
723 "Move the point to the first position after the list sexp containing POS,
724 or containing the point if POS is left out. Return t if such a
725 position exists, otherwise nil is returned and the point isn't moved.
727 A limit for the search may be given. The start position is assumed to
728 be before it."
734 res)))
737 "Move the point to the position of the start of the list sexp containing POS,
738 or containing the point if POS is left out. Return t if such a
739 position exists, otherwise nil is returned and the point isn't moved.
741 A limit for the search may be given. The start position is assumed to
742 be after it."
748 res)))
751 "Move the point to the first position inside the first list sexp after POS,
752 or before the point if POS is left out. Return t if such a position
753 exists, otherwise nil is returned and the point isn't moved.
755 A limit for the search may be given. The start position is assumed to
756 be before it."
762 res)))
765 "Move the point to the last position inside the last list sexp before POS,
766 or before the point if POS is left out. Return t if such a position
767 exists, otherwise nil is returned and the point isn't moved.
769 A limit for the search may be given. The start position is assumed to
770 be after it."
776 res)))
778 \f
780 ;; Wrapper around beginning-of-defun.
781 ;;
782 ;; NOTE: This function should contain the only explicit use of
783 ;; beginning-of-defun in CC Mode. Eventually something better than
784 ;; b-o-d will be available and this should be the only place the
785 ;; code needs to change. Everything else should use
786 ;; (c-beginning-of-defun-1)
787 ;;
788 ;; This is really a bit too large to be a macro but that isn't a
789 ;; problem as long as it only is used in one place in
790 ;; `c-parse-state'.
794 c-enable-xemacs-performance-kludge-p)
796 ;; XEmacs only. This can improve the performance of
797 ;; c-parse-state to between 3 and 60 times faster when
798 ;; braces are hung. It can also degrade performance by
799 ;; about as much when braces are not hung.
801 pos)
811 ;; unbalanced parenthesis, while invalid C code,
812 ;; shouldn't cause an infloop! See unbal.c
814 ;; Punt!
821 ))
823 ;; Emacs, which doesn't have buffer-syntactic-context-depth
826 ;; if defun-prompt-regexp is non-nil, b-o-d won't leave us at the
827 ;; open brace.
832 \f
833 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
834 ;; V i r t u a l S e m i c o l o n s
835 ;;
836 ;; In most CC Mode languages, statements are terminated explicitly by
837 ;; semicolons or closing braces. In some of the CC modes (currently AWK Mode
838 ;; and certain user-specified #define macros in C, C++, etc. (November 2008)),
839 ;; statements are (or can be) terminated by EOLs. Such a statement is said to
840 ;; be terminated by a "virtual semicolon" (VS). A statement terminated by an
841 ;; actual semicolon or brace is never considered to have a VS.
842 ;;
843 ;; The indentation engine (or whatever) tests for a VS at a specific position
844 ;; by invoking the macro `c-at-vsemi-p', which in its turn calls the mode
845 ;; specific function (if any) which is the value of the language variable
846 ;; `c-at-vsemi-p-fn'. This function should only use "low-level" features of
847 ;; CC Mode, i.e. features which won't trigger infinite recursion. ;-) The
848 ;; actual details of what constitutes a VS in a language are thus encapsulated
849 ;; in code specific to that language (e.g. cc-awk.el). `c-at-vsemi-p' returns
850 ;; non-nil if point (or the optional parameter POS) is at a VS, nil otherwise.
851 ;;
852 ;; The language specific function might well do extensive analysis of the
853 ;; source text, and may use a caching scheme to speed up repeated calls.
854 ;;
855 ;; The "virtual semicolon" lies just after the last non-ws token on the line.
856 ;; Like POINT, it is considered to lie between two characters. For example,
857 ;; at the place shown in the following AWK source line:
858 ;;
859 ;; kbyte = 1024 # 1000 if you're not picky
860 ;; ^
861 ;; |
862 ;; Virtual Semicolon
863 ;;
864 ;; In addition to `c-at-vsemi-p-fn', a mode may need to supply a function for
865 ;; `c-vsemi-status-unknown-p-fn'. The macro `c-vsemi-status-unknown-p' is a
866 ;; rather recondite kludge. It exists because the function
867 ;; `c-beginning-of-statement-1' sometimes tests for VSs as an optimization,
868 ;; but `c-at-vsemi-p' might well need to call `c-beginning-of-statement-1' in
869 ;; its calculations, thus potentially leading to infinite recursion.
870 ;;
871 ;; The macro `c-vsemi-status-unknown-p' resolves this problem; it may return
872 ;; non-nil at any time; returning nil is a guarantee that an immediate
873 ;; invocation of `c-at-vsemi-p' at point will NOT call
874 ;; `c-beginning-of-statement-1'. `c-vsemi-status-unknown-p' may not itself
875 ;; call `c-beginning-of-statement-1'.
876 ;;
877 ;; The macro `c-vsemi-status-unknown-p' will typically check the caching
878 ;; scheme used by the `c-at-vsemi-p-fn', hence the name - the status is
879 ;; "unknown" if there is no cache entry current for the line.
880 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
883 ;; Is there a virtual semicolon (not a real one or a }) at POS (defaults to
884 ;; point)? Always returns nil for languages which don't have Virtual
885 ;; semicolons.
886 ;; This macro might do hidden buffer changes.
891 ;; Return NIL only if it can be guaranteed that an immediate
892 ;; (c-at-vsemi-p) will NOT call c-beginning-of-statement-1. Otherwise,
893 ;; return non-nil. (See comments above). The function invoked by this
894 ;; macro MUST NOT UNDER ANY CIRCUMSTANCES itself call
895 ;; c-beginning-of-statement-1.
896 ;; Languages which don't have EOL terminated statements always return NIL
897 ;; (they _know_ there's no vsemi ;-).
900 \f
902 ;; Formats an error message for the echo area and dings, i.e. like
903 ;; `error' but doesn't abort.
909 ;; Temporarily switches to the specified syntax table in a failsafe
910 ;; way to execute code.
911 ;; Maintainers' note: If TABLE is `c++-template-syntax-table', DON'T call
912 ;; any forms inside this that call `c-parse-state'. !!!!
922 "Skip over any whitespace following point.
923 This function skips over horizontal and vertical whitespace and line
924 continuations."
928 ;; skip-syntax-* doesn't count \n as whitespace..
943 "Skip over any whitespace preceding point.
944 This function skips over horizontal and vertical whitespace and line
945 continuations."
949 ;; skip-syntax-* doesn't count \n as whitespace..
965 "Return non-nil if the current CC Mode major mode is MODE.
966 MODE is either a mode symbol or a list of mode symbols."
969 ;; Inside a `c-lang-defconst'.
983 \f
984 ;; Macros/functions to handle so-called "char properties", which are
985 ;; properties set on a single character and that never spread to any
986 ;; other characters.
989 ;; Constant used at compile time to decide whether or not to use
990 ;; XEmacs extents. Check all the extent functions we'll use since
991 ;; some packages might add compatibility aliases for some of them in
992 ;; Emacs.
1007 ;; `c-put-char-property' is complex enough in XEmacs and Emacs < 21 to
1008 ;; make it a function.
1012 ;; XEmacs.
1022 end-open t)))))))))
1025 ;; In Emacs < 21 we have to mess with the `rear-nonsticky' property.
1032 'rear-nonsticky
1034 ;; This won't be used for anything.
1039 ;; Put the given property with the given value on the character at
1040 ;; POS and make it front and rear nonsticky, or start and end open
1041 ;; in XEmacs vocabulary. If the character already has the given
1042 ;; property then the value is replaced, and the behavior is
1043 ;; undefined if that property has been put by some other function.
1044 ;; PROPERTY is assumed to be constant.
1045 ;;
1046 ;; If there's a `text-property-default-nonsticky' variable (Emacs
1047 ;; 21) then it's assumed that the property is present on it.
1048 ;;
1049 ;; This macro does a hidden buffer change.
1053 ;; XEmacs and Emacs < 21.
1055 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1056 ;; by `text-property-default-nonsticky'.
1061 ;; Get the value of the given property on the character at POS if
1062 ;; it's been put there by `c-put-char-property'. PROPERTY is
1063 ;; assumed to be constant.
1066 ;; XEmacs.
1069 ;; Emacs.
1072 ;; `c-clear-char-property' is complex enough in Emacs < 21 to make it
1073 ;; a function, since we have to mess with the `rear-nonsticky' property.
1083 'rear-nonsticky
1089 ;; Remove the given property on the character at POS if it's been put
1090 ;; there by `c-put-char-property'. PROPERTY is assumed to be
1091 ;; constant.
1092 ;;
1093 ;; This macro does a hidden buffer change.
1096 ;; XEmacs.
1100 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1101 ;; by `text-property-default-nonsticky'.
1106 ;; Emacs < 21.
1110 ;; Remove all the occurrences of the given property in the given
1111 ;; region that has been put with `c-put-char-property'. PROPERTY is
1112 ;; assumed to be constant.
1113 ;;
1114 ;; Note that this function does not clean up the property from the
1115 ;; lists of the `rear-nonsticky' properties in the region, if such
1116 ;; are used. Thus it should not be used for common properties like
1117 ;; `syntax-table'.
1118 ;;
1119 ;; This macro does hidden buffer changes.
1122 ;; XEmacs.
1126 ;; Emacs.
1130 "Search forward for a text-property PROPERTY having value VALUE.
1131 LIMIT bounds the search. The comparison is done with `equal'.
1133 Leave point just after the character, and set the match data on
1134 this character, and return point. If VALUE isn't found, Return
1135 nil; point is then left undefined."
1149 "Search backward for a text-property PROPERTY having value VALUE.
1150 LIMIT bounds the search. The comparison is done with `equal'.
1152 Leave point just before the character, set the match data on this
1153 character, and return point. If VALUE isn't found, Return nil;
1154 point is then left undefined."
1162 ;; XEmacs > 2005-01-25.
1163 'previous-single-char-property-change
1164 ;; Emacs and earlier XEmacs.
1173 "Remove all text-properties PROPERTY from the region (FROM, TO)
1174 which have the value VALUE, as tested by `equal'. These
1175 properties are assumed to be over individual characters, having
1176 been put there by c-put-char-property. POINT remains unchanged."
1188 ;; Do we have to do anything with stickiness here?
1192 "Remove all text-properties PROPERTY from the region [FROM, TO)
1193 which have the value VALUE, as tested by `equal'. These
1194 properties are assumed to be over individual characters, having
1195 been put there by c-put-char-property. POINT remains unchanged."
1197 ;; XEmacs
1203 ;; GNU Emacs
1205 \f
1206 ;; Macros to put overlays (Emacs) or extents (XEmacs) on buffer text.
1207 ;; For our purposes, these are characterized by being possible to
1208 ;; remove again without affecting the other text properties in the
1209 ;; buffer that got overridden when they were put.
1212 ;; Put an overlay/extent covering the given range in the current
1213 ;; buffer. It's currently undefined whether it's front/end sticky
1214 ;; or not. The overlay/extent object is returned.
1216 ;; Emacs.
1219 ol)
1220 ;; XEmacs.
1223 ext)))
1226 ;; Deletes an overlay/extent object previously retrieved using
1227 ;; `c-put-overlay'.
1229 ;; Emacs.
1231 ;; XEmacs.
1234 \f
1235 ;; Make edebug understand the macros.
1236 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1237 ; '(progn
1266 \f
1267 ;;; Functions.
1269 ;; Note: All these after the macros, to be on safe side in avoiding
1270 ;; bugs where macros are defined too late. These bugs often only show
1271 ;; when the files are compiled in a certain order within the same
1272 ;; session.
1275 ;; Replacement for end-of-defun that use c-beginning-of-defun-1.
1277 ;; Skip forward into the next defun block. Don't bother to avoid
1278 ;; comments, literals etc, since beginning-of-defun doesn't do that
1279 ;; anyway.
1288 ;; Mark the "<" character at POS as a template opener using the
1289 ;; `syntax-table' property either directly (XEmacs) or via a `category'
1290 ;; property (GNU Emacs).
1291 ;;
1292 ;; This function does a hidden buffer change. Note that we use
1293 ;; indirection through the `category' text property. This allows us to
1294 ;; toggle the property in all template brackets simultaneously and
1295 ;; cheaply. We use this, for instance, in `c-parse-state'.
1302 ;; Mark the ">" character at POS as an sexp list closer using the
1303 ;; `syntax-table' property either directly (XEmacs) or via a `category'
1304 ;; property (GNU Emacs).
1305 ;;
1306 ;; This function does a hidden buffer change. Note that we use
1307 ;; indirection through the `category' text property. This allows us to
1308 ;; toggle the property in all template brackets simultaneously and
1309 ;; cheaply. We use this, for instance, in `c-parse-state'.
1315 ;; Unmark the "<" or "<" character at POS as an sexp list opener using the
1316 ;; `syntax-table' property either directly or indirectly through a
1317 ;; `category' text property.
1318 ;;
1319 ;; This function does a hidden buffer change. Note that we try to use
1320 ;; indirection through the `category' text property. This allows us to
1321 ;; toggle the property in all template brackets simultaneously and
1322 ;; cheaply. We use this, for instance, in `c-parse-state'.
1326 ;; Suppress the syntactic effect of all marked < and > as parens. Note
1327 ;; that this effect is NOT buffer local. You should probably not use
1328 ;; this directly, but only through the macro
1329 ;; `c-with-<->-as-parens-suppressed'
1334 ;; Restore the syntactic effect of all marked <s and >s as parens. This
1335 ;; has no effect on unmarked <s and >s
1340 ;; Like progn, except that the paren property is suppressed on all
1341 ;; template brackets whilst they are running. This macro does a hidden
1342 ;; buffer change.
1349 ;;;;;;;;;;;;;;;
1352 ;; This is the value of the `category' text property placed on every #
1353 ;; which introduces a CPP construct and every EOL (or EOB, or character
1354 ;; preceding //, etc.) which terminates it. We can instantly "comment
1355 ;; out" all CPP constructs by giving `c-cpp-delimiter' a syntax-table
1356 ;; property '(14) (generic comment delimiter).
1358 ;; This macro does a hidden buffer change.
1364 ;; This macro does a hidden buffer change.
1371 ;; Render all preprocessor constructs syntactically commented out.
1374 ;; Restore the syntactic visibility of preprocessor constructs.
1378 ;; Execute FORMS... whilst the syntactic effect of all characters in
1379 ;; all CPP regions is suppressed. In particular, this is to suppress
1380 ;; the syntactic significance of parens/braces/brackets to functions
1381 ;; such as `scan-lists' and `parse-partial-sexp'.
1390 ;; Execute FORMS... whilst the syntactic effect of all characters in
1391 ;; every CPP region APART FROM THE ONE BETWEEN BEG and END is
1392 ;; suppressed.
1403 \f
1404 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1405 ;; The following macros are to be used only in `c-parse-state' and its
1406 ;; subroutines. Their main purpose is to simplify the handling of C++/Java
1407 ;; template delimiters and CPP macros. In GNU Emacs, this is done slickly by
1408 ;; the judicious use of 'category properties. These don't exist in XEmacs.
1409 ;;
1410 ;; Note: in the following macros, there is no special handling for parentheses
1411 ;; inside CPP constructs. That is because CPPs are always syntactically
1412 ;; balanced, thanks to `c-neutralize-CPP-line' in cc-mode.el.
1414 ;; Do a (scan-lists FROM 1 1). Any finishing position which either (i) is
1415 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1416 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1421 pos))
1424 ;; Do a (scan-lists FROM 1 -1). Any finishing position which either (i) is
1425 ;; determined by an angle bracket; or (ii) is inside a macro whose start
1426 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1432 pos))
1435 ;; Do a (scan-lists FROM -1 1). Any finishing position which either (i) is
1436 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1437 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1442 pos))
1445 ;; Do a (scan-lists FROM -1 -1). Any finishing position which either (i) is
1446 ;; determined by and angle bracket; or (ii) is inside a macro whose start
1447 ;; isn't POINT-MACRO-START doesn't count as a finishing position.
1453 pos))
1471 oldstate)
1472 ;; Do a parse-partial-sexp using the supplied arguments, disregarding
1473 ;; template/generic delimiters < > and disregarding macros other than the
1474 ;; one at POINT-MACRO-START.
1475 ;;
1476 ;; NOTE that STOPBEFORE must be nil. TARGETDEPTH should be one less than
1477 ;; the depth in OLDSTATE. This function is thus a SPECIAL PURPOSE variation
1478 ;; on parse-partial-sexp, designed for calling from
1479 ;; `c-remove-stale-state-cache'.
1480 ;;
1481 ;; Any finishing position which is determined by an angle bracket delimiter
1482 ;; doesn't count as a finishing position.
1483 ;;
1484 ;; Note there is no special handling of CPP constructs here, since these are
1485 ;; always syntactically balanced (thanks to `c-neutralize-CPP-line').
1490 ;; We must have hit targetdepth.
1499 state))
1502 oldstate)
1508 \f
1512 "Are we looking at a character which isn't alphanumeric or space?"
1521 \f
1523 ;; return the element of ALIST that matches the first element found
1524 ;; in LIST. Uses assq.
1529 match))
1532 ;; first, find the first entry from LIST that is present in ALIST1,
1533 ;; then find the entry in ALIST2 for that entry.
1537 "Return the syntactic symbol in LANGELEM.
1541 form as used in `c-syntactic-element'."
1545 "Return the anchor position in LANGELEM, or nil if there is none.
1549 form as used in `c-syntactic-element'."
1555 "Return the column of the anchor position in LANGELEM.
1556 Also move the point to that position unless PRESERVE-POINT is non-nil.
1560 form as used in `c-syntactic-element'."
1572 "Return the secondary position in LANGELEM, or nil if there is none.
1575 in `c-syntactic-element'. It may also be a cons cell as passed in the
1576 first argument to lineup functions, but then the returned value always
1577 will be nil."
1581 ;; Do whatever is necessary to keep the region active in XEmacs.
1582 ;; This is not needed for Emacs.
1596 the corresponding symbol."
1602 c-buffer-is-cc-mode))
1607 the value of the variable with that name."
1611 "Return non-nil if position POS in the current buffer has any of the
1612 faces in the list FACES."
1619 pos-faces)
1623 ;; Return t if FACENAME is the name of a face. This method is
1624 ;; necessary since facep in XEmacs only returns t for the actual
1625 ;; face objects (while it's only their names that are used just
1626 ;; about anywhere else) without providing a predicate that tests
1627 ;; face names.
1631 "Like `concat' on LIST, but separate each element with SEPARATOR.
1632 Notably, null elements in LIST are ignored."
1636 "Make a regexp that matches all the strings the list.
1637 Duplicates and nil elements in the list are removed. The
1638 resulting regexp may contain zero or more submatch expressions.
1640 If ADORN is t there will be at least one submatch and the first
1641 surrounds the matched alternative, and the regexp will also not match
1642 a prefix of any identifier. Adorned regexps cannot be appended. The
1643 language variable `c-nonsymbol-key' is used to make the adornment.
1645 A value `appendable' for ADORN is like above, but all alternatives in
1647 instead, so that the regexp remains appendable. Note that this
1648 variant doesn't always guarantee that an identifier prefix isn't
1649 matched since the symbol constituent `_' is normally considered a
1652 The optional MODE specifies the language to get `c-nonsymbol-key' from
1653 when it's needed. The default is the current language taken from
1654 `c-buffer-is-cc-mode'."
1661 ;; This is kludgy but it works: Search for a string that
1662 ;; doesn't occur in any word in LIST. Append it to all
1663 ;; the alternatives where we want to add \>. Run through
1664 ;; `regexp-opt' and then replace it with \>.
1668 pos list)
1672 nil)
1673 t))
1675 found))
1689 ;; Emacs 20 and XEmacs (all versions so far) has a buggy
1690 ;; regexp-opt that doesn't always cope with strings containing
1691 ;; newlines. This kludge doesn't handle shy parens correctly
1692 ;; so we can't advice regexp-opt directly with it.
1716 ;; Add our own grouping parenthesis around re instead of
1717 ;; passing adorn to `regexp-opt', since in XEmacs it makes the
1718 ;; top level grouping "shy".
1727 re)))
1729 ;; Produce a regexp that matches nothing.
1737 "Make a character alternative string from the list of characters CHARS.
1738 The returned string is of the type that can be used with
1739 `skip-chars-forward' and `skip-chars-backward'. If INVERTED is
1740 non-nil, a caret is prepended to invert the set."
1741 ;; This function ought to be in the elisp core somewhere.
1747 ;; Quoting necessary (this method only works in the skip
1748 ;; functions).
1751 ;; Check for range.
1759 str))
1761 ;; Leftovers from (X)Emacs 19 compatibility.
1765 \f
1766 ;; Figure out what features this Emacs has
1776 ;; I've no idea what this actually is, but it's legacy. /mast
1779 ;; XEmacs uses 8-bit modify-syntax-entry flags.
1780 ;; Emacs uses a 1-bit flag. We will have to set up our
1781 ;; syntax tables differently to handle this.
1783 entry)
1786 ;; Emacs
1789 ;; In Emacs, table entries are cons cells
1791 ;; XEmacs
1794 ;; incompatible
1799 list)))
1801 ;; Check whether beginning/end-of-defun call
1802 ;; beginning/end-of-defun-function nicely, passing through the
1803 ;; argument and respecting the return code.
1823 ;; Record whether the `category' text property works.
1827 parse-sexp-lookup-properties
1828 parse-sexp-ignore-comments
1833 ;; For some reason we have to set some of these after the
1834 ;; buffer has been made current. (Specifically,
1835 ;; `parse-sexp-ignore-comments' in Emacs 21.)
1837 parse-sexp-ignore-comments t
1838 lookup-syntax-properties t)
1840 ;; Find out if the `syntax-table' text property works.
1851 "CC Mode is incompatible with this version of Emacs - "
1852 "support for the `syntax-table' text property "
1855 ;; Find out if "\\s!" (generic comment delimiters) work.
1861 ;; Find out if "\\s|" (generic string delimiters) work.
1867 ;; See if POSIX char classes work.
1869 ;; All versions of Emacs 21 so far haven't fixed
1870 ;; char classes in `skip-chars-forward' and
1871 ;; `skip-chars-backward'.
1880 ;; See if `open-paren-in-column-0-is-defun-start' exists and
1881 ;; isn't buggy (Emacs >= 21.4).
1889 ;; XEmacs. Afaik this is currently an Emacs-only
1890 ;; feature, but it's good to be prepared.
1894 ;; Emacs
1907 ;; See if `parse-partial-sexp' returns the eighth element.
1913 "CC Mode is incompatible with this version of Emacs - "
1916 ;;(message "c-emacs-features: %S" list)
1917 list)
1918 "A list of certain features in the (X)Emacs you are using.
1919 There are many flavors of Emacs out there, each with different
1920 features supporting those needed by CC Mode. The following values
1921 might be present:
1923 `8-bit' 8 bit syntax entry flags (XEmacs style).
1924 `1-bit' 1 bit syntax entry flags (Emacs style).
1925 `argumentative-bod-function' beginning-of-defun and end-of-defun pass
1926 ARG through to beginning/end-of-defun-function.
1927 `syntax-properties' It works to override the syntax for specific characters
1928 in the buffer with the `syntax-table' property. It's
1929 always set - CC Mode no longer works in emacsen without
1930 this feature.
1931 `category-properties' Syntax routines can add a level of indirection to text
1932 properties using the `category' property.
1933 `gen-comment-delim' Generic comment delimiters work
1934 (i.e. the syntax class `!').
1935 `gen-string-delim' Generic string delimiters work
1936 (i.e. the syntax class `|').
1937 `pps-extended-state' `parse-partial-sexp' returns a list with at least 10
1938 elements, i.e. it contains the position of the start of
1939 the last comment or string. It's always set - CC Mode
1940 no longer works in emacsen without this feature.
1941 `posix-char-classes' The regexp engine understands POSIX character classes.
1942 `col-0-paren' It's possible to turn off the ad-hoc rule that a paren
1943 in column zero is the start of a defun.
1944 `infodock' This is Infodock (based on XEmacs).
1948 \f
1949 ;;; Some helper constants.
1951 ;; If the regexp engine supports POSIX char classes then we can use
1952 ;; them to handle extended charsets correctly.
1966 \f
1967 ;;; System for handling language dependent constants.
1969 ;; This is used to set various language dependent data in a flexible
1970 ;; way: Language constants can be built from the values of other
1971 ;; language constants, also those for other languages. They can also
1972 ;; process the values of other language constants uniformly across all
1973 ;; the languages. E.g. one language constant can list all the type
1974 ;; keywords in each language, and another can build a regexp for each
1975 ;; language from those lists without code duplication.
1976 ;;
1977 ;; Language constants are defined with `c-lang-defconst', and their
1978 ;; value forms (referred to as source definitions) are evaluated only
1979 ;; on demand when requested for a particular language with
1980 ;; `c-lang-const'. It's therefore possible to refer to the values of
1981 ;; constants defined later in the file, or in another file, just as
1982 ;; long as all the relevant `c-lang-defconst' have been loaded when
1983 ;; `c-lang-const' is actually evaluated from somewhere else.
1984 ;;
1985 ;; `c-lang-const' forms are also evaluated at compile time and
1986 ;; replaced with the values they produce. Thus there's no overhead
1987 ;; for this system when compiled code is used - only the values
1988 ;; actually used in the code are present, and the file(s) containing
1989 ;; the `c-lang-defconst' forms don't need to be loaded at all then.
1990 ;; There are however safeguards to make sure that they can be loaded
1991 ;; to get the source definitions for the values if there's a mismatch
1992 ;; in compiled versions, or if `c-lang-const' is used uncompiled.
1993 ;;
1994 ;; Note that the source definitions in a `c-lang-defconst' form are
1995 ;; compiled into the .elc file where it stands; there's no need to
1996 ;; load the source file to get it.
1997 ;;
1998 ;; See cc-langs.el for more details about how this system is deployed
1999 ;; in CC Mode, and how the associated language variable system
2000 ;; (`c-lang-defvar') works. That file also contains a lot of
2001 ;; examples.
2004 "Declare a new language in the language dependent variable system.
2005 This is intended to be used by modes that inherit CC Mode to add new
2006 languages. It should be used at the top level before any calls to
2007 `c-lang-defconst'. MODE is the mode name symbol for the new language,
2008 and BASE-MODE is the mode name symbol for the language in CC Mode that
2009 is to be the template for the new mode.
2011 The exact effect of BASE-MODE is to make all language constants that
2012 haven't got a setting in the new language fall back to their values in
2013 BASE-MODE. It does not have any effect outside the language constant
2014 system."
2023 ;; Obarray used as a cache to keep track of the language constants.
2024 ;; The constants stored are those defined by `c-lang-defconst' and the values
2025 ;; computed by `c-lang-const'. It's mostly used at compile time but it's not
2026 ;; stored in compiled files.
2028 ;; The obarray contains all the language constants as symbols. The
2029 ;; value cells hold the evaluated values as alists where each car is
2030 ;; the mode name symbol and the corresponding cdr is the evaluated
2031 ;; value in that mode. The property lists hold the source definitions
2032 ;; and other miscellaneous data. The obarray might also contain
2033 ;; various other symbols, but those don't have any variable bindings.
2037 ;; Ugly hack to pull in the definition of `cc-bytecomp-compiling-or-loading'
2038 ;; from cc-bytecomp to make it available at loadtime. This is the same
2039 ;; mechanism used in cc-mode.el for `c-populate-syntax-table'.
2046 ;; Return the base name of the current file.
2058 "Can be used inside a VAL in `c-lang-defconst' to evaluate FORM
2059 immediately, i.e. at the same time as the `c-lang-defconst' form
2060 itself is evaluated."
2061 ;; Evaluate at macro expansion time, i.e. in the
2062 ;; `c--macroexpand-all' inside `c-lang-defconst'.
2066 "Set the language specific values of the language constant NAME.
2067 The second argument can optionally be a docstring. The rest of the
2068 arguments are one or more repetitions of LANG VAL where LANG specifies
2069 the language(s) that VAL applies to. LANG is the name of the
2071 of such language names, or t for all languages. VAL is a form to
2072 evaluate to get the value.
2074 If LANG isn't t or one of the core languages in CC Mode, it must
2075 have been declared with `c-add-language'.
2077 Neither NAME, LANG nor VAL are evaluated directly - they should not be
2078 quoted. `c-lang-defconst-eval-immediately' can however be used inside
2079 VAL to evaluate parts of it directly.
2081 When VAL is evaluated for some language, that language is temporarily
2082 made current so that `c-lang-const' without an explicit language can
2083 be used inside VAL to refer to the value of a language constant in the
2084 same language. That is particularly useful if LANG is t.
2086 VAL is not evaluated right away but rather when the value is requested
2087 with `c-lang-const'. Thus it's possible to use `c-lang-const' inside
2088 VAL to refer to language constants that haven't been defined yet.
2089 However, if the definition of a language constant is in another file
2090 then that file must be loaded \(at compile time) before it's safe to
2091 reference the constant.
2093 The assignments in ARGS are processed in sequence like `setq', so
2094 \(c-lang-const NAME) may be used inside a VAL to refer to the last
2095 assigned value to this language constant, or a value that it has
2096 gotten in another earlier loaded file.
2098 To work well with repeated loads and interactive reevaluation, only
2099 one `c-lang-defconst' for each NAME is permitted per file. If there
2100 already is one it will be completely replaced; the value in the
2101 earlier definition will not affect `c-lang-const' on the same
2102 constant. A file is identified by its base name."
2105 ;; Make `c-lang-const' expand to a straightforward call to
2106 ;; `c-get-lang-constant' in `c--macroexpand-all' below.
2107 ;;
2108 ;; (The default behavior, i.e. to expand to a call inside
2109 ;; `eval-when-compile' should be equivalent, since that macro
2110 ;; should only expand to its content if it's used inside a
2111 ;; form that's already evaluated at compile time. It's
2112 ;; however necessary to use our cover macro
2113 ;; `cc-eval-when-compile' due to bugs in `eval-when-compile',
2114 ;; and it expands to a bulkier form that in this case only is
2115 ;; unnecessary garbage that we don't want to store in the
2116 ;; language constant source definitions.)
2122 bindings
2123 pre-files)
2129 ;; The docstring is hardly used anywhere since there's no normal
2130 ;; symbol to attach it to. It's primarily for getting the right
2131 ;; format in the source.
2138 ;; Rework ARGS to an association list to make it easier to handle.
2139 ;; It's reversed at the same time to make it easier to implement
2140 ;; the demand-driven (i.e. reversed) evaluation in `c-lang-const'.
2157 val)
2164 ;; Emacs has a weird bug where it seems to fail to read
2165 ;; backquote lists from byte compiled files correctly (,@
2166 ;; forms, to be specific), so make sure the bindings in the
2167 ;; expansion below don't contain any backquote stuff.
2168 ;; (XEmacs handles it correctly and doesn't need this for that
2169 ;; reason, but we also use this expansion handle
2170 ;; `c-lang-defconst-eval-immediately' and to register
2171 ;; dependencies on the `c-lang-const's in VAL.)
2177 ;; Compile in the other files that have provided source
2178 ;; definitions for this symbol, to make sure the order in the
2179 ;; `source' property is correct even when files are loaded out of
2180 ;; order.
2183 ;; This can happen when the source file (e.g. cc-langs.el) is first
2184 ;; loaded as source, setting a 'source property entry, and then itself
2185 ;; being compiled.
2187 ;; Reverse to get the right load order.
2195 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
2196 ; '
2201 ;; Used by `c-lang-defconst'.
2210 ;;(when (cdr-safe elem)
2211 ;; (message "Language constant %s redefined in %S" name file))
2213 ;; Note that the order in the source alist is relevant. Like how
2214 ;; `c-lang-defconst' reverses the bindings, this reverses the
2215 ;; order between files so that the last to evaluate comes first.
2225 ;; Bind the symbol as a variable, or clear any earlier evaluated
2226 ;; value it has.
2229 ;; Clear the evaluated values that depend on this source.
2232 ptr)
2245 name))
2248 "Get the mode specific value of the language constant NAME in language LANG.
2249 LANG is the name of the language, i.e. the mode name without the
2251 `c-lang-defvar', LANG may be left out to refer to the current
2252 language. NAME and LANG are not evaluated so they should not be
2253 quoted."
2265 lang))
2268 ;; No need to find out the source file(s) when we evaluate
2269 ;; immediately since all the info is already there in the
2270 ;; `source' property.
2276 ;; Get the source file(s) that must be loaded to get the value
2277 ;; of the constant. If the symbol isn't defined yet we assume
2278 ;; that its definition will come later in this file, and thus
2279 ;; are no file dependencies needed.
2281 ;; Reverse to get the right load order.
2284 nil ; Exclude our own file.
2288 ;; Make some effort to do a compact call to
2289 ;; `c-get-lang-constant' since it will be compiled in.
2299 ;; Either a straight call is requested in the context, or
2300 ;; we're in an "uncontrolled" context and got no language,
2301 ;; or we're not being byte compiled so the compile time
2302 ;; stuff below is unnecessary.
2305 ;; Being compiled. If the loading and compiling version is
2306 ;; the same we use a value that is evaluated at compile time,
2307 ;; otherwise it's evaluated at runtime.
2314 "Alist of constants in the process of being evaluated.
2315 The `cdr' of each entry indicates how far we've looked in the list
2316 of definitions, so that the def for var FOO in c-mode can be defined in
2317 terms of the def for that same var FOO (which will then rely on the
2323 ;; Used by `c-lang-const'.
2331 elem
2335 ;; Record the dependencies between this symbol and the one we're
2336 ;; being evaluated in.
2341 ;; Make sure the source files have entries on the `source'
2342 ;; property so that loading will take place when necessary.
2347 ;; Might pull in more definitions which affect the value. The
2348 ;; clearing of dependent values etc is done when the
2349 ;; definition is encountered during the load; this is just to
2350 ;; jump past the check for a cached value below.
2358 ;; Check if an evaluation of this symbol is already underway.
2359 ;; In that case we just continue with the "assignment" before
2360 ;; the one currently being evaluated, thereby creating the
2361 ;; illusion if a `setq'-like sequence of assignments.
2366 ;; Append `c-lang-constants-under-evaluation' even if an
2367 ;; earlier entry is found. It's only necessary to get
2368 ;; the recording of dependencies above correct.
2372 value
2373 ;; Make sure the recursion limits aren't very low
2374 ;; since the `c-lang-const' dependencies can go deep.
2381 ;; First try the original mode but don't accept an
2382 ;; entry matching all languages since the fallback
2383 ;; mode might have an explicit entry before that.
2386 c-lang--novalue)
2387 ;; Try again with the fallback mode from the
2388 ;; original position. Note that
2389 ;; `c-buffer-is-cc-mode' still is the real mode if
2390 ;; language parameterization takes place.
2393 fallback t name))
2394 c-lang--novalue)))
2395 ;; A simple lookup with no fallback mode.
2398 c-lang--novalue))
2400 "`%s' got no (prior) value in %S (might be a cyclic reference)"
2401 name mode))
2406 ;; Print a message to aid in locating the error. We don't
2407 ;; print the error itself since that will be done later by
2408 ;; some caller higher up.
2410 sym mode)
2415 value))))
2418 ;; Find the first assignment entry that applies to MODE at or after
2419 ;; SOURCE-POS. If MATCH-ANY-LANG is non-nil, entries with t as
2420 ;; the language list are considered to match, otherwise they don't.
2421 ;; On return SOURCE-POS is updated to point to the next assignment
2422 ;; after the returned one. If no assignment is found,
2423 ;; `c-lang--novalue' is returned as a magic value.
2424 ;;
2425 ;; SOURCE-POS is a vector that points out a specific assignment in
2426 ;; the double alist that's used in the `source' property. The first
2427 ;; element is the position in the top alist which is indexed with
2428 ;; the source files, and the second element is the position in the
2429 ;; nested bindings alist.
2430 ;;
2431 ;; NAME is only used for error messages.
2436 assignment)
2439 t
2440 ;; Handled the last assignment from one file, begin on the
2441 ;; next. Due to the check in `c-lang-defconst', we know
2442 ;; there's at least one.
2447 ;; The file containing the source definitions has not
2448 ;; been loaded.
2451 ;;(message (concat "Loading %s to get the source "
2452 ;; "value for language constant %s")
2453 ;; file name)
2457 ;; The load didn't fill in the source for the
2458 ;; constant as expected. The situation is
2459 ;; probably that a derived mode was written for
2460 ;; and compiled with another version of CC Mode,
2461 ;; and the requested constant isn't in the
2462 ;; currently loaded one. Put in a dummy
2463 ;; assignment that matches no language.
2468 t))
2476 match-any-lang)
2479 c-lang--novalue)))
2482 ;; `c-major-mode-is' expands to a call to this function inside
2483 ;; `c-lang-defconst'. Here we also match the mode(s) against any
2484 ;; fallback modes for the one in `c-buffer-is-cc-mode', so that
2485 ;; e.g. (c-major-mode-is 'c++-mode) is true in a derived language
2486 ;; that has c++-mode as base mode.
2493 nil)
2495 match))
2497 \f
2500 ;; Local Variables:
2501 ;; indent-tabs-mode: t
2502 ;; tab-width: 8
2503 ;; End:
2504 ;;; cc-defs.el ends here