| blob | ce38cf8850bd4f393cee8ef8988a8da3b32af587 |
1 ;;; cc-defs.el --- compile time definitions for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2011 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.
63 \f
64 ;; cc-fix.el contains compatibility macros that should be used if
65 ;; needed.
71 ; (eval-after-load "font-lock" ; 2006-07-09. font-lock is now preloaded
72 ; '
74 ; to make the call to f-l-c-k throw an error.
81 ;; The above takes care of the delayed loading, but this is necessary
82 ;; to ensure correct byte compilation.
90 font-lock-keywords)))
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).
176 \f
177 ;;; Macros.
180 "Return the value of certain commonly referenced POSITIONs relative to POINT.
181 The current point is used if POINT isn't specified. POSITION can be
182 one of the following symbols:
184 `bol' -- beginning of line
185 `eol' -- end of line
186 `bod' -- beginning of defun
187 `eod' -- end of defun
188 `boi' -- beginning of indentation
189 `ionl' -- indentation of next line
190 `iopl' -- indentation of previous line
191 `bonl' -- beginning of next line
192 `eonl' -- end of next line
193 `bopl' -- beginning of previous line
194 `eopl' -- end of previous line
195 `bosws' -- beginning of syntactic whitespace
196 `eosws' -- end of syntactic whitespace
198 If the referenced position doesn't exist, the closest accessible point
199 to it is returned. This function does not modify the point or the mark."
301 ;; The bulk of this should perhaps be in a function to avoid large
302 ;; expansions, but this case is not used anywhere in CC Mode (and
303 ;; probably not anywhere else either) so we only have it to be on
304 ;; the safe side.
335 ;; Return t when the region is active. The determination of region
336 ;; activeness is different in both Emacs and XEmacs.
338 ;; Emacs.
339 'mark-active
340 ;; XEmacs.
344 ;; Activate the region if ACTIVE is non-nil, deactivate it
345 ;; otherwise. Covers the differences between Emacs and XEmacs.
347 ;; XEmacs.
351 ;; Emacs.
355 "Delete the text between START and END and return it."
357 ;; Emacs 21.1 and later
359 ;; XEmacs and Emacs 20.x
365 ;; safely execute BODY, return nil if an error occurred
372 ;; In GNU Emacs, a character is an integer. In XEmacs, a character is a
373 ;; type distinct from an integer. Sometimes we need to convert integers to
374 ;; characters. `c-int-to-char' makes this conversion, if necessary.
377 integer))
380 ;; Get the regular expression `sentence-end'.
382 ;; Emacs 22:
384 ;; Emacs <22 + XEmacs
388 ;; Get the default value of the variable sentence end.
390 ;; Emacs 22:
392 ;; Emacs <22 + XEmacs
395 ;; The following is essentially `save-buffer-state' from lazy-lock.el.
396 ;; It ought to be a standard macro.
398 "Bind variables according to VARLIST (in `let*' style) and eval BODY,
399 then restore the buffer state under the assumption that no significant
400 modification has been made in BODY. A change is considered
401 significant if it affects the buffer text in any way that isn't
402 completely restored again. Changes in text properties like `face' or
403 `syntax-table' are considered insignificant. This macro allows text
404 properties to be changed, even in a read-only buffer.
406 This macro should be placed around all calculations which set
408 known to be writable. That way, these text properties remain set
409 even if the user undoes the command which set them.
412 changes \(like adding a newline to calculate a text-property then
413 deleting it again\), so that the user never sees them on his
414 `buffer-undo-list'. See also `c-tentative-buffer-changes'.
416 However, any user-visible changes to the buffer \(like auto-newlines\)
417 must not be within a `c-save-buffer-state', since the user then
418 wouldn't be able to undo them.
420 The return value is the value of the last form in BODY."
423 before-change-functions after-change-functions
424 deactivate-mark
425 buffer-file-name buffer-file-truename ; Prevent primitives checking
426 ; for file modification
436 "Eval BODY and optionally restore the buffer contents to the state it
437 was in before BODY. Any changes are kept if the last form in BODY
438 returns non-nil. Otherwise it's undone using the undo facility, and
439 various other buffer state that might be affected by the changes is
440 restored. That includes the current buffer, point, mark, mark
441 activation \(similar to `save-excursion'), and the modified state.
442 The state is also restored if BODY exits nonlocally.
444 If BODY makes a change that unconditionally is undone then wrap this
445 macro inside `c-save-buffer-state'. That way the change can be done
446 even when the buffer is read-only, and without interference from
447 various buffer change hooks."
449 -tnt-chng-state)
451 ;; Insert an undo boundary for use with `undo-more'. We
452 ;; don't use `undo-boundary' since it doesn't insert one
453 ;; unconditionally.
461 ;; Used internally in `c-tentative-buffer-changes'.
464 ;; No need to use markers for the point and mark; if the
465 ;; undo got out of synch we're hosed anyway.
472 ;; Used internally in `c-tentative-buffer-changes'.
476 ;; No change was done afterall.
480 ;; Find and remove the undo boundary.
486 ;; `primitive-undo' will remove the boundary.
491 saved-undo-list))))
503 "Forward skip over syntactic whitespace.
504 Syntactic whitespace is defined as whitespace characters, comments,
505 and preprocessor directives. However if point starts inside a comment
506 or preprocessor directive, the content of it is not treated as
507 whitespace.
509 LIMIT sets an upper limit of the forward movement, if specified. If
510 LIMIT or the end of the buffer is reached inside a comment or
511 preprocessor directive, the point will be left there.
513 Note that this function might do hidden buffer changes. See the
514 comment at the start of cc-engine.el for more info."
522 "Backward skip over syntactic whitespace.
523 Syntactic whitespace is defined as whitespace characters, comments,
524 and preprocessor directives. However if point starts inside a comment
525 or preprocessor directive, the content of it is not treated as
526 whitespace.
528 LIMIT sets a lower limit of the backward movement, if specified. If
529 LIMIT is reached inside a line comment or preprocessor directive then
530 the point is moved into it past the whitespace at the end.
532 Note that this function might do hidden buffer changes. See the
533 comment at the start of cc-engine.el for more info."
541 "Move forward across COUNT balanced expressions.
542 A negative COUNT means move backward. Signal an error if the move
543 fails for any reason.
545 This is like `forward-sexp' except that it isn't interactive and does
546 not do any user friendly adjustments of the point and that it isn't
547 susceptible to user configurations such as disabling of signals in
548 certain situations."
553 "See `c-forward-sexp' and reverse directions."
558 "Like `scan-lists' but returns nil instead of signalling errors
559 for unbalanced parens.
561 A limit for the search may be given. FROM is assumed to be on the
562 right side of it."
576 res)))
578 \f
579 ;; Wrappers for common scan-lists cases, mainly because it's almost
580 ;; impossible to get a feel for how that function works.
583 "Move backward across one balanced group of parentheses.
585 Return POINT when we succeed, NIL when we fail. In the latter case, leave
586 point unmoved."
589 endpos)))
592 "Move backward across one balanced group of parentheses.
594 Return POINT when we succeed, NIL when we fail. In the latter case, leave
595 point unmoved."
598 endpos)))
601 "Return the first position after the list sexp containing POS,
602 or nil if no such position exists. The point is used if POS is left out.
604 A limit for the search may be given. The start position is assumed to
605 be before it."
609 "Return the position of the start of the list sexp containing POS,
610 or nil if no such position exists. The point is used if POS is left out.
612 A limit for the search may be given. The start position is assumed to
613 be after it."
617 "Return the first position inside the first list sexp after POS,
618 or nil if no such position exists. The point is used if POS is left out.
620 A limit for the search may be given. The start position is assumed to
621 be before it."
625 "Return the last position inside the last list sexp before POS,
626 or nil if no such position exists. The point is used if POS is left out.
628 A limit for the search may be given. The start position is assumed to
629 be after it."
633 "Move the point to the first position after the list sexp containing POS,
634 or containing the point if POS is left out. Return t if such a
635 position exists, otherwise nil is returned and the point isn't moved.
637 A limit for the search may be given. The start position is assumed to
638 be before it."
644 res)))
647 "Move the point to the position of the start of the list sexp containing POS,
648 or containing the point if POS is left out. Return t if such a
649 position exists, otherwise nil is returned and the point isn't moved.
651 A limit for the search may be given. The start position is assumed to
652 be after it."
658 res)))
661 "Move the point to the first position inside the first list sexp after POS,
662 or before the point if POS is left out. Return t if such a position
663 exists, otherwise nil is returned and the point isn't moved.
665 A limit for the search may be given. The start position is assumed to
666 be before it."
672 res)))
675 "Move the point to the last position inside the last list sexp before POS,
676 or before the point if POS is left out. Return t if such a position
677 exists, otherwise nil is returned and the point isn't moved.
679 A limit for the search may be given. The start position is assumed to
680 be after it."
686 res)))
688 \f
690 ;; Wrapper around beginning-of-defun.
691 ;;
692 ;; NOTE: This function should contain the only explicit use of
693 ;; beginning-of-defun in CC Mode. Eventually something better than
694 ;; b-o-d will be available and this should be the only place the
695 ;; code needs to change. Everything else should use
696 ;; (c-beginning-of-defun-1)
697 ;;
698 ;; This is really a bit too large to be a macro but that isn't a
699 ;; problem as long as it only is used in one place in
700 ;; `c-parse-state'.
704 c-enable-xemacs-performance-kludge-p)
706 ;; XEmacs only. This can improve the performance of
707 ;; c-parse-state to between 3 and 60 times faster when
708 ;; braces are hung. It can also degrade performance by
709 ;; about as much when braces are not hung.
711 pos)
721 ;; unbalanced parenthesis, while invalid C code,
722 ;; shouldn't cause an infloop! See unbal.c
724 ;; Punt!
731 ))
733 ;; Emacs, which doesn't have buffer-syntactic-context-depth
736 ;; if defun-prompt-regexp is non-nil, b-o-d won't leave us at the
737 ;; open brace.
742 \f
743 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
744 ;; V i r t u a l S e m i c o l o n s
745 ;;
746 ;; In most CC Mode languages, statements are terminated explicitly by
747 ;; semicolons or closing braces. In some of the CC modes (currently only AWK
748 ;; Mode (April 2004)), statements are (or can be) terminated by EOLs. Such a
749 ;; statement is said to be terminated by a "virtual semicolon" (VS). A
750 ;; statement terminated by an actual semicolon or brace is never considered to
751 ;; have a VS.
752 ;;
753 ;; The indentation engine (or whatever) tests for a VS at a specific position
754 ;; by invoking the macro `c-at-vsemi-p', which in its turn calls the mode
755 ;; specific function (if any) which is the value of the language variable
756 ;; `c-at-vsemi-p-fn'. The actual details of what constitutes a VS in a
757 ;; language are thus encapsulated in code specific to that language
758 ;; (e.g. cc-awk.el). `c-at-vsemi-p' returns non-nil if point (or the optional
759 ;; parameter POS) is at a VS, nil otherwise.
760 ;;
761 ;; The language specific function might well do extensive analysis of the
762 ;; source text, and may use a cacheing scheme to speed up repeated calls.
763 ;;
764 ;; The "virtual semicolon" lies just after the last non-ws token on the line.
765 ;; Like POINT, it is considered to lie between two characters. For example,
766 ;; at the place shown in the following AWK source line:
767 ;;
768 ;; kbyte = 1024 # 1000 if you're not picky
769 ;; ^
770 ;; |
771 ;; Virtual Semicolon
772 ;;
773 ;; In addition to `c-at-vsemi-p-fn', a mode may need to supply a function for
774 ;; `c-vsemi-status-unknown-p-fn'. The macro `c-vsemi-status-unknown-p' is a
775 ;; rather recondite kludge. It exists because the function
776 ;; `c-beginning-of-statement-1' sometimes tests for VSs as an optimisation,
777 ;; but `c-at-vsemi-p' might well need to call `c-beginning-of-statement-1' in
778 ;; its calculations, thus potentially leading to infinite recursion.
779 ;;
780 ;; The macro `c-vsemi-status-unknown-p' resolves this problem; it may return
781 ;; non-nil at any time; returning nil is a guarantee that an immediate
782 ;; invocation of `c-at-vsemi-p' at point will NOT call
783 ;; `c-beginning-of-statement-1'. `c-vsemi-status-unknown-p' may not itself
784 ;; call `c-beginning-of-statement-1'.
785 ;;
786 ;; The macro `c-vsemi-status-unknown-p' will typically check the cacheing
787 ;; scheme used by the `c-at-vsemi-p-fn', hence the name - the status is
788 ;; "unknown" if there is no cache entry current for the line.
789 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
792 ;; Is there a virtual semicolon (not a real one or a }) at POS (defaults to
793 ;; point)? Always returns nil for languages which don't have Virtual
794 ;; semicolons.
795 ;; This macro might do hidden buffer changes.
800 ;; Return NIL only if it can be guaranteed that an immediate
801 ;; (c-at-vsemi-p) will NOT call c-beginning-of-statement-1. Otherwise,
802 ;; return non-nil. (See comments above). The function invoked by this
803 ;; macro MUST NOT UNDER ANY CIRCUMSTANCES itself call
804 ;; c-beginning-of-statement-1.
805 ;; Languages which don't have EOL terminated statements always return NIL
806 ;; (they _know_ there's no vsemi ;-).
809 \f
811 ;; Formats an error message for the echo area and dings, i.e. like
812 ;; `error' but doesn't abort.
818 ;; Temporarily switches to the specified syntax table in a failsafe
819 ;; way to execute code.
829 "Skip over any whitespace following point.
830 This function skips over horizontal and vertical whitespace and line
831 continuations."
835 ;; skip-syntax-* doesn't count \n as whitespace..
850 "Skip over any whitespace preceding point.
851 This function skips over horizontal and vertical whitespace and line
852 continuations."
856 ;; skip-syntax-* doesn't count \n as whitespace..
872 "Return non-nil if the current CC Mode major mode is MODE.
873 MODE is either a mode symbol or a list of mode symbols."
876 ;; Inside a `c-lang-defconst'.
890 \f
891 ;; Macros/functions to handle so-called "char properties", which are
892 ;; properties set on a single character and that never spread to any
893 ;; other characters.
896 ;; Constant used at compile time to decide whether or not to use
897 ;; XEmacs extents. Check all the extent functions we'll use since
898 ;; some packages might add compatibility aliases for some of them in
899 ;; Emacs.
908 ;; `c-put-char-property' is complex enough in XEmacs and Emacs < 21 to
909 ;; make it a function.
913 ;; XEmacs.
923 end-open t)))))))))
926 ;; In Emacs < 21 we have to mess with the `rear-nonsticky' property.
933 'rear-nonsticky
935 ;; This won't be used for anything.
940 ;; Put the given property with the given value on the character at
941 ;; POS and make it front and rear nonsticky, or start and end open
942 ;; in XEmacs vocabulary. If the character already has the given
943 ;; property then the value is replaced, and the behavior is
944 ;; undefined if that property has been put by some other function.
945 ;; PROPERTY is assumed to be constant.
946 ;;
947 ;; If there's a `text-property-default-nonsticky' variable (Emacs
948 ;; 21) then it's assumed that the property is present on it.
949 ;;
950 ;; This macro does a hidden buffer change.
954 ;; XEmacs and Emacs < 21.
956 ;; In Emacs 21 we got the `rear-nonsticky' property covered
957 ;; by `text-property-default-nonsticky'.
962 ;; Get the value of the given property on the character at POS if
963 ;; it's been put there by `c-put-char-property'. PROPERTY is
964 ;; assumed to be constant.
967 ;; XEmacs.
970 ;; Emacs.
973 ;; `c-clear-char-property' is complex enough in Emacs < 21 to make it
974 ;; a function, since we have to mess with the `rear-nonsticky' property.
984 'rear-nonsticky
990 ;; Remove the given property on the character at POS if it's been put
991 ;; there by `c-put-char-property'. PROPERTY is assumed to be
992 ;; constant.
993 ;;
994 ;; This macro does a hidden buffer change.
997 ;; XEmacs.
1001 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1002 ;; by `text-property-default-nonsticky'.
1007 ;; Emacs < 21.
1011 ;; Remove all the occurrences of the given property in the given
1012 ;; region that has been put with `c-put-char-property'. PROPERTY is
1013 ;; assumed to be constant.
1014 ;;
1015 ;; Note that this function does not clean up the property from the
1016 ;; lists of the `rear-nonsticky' properties in the region, if such
1017 ;; are used. Thus it should not be used for common properties like
1018 ;; `syntax-table'.
1019 ;;
1020 ;; This macro does hidden buffer changes.
1023 ;; XEmacs.
1027 ;; Emacs.
1031 "Search forward for a text-property PROPERTY having value VALUE.
1032 LIMIT bounds the search. The comparison is done with `equal'.
1034 Leave point just after the character, and set the match data on
1035 this character, and return point. If VALUE isn't found, Return
1036 nil; point is then left undefined."
1050 "Search backward for a text-property PROPERTY having value VALUE.
1051 LIMIT bounds the search. The comparison is done with `equal'.
1053 Leave point just before the character, set the match data on this
1054 character, and return point. If VALUE isn't found, Return nil;
1055 point is then left undefined."
1069 "Remove all text-properties PROPERTY from the region (FROM, TO)
1070 which have the value VALUE, as tested by `equal'. These
1071 properties are assumed to be over individual characters, having
1072 been put there by c-put-char-property. POINT remains unchanged."
1084 ;; Do we have to do anything with stickiness here?
1088 "Remove all text-properties PROPERTY from the region [FROM, TO)
1089 which have the value VALUE, as tested by `equal'. These
1090 properties are assumed to be over individual characters, having
1091 been put there by c-put-char-property. POINT remains unchanged."
1093 ;; XEmacs
1099 ;; Gnu Emacs
1101 \f
1102 ;; Macros to put overlays (Emacs) or extents (XEmacs) on buffer text.
1103 ;; For our purposes, these are characterized by being possible to
1104 ;; remove again without affecting the other text properties in the
1105 ;; buffer that got overridden when they were put.
1108 ;; Put an overlay/extent covering the given range in the current
1109 ;; buffer. It's currently undefined whether it's front/end sticky
1110 ;; or not. The overlay/extent object is returned.
1112 ;; Emacs.
1115 ol)
1116 ;; XEmacs.
1119 ext)))
1122 ;; Deletes an overlay/extent object previously retrieved using
1123 ;; `c-put-overlay'.
1125 ;; Emacs.
1127 ;; XEmacs.
1130 \f
1131 ;; Make edebug understand the macros.
1132 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1133 ; '(progn
1162 \f
1163 ;;; Functions.
1165 ;; Note: All these after the macros, to be on safe side in avoiding
1166 ;; bugs where macros are defined too late. These bugs often only show
1167 ;; when the files are compiled in a certain order within the same
1168 ;; session.
1171 ;; Replacement for end-of-defun that use c-beginning-of-defun-1.
1173 ;; Skip forward into the next defun block. Don't bother to avoid
1174 ;; comments, literals etc, since beginning-of-defun doesn't do that
1175 ;; anyway.
1187 ;; Mark the "<" character at POS as a template opener using the
1188 ;; `syntax-table' property via the `category' property.
1189 ;;
1190 ;; This function does a hidden buffer change. Note that we use
1191 ;; indirection through the `category' text property. This allows us to
1192 ;; toggle the property in all template brackets simultaneously and
1193 ;; cheaply. We use this, for instance, in `c-parse-state'.
1200 ;; Mark the ">" character at POS as an sexp list closer using the
1201 ;; syntax-table property.
1202 ;;
1203 ;; This function does a hidden buffer change. Note that we use
1204 ;; indirection through the `category' text property. This allows us to
1205 ;; toggle the property in all template brackets simultaneously and
1206 ;; cheaply. We use this, for instance, in `c-parse-state'.
1210 ;; Unmark the "<" or "<" character at POS as an sexp list opener using
1211 ;; the syntax-table property indirectly through the `category' text
1212 ;; property.
1213 ;;
1214 ;; This function does a hidden buffer change. Note that we use
1215 ;; indirection through the `category' text property. This allows us to
1216 ;; toggle the property in all template brackets simultaneously and
1217 ;; cheaply. We use this, for instance, in `c-parse-state'.
1221 ;; Suppress the syntactic effect of all marked < and > as parens. Note
1222 ;; that this effect is NOT buffer local. You should probably not use
1223 ;; this directly, but only through the macro
1224 ;; `c-with-<->-as-parens-suppressed'
1229 ;; Restore the syntactic effect of all marked <s and >s as parens. This
1230 ;; has no effect on unmarked <s and >s
1235 ;; Like progn, except that the paren property is suppressed on all
1236 ;; template brackets whilst they are running. This macro does a hidden
1237 ;; buffer change.
1244 ;;;;;;;;;;;;;;;
1247 ;; This is the value of the `category' text property placed on every #
1248 ;; which introduces a CPP construct and every EOL (or EOB, or character
1249 ;; preceding //, etc.) which terminates it. We can instantly "comment
1250 ;; out" all CPP constructs by giving `c-cpp-delimiter' a syntax-table
1251 ;; propery '(14) (generic comment delimiter).
1253 ;; This macro does a hidden buffer change.
1259 ;; This macro does a hidden buffer change.
1266 ;; Render all preprocessor constructs syntactically commented out.
1269 ;; Restore the syntactic visibility of preprocessor constructs.
1273 ;; Execute FORMS... whilst the syntactic effect of all characters in
1274 ;; all CPP regions is suppressed. In particular, this is to suppress
1275 ;; the syntactic significance of parens/braces/brackets to functions
1276 ;; such as `scan-lists' and `parse-partial-sexp'.
1285 ;; Execute FORMS... whilst the syntactic effect of all characters in
1286 ;; every CPP region APART FROM THE ONE BETWEEN BEG and END is
1287 ;; suppressed.
1294 \f
1296 ;; return the element of ALIST that matches the first element found
1297 ;; in LIST. Uses assq.
1302 match))
1305 ;; first, find the first entry from LIST that is present in ALIST1,
1306 ;; then find the entry in ALIST2 for that entry.
1310 "Return the syntactic symbol in LANGELEM.
1314 form as used in `c-syntactic-element'."
1318 "Return the anchor position in LANGELEM, or nil if there is none.
1322 form as used in `c-syntactic-element'."
1328 "Return the column of the anchor position in LANGELEM.
1329 Also move the point to that position unless PRESERVE-POINT is non-nil.
1333 form as used in `c-syntactic-element'."
1345 "Return the secondary position in LANGELEM, or nil if there is none.
1348 in `c-syntactic-element'. It may also be a cons cell as passed in the
1349 first argument to lineup functions, but then the returned value always
1350 will be nil."
1354 ;; Do whatever is necessary to keep the region active in XEmacs.
1355 ;; This is not needed for Emacs.
1369 the corresponding symbol."
1375 c-buffer-is-cc-mode))
1380 the value of the variable with that name."
1384 "Return non-nil if position POS in the current buffer has any of the
1385 faces in the list FACES."
1392 pos-faces)
1396 ;; Return t if FACENAME is the name of a face. This method is
1397 ;; necessary since facep in XEmacs only returns t for the actual
1398 ;; face objects (while it's only their names that are used just
1399 ;; about anywhere else) without providing a predicate that tests
1400 ;; face names.
1404 "Like `concat' on LIST, but separate each element with SEPARATOR.
1405 Notably, null elements in LIST are ignored."
1409 "Make a regexp that matches all the strings the list.
1410 Duplicates and nil elements in the list are removed. The resulting
1411 regexp may contain zero or more submatch expressions.
1413 If ADORN is t there will be at least one submatch and the first
1414 surrounds the matched alternative, and the regexp will also not match
1415 a prefix of any identifier. Adorned regexps cannot be appended. The
1416 language variable `c-nonsymbol-key' is used to make the adornment.
1418 A value 'appendable for ADORN is like above, but all alternatives in
1420 instead, so that the regexp remains appendable. Note that this
1421 variant doesn't always guarantee that an identifier prefix isn't
1422 matched since the symbol constituent '_' is normally considered a
1425 The optional MODE specifies the language to get `c-nonsymbol-key' from
1426 when it's needed. The default is the current language taken from
1427 `c-buffer-is-cc-mode'."
1438 ;; This is kludgy but it works: Search for a string that
1439 ;; doesn't occur in any word in LIST. Append it to all
1440 ;; the alternatives where we want to add \>. Run through
1441 ;; `regexp-opt' and then replace it with \>.
1445 pos list)
1449 nil)
1450 t))
1452 found))
1466 ;; Emacs 20 and XEmacs (all versions so far) has a buggy
1467 ;; regexp-opt that doesn't always cope with strings containing
1468 ;; newlines. This kludge doesn't handle shy parens correctly
1469 ;; so we can't advice regexp-opt directly with it.
1493 ;; Add our own grouping parenthesis around re instead of
1494 ;; passing adorn to `regexp-opt', since in XEmacs it makes the
1495 ;; top level grouping "shy".
1504 re)))
1506 ;; Produce a regexp that matches nothing.
1514 "Make a character alternative string from the list of characters CHARS.
1515 The returned string is of the type that can be used with
1516 `skip-chars-forward' and `skip-chars-backward'. If INVERTED is
1517 non-nil, a caret is prepended to invert the set."
1518 ;; This function ought to be in the elisp core somewhere.
1524 ;; Quoting necessary (this method only works in the skip
1525 ;; functions).
1528 ;; Check for range.
1536 str))
1538 ;; Leftovers from (X)Emacs 19 compatibility.
1542 \f
1543 ;; Figure out what features this Emacs has
1551 ;; I've no idea what this actually is, but it's legacy. /mast
1554 ;; XEmacs uses 8-bit modify-syntax-entry flags.
1555 ;; Emacs uses a 1-bit flag. We will have to set up our
1556 ;; syntax tables differently to handle this.
1558 entry)
1561 ;; Emacs
1564 ;; In Emacs, table entries are cons cells
1566 ;; XEmacs
1569 ;; incompatible
1574 list)))
1576 ;; Check whether beginning/end-of-defun call
1577 ;; beginning/end-of-defun-function nicely, passing through the
1578 ;; argument and respecting the return code.
1599 parse-sexp-lookup-properties
1600 parse-sexp-ignore-comments
1601 lookup-syntax-properties)
1605 ;; For some reason we have to set some of these after the
1606 ;; buffer has been made current. (Specifically,
1607 ;; `parse-sexp-ignore-comments' in Emacs 21.)
1609 parse-sexp-ignore-comments t
1610 lookup-syntax-properties t)
1612 ;; Find out if the `syntax-table' text property works.
1623 "CC Mode is incompatible with this version of Emacs - "
1624 "support for the `syntax-table' text property "
1627 ;; Find out if generic comment delimiters work.
1633 ;; Find out if generic string delimiters work.
1639 ;; See if POSIX char classes work.
1641 ;; All versions of Emacs 21 so far haven't fixed
1642 ;; char classes in `skip-chars-forward' and
1643 ;; `skip-chars-backward'.
1652 ;; See if `open-paren-in-column-0-is-defun-start' exists and
1653 ;; isn't buggy (Emacs >= 21.4).
1661 ;; XEmacs. Afaik this is currently an Emacs-only
1662 ;; feature, but it's good to be prepared.
1666 ;; Emacs
1679 ;; See if `parse-partial-sexp' returns the eighth element.
1684 "CC Mode is incompatible with this version of Emacs - "
1687 ;;(message "c-emacs-features: %S" list)
1688 list)
1689 "A list of certain features in the (X)Emacs you are using.
1690 There are many flavors of Emacs out there, each with different
1691 features supporting those needed by CC Mode. The following values
1692 might be present:
1694 '8-bit 8 bit syntax entry flags (XEmacs style).
1695 '1-bit 1 bit syntax entry flags (Emacs style).
1696 'argumentative-bod-function beginning-of-defun passes ARG through
1697 to a non-null beginning-of-defun-function. It is assumed
1698 the end-of-defun does the same thing.
1699 'syntax-properties It works to override the syntax for specific characters
1700 in the buffer with the 'syntax-table property. It's
1701 always set - CC Mode no longer works in emacsen without
1702 this feature.
1703 'gen-comment-delim Generic comment delimiters work
1704 (i.e. the syntax class `!').
1705 'gen-string-delim Generic string delimiters work
1706 (i.e. the syntax class `|').
1707 'pps-extended-state `parse-partial-sexp' returns a list with at least 10
1708 elements, i.e. it contains the position of the start of
1709 the last comment or string. It's always set - CC Mode
1710 no longer works in emacsen without this feature.
1711 'posix-char-classes The regexp engine understands POSIX character classes.
1712 'col-0-paren It's possible to turn off the ad-hoc rule that a paren
1713 in column zero is the start of a defun.
1714 'infodock This is Infodock (based on XEmacs).
1718 \f
1719 ;;; Some helper constants.
1721 ;; If the regexp engine supports POSIX char classes then we can use
1722 ;; them to handle extended charsets correctly.
1736 \f
1737 ;;; System for handling language dependent constants.
1739 ;; This is used to set various language dependent data in a flexible
1740 ;; way: Language constants can be built from the values of other
1741 ;; language constants, also those for other languages. They can also
1742 ;; process the values of other language constants uniformly across all
1743 ;; the languages. E.g. one language constant can list all the type
1744 ;; keywords in each language, and another can build a regexp for each
1745 ;; language from those lists without code duplication.
1746 ;;
1747 ;; Language constants are defined with `c-lang-defconst', and their
1748 ;; value forms (referred to as source definitions) are evaluated only
1749 ;; on demand when requested for a particular language with
1750 ;; `c-lang-const'. It's therefore possible to refer to the values of
1751 ;; constants defined later in the file, or in another file, just as
1752 ;; long as all the relevant `c-lang-defconst' have been loaded when
1753 ;; `c-lang-const' is actually evaluated from somewhere else.
1754 ;;
1755 ;; `c-lang-const' forms are also evaluated at compile time and
1756 ;; replaced with the values they produce. Thus there's no overhead
1757 ;; for this system when compiled code is used - only the values
1758 ;; actually used in the code are present, and the file(s) containing
1759 ;; the `c-lang-defconst' forms don't need to be loaded at all then.
1760 ;; There are however safeguards to make sure that they can be loaded
1761 ;; to get the source definitions for the values if there's a mismatch
1762 ;; in compiled versions, or if `c-lang-const' is used uncompiled.
1763 ;;
1764 ;; Note that the source definitions in a `c-lang-defconst' form are
1765 ;; compiled into the .elc file where it stands; there's no need to
1766 ;; load the source file to get it.
1767 ;;
1768 ;; See cc-langs.el for more details about how this system is deployed
1769 ;; in CC Mode, and how the associated language variable system
1770 ;; (`c-lang-defvar') works. That file also contains a lot of
1771 ;; examples.
1774 "Declare a new language in the language dependent variable system.
1775 This is intended to be used by modes that inherit CC Mode to add new
1776 languages. It should be used at the top level before any calls to
1777 `c-lang-defconst'. MODE is the mode name symbol for the new language,
1778 and BASE-MODE is the mode name symbol for the language in CC Mode that
1779 is to be the template for the new mode.
1781 The exact effect of BASE-MODE is to make all language constants that
1782 haven't got a setting in the new language fall back to their values in
1783 BASE-MODE. It does not have any effect outside the language constant
1784 system."
1793 ;; This obarray is a cache to keep track of the language constants
1794 ;; defined by `c-lang-defconst' and the evaluated values returned by
1795 ;; `c-lang-const'. It's mostly used at compile time but it's not
1796 ;; stored in compiled files.
1797 ;;
1798 ;; The obarray contains all the language constants as symbols. The
1799 ;; value cells hold the evaluated values as alists where each car is
1800 ;; the mode name symbol and the corresponding cdr is the evaluated
1801 ;; value in that mode. The property lists hold the source definitions
1802 ;; and other miscellaneous data. The obarray might also contain
1803 ;; various other symbols, but those don't have any variable bindings.
1808 ;; Return the base name of the current file.
1811 ;; Being loaded.
1812 load-file-name)
1815 ;; Being compiled.
1816 byte-compile-dest-file)
1818 ;; Being evaluated interactively.
1825 "Can be used inside a VAL in `c-lang-defconst' to evaluate FORM
1826 immediately, i.e. at the same time as the `c-lang-defconst' form
1827 itself is evaluated."
1828 ;; Evaluate at macro expansion time, i.e. in the
1829 ;; `cl-macroexpand-all' inside `c-lang-defconst'.
1832 ;; Only used at compile time - suppress "might not be defined at runtime".
1836 "Set the language specific values of the language constant NAME.
1837 The second argument can optionally be a docstring. The rest of the
1838 arguments are one or more repetitions of LANG VAL where LANG specifies
1839 the language(s) that VAL applies to. LANG is the name of the
1841 of such language names, or `t' for all languages. VAL is a form to
1842 evaluate to get the value.
1844 If LANG isn't `t' or one of the core languages in CC Mode, it must
1845 have been declared with `c-add-language'.
1847 Neither NAME, LANG nor VAL are evaluated directly - they should not be
1848 quoted. `c-lang-defconst-eval-immediately' can however be used inside
1849 VAL to evaluate parts of it directly.
1851 When VAL is evaluated for some language, that language is temporarily
1852 made current so that `c-lang-const' without an explicit language can
1853 be used inside VAL to refer to the value of a language constant in the
1854 same language. That is particularly useful if LANG is `t'.
1856 VAL is not evaluated right away but rather when the value is requested
1857 with `c-lang-const'. Thus it's possible to use `c-lang-const' inside
1858 VAL to refer to language constants that haven't been defined yet.
1859 However, if the definition of a language constant is in another file
1860 then that file must be loaded \(at compile time) before it's safe to
1861 reference the constant.
1863 The assignments in ARGS are processed in sequence like `setq', so
1864 \(c-lang-const NAME) may be used inside a VAL to refer to the last
1865 assigned value to this language constant, or a value that it has
1866 gotten in another earlier loaded file.
1868 To work well with repeated loads and interactive reevaluation, only
1869 one `c-lang-defconst' for each NAME is permitted per file. If there
1870 already is one it will be completely replaced; the value in the
1871 earlier definition will not affect `c-lang-const' on the same
1872 constant. A file is identified by its base name."
1875 ;; Make `c-lang-const' expand to a straightforward call to
1876 ;; `c-get-lang-constant' in `cl-macroexpand-all' below.
1877 ;;
1878 ;; (The default behavior, i.e. to expand to a call inside
1879 ;; `eval-when-compile' should be equivalent, since that macro
1880 ;; should only expand to its content if it's used inside a
1881 ;; form that's already evaluated at compile time. It's
1882 ;; however necessary to use our cover macro
1883 ;; `cc-eval-when-compile' due to bugs in `eval-when-compile',
1884 ;; and it expands to a bulkier form that in this case only is
1885 ;; unnecessary garbage that we don't want to store in the
1886 ;; language constant source definitions.)
1889 bindings
1890 pre-files)
1896 ;; The docstring is hardly used anywhere since there's no normal
1897 ;; symbol to attach it to. It's primarily for getting the right
1898 ;; format in the source.
1905 ;; Rework ARGS to an association list to make it easier to handle.
1906 ;; It's reversed at the same time to make it easier to implement
1907 ;; the demand-driven (i.e. reversed) evaluation in `c-lang-const'.
1924 val)
1931 ;; Emacs has a weird bug where it seems to fail to read
1932 ;; backquote lists from byte compiled files correctly (,@
1933 ;; forms, to be specific), so make sure the bindings in the
1934 ;; expansion below don't contain any backquote stuff.
1935 ;; (XEmacs handles it correctly and doesn't need this for that
1936 ;; reason, but we also use this expansion handle
1937 ;; `c-lang-defconst-eval-immediately' and to register
1938 ;; dependencies on the `c-lang-const's in VAL.)
1944 ;; Compile in the other files that have provided source
1945 ;; definitions for this symbol, to make sure the order in the
1946 ;; `source' property is correct even when files are loaded out of
1947 ;; order.
1949 ;; Reverse to get the right load order.
1957 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1958 ; '
1963 ;; Used by `c-lang-defconst'.
1972 ;;(when (cdr-safe elem)
1973 ;; (message "Language constant %s redefined in %S" name file))
1975 ;; Note that the order in the source alist is relevant. Like how
1976 ;; `c-lang-defconst' reverses the bindings, this reverses the
1977 ;; order between files so that the last to evaluate comes first.
1987 ;; Bind the symbol as a variable, or clear any earlier evaluated
1988 ;; value it has.
1991 ;; Clear the evaluated values that depend on this source.
1994 ptr)
2007 name))
2010 "Get the mode specific value of the language constant NAME in language LANG.
2011 LANG is the name of the language, i.e. the mode name without the
2013 `c-lang-defvar', LANG may be left out to refer to the current
2014 language. NAME and LANG are not evaluated so they should not be
2015 quoted."
2023 mode source-files args)
2029 "Unknown language %S since it got no `c-mode-prefix' property"
2033 ;; No need to find out the source file(s) when we evaluate
2034 ;; immediately since all the info is already there in the
2035 ;; `source' property.
2040 ;; Get the source file(s) that must be loaded to get the value
2041 ;; of the constant. If the symbol isn't defined yet we assume
2042 ;; that its definition will come later in this file, and thus
2043 ;; are no file dependencies needed.
2045 ;; Reverse to get the right load order.
2049 nil ; Exclude our own file.
2053 ;; Make some effort to do a compact call to
2054 ;; `c-get-lang-constant' since it will be compiled in.
2058 args)))
2063 load-in-progress
2066 ;; Either a straight call is requested in the context, or
2067 ;; we're in an "uncontrolled" context and got no language,
2068 ;; or we're not being byte compiled so the compile time
2069 ;; stuff below is unnecessary.
2072 ;; Being compiled. If the loading and compiling version is
2073 ;; the same we use a value that is evaluated at compile time,
2074 ;; otherwise it's evaluated at runtime.
2083 ;; Used by `c-lang-const'.
2091 elem
2095 ;; Record the dependencies between this symbol and the one we're
2096 ;; being evaluated in.
2101 ;; Make sure the source files have entries on the `source'
2102 ;; property so that loading will take place when necessary.
2107 ;; Might pull in more definitions which affect the value. The
2108 ;; clearing of dependent values etc is done when the
2109 ;; definition is encountered during the load; this is just to
2110 ;; jump past the check for a cached value below.
2118 ;; Check if an evaluation of this symbol is already underway.
2119 ;; In that case we just continue with the "assignment" before
2120 ;; the one currently being evaluated, thereby creating the
2121 ;; illusion if a `setq'-like sequence of assignments.
2126 ;; Append `c-lang-constants-under-evaluation' even if an
2127 ;; earlier entry is found. It's only necessary to get
2128 ;; the recording of dependencies above correct.
2132 value
2133 ;; Make sure the recursion limits aren't very low
2134 ;; since the `c-lang-const' dependencies can go deep.
2141 ;; First try the original mode but don't accept an
2142 ;; entry matching all languages since the fallback
2143 ;; mode might have an explicit entry before that.
2146 c-lang-constants)
2147 ;; Try again with the fallback mode from the
2148 ;; original position. Note that
2149 ;; `c-buffer-is-cc-mode' still is the real mode if
2150 ;; language parameterization takes place.
2153 fallback t name))
2154 c-lang-constants)))
2155 ;; A simple lookup with no fallback mode.
2158 c-lang-constants))
2160 "`%s' got no (prior) value in %s (might be a cyclic reference)"
2161 name mode))
2166 ;; Print a message to aid in locating the error. We don't
2167 ;; print the error itself since that will be done later by
2168 ;; some caller higher up.
2170 sym mode)
2175 value))))
2178 ;; Find the first assignment entry that applies to MODE at or after
2179 ;; SOURCE-POS. If MATCH-ANY-LANG is non-nil, entries with `t' as
2180 ;; the language list are considered to match, otherwise they don't.
2181 ;; On return SOURCE-POS is updated to point to the next assignment
2182 ;; after the returned one. If no assignment is found,
2183 ;; `c-lang-constants' is returned as a magic value.
2184 ;;
2185 ;; SOURCE-POS is a vector that points out a specific assignment in
2186 ;; the double alist that's used in the `source' property. The first
2187 ;; element is the position in the top alist which is indexed with
2188 ;; the source files, and the second element is the position in the
2189 ;; nested bindings alist.
2190 ;;
2191 ;; NAME is only used for error messages.
2196 assignment)
2199 t
2200 ;; Handled the last assignment from one file, begin on the
2201 ;; next. Due to the check in `c-lang-defconst', we know
2202 ;; there's at least one.
2207 ;; The file containing the source definitions has not
2208 ;; been loaded.
2211 ;;(message (concat "Loading %s to get the source "
2212 ;; "value for language constant %s")
2213 ;; file name)
2217 ;; The load didn't fill in the source for the
2218 ;; constant as expected. The situation is
2219 ;; probably that a derived mode was written for
2220 ;; and compiled with another version of CC Mode,
2221 ;; and the requested constant isn't in the
2222 ;; currently loaded one. Put in a dummy
2223 ;; assignment that matches no language.
2228 t))
2236 match-any-lang)
2239 c-lang-constants)))
2242 ;; `c-major-mode-is' expands to a call to this function inside
2243 ;; `c-lang-defconst'. Here we also match the mode(s) against any
2244 ;; fallback modes for the one in `c-buffer-is-cc-mode', so that
2245 ;; e.g. (c-major-mode-is 'c++-mode) is true in a derived language
2246 ;; that has c++-mode as base mode.
2253 nil)
2255 match))
2257 \f
2260 ;;; cc-defs.el ends here