| blob | 594ff053d4448e23bd6ab667c9ea3f1fb265d4f0 |
1 ;;; cc-defs.el --- compile time definitions for CC Mode
3 ;; Copyright (C) 1985, 1987, 1992-2014 Free Software Foundation, Inc.
5 ;; Authors: 2003- Alan Mackenzie
6 ;; 1998- Martin Stjernholm
7 ;; 1992-1999 Barry A. Warsaw
8 ;; 1987 Dave Detlefs
9 ;; 1987 Stewart Clamen
10 ;; 1985 Richard M. Stallman
11 ;; Maintainer: bug-cc-mode@gnu.org
12 ;; Created: 22-Apr-1997 (split from cc-mode.el)
13 ;; Keywords: c languages
14 ;; Package: cc-mode
16 ;; This file is part of GNU Emacs.
18 ;; GNU Emacs is free software: you can redistribute it and/or modify
19 ;; it under the terms of the GNU General Public License as published by
20 ;; the Free Software Foundation, either version 3 of the License, or
21 ;; (at your option) any later version.
23 ;; GNU Emacs is distributed in the hope that it will be useful,
24 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
25 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
26 ;; GNU General Public License for more details.
28 ;; You should have received a copy of the GNU General Public License
29 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
31 ;;; Commentary:
33 ;; This file contains macros, defsubsts, and various other things that
34 ;; must be loaded early both during compilation and at runtime.
36 ;;; Code:
43 load-path)))
49 ;; Silence the compiler.
59 \f
60 ;; cc-fix.el contains compatibility macros that should be used if
61 ;; needed.
67 ; (eval-after-load "font-lock" ; 2006-07-09. font-lock is now preloaded
68 ; '
70 ; to make the call to f-l-c-k throw an error.
77 ;; The above takes care of the delayed loading, but this is necessary
78 ;; to ensure correct byte compilation.
86 font-lock-keywords)))
89 \f
90 ;;; Variables also used at compile time.
96 ;; A little more compact and faster in comparisons.
99 "Non-nil for all buffers with a major mode derived from CC Mode.
100 Otherwise, this variable is nil. I.e. this variable is non-nil for
101 `c-mode', `c++-mode', `objc-mode', `java-mode', `idl-mode',
102 `pike-mode', `awk-mode', and any other non-CC Mode mode that calls
103 `c-initialize-cc-mode'. The value is the mode symbol itself
104 \(i.e. `c-mode' etc) of the original CC Mode mode, or just t if it's
108 ;; Have to make `c-buffer-is-cc-mode' permanently local so that it
109 ;; survives the initialization of the derived mode.
112 \f
113 ;; The following is used below during compilation.
118 "Like `progn', but evaluates the body at compile time.
119 The result of the body appears to the compiler as a quoted constant.
121 This variant works around bugs in `eval-when-compile' in various
122 \(X)Emacs versions. See cc-defs.el for details."
125 ;; XEmacs 21.4.6 has a bug in `eval-when-compile' in that it
126 ;; evaluates its body at macro expansion time if it's nested
127 ;; inside another `eval-when-compile'. So we use a dynamically
128 ;; bound variable to avoid nesting them.
132 ;; In all (X)Emacsen so far, `eval-when-compile' byte compiles
133 ;; its contents before evaluating it. That can cause forms to
134 ;; be compiled in situations they aren't intended to be
135 ;; compiled.
136 ;;
137 ;; Example: It's not possible to defsubst a primitive, e.g. the
138 ;; following will produce an error (in any emacs flavor), since
139 ;; `nthcdr' is a primitive function that's handled specially by
140 ;; the byte compiler and thus can't be redefined:
141 ;;
142 ;; (defsubst nthcdr (val) val)
143 ;;
144 ;; `defsubst', like `defmacro', needs to be evaluated at
145 ;; compile time, so this will produce an error during byte
146 ;; compilation.
147 ;;
148 ;; CC Mode occasionally needs to do things like this for
149 ;; cross-emacs compatibility. It therefore uses the following
150 ;; to conditionally do a `defsubst':
151 ;;
152 ;; (eval-when-compile
153 ;; (if (not (fboundp 'foo))
154 ;; (defsubst foo ...)))
155 ;;
156 ;; But `eval-when-compile' byte compiles its contents and
157 ;; _then_ evaluates it (in all current emacs versions, up to
158 ;; and including Emacs 20.6 and XEmacs 21.1 as of this
159 ;; writing). So this will still produce an error, since the
160 ;; byte compiler will get to the defsubst anyway. That's
161 ;; arguably a bug because the point with `eval-when-compile' is
162 ;; that it should evaluate rather than compile its contents.
163 ;;
164 ;; We get around it by expanding the body to a quoted
165 ;; constant that we eval. That otoh introduce a problem in
166 ;; that a returned lambda expression doesn't get byte
167 ;; compiled (even if `function' is used).
172 \f
173 ;;; Macros.
176 "Return the value of certain commonly referenced POSITIONs relative to POINT.
177 The current point is used if POINT isn't specified. POSITION can be
178 one of the following symbols:
180 `bol' -- beginning of line
181 `eol' -- end of line
182 `bod' -- beginning of defun
183 `eod' -- end of defun
184 `boi' -- beginning of indentation
185 `ionl' -- indentation of next line
186 `iopl' -- indentation of previous line
187 `bonl' -- beginning of next line
188 `eonl' -- end of next line
189 `bopl' -- beginning of previous line
190 `eopl' -- end of previous line
191 `bosws' -- beginning of syntactic whitespace
192 `eosws' -- end of syntactic whitespace
194 If the referenced position doesn't exist, the closest accessible point
195 to it is returned. This function does not modify the point or the mark."
297 ;; The bulk of this should perhaps be in a function to avoid large
298 ;; expansions, but this case is not used anywhere in CC Mode (and
299 ;; probably not anywhere else either) so we only have it to be on
300 ;; the safe side.
331 ;; Return t when the region is active. The determination of region
332 ;; activeness is different in both Emacs and XEmacs.
333 ;; FIXME? Emacs has region-active-p since 23.1, so maybe this test
334 ;; should be updated.
336 ;; Emacs.
337 'mark-active
338 ;; XEmacs.
342 ;; Activate the region if ACTIVE is non-nil, deactivate it
343 ;; otherwise. Covers the differences between Emacs and XEmacs.
345 ;; XEmacs.
349 ;; Emacs.
353 "Delete the text between START and END and return it."
355 ;; Emacs 21.1 and later
357 ;; XEmacs and Emacs 20.x
363 ;; safely execute BODY, return nil if an error occurred
370 ;; In Emacs, a character is an integer. In XEmacs, a character is a
371 ;; type distinct from an integer. Sometimes we need to convert integers to
372 ;; characters. `c-int-to-char' makes this conversion, if necessary.
375 integer))
378 ;; The last character just typed. Note that `last-command-event' exists in
379 ;; both Emacs and XEmacs, but with confusingly different meanings.
381 'last-command-char
385 ;; Get the regular expression `sentence-end'.
387 ;; Emacs 22:
389 ;; Emacs <22 + XEmacs
393 ;; Get the default value of the variable sentence end.
395 ;; Emacs 22:
397 ;; Emacs <22 + XEmacs
400 ;; The following is essentially `save-buffer-state' from lazy-lock.el.
401 ;; It ought to be a standard macro.
403 "Bind variables according to VARLIST (in `let*' style) and eval BODY,
404 then restore the buffer state under the assumption that no significant
405 modification has been made in BODY. A change is considered
406 significant if it affects the buffer text in any way that isn't
407 completely restored again. Changes in text properties like `face' or
408 `syntax-table' are considered insignificant. This macro allows text
409 properties to be changed, even in a read-only buffer.
411 This macro should be placed around all calculations which set
413 known to be writable. That way, these text properties remain set
414 even if the user undoes the command which set them.
417 changes \(like adding a newline to calculate a text-property then
418 deleting it again\), so that the user never sees them on his
419 `buffer-undo-list'. See also `c-tentative-buffer-changes'.
421 However, any user-visible changes to the buffer \(like auto-newlines\)
422 must not be within a `c-save-buffer-state', since the user then
423 wouldn't be able to undo them.
425 The return value is the value of the last form in BODY."
428 before-change-functions after-change-functions
429 deactivate-mark
430 buffer-file-name buffer-file-truename ; Prevent primitives checking
431 ; for file modification
441 "Eval BODY and optionally restore the buffer contents to the state it
442 was in before BODY. Any changes are kept if the last form in BODY
443 returns non-nil. Otherwise it's undone using the undo facility, and
444 various other buffer state that might be affected by the changes is
445 restored. That includes the current buffer, point, mark, mark
446 activation \(similar to `save-excursion'), and the modified state.
447 The state is also restored if BODY exits nonlocally.
449 If BODY makes a change that unconditionally is undone then wrap this
450 macro inside `c-save-buffer-state'. That way the change can be done
451 even when the buffer is read-only, and without interference from
452 various buffer change hooks."
454 -tnt-chng-state)
456 ;; Insert an undo boundary for use with `undo-more'. We
457 ;; don't use `undo-boundary' since it doesn't insert one
458 ;; unconditionally.
466 ;; Used internally in `c-tentative-buffer-changes'.
469 ;; No need to use markers for the point and mark; if the
470 ;; undo got out of synch we're hosed anyway.
477 ;; Used internally in `c-tentative-buffer-changes'.
481 ;; No change was done after all.
485 ;; Find and remove the undo boundary.
491 ;; `primitive-undo' will remove the boundary.
496 saved-undo-list))))
508 "Forward skip over syntactic whitespace.
509 Syntactic whitespace is defined as whitespace characters, comments,
510 and preprocessor directives. However if point starts inside a comment
511 or preprocessor directive, the content of it is not treated as
512 whitespace.
514 LIMIT sets an upper limit of the forward movement, if specified. If
515 LIMIT or the end of the buffer is reached inside a comment or
516 preprocessor directive, the point will be left there.
518 Note that this function might do hidden buffer changes. See the
519 comment at the start of cc-engine.el for more info."
527 "Backward skip over syntactic whitespace.
528 Syntactic whitespace is defined as whitespace characters, comments,
529 and preprocessor directives. However if point starts inside a comment
530 or preprocessor directive, the content of it is not treated as
531 whitespace.
533 LIMIT sets a lower limit of the backward movement, if specified. If
534 LIMIT is reached inside a line comment or preprocessor directive then
535 the point is moved into it past the whitespace at the end.
537 Note that this function might do hidden buffer changes. See the
538 comment at the start of cc-engine.el for more info."
546 "Move forward across COUNT balanced expressions.
547 A negative COUNT means move backward. Signal an error if the move
548 fails for any reason.
550 This is like `forward-sexp' except that it isn't interactive and does
551 not do any user friendly adjustments of the point and that it isn't
552 susceptible to user configurations such as disabling of signals in
553 certain situations."
558 "See `c-forward-sexp' and reverse directions."
563 "Like `scan-lists' but returns nil instead of signaling errors
564 for unbalanced parens.
566 A limit for the search may be given. FROM is assumed to be on the
567 right side of it."
581 res)))
583 \f
584 ;; Wrappers for common scan-lists cases, mainly because it's almost
585 ;; impossible to get a feel for how that function works.
588 "Move backward across one balanced group of parentheses.
590 Return POINT when we succeed, NIL when we fail. In the latter case, leave
591 point unmoved."
594 endpos)))
597 "Move backward across one balanced group of parentheses.
599 Return POINT when we succeed, NIL when we fail. In the latter case, leave
600 point unmoved."
603 endpos)))
606 "Return the first position after the list sexp containing POS,
607 or nil if no such position exists. The point is used if POS is left out.
609 A limit for the search may be given. The start position is assumed to
610 be before it."
614 "Return the position of the start of the list sexp containing POS,
615 or nil if no such position exists. The point is used if POS is left out.
617 A limit for the search may be given. The start position is assumed to
618 be after it."
622 "Return the first position inside the first list sexp after POS,
623 or nil if no such position exists. The point is used if POS is left out.
625 A limit for the search may be given. The start position is assumed to
626 be before it."
630 "Return the last position inside the last list sexp before POS,
631 or nil if no such position exists. The point is used if POS is left out.
633 A limit for the search may be given. The start position is assumed to
634 be after it."
638 "Move the point to the first position after the list sexp containing POS,
639 or containing the point if POS is left out. Return t if such a
640 position exists, otherwise nil is returned and the point isn't moved.
642 A limit for the search may be given. The start position is assumed to
643 be before it."
649 res)))
652 "Move the point to the position of the start of the list sexp containing POS,
653 or containing the point if POS is left out. Return t if such a
654 position exists, otherwise nil is returned and the point isn't moved.
656 A limit for the search may be given. The start position is assumed to
657 be after it."
663 res)))
666 "Move the point to the first position inside the first list sexp after POS,
667 or before the point if POS is left out. Return t if such a position
668 exists, otherwise nil is returned and the point isn't moved.
670 A limit for the search may be given. The start position is assumed to
671 be before it."
677 res)))
680 "Move the point to the last position inside the last list sexp before POS,
681 or before the point if POS is left out. Return t if such a position
682 exists, otherwise nil is returned and the point isn't moved.
684 A limit for the search may be given. The start position is assumed to
685 be after it."
691 res)))
693 \f
695 ;; Wrapper around beginning-of-defun.
696 ;;
697 ;; NOTE: This function should contain the only explicit use of
698 ;; beginning-of-defun in CC Mode. Eventually something better than
699 ;; b-o-d will be available and this should be the only place the
700 ;; code needs to change. Everything else should use
701 ;; (c-beginning-of-defun-1)
702 ;;
703 ;; This is really a bit too large to be a macro but that isn't a
704 ;; problem as long as it only is used in one place in
705 ;; `c-parse-state'.
709 c-enable-xemacs-performance-kludge-p)
711 ;; XEmacs only. This can improve the performance of
712 ;; c-parse-state to between 3 and 60 times faster when
713 ;; braces are hung. It can also degrade performance by
714 ;; about as much when braces are not hung.
716 pos)
726 ;; unbalanced parenthesis, while invalid C code,
727 ;; shouldn't cause an infloop! See unbal.c
729 ;; Punt!
736 ))
738 ;; Emacs, which doesn't have buffer-syntactic-context-depth
741 ;; if defun-prompt-regexp is non-nil, b-o-d won't leave us at the
742 ;; open brace.
747 \f
748 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
749 ;; V i r t u a l S e m i c o l o n s
750 ;;
751 ;; In most CC Mode languages, statements are terminated explicitly by
752 ;; semicolons or closing braces. In some of the CC modes (currently AWK Mode
753 ;; and certain user-specified #define macros in C, C++, etc. (November 2008)),
754 ;; statements are (or can be) terminated by EOLs. Such a statement is said to
755 ;; be terminated by a "virtual semicolon" (VS). A statement terminated by an
756 ;; actual semicolon or brace is never considered to have a VS.
757 ;;
758 ;; The indentation engine (or whatever) tests for a VS at a specific position
759 ;; by invoking the macro `c-at-vsemi-p', which in its turn calls the mode
760 ;; specific function (if any) which is the value of the language variable
761 ;; `c-at-vsemi-p-fn'. This function should only use "low-level" features of
762 ;; CC Mode, i.e. features which won't trigger infinite recursion. ;-) The
763 ;; actual details of what constitutes a VS in a language are thus encapsulated
764 ;; in code specific to that language (e.g. cc-awk.el). `c-at-vsemi-p' returns
765 ;; non-nil if point (or the optional parameter POS) is at a VS, nil otherwise.
766 ;;
767 ;; The language specific function might well do extensive analysis of the
768 ;; source text, and may use a caching scheme to speed up repeated calls.
769 ;;
770 ;; The "virtual semicolon" lies just after the last non-ws token on the line.
771 ;; Like POINT, it is considered to lie between two characters. For example,
772 ;; at the place shown in the following AWK source line:
773 ;;
774 ;; kbyte = 1024 # 1000 if you're not picky
775 ;; ^
776 ;; |
777 ;; Virtual Semicolon
778 ;;
779 ;; In addition to `c-at-vsemi-p-fn', a mode may need to supply a function for
780 ;; `c-vsemi-status-unknown-p-fn'. The macro `c-vsemi-status-unknown-p' is a
781 ;; rather recondite kludge. It exists because the function
782 ;; `c-beginning-of-statement-1' sometimes tests for VSs as an optimization,
783 ;; but `c-at-vsemi-p' might well need to call `c-beginning-of-statement-1' in
784 ;; its calculations, thus potentially leading to infinite recursion.
785 ;;
786 ;; The macro `c-vsemi-status-unknown-p' resolves this problem; it may return
787 ;; non-nil at any time; returning nil is a guarantee that an immediate
788 ;; invocation of `c-at-vsemi-p' at point will NOT call
789 ;; `c-beginning-of-statement-1'. `c-vsemi-status-unknown-p' may not itself
790 ;; call `c-beginning-of-statement-1'.
791 ;;
792 ;; The macro `c-vsemi-status-unknown-p' will typically check the caching
793 ;; scheme used by the `c-at-vsemi-p-fn', hence the name - the status is
794 ;; "unknown" if there is no cache entry current for the line.
795 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
798 ;; Is there a virtual semicolon (not a real one or a }) at POS (defaults to
799 ;; point)? Always returns nil for languages which don't have Virtual
800 ;; semicolons.
801 ;; This macro might do hidden buffer changes.
806 ;; Return NIL only if it can be guaranteed that an immediate
807 ;; (c-at-vsemi-p) will NOT call c-beginning-of-statement-1. Otherwise,
808 ;; return non-nil. (See comments above). The function invoked by this
809 ;; macro MUST NOT UNDER ANY CIRCUMSTANCES itself call
810 ;; c-beginning-of-statement-1.
811 ;; Languages which don't have EOL terminated statements always return NIL
812 ;; (they _know_ there's no vsemi ;-).
815 \f
817 ;; Formats an error message for the echo area and dings, i.e. like
818 ;; `error' but doesn't abort.
824 ;; Temporarily switches to the specified syntax table in a failsafe
825 ;; way to execute code.
826 ;; Maintainers' note: If TABLE is `c++-template-syntax-table', DON'T call
827 ;; any forms inside this that call `c-parse-state'. !!!!
837 "Skip over any whitespace following point.
838 This function skips over horizontal and vertical whitespace and line
839 continuations."
843 ;; skip-syntax-* doesn't count \n as whitespace..
858 "Skip over any whitespace preceding point.
859 This function skips over horizontal and vertical whitespace and line
860 continuations."
864 ;; skip-syntax-* doesn't count \n as whitespace..
880 "Return non-nil if the current CC Mode major mode is MODE.
881 MODE is either a mode symbol or a list of mode symbols."
884 ;; Inside a `c-lang-defconst'.
898 \f
899 ;; Macros/functions to handle so-called "char properties", which are
900 ;; properties set on a single character and that never spread to any
901 ;; other characters.
904 ;; Constant used at compile time to decide whether or not to use
905 ;; XEmacs extents. Check all the extent functions we'll use since
906 ;; some packages might add compatibility aliases for some of them in
907 ;; Emacs.
916 ;; `c-put-char-property' is complex enough in XEmacs and Emacs < 21 to
917 ;; make it a function.
921 ;; XEmacs.
931 end-open t)))))))))
934 ;; In Emacs < 21 we have to mess with the `rear-nonsticky' property.
941 'rear-nonsticky
943 ;; This won't be used for anything.
948 ;; Put the given property with the given value on the character at
949 ;; POS and make it front and rear nonsticky, or start and end open
950 ;; in XEmacs vocabulary. If the character already has the given
951 ;; property then the value is replaced, and the behavior is
952 ;; undefined if that property has been put by some other function.
953 ;; PROPERTY is assumed to be constant.
954 ;;
955 ;; If there's a `text-property-default-nonsticky' variable (Emacs
956 ;; 21) then it's assumed that the property is present on it.
957 ;;
958 ;; This macro does a hidden buffer change.
962 ;; XEmacs and Emacs < 21.
964 ;; In Emacs 21 we got the `rear-nonsticky' property covered
965 ;; by `text-property-default-nonsticky'.
970 ;; Get the value of the given property on the character at POS if
971 ;; it's been put there by `c-put-char-property'. PROPERTY is
972 ;; assumed to be constant.
975 ;; XEmacs.
978 ;; Emacs.
981 ;; `c-clear-char-property' is complex enough in Emacs < 21 to make it
982 ;; a function, since we have to mess with the `rear-nonsticky' property.
992 'rear-nonsticky
998 ;; Remove the given property on the character at POS if it's been put
999 ;; there by `c-put-char-property'. PROPERTY is assumed to be
1000 ;; constant.
1001 ;;
1002 ;; This macro does a hidden buffer change.
1005 ;; XEmacs.
1009 ;; In Emacs 21 we got the `rear-nonsticky' property covered
1010 ;; by `text-property-default-nonsticky'.
1015 ;; Emacs < 21.
1019 ;; Remove all the occurrences of the given property in the given
1020 ;; region that has been put with `c-put-char-property'. PROPERTY is
1021 ;; assumed to be constant.
1022 ;;
1023 ;; Note that this function does not clean up the property from the
1024 ;; lists of the `rear-nonsticky' properties in the region, if such
1025 ;; are used. Thus it should not be used for common properties like
1026 ;; `syntax-table'.
1027 ;;
1028 ;; This macro does hidden buffer changes.
1031 ;; XEmacs.
1035 ;; Emacs.
1039 "Search forward for a text-property PROPERTY having value VALUE.
1040 LIMIT bounds the search. The comparison is done with `equal'.
1042 Leave point just after the character, and set the match data on
1043 this character, and return point. If VALUE isn't found, Return
1044 nil; point is then left undefined."
1058 "Search backward for a text-property PROPERTY having value VALUE.
1059 LIMIT bounds the search. The comparison is done with `equal'.
1061 Leave point just before the character, set the match data on this
1062 character, and return point. If VALUE isn't found, Return nil;
1063 point is then left undefined."
1077 "Remove all text-properties PROPERTY from the region (FROM, TO)
1078 which have the value VALUE, as tested by `equal'. These
1079 properties are assumed to be over individual characters, having
1080 been put there by c-put-char-property. POINT remains unchanged."
1092 ;; Do we have to do anything with stickiness here?
1096 "Remove all text-properties PROPERTY from the region [FROM, TO)
1097 which have the value VALUE, as tested by `equal'. These
1098 properties are assumed to be over individual characters, having
1099 been put there by c-put-char-property. POINT remains unchanged."
1101 ;; XEmacs
1107 ;; Gnu Emacs
1109 \f
1110 ;; Macros to put overlays (Emacs) or extents (XEmacs) on buffer text.
1111 ;; For our purposes, these are characterized by being possible to
1112 ;; remove again without affecting the other text properties in the
1113 ;; buffer that got overridden when they were put.
1116 ;; Put an overlay/extent covering the given range in the current
1117 ;; buffer. It's currently undefined whether it's front/end sticky
1118 ;; or not. The overlay/extent object is returned.
1120 ;; Emacs.
1123 ol)
1124 ;; XEmacs.
1127 ext)))
1130 ;; Deletes an overlay/extent object previously retrieved using
1131 ;; `c-put-overlay'.
1133 ;; Emacs.
1135 ;; XEmacs.
1138 \f
1139 ;; Make edebug understand the macros.
1140 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1141 ; '(progn
1170 \f
1171 ;;; Functions.
1173 ;; Note: All these after the macros, to be on safe side in avoiding
1174 ;; bugs where macros are defined too late. These bugs often only show
1175 ;; when the files are compiled in a certain order within the same
1176 ;; session.
1179 ;; Replacement for end-of-defun that use c-beginning-of-defun-1.
1181 ;; Skip forward into the next defun block. Don't bother to avoid
1182 ;; comments, literals etc, since beginning-of-defun doesn't do that
1183 ;; anyway.
1195 ;; Mark the "<" character at POS as a template opener using the
1196 ;; `syntax-table' property via the `category' property.
1197 ;;
1198 ;; This function does a hidden buffer change. Note that we use
1199 ;; indirection through the `category' text property. This allows us to
1200 ;; toggle the property in all template brackets simultaneously and
1201 ;; cheaply. We use this, for instance, in `c-parse-state'.
1208 ;; Mark the ">" character at POS as an sexp list closer using the
1209 ;; syntax-table property.
1210 ;;
1211 ;; This function does a hidden buffer change. Note that we use
1212 ;; indirection through the `category' text property. This allows us to
1213 ;; toggle the property in all template brackets simultaneously and
1214 ;; cheaply. We use this, for instance, in `c-parse-state'.
1218 ;; Unmark the "<" or "<" character at POS as an sexp list opener using
1219 ;; the syntax-table property indirectly through the `category' text
1220 ;; property.
1221 ;;
1222 ;; This function does a hidden buffer change. Note that we use
1223 ;; indirection through the `category' text property. This allows us to
1224 ;; toggle the property in all template brackets simultaneously and
1225 ;; cheaply. We use this, for instance, in `c-parse-state'.
1229 ;; Suppress the syntactic effect of all marked < and > as parens. Note
1230 ;; that this effect is NOT buffer local. You should probably not use
1231 ;; this directly, but only through the macro
1232 ;; `c-with-<->-as-parens-suppressed'
1237 ;; Restore the syntactic effect of all marked <s and >s as parens. This
1238 ;; has no effect on unmarked <s and >s
1243 ;; Like progn, except that the paren property is suppressed on all
1244 ;; template brackets whilst they are running. This macro does a hidden
1245 ;; buffer change.
1252 ;;;;;;;;;;;;;;;
1255 ;; This is the value of the `category' text property placed on every #
1256 ;; which introduces a CPP construct and every EOL (or EOB, or character
1257 ;; preceding //, etc.) which terminates it. We can instantly "comment
1258 ;; out" all CPP constructs by giving `c-cpp-delimiter' a syntax-table
1259 ;; property '(14) (generic comment delimiter).
1261 ;; This macro does a hidden buffer change.
1267 ;; This macro does a hidden buffer change.
1274 ;; Render all preprocessor constructs syntactically commented out.
1277 ;; Restore the syntactic visibility of preprocessor constructs.
1281 ;; Execute FORMS... whilst the syntactic effect of all characters in
1282 ;; all CPP regions is suppressed. In particular, this is to suppress
1283 ;; the syntactic significance of parens/braces/brackets to functions
1284 ;; such as `scan-lists' and `parse-partial-sexp'.
1293 ;; Execute FORMS... whilst the syntactic effect of all characters in
1294 ;; every CPP region APART FROM THE ONE BETWEEN BEG and END is
1295 ;; suppressed.
1306 \f
1308 ;; return the element of ALIST that matches the first element found
1309 ;; in LIST. Uses assq.
1314 match))
1317 ;; first, find the first entry from LIST that is present in ALIST1,
1318 ;; then find the entry in ALIST2 for that entry.
1322 "Return the syntactic symbol in LANGELEM.
1326 form as used in `c-syntactic-element'."
1330 "Return the anchor position in LANGELEM, or nil if there is none.
1334 form as used in `c-syntactic-element'."
1340 "Return the column of the anchor position in LANGELEM.
1341 Also move the point to that position unless PRESERVE-POINT is non-nil.
1345 form as used in `c-syntactic-element'."
1357 "Return the secondary position in LANGELEM, or nil if there is none.
1360 in `c-syntactic-element'. It may also be a cons cell as passed in the
1361 first argument to lineup functions, but then the returned value always
1362 will be nil."
1366 ;; Do whatever is necessary to keep the region active in XEmacs.
1367 ;; This is not needed for Emacs.
1381 the corresponding symbol."
1387 c-buffer-is-cc-mode))
1392 the value of the variable with that name."
1396 "Return non-nil if position POS in the current buffer has any of the
1397 faces in the list FACES."
1404 pos-faces)
1408 ;; Return t if FACENAME is the name of a face. This method is
1409 ;; necessary since facep in XEmacs only returns t for the actual
1410 ;; face objects (while it's only their names that are used just
1411 ;; about anywhere else) without providing a predicate that tests
1412 ;; face names.
1416 "Like `concat' on LIST, but separate each element with SEPARATOR.
1417 Notably, null elements in LIST are ignored."
1421 "Make a regexp that matches all the strings the list.
1422 Duplicates and nil elements in the list are removed. The resulting
1423 regexp may contain zero or more submatch expressions.
1425 If ADORN is t there will be at least one submatch and the first
1426 surrounds the matched alternative, and the regexp will also not match
1427 a prefix of any identifier. Adorned regexps cannot be appended. The
1428 language variable `c-nonsymbol-key' is used to make the adornment.
1430 A value 'appendable for ADORN is like above, but all alternatives in
1432 instead, so that the regexp remains appendable. Note that this
1433 variant doesn't always guarantee that an identifier prefix isn't
1434 matched since the symbol constituent '_' is normally considered a
1437 The optional MODE specifies the language to get `c-nonsymbol-key' from
1438 when it's needed. The default is the current language taken from
1439 `c-buffer-is-cc-mode'."
1450 ;; This is kludgy but it works: Search for a string that
1451 ;; doesn't occur in any word in LIST. Append it to all
1452 ;; the alternatives where we want to add \>. Run through
1453 ;; `regexp-opt' and then replace it with \>.
1457 pos list)
1461 nil)
1462 t))
1464 found))
1478 ;; Emacs 20 and XEmacs (all versions so far) has a buggy
1479 ;; regexp-opt that doesn't always cope with strings containing
1480 ;; newlines. This kludge doesn't handle shy parens correctly
1481 ;; so we can't advice regexp-opt directly with it.
1505 ;; Add our own grouping parenthesis around re instead of
1506 ;; passing adorn to `regexp-opt', since in XEmacs it makes the
1507 ;; top level grouping "shy".
1516 re)))
1518 ;; Produce a regexp that matches nothing.
1526 "Make a character alternative string from the list of characters CHARS.
1527 The returned string is of the type that can be used with
1528 `skip-chars-forward' and `skip-chars-backward'. If INVERTED is
1529 non-nil, a caret is prepended to invert the set."
1530 ;; This function ought to be in the elisp core somewhere.
1536 ;; Quoting necessary (this method only works in the skip
1537 ;; functions).
1540 ;; Check for range.
1548 str))
1550 ;; Leftovers from (X)Emacs 19 compatibility.
1554 \f
1555 ;; Figure out what features this Emacs has
1563 ;; I've no idea what this actually is, but it's legacy. /mast
1566 ;; XEmacs uses 8-bit modify-syntax-entry flags.
1567 ;; Emacs uses a 1-bit flag. We will have to set up our
1568 ;; syntax tables differently to handle this.
1570 entry)
1573 ;; Emacs
1576 ;; In Emacs, table entries are cons cells
1578 ;; XEmacs
1581 ;; incompatible
1586 list)))
1588 ;; Check whether beginning/end-of-defun call
1589 ;; beginning/end-of-defun-function nicely, passing through the
1590 ;; argument and respecting the return code.
1611 parse-sexp-lookup-properties
1612 parse-sexp-ignore-comments
1617 ;; For some reason we have to set some of these after the
1618 ;; buffer has been made current. (Specifically,
1619 ;; `parse-sexp-ignore-comments' in Emacs 21.)
1621 parse-sexp-ignore-comments t
1622 lookup-syntax-properties t)
1624 ;; Find out if the `syntax-table' text property works.
1635 "CC Mode is incompatible with this version of Emacs - "
1636 "support for the `syntax-table' text property "
1639 ;; Find out if generic comment delimiters work.
1645 ;; Find out if generic string delimiters work.
1651 ;; See if POSIX char classes work.
1653 ;; All versions of Emacs 21 so far haven't fixed
1654 ;; char classes in `skip-chars-forward' and
1655 ;; `skip-chars-backward'.
1664 ;; See if `open-paren-in-column-0-is-defun-start' exists and
1665 ;; isn't buggy (Emacs >= 21.4).
1673 ;; XEmacs. Afaik this is currently an Emacs-only
1674 ;; feature, but it's good to be prepared.
1678 ;; Emacs
1691 ;; See if `parse-partial-sexp' returns the eighth element.
1696 "CC Mode is incompatible with this version of Emacs - "
1699 ;;(message "c-emacs-features: %S" list)
1700 list)
1701 "A list of certain features in the (X)Emacs you are using.
1702 There are many flavors of Emacs out there, each with different
1703 features supporting those needed by CC Mode. The following values
1704 might be present:
1706 '8-bit 8 bit syntax entry flags (XEmacs style).
1707 '1-bit 1 bit syntax entry flags (Emacs style).
1708 'argumentative-bod-function beginning-of-defun passes ARG through
1709 to a non-null beginning-of-defun-function. It is assumed
1710 the end-of-defun does the same thing.
1711 'syntax-properties It works to override the syntax for specific characters
1712 in the buffer with the 'syntax-table property. It's
1713 always set - CC Mode no longer works in emacsen without
1714 this feature.
1715 'gen-comment-delim Generic comment delimiters work
1716 (i.e. the syntax class `!').
1717 'gen-string-delim Generic string delimiters work
1718 (i.e. the syntax class `|').
1719 'pps-extended-state `parse-partial-sexp' returns a list with at least 10
1720 elements, i.e. it contains the position of the start of
1721 the last comment or string. It's always set - CC Mode
1722 no longer works in emacsen without this feature.
1723 'posix-char-classes The regexp engine understands POSIX character classes.
1724 'col-0-paren It's possible to turn off the ad-hoc rule that a paren
1725 in column zero is the start of a defun.
1726 'infodock This is Infodock (based on XEmacs).
1730 \f
1731 ;;; Some helper constants.
1733 ;; If the regexp engine supports POSIX char classes then we can use
1734 ;; them to handle extended charsets correctly.
1748 \f
1749 ;;; System for handling language dependent constants.
1751 ;; This is used to set various language dependent data in a flexible
1752 ;; way: Language constants can be built from the values of other
1753 ;; language constants, also those for other languages. They can also
1754 ;; process the values of other language constants uniformly across all
1755 ;; the languages. E.g. one language constant can list all the type
1756 ;; keywords in each language, and another can build a regexp for each
1757 ;; language from those lists without code duplication.
1758 ;;
1759 ;; Language constants are defined with `c-lang-defconst', and their
1760 ;; value forms (referred to as source definitions) are evaluated only
1761 ;; on demand when requested for a particular language with
1762 ;; `c-lang-const'. It's therefore possible to refer to the values of
1763 ;; constants defined later in the file, or in another file, just as
1764 ;; long as all the relevant `c-lang-defconst' have been loaded when
1765 ;; `c-lang-const' is actually evaluated from somewhere else.
1766 ;;
1767 ;; `c-lang-const' forms are also evaluated at compile time and
1768 ;; replaced with the values they produce. Thus there's no overhead
1769 ;; for this system when compiled code is used - only the values
1770 ;; actually used in the code are present, and the file(s) containing
1771 ;; the `c-lang-defconst' forms don't need to be loaded at all then.
1772 ;; There are however safeguards to make sure that they can be loaded
1773 ;; to get the source definitions for the values if there's a mismatch
1774 ;; in compiled versions, or if `c-lang-const' is used uncompiled.
1775 ;;
1776 ;; Note that the source definitions in a `c-lang-defconst' form are
1777 ;; compiled into the .elc file where it stands; there's no need to
1778 ;; load the source file to get it.
1779 ;;
1780 ;; See cc-langs.el for more details about how this system is deployed
1781 ;; in CC Mode, and how the associated language variable system
1782 ;; (`c-lang-defvar') works. That file also contains a lot of
1783 ;; examples.
1786 "Declare a new language in the language dependent variable system.
1787 This is intended to be used by modes that inherit CC Mode to add new
1788 languages. It should be used at the top level before any calls to
1789 `c-lang-defconst'. MODE is the mode name symbol for the new language,
1790 and BASE-MODE is the mode name symbol for the language in CC Mode that
1791 is to be the template for the new mode.
1793 The exact effect of BASE-MODE is to make all language constants that
1794 haven't got a setting in the new language fall back to their values in
1795 BASE-MODE. It does not have any effect outside the language constant
1796 system."
1805 ;; This obarray is a cache to keep track of the language constants
1806 ;; defined by `c-lang-defconst' and the evaluated values returned by
1807 ;; `c-lang-const'. It's mostly used at compile time but it's not
1808 ;; stored in compiled files.
1809 ;;
1810 ;; The obarray contains all the language constants as symbols. The
1811 ;; value cells hold the evaluated values as alists where each car is
1812 ;; the mode name symbol and the corresponding cdr is the evaluated
1813 ;; value in that mode. The property lists hold the source definitions
1814 ;; and other miscellaneous data. The obarray might also contain
1815 ;; various other symbols, but those don't have any variable bindings.
1820 ;; Return the base name of the current file.
1823 ;; Being loaded.
1824 load-file-name)
1827 ;; Being compiled.
1828 byte-compile-dest-file)
1830 ;; Being evaluated interactively.
1835 "Can be used inside a VAL in `c-lang-defconst' to evaluate FORM
1836 immediately, i.e. at the same time as the `c-lang-defconst' form
1837 itself is evaluated."
1838 ;; Evaluate at macro expansion time, i.e. in the
1839 ;; `cl-macroexpand-all' inside `c-lang-defconst'.
1842 ;; Only used at compile time - suppress "might not be defined at runtime".
1846 "Set the language specific values of the language constant NAME.
1847 The second argument can optionally be a docstring. The rest of the
1848 arguments are one or more repetitions of LANG VAL where LANG specifies
1849 the language(s) that VAL applies to. LANG is the name of the
1851 of such language names, or `t' for all languages. VAL is a form to
1852 evaluate to get the value.
1854 If LANG isn't `t' or one of the core languages in CC Mode, it must
1855 have been declared with `c-add-language'.
1857 Neither NAME, LANG nor VAL are evaluated directly - they should not be
1858 quoted. `c-lang-defconst-eval-immediately' can however be used inside
1859 VAL to evaluate parts of it directly.
1861 When VAL is evaluated for some language, that language is temporarily
1862 made current so that `c-lang-const' without an explicit language can
1863 be used inside VAL to refer to the value of a language constant in the
1864 same language. That is particularly useful if LANG is `t'.
1866 VAL is not evaluated right away but rather when the value is requested
1867 with `c-lang-const'. Thus it's possible to use `c-lang-const' inside
1868 VAL to refer to language constants that haven't been defined yet.
1869 However, if the definition of a language constant is in another file
1870 then that file must be loaded \(at compile time) before it's safe to
1871 reference the constant.
1873 The assignments in ARGS are processed in sequence like `setq', so
1874 \(c-lang-const NAME) may be used inside a VAL to refer to the last
1875 assigned value to this language constant, or a value that it has
1876 gotten in another earlier loaded file.
1878 To work well with repeated loads and interactive reevaluation, only
1879 one `c-lang-defconst' for each NAME is permitted per file. If there
1880 already is one it will be completely replaced; the value in the
1881 earlier definition will not affect `c-lang-const' on the same
1882 constant. A file is identified by its base name."
1885 ;; Make `c-lang-const' expand to a straightforward call to
1886 ;; `c-get-lang-constant' in `cl-macroexpand-all' below.
1887 ;;
1888 ;; (The default behavior, i.e. to expand to a call inside
1889 ;; `eval-when-compile' should be equivalent, since that macro
1890 ;; should only expand to its content if it's used inside a
1891 ;; form that's already evaluated at compile time. It's
1892 ;; however necessary to use our cover macro
1893 ;; `cc-eval-when-compile' due to bugs in `eval-when-compile',
1894 ;; and it expands to a bulkier form that in this case only is
1895 ;; unnecessary garbage that we don't want to store in the
1896 ;; language constant source definitions.)
1899 bindings
1900 pre-files)
1906 ;; The docstring is hardly used anywhere since there's no normal
1907 ;; symbol to attach it to. It's primarily for getting the right
1908 ;; format in the source.
1915 ;; Rework ARGS to an association list to make it easier to handle.
1916 ;; It's reversed at the same time to make it easier to implement
1917 ;; the demand-driven (i.e. reversed) evaluation in `c-lang-const'.
1934 val)
1941 ;; Emacs has a weird bug where it seems to fail to read
1942 ;; backquote lists from byte compiled files correctly (,@
1943 ;; forms, to be specific), so make sure the bindings in the
1944 ;; expansion below don't contain any backquote stuff.
1945 ;; (XEmacs handles it correctly and doesn't need this for that
1946 ;; reason, but we also use this expansion handle
1947 ;; `c-lang-defconst-eval-immediately' and to register
1948 ;; dependencies on the `c-lang-const's in VAL.)
1954 ;; Compile in the other files that have provided source
1955 ;; definitions for this symbol, to make sure the order in the
1956 ;; `source' property is correct even when files are loaded out of
1957 ;; order.
1959 ;; Reverse to get the right load order.
1967 ;(eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
1968 ; '
1973 ;; Used by `c-lang-defconst'.
1982 ;;(when (cdr-safe elem)
1983 ;; (message "Language constant %s redefined in %S" name file))
1985 ;; Note that the order in the source alist is relevant. Like how
1986 ;; `c-lang-defconst' reverses the bindings, this reverses the
1987 ;; order between files so that the last to evaluate comes first.
1997 ;; Bind the symbol as a variable, or clear any earlier evaluated
1998 ;; value it has.
2001 ;; Clear the evaluated values that depend on this source.
2004 ptr)
2017 name))
2020 "Get the mode specific value of the language constant NAME in language LANG.
2021 LANG is the name of the language, i.e. the mode name without the
2023 `c-lang-defvar', LANG may be left out to refer to the current
2024 language. NAME and LANG are not evaluated so they should not be
2025 quoted."
2033 mode source-files args)
2039 "Unknown language %S since it got no `c-mode-prefix' property"
2043 ;; No need to find out the source file(s) when we evaluate
2044 ;; immediately since all the info is already there in the
2045 ;; `source' property.
2050 ;; Get the source file(s) that must be loaded to get the value
2051 ;; of the constant. If the symbol isn't defined yet we assume
2052 ;; that its definition will come later in this file, and thus
2053 ;; are no file dependencies needed.
2055 ;; Reverse to get the right load order.
2059 nil ; Exclude our own file.
2063 ;; Make some effort to do a compact call to
2064 ;; `c-get-lang-constant' since it will be compiled in.
2068 args)))
2073 load-in-progress
2076 ;; Either a straight call is requested in the context, or
2077 ;; we're in an "uncontrolled" context and got no language,
2078 ;; or we're not being byte compiled so the compile time
2079 ;; stuff below is unnecessary.
2082 ;; Being compiled. If the loading and compiling version is
2083 ;; the same we use a value that is evaluated at compile time,
2084 ;; otherwise it's evaluated at runtime.
2093 ;; Used by `c-lang-const'.
2101 elem
2105 ;; Record the dependencies between this symbol and the one we're
2106 ;; being evaluated in.
2111 ;; Make sure the source files have entries on the `source'
2112 ;; property so that loading will take place when necessary.
2117 ;; Might pull in more definitions which affect the value. The
2118 ;; clearing of dependent values etc is done when the
2119 ;; definition is encountered during the load; this is just to
2120 ;; jump past the check for a cached value below.
2128 ;; Check if an evaluation of this symbol is already underway.
2129 ;; In that case we just continue with the "assignment" before
2130 ;; the one currently being evaluated, thereby creating the
2131 ;; illusion if a `setq'-like sequence of assignments.
2136 ;; Append `c-lang-constants-under-evaluation' even if an
2137 ;; earlier entry is found. It's only necessary to get
2138 ;; the recording of dependencies above correct.
2142 value
2143 ;; Make sure the recursion limits aren't very low
2144 ;; since the `c-lang-const' dependencies can go deep.
2151 ;; First try the original mode but don't accept an
2152 ;; entry matching all languages since the fallback
2153 ;; mode might have an explicit entry before that.
2156 c-lang-constants)
2157 ;; Try again with the fallback mode from the
2158 ;; original position. Note that
2159 ;; `c-buffer-is-cc-mode' still is the real mode if
2160 ;; language parameterization takes place.
2163 fallback t name))
2164 c-lang-constants)))
2165 ;; A simple lookup with no fallback mode.
2168 c-lang-constants))
2170 "`%s' got no (prior) value in %s (might be a cyclic reference)"
2171 name mode))
2176 ;; Print a message to aid in locating the error. We don't
2177 ;; print the error itself since that will be done later by
2178 ;; some caller higher up.
2180 sym mode)
2185 value))))
2188 ;; Find the first assignment entry that applies to MODE at or after
2189 ;; SOURCE-POS. If MATCH-ANY-LANG is non-nil, entries with `t' as
2190 ;; the language list are considered to match, otherwise they don't.
2191 ;; On return SOURCE-POS is updated to point to the next assignment
2192 ;; after the returned one. If no assignment is found,
2193 ;; `c-lang-constants' is returned as a magic value.
2194 ;;
2195 ;; SOURCE-POS is a vector that points out a specific assignment in
2196 ;; the double alist that's used in the `source' property. The first
2197 ;; element is the position in the top alist which is indexed with
2198 ;; the source files, and the second element is the position in the
2199 ;; nested bindings alist.
2200 ;;
2201 ;; NAME is only used for error messages.
2206 assignment)
2209 t
2210 ;; Handled the last assignment from one file, begin on the
2211 ;; next. Due to the check in `c-lang-defconst', we know
2212 ;; there's at least one.
2217 ;; The file containing the source definitions has not
2218 ;; been loaded.
2221 ;;(message (concat "Loading %s to get the source "
2222 ;; "value for language constant %s")
2223 ;; file name)
2227 ;; The load didn't fill in the source for the
2228 ;; constant as expected. The situation is
2229 ;; probably that a derived mode was written for
2230 ;; and compiled with another version of CC Mode,
2231 ;; and the requested constant isn't in the
2232 ;; currently loaded one. Put in a dummy
2233 ;; assignment that matches no language.
2238 t))
2246 match-any-lang)
2249 c-lang-constants)))
2252 ;; `c-major-mode-is' expands to a call to this function inside
2253 ;; `c-lang-defconst'. Here we also match the mode(s) against any
2254 ;; fallback modes for the one in `c-buffer-is-cc-mode', so that
2255 ;; e.g. (c-major-mode-is 'c++-mode) is true in a derived language
2256 ;; that has c++-mode as base mode.
2263 nil)
2265 match))
2267 \f
2270 ;;; cc-defs.el ends here