| blob | 5fa0403458527a805c20c3eb0e431a5860611321 |
1 ;;; cc-engine.el --- core syntax guessing engine for CC mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2016 Free Software Foundation, Inc.
5 ;; Authors: 2001- 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 ;; The functions which have docstring documentation can be considered
34 ;; part of an API which other packages can use in CC Mode buffers.
35 ;; Otoh, undocumented functions and functions with the documentation
36 ;; in comments are considered purely internal and can change semantics
37 ;; or even disappear in the future.
38 ;;
39 ;; (This policy applies to CC Mode as a whole, not just this file. It
40 ;; probably also applies to many other Emacs packages, but here it's
41 ;; clearly spelled out.)
43 ;; Hidden buffer changes
44 ;;
45 ;; Various functions in CC Mode use text properties for caching and
46 ;; syntactic markup purposes, and those of them that might modify such
47 ;; properties but still don't modify the buffer in a visible way are
48 ;; said to do "hidden buffer changes". They should be used within
49 ;; `c-save-buffer-state' or a similar function that saves and restores
50 ;; buffer modifiedness, disables buffer change hooks, etc.
51 ;;
52 ;; Interactive functions are assumed to not do hidden buffer changes,
53 ;; except in the specific parts of them that do real changes.
54 ;;
55 ;; Lineup functions are assumed to do hidden buffer changes. They
56 ;; must not do real changes, though.
57 ;;
58 ;; All other functions that do hidden buffer changes have that noted
59 ;; in their doc string or comment.
60 ;;
61 ;; The intention with this system is to avoid wrapping every leaf
62 ;; function that do hidden buffer changes inside
63 ;; `c-save-buffer-state'. It should be used as near the top of the
64 ;; interactive functions as possible.
65 ;;
66 ;; Functions called during font locking are allowed to do hidden
67 ;; buffer changes since the font-lock package run them in a context
68 ;; similar to `c-save-buffer-state' (in fact, that function is heavily
69 ;; inspired by `save-buffer-state' in the font-lock package).
71 ;; Use of text properties
72 ;;
73 ;; CC Mode uses several text properties internally to mark up various
74 ;; positions, e.g. to improve speed and to eliminate glitches in
75 ;; interactive refontification.
76 ;;
77 ;; Note: This doc is for internal use only. Other packages should not
78 ;; assume that these text properties are used as described here.
79 ;;
80 ;; 'category
81 ;; Used for "indirection". With its help, some other property can
82 ;; be cheaply and easily switched on or off everywhere it occurs.
83 ;;
84 ;; 'syntax-table
85 ;; Used to modify the syntax of some characters. It is used to
86 ;; mark the "<" and ">" of angle bracket parens with paren syntax, to
87 ;; "hide" obtrusive characters in preprocessor lines, and to mark C++
88 ;; raw strings to enable their fontification.
89 ;;
90 ;; This property is used on single characters and is therefore
91 ;; always treated as front and rear nonsticky (or start and end open
92 ;; in XEmacs vocabulary). It's therefore installed on
93 ;; `text-property-default-nonsticky' if that variable exists (Emacs
94 ;; >= 21).
95 ;;
96 ;; 'c-is-sws and 'c-in-sws
97 ;; Used by `c-forward-syntactic-ws' and `c-backward-syntactic-ws' to
98 ;; speed them up. See the comment blurb before `c-put-is-sws'
99 ;; below for further details.
100 ;;
101 ;; 'c-type
102 ;; This property is used on single characters to mark positions with
103 ;; special syntactic relevance of various sorts. Its primary use is
104 ;; to avoid glitches when multiline constructs are refontified
105 ;; interactively (on font lock decoration level 3). It's cleared in
106 ;; a region before it's fontified and is then put on relevant chars
107 ;; in that region as they are encountered during the fontification.
108 ;; The value specifies the kind of position:
109 ;;
110 ;; 'c-decl-arg-start
111 ;; Put on the last char of the token preceding each declaration
112 ;; inside a declaration style arglist (typically in a function
113 ;; prototype).
114 ;;
115 ;; 'c-decl-end
116 ;; Put on the last char of the token preceding a declaration.
117 ;; This is used in cases where declaration boundaries can't be
118 ;; recognized simply by looking for a token like ";" or "}".
119 ;; `c-type-decl-end-used' must be set if this is used (see also
120 ;; `c-find-decl-spots').
121 ;;
122 ;; 'c-<>-arg-sep
123 ;; Put on the commas that separate arguments in angle bracket
124 ;; arglists like C++ template arglists.
125 ;;
126 ;; 'c-decl-id-start and 'c-decl-type-start
127 ;; Put on the last char of the token preceding each declarator
128 ;; in the declarator list of a declaration. They are also used
129 ;; between the identifiers cases like enum declarations.
130 ;; 'c-decl-type-start is used when the declarators are types,
131 ;; 'c-decl-id-start otherwise.
132 ;;
133 ;; 'c-awk-NL-prop
134 ;; Used in AWK mode to mark the various kinds of newlines. See
135 ;; cc-awk.el.
137 ;;; Code:
144 load-path)))
153 \f
154 ;; Make declarations for all the `c-lang-defvar' variables in cc-langs.
166 \f
167 ;;; Internal state variables.
169 ;; Internal state of hungry delete key feature
173 ;; The electric flag (toggled by `c-toggle-electric-state').
174 ;; If t, electric actions (like automatic reindentation, and (if
175 ;; c-auto-newline is also set) auto newlining) will happen when an electric
176 ;; key like `{' is pressed (or an electric keyword like `else').
180 ;; Internal state of auto newline feature.
184 ;; Included in the mode line to indicate the active submodes.
185 ;; (defvar c-submode-indicators nil)
186 ;; (make-variable-buffer-local 'c-submode-indicators)
189 ;; Calculate the new state of PREVSTATE, t or nil, based on arg. If
190 ;; arg is nil or zero, toggle the state. If arg is negative, turn
191 ;; the state off, and if arg is positive, turn the state on
197 \f
198 ;; Basic handling of preprocessor directives.
200 ;; This is a dynamically bound cache used together with
201 ;; `c-query-macro-start' and `c-query-and-set-macro-start'. It only
202 ;; works as long as point doesn't cross a macro boundary.
211 c-macro-start))
219 c-macro-start))
221 ;; One element macro cache to cope with continual movement within very large
222 ;; CPP macros.
225 ;; Nil or cons of the bounds of the most recent CPP form probed by
226 ;; `c-beginning-of-macro', `c-end-of-macro' or `c-syntactic-end-of-macro'.
227 ;; The cdr will be nil if we know only the start of the CPP form.
230 ;; The starting position from where we determined `c-macro-cache'.
233 ;; Either nil, or the syntactic end of the macro currently represented by
234 ;; `c-macro-cache'.
237 ;; Either nil, or the last character of the macro currently represented by
238 ;; `c-macro-cache' which isn't in a comment. */
241 ;; Called from a before-change function. If the change region is before or
242 ;; in the macro characterized by `c-macro-cache' etc., nullify it
243 ;; appropriately. BEG and END are the standard before-change-functions
244 ;; parameters. END isn't used.
249 c-macro-cache-start-pos nil
250 c-macro-cache-syntactic nil
251 c-macro-cache-no-comment nil))
256 c-macro-cache-syntactic nil
257 c-macro-cache-no-comment nil))))
260 ;; Check that the ostensible CPP construct at point is a real one. In
261 ;; particular, if point is on the first line of a narrowed buffer, make sure
262 ;; that the "#" isn't, say, the second character of a "##" operator. Return
263 ;; t when the macro is real, nil otherwise.
274 t)
278 "Go to the beginning of a preprocessor directive.
279 Leave point at the beginning of the directive and return t if in one,
280 otherwise return nil and leave point unchanged.
282 Note that this function might do hidden buffer changes. See the
283 comment at the start of cc-engine.el for more info."
295 t))
297 c-macro-cache-start-pos nil
298 c-macro-cache-syntactic nil
299 c-macro-cache-no-comment nil)
312 c-macro-cache-start-pos here)
313 t)
315 nil))))))
318 "Go to the end of a preprocessor directive.
319 More accurately, move the point to the end of the closest following
320 line that doesn't end with a line continuation backslash - no check is
321 done that the point is inside a cpp directive to begin with.
323 Note that this function might do hidden buffer changes. See the
324 comment at the start of cc-engine.el for more info."
333 c-macro-cache-start-pos nil
334 c-macro-cache-syntactic nil
335 c-macro-cache-no-comment nil))
341 t)))
346 ;; Go to the end of a CPP directive, or a "safe" pos just before.
347 ;;
348 ;; This is normally the end of the next non-escaped line. A "safe"
349 ;; position is one not within a string or comment. (The EOL on a line
350 ;; comment is NOT "safe").
351 ;;
352 ;; This function must only be called from the beginning of a CPP construct.
353 ;;
354 ;; Note that this function might do hidden buffer changes. See the comment
355 ;; at the start of cc-engine.el for more info.
358 s)
371 ;; Go to the end of a CPP directive, or a pos just before which isn't in a
372 ;; comment. For this purpose, open strings are ignored.
373 ;;
374 ;; This function must only be called from the beginning of a CPP construct.
375 ;;
376 ;; Note that this function might do hidden buffer changes. See the comment
377 ;; at the start of cc-engine.el for more info.
380 s)
394 ;; Assuming point is at the "#" that introduces a preprocessor
395 ;; directive, it's moved forward to the end of the identifier which is
396 ;; "#define"d (or whatever c-opt-cpp-macro-define specifies). Non-nil
397 ;; is returned in this case, in all other cases nil is returned and
398 ;; point isn't moved.
399 ;;
400 ;; This function might do hidden buffer changes.
406 ;; Assuming point is at the "#" that introduces a preprocessor
407 ;; directive, it's moved forward to the start of the definition body
408 ;; if it's a "#define" (or whatever c-opt-cpp-macro-define
409 ;; specifies). Non-nil is returned in this case, in all other cases
410 ;; nil is returned and point isn't moved.
411 ;;
412 ;; This function might do hidden buffer changes.
418 \f
419 ;;; Basic utility functions.
422 ;; If ELT is a member of the (possibly dotted) list DLIST, remove all
423 ;; occurrences of it (except for any in the last cdr of DLIST).
424 ;;
425 ;; Call this as (setq DLIST (c-delq-from-dotted-list ELT DLIST)), as
426 ;; sometimes the original structure is changed, sometimes it's not.
427 ;;
428 ;; This function is needed in Emacs < 24.5, and possibly XEmacs, because
429 ;; `delq' throws an error in these versions when given a dotted list.
438 dlist))
441 ;; Return the given region as a string where all syntactic
442 ;; whitespace is removed or, where necessary, replaced with a single
443 ;; space. If PAREN-LEVEL is given then all parens in the region are
444 ;; collapsed to "()", "[]" etc.
445 ;;
446 ;; This function might do hidden buffer changes.
490 ;; Shift the indentation of the current line with the specified
491 ;; amount (positive inwards). The buffer is modified only if
492 ;; SHIFT-AMT isn't equal to zero.
495 tmp-char-inserted)
497 nil
498 ;; If we're on an empty line inside a macro, we take the point
499 ;; to be at the current indentation and shift it to the
500 ;; appropriate column. This way we don't treat the extra
501 ;; whitespace out to the line continuation as indentation.
517 ;; If initial point was within line's indentation and we're not on
518 ;; a line with a line continuation in a macro, position after the
519 ;; indentation. Else stay at same point in text.
527 ;; Return non-nil if the string KEYWORD is a known keyword. More
528 ;; precisely, the value is the symbol for the keyword in
529 ;; `c-keywords-obarray'.
533 ;; Return non-nil if the symbol KEYWORD-SYM, as returned by
534 ;; `c-keyword-sym', is a member of LANG-CONSTANT, which is the name
535 ;; of a language constant that ends with "-kwds". If KEYWORD-SYM is
536 ;; nil then the result is nil.
539 ;; String syntax chars, suitable for skip-syntax-(forward|backward).
544 ;; Regexp matching string limit syntax.
549 ;; Regexp matching WS followed by string limit syntax.
553 ;; Holds formatted error strings for the few cases where parse errors
554 ;; are reported.
561 c-parsing-error)
563 ;; Faces given to comments and string literals. This is used in some
564 ;; situations to speed up recognition; it isn't mandatory that font
565 ;; locking is in use. This variable is extended with the face in
566 ;; `c-doc-face-name' when fontification is activated in cc-fonts.el.
570 ;; New in Emacs 22.
574 ;; Put a c-type property with the given value at POS.
578 ;; Remove all occurrences of the c-type property that has the given
579 ;; value in the region between FROM and TO. VALUE is assumed to not
580 ;; be nil.
581 ;;
582 ;; Note: This assumes that c-type is put on single chars only; it's
583 ;; very inefficient if matching properties cover large regions.
592 \f
593 ;; Some debug tools to visualize various special positions. This
594 ;; debug code isn't as portable as the rest of CC Mode.
630 \f
631 ;; `c-beginning-of-statement-1' and accompanying stuff.
633 ;; KLUDGE ALERT: c-maybe-labelp is used to pass information between
634 ;; c-crosses-statement-barrier-p and c-beginning-of-statement-1. A
635 ;; better way should be implemented, but this will at least shut up
636 ;; the byte compiler.
639 ;; New awk-compatible version of c-beginning-of-statement-1, ACM 2002/6/22
641 ;; Macros used internally in c-beginning-of-statement-1 for the
642 ;; automaton actions.
645 stack)))
650 t
651 ,do-if-done
656 ;; Throw nil if stack is empty, else throw non-nil.
674 "No matching `%s' found for `%s' on line %d"
681 noerror comma-delim)
682 "Move to the start of the current statement or declaration, or to
683 the previous one if already at the beginning of one. Only
684 statements/declarations on the same level are considered, i.e. don't
685 move into or out of sexps (not even normal expression parentheses).
687 If point is already at the earliest statement within braces or parens,
688 this function doesn't move back into any whitespace preceding it; it
689 returns `same' in this case.
693 is within the continuation. If starting at such a token, move to the
694 corresponding statement start. If at the beginning of a statement,
695 move to the closest containing statement if there is any. This might
696 also stop at a continuation clause.
698 Labels are treated as part of the following statements if
699 IGNORE-LABELS is non-nil. (FIXME: Doesn't work if we stop at a known
700 statement start keyword.) Otherwise, each label is treated as a
701 separate statement.
703 Macros are ignored \(i.e. skipped over) unless point is within one, in
704 which case the content of the macro is treated as normal code. Aside
705 from any normal statement starts found in it, stop at the first token
708 macros before leaving them.
710 Return:
712 `same' if stopped at the beginning of the current statement;
713 `up' if stepped to a containing statement;
714 `previous' if stepped to a preceding statement;
715 `beginning' if stepped from a statement continuation clause to
716 its start clause; or
717 `macro' if stepped to a macro start.
718 Note that `same' and not `label' is returned if stopped at the same
719 label without crossing the colon character.
721 LIM may be given to limit the search. If the search hits the limit,
722 point will be left at the closest following token, or at the start
723 position if that is less (`same' is returned in this case).
725 NOERROR turns off error logging to `c-parsing-error'.
727 Normally only `;' and virtual semicolons are considered to delimit
728 statements, but if COMMA-DELIM is non-nil then `,' is treated
729 as a delimiter too.
731 Note that this function might do hidden buffer changes. See the
732 comment at the start of cc-engine.el for more info."
734 ;; The bulk of this function is a pushdown automaton that looks at statement
735 ;; boundaries and the tokens (such as "while") in c-opt-block-stmt-key. Its
736 ;; purpose is to keep track of nested statements, ensuring that such
737 ;; statements are skipped over in their entirety (somewhat akin to what C-M-p
738 ;; does with nested braces/brackets/parentheses).
739 ;;
740 ;; Note: The position of a boundary is the following token.
741 ;;
742 ;; Beginning with the current token (the one following point), move back one
743 ;; sexp at a time (where a sexp is, more or less, either a token or the
744 ;; entire contents of a brace/bracket/paren pair). Each time a statement
745 ;; boundary is crossed or a "while"-like token is found, update the state of
746 ;; the PDA. Stop at the beginning of a statement when the stack (holding
747 ;; nested statement info) is empty and the position has been moved.
748 ;;
749 ;; The following variables constitute the PDA:
750 ;;
751 ;; sym: This is either the "while"-like token (e.g. 'for) we've just
752 ;; scanned back over, 'boundary if we've just gone back over a
753 ;; statement boundary, or nil otherwise.
754 ;; state: takes one of the values (nil else else-boundary while
755 ;; while-boundary catch catch-boundary).
756 ;; nil means "no "while"-like token yet scanned".
757 ;; 'else, for example, means "just gone back over an else".
758 ;; 'else-boundary means "just gone back over a statement boundary
759 ;; immediately after having gone back over an else".
760 ;; saved-pos: A vector of either saved positions (tok ptok pptok, etc.) or
761 ;; of error reporting information.
762 ;; stack: The stack onto which the PDA pushes its state. Each entry
763 ;; consists of a saved value of state and saved-pos. An entry is
764 ;; pushed when we move back over a "continuation" token (e.g. else)
765 ;; and popped when we encounter the corresponding opening token
766 ;; (e.g. if).
767 ;;
768 ;;
769 ;; The following diagram briefly outlines the PDA.
770 ;;
771 ;; Common state:
772 ;; "else": Push state, goto state `else'.
773 ;; "while": Push state, goto state `while'.
774 ;; "catch" or "finally": Push state, goto state `catch'.
775 ;; boundary: Pop state.
776 ;; other: Do nothing special.
777 ;;
778 ;; State `else':
779 ;; boundary: Goto state `else-boundary'.
780 ;; other: Error, pop state, retry token.
781 ;;
782 ;; State `else-boundary':
783 ;; "if": Pop state.
784 ;; boundary: Error, pop state.
785 ;; other: See common state.
786 ;;
787 ;; State `while':
788 ;; boundary: Save position, goto state `while-boundary'.
789 ;; other: Pop state, retry token.
790 ;;
791 ;; State `while-boundary':
792 ;; "do": Pop state.
793 ;; boundary: Restore position if it's not at start, pop state. [*see below]
794 ;; other: See common state.
795 ;;
796 ;; State `catch':
797 ;; boundary: Goto state `catch-boundary'.
798 ;; other: Error, pop state, retry token.
799 ;;
800 ;; State `catch-boundary':
801 ;; "try": Pop state.
802 ;; "catch": Goto state `catch'.
803 ;; boundary: Error, pop state.
804 ;; other: See common state.
805 ;;
806 ;; [*] In the `while-boundary' state, we had pushed a 'while state, and were
807 ;; searching for a "do" which would have opened a do-while. If we didn't
808 ;; find it, we discard the analysis done since the "while", go back to this
809 ;; token in the buffer and restart the scanning there, this time WITHOUT
810 ;; pushing the 'while state onto the stack.
811 ;;
812 ;; In addition to the above there is some special handling of labels
813 ;; and macros.
817 macro-start
820 c-stmt-delim-chars-with-comma
821 c-stmt-delim-chars))
822 c-in-literal-cache c-maybe-labelp after-case:-pos saved
823 ;; Current position.
824 pos
825 ;; Position of last stmt boundary character (e.g. ;).
826 boundary-pos
827 ;; The position of the last sexp or bound that follows the
828 ;; first found colon, i.e. the start of the nonlabel part of
829 ;; the statement. It's `start' if a colon is found just after
830 ;; the start.
831 after-labels-pos
832 ;; Like `after-labels-pos', but the first such position inside
833 ;; a label, i.e. the start of the last label before the start
834 ;; of the nonlabel part of the statement.
835 last-label-pos
836 ;; The last position where a label is possible provided the
837 ;; statement started there. It's nil as long as no invalid
838 ;; label content has been found (according to
839 ;; `c-nonlabel-token-key'). It's `start' if no valid label
840 ;; content was found in the label. Note that we might still
841 ;; regard it a label if it starts with `c-label-kwds'.
842 label-good-pos
843 ;; Putative positions of the components of a bitfield declaration,
844 ;; e.g. "int foo : NUM_FOO_BITS ;"
845 bitfield-type-pos bitfield-id-pos bitfield-size-pos
846 ;; Symbol just scanned back over (e.g. 'while or 'boundary).
847 ;; See above.
848 sym
849 ;; Current state in the automaton. See above.
850 state
851 ;; Current saved positions. See above.
852 saved-pos
853 ;; Stack of conses (state . saved-pos).
854 stack
855 ;; Regexp which matches "for", "if", etc.
858 ;; Return value.
860 ;; Positions of the last three sexps or bounds we've stopped at.
861 tok ptok pptok)
871 ;; Try to skip back over unary operator characters, to register
872 ;; that we've moved.
876 ;; Protect post-++/-- operators just before a virtual semicolon.
880 ;; Skip back over any semicolon here. If it was a bare semicolon, we're
881 ;; done. Later on we ignore the boundaries for statements that don't
882 ;; contain any sexp. The only thing that is affected is that the error
883 ;; checking is a little less strict, and we really don't bother.
893 pos saved)
895 ;; Begin at start and not pos to detect macros if we stand
896 ;; directly after the #.
899 ;; Record this as the first token if not starting inside it.
902 ;; The following while loop goes back one sexp (balanced parens,
903 ;; etc. with contents, or symbol or suchlike) each iteration. This
904 ;; movement is accomplished with a call to c-backward-sexp approx 170
905 ;; lines below.
906 ;;
907 ;; The loop is exited only by throwing nil to the (catch 'loop ...):
908 ;; 1. On reaching the start of a macro;
909 ;; 2. On having passed a stmt boundary with the PDA stack empty;
910 ;; 3. On reaching the start of an Objective C method def;
911 ;; 4. From macro `c-bos-pop-state'; when the stack is empty;
912 ;; 5. From macro `c-bos-pop-state-and-retry' when the stack is empty.
916 ;; Are we in a macro, just after the opening #?
931 ;; Stop at the first token in the content of the macro.
935 ret 'macro
936 ignore-labels t))
939 ;; Do a round through the automaton if we've just passed a
940 ;; statement boundary or passed a "while"-like token.
948 ;; The PDA state handling.
949 ;;
950 ;; Refer to the description of the PDA in the opening
951 ;; comments. In the following OR form, the first leaf
952 ;; attempts to handles one of the specific actions detailed
953 ;; (e.g., finding token "if" whilst in state `else-boundary').
954 ;; We drop through to the second leaf (which handles common
955 ;; state) if no specific handler is found in the first cond.
956 ;; If a parsing error is detected (e.g. an "else" with no
957 ;; preceding "if"), we throw to the enclosing catch.
958 ;;
959 ;; Note that the (eq state 'else) means
960 ;; "we've just passed an else", NOT "we're looking for an
961 ;; else".
978 ;; Since this can cause backtracking we do a
979 ;; little more careful analysis to avoid it:
980 ;; If there's a label in front of the while
981 ;; it can't be part of a do-while.
1010 ;; This is state common. We get here when the previous
1011 ;; cond statement found no particular state handler.
1013 ;; If we have a boundary at the start
1014 ;; position we push a frame to go to the
1015 ;; previous statement.
1024 ;; Is this a real while, or a do-while?
1025 ;; The next `when' triggers unless we are SURE that
1026 ;; the `while' is not the tail end of a `do-while'.
1029 ;; The following kludge is to prevent
1030 ;; infinite recursion when called from
1031 ;; c-awk-after-if-for-while-condition-p,
1032 ;; or the like.
1036 ;; Since this can cause backtracking we do a
1037 ;; little more careful analysis to avoid it: If
1038 ;; the while isn't followed by a (possibly
1039 ;; virtual) semicolon it can't be a do-while.
1048 ;; We're either past a statement boundary or at the
1049 ;; start of a statement, so throw away any label data
1050 ;; for the previous one.
1052 last-label-pos nil
1053 c-maybe-labelp nil))))
1055 ;; Step to the previous sexp, but not if we crossed a
1056 ;; boundary, since that doesn't consume an sexp.
1060 ;; HERE IS THE SINGLE PLACE INSIDE THE PDA LOOP WHERE WE MOVE
1061 ;; BACKWARDS THROUGH THE SOURCE.
1065 ;; The end position of the area to search for statement
1066 ;; barriers in this round.
1069 ;; Go back over exactly one logical sexp, taking proper
1070 ;; account of macros and escaped EOLs.
1074 ;; Give up if we hit an unbalanced block. Since the
1075 ;; stack won't be empty the code below will report a
1076 ;; suitable error.
1079 ;; Have we moved into a macro?
1082 ;; Have we crossed a statement boundary? If not,
1083 ;; keep going back until we find one or a "real" sexp.
1090 ;; Have we just gone back over an escaped NL? This
1091 ;; doesn't count as a sexp.
1094 ;; Have we crossed a statement boundary?
1097 ;; Are we at a macro beginning?
1099 c-opt-cpp-prefix
1105 ;; Just gone back over a brace block?
1114 ;; Just gone back over some paren block?
1118 before-sws-pos)))
1121 ;; Just gone back over an ordinary symbol of some sort?
1127 ptok tok
1128 tok boundary-pos
1130 ;; Like a C "continue". Analyze the next sexp.
1133 ;; ObjC method def?
1140 ;; Might we have a bitfield declaration, "<type> <id> : <size>"?
1143 ;; The : <size> and <id> fields?
1153 ;; The <type> field?
1161 bitfield-id-pos nil)))))
1163 ;; Handle labels.
1166 ;; `c-crosses-statement-barrier-p' has found a colon, so we
1167 ;; might be in a label now. Have we got a real label
1168 ;; (including a case label) or something like C++'s "public:"?
1169 ;; A case label might use an expression rather than a token.
1172 ;; Catch C++'s inheritance construct "class foo : bar".
1186 ; been found.
1188 ;; We're in a potential label and it's the first
1189 ;; time we've found something that isn't allowed in
1190 ;; one.
1193 ;; We've moved back by a sexp, so update the token positions.
1195 pptok ptok
1196 ptok tok
1202 ;; If the stack isn't empty there might be errors to report.
1211 ;; Need to investigate closer whether we've crossed
1212 ;; between a substatement and its containing statement.
1216 pptok)
1218 ptok)
1226 after-labels-pos
1233 last-label-pos
1234 pos))
1236 ;; We're in a label. Maybe we should step to the statement
1237 ;; after it.
1242 ;; Might have jumped over several labels. Go to the last one.
1245 ;; Have we got "case <expression>:"?
1255 ;; Skip over the unary operators that can start the statement.
1258 ;; protect AWK post-inc/decrement operators, etc.
1263 ret)))
1266 "Return non-nil if there is a non-comment non-macro punctuation character
1267 between FROM and TO. FROM must not be in a string or comment. The returned
1268 value is the position of the first such character."
1279 "Return non-nil if buffer positions FROM to TO cross one or more
1280 statement or declaration boundaries. The returned value is actually
1281 the position of the earliest boundary char. FROM must not be within
1282 a string or comment.
1284 The variable `c-maybe-labelp' is set to the position of the first `:' that
1285 might start a label (i.e. not part of `::' and not preceded by `?'). If a
1286 single `?' is found, then `c-maybe-labelp' is cleared.
1288 For AWK, a statement which is terminated by an EOL (not a ; or a }) is
1290 the line. If this virtual semicolon is _at_ from, the function recognizes it.
1292 Note that this function might do hidden buffer changes. See the
1293 comment at the start of cc-engine.el for more info."
1295 ;; If the current language has CPP macros, insert # into skip-chars.
1298 c-opt-cpp-symbol ; usually "#"
1300 c-stmt-delim-chars))
1303 lit-range vsemi-pos)
1310 skip-chars
1314 ;; Virtual semicolon?
1324 ;; In a string/comment?
1331 ;; Ignore scope operators.
1335 ;; A question mark. Can't be a label, so stop
1336 ;; looking for more : and ?.
1339 ;; At a CPP construct or a "#" or "##" operator?
1350 ;; In trailing space after an as yet undetected virtual semicolon?
1353 ; unterminated string/regexp.
1358 nil))))))
1361 "Return non-nil if the point is at the first token in a statement
1362 or somewhere in the syntactic whitespace before it.
1365 Any kind of declaration-like construct that occur outside function
1368 Note that this function might do hidden buffer changes. See the
1369 comment at the start of cc-engine.el for more info."
1373 c-maybe-labelp)
1384 "Return non-nil if the point is at the first token in an expression or
1385 statement, or somewhere in the syntactic whitespace before it.
1388 grammar sense: It's any sequence of expression tokens except commas,
1389 unless they are enclosed inside parentheses of some kind. Also, an
1390 expression never continues past an enclosing parenthesis, but it might
1391 contain parenthesis pairs of any sort except braces.
1393 Since expressions never cross statement boundaries, this function also
1394 recognizes statement beginnings, just like `c-at-statement-start-p'.
1396 Note that this function might do hidden buffer changes. See the
1397 comment at the start of cc-engine.el for more info."
1402 c-maybe-labelp)
1410 \f
1411 ;; A set of functions that covers various idiosyncrasies in
1412 ;; implementations of `forward-comment'.
1414 ;; Note: Some emacsen considers incorrectly that any line comment
1415 ;; ending with a backslash continues to the next line. I can't think
1416 ;; of any way to work around that in a reliable way without changing
1417 ;; the buffer, though. Suggestions welcome. ;) (No, temporarily
1418 ;; changing the syntax for backslash doesn't work since we must treat
1419 ;; escapes in string literals correctly.)
1422 "Move forward past whitespace and the closest following comment, if any.
1423 Return t if a comment was found, nil otherwise. In either case, the
1424 point is moved past the following whitespace. Line continuations,
1425 i.e. a backslashes followed by line breaks, are treated as whitespace.
1426 The line breaks that end line comments are considered to be the
1427 comment enders, so the point will be put on the beginning of the next
1428 line if it moved past a line comment.
1430 This function does not do any hidden buffer changes."
1438 ;; Some emacsen (e.g. XEmacs 21) return t when moving
1439 ;; forwards at eob.
1440 nil
1442 ;; Emacs includes the ending newline in a b-style (c++)
1443 ;; comment, but XEmacs doesn't. We depend on the Emacs
1444 ;; behavior (which also is symmetric).
1448 t))))
1451 "Move forward past all following whitespace and comments.
1452 Line continuations, i.e. a backslashes followed by line breaks, are
1453 treated as whitespace.
1455 Note that this function might do hidden buffer changes. See the
1456 comment at the start of cc-engine.el for more info."
1459 ;; If forward-comment in at least XEmacs 21 is given a large
1460 ;; positive value, it'll loop all the way through if it hits
1461 ;; eob.
1463 ;; Some emacsen (e.g. XEmacs 21) return t when moving
1464 ;; forwards at eob.
1469 t))))
1472 "Move backward past whitespace and the closest preceding comment, if any.
1473 Return t if a comment was found, nil otherwise. In either case, the
1474 point is moved past the preceding whitespace. Line continuations,
1475 i.e. a backslashes followed by line breaks, are treated as whitespace.
1476 The line breaks that end line comments are considered to be the
1477 comment enders, so the point cannot be at the end of the same line to
1478 move over a line comment.
1480 This function does not do any hidden buffer changes."
1483 ;; When we got newline terminated comments, forward-comment in all
1484 ;; supported emacsen so far will stop at eol of each line not
1485 ;; ending with a comment when moving backwards. This corrects for
1486 ;; that, and at the same time handles line continuations.
1494 ;; Some emacsen (e.g. Emacs 19.34) return t when moving
1495 ;; backwards at bob.
1496 nil
1498 ;; Leave point after the closest following newline if we've
1499 ;; backed up over any above, since forward-comment won't move
1500 ;; backward over a line comment if point is at the end of the
1501 ;; same line.
1506 ;; If forward-comment above succeeded and we're at eol
1507 ;; then the newline we moved over above didn't end a
1508 ;; line comment, so we give it another go.
1510 t))
1512 ;; Emacs <= 20 and XEmacs move back over the closer of a
1513 ;; block comment that lacks an opener.
1516 t)))))
1519 "Move backward past all preceding whitespace and comments.
1520 Line continuations, i.e. a backslashes followed by line breaks, are
1521 treated as whitespace. The line breaks that end line comments are
1522 considered to be the comment enders, so the point cannot be at the end
1523 of the same line to move over a line comment. Unlike
1524 c-backward-syntactic-ws, this function doesn't move back over
1525 preprocessor directives.
1527 Note that this function might do hidden buffer changes. See the
1528 comment at the start of cc-engine.el for more info."
1532 ;; `forward-comment' in some emacsen (e.g. XEmacs 21.4)
1533 ;; return t when moving backwards at bob.
1539 ;; Cope specifically with ^M^J here -
1540 ;; forward-comment sometimes gets stuck after ^Ms,
1541 ;; sometimes after ^M^J.
1545 t)
1549 t))))
1550 moved-comment)
1552 ;; Emacs <= 20 and XEmacs move back over the
1553 ;; closer of a block comment that lacks an opener.
1555 t)
1557 ;; XEmacs treats line continuations as whitespace but
1558 ;; only in the backward direction, which seems a bit
1559 ;; odd. Anyway, this is necessary for Emacs.
1564 t))))))
1566 \f
1567 ;; Tools for skipping over syntactic whitespace.
1569 ;; The following functions use text properties to cache searches over
1570 ;; large regions of syntactic whitespace. It works as follows:
1571 ;;
1572 ;; o If a syntactic whitespace region contains anything but simple
1573 ;; whitespace (i.e. space, tab and line breaks), the text property
1574 ;; `c-in-sws' is put over it. At places where we have stopped
1575 ;; within that region there's also a `c-is-sws' text property.
1576 ;; That since there typically are nested whitespace inside that
1577 ;; must be handled separately, e.g. whitespace inside a comment or
1578 ;; cpp directive. Thus, from one point with `c-is-sws' it's safe
1579 ;; to jump to another point with that property within the same
1580 ;; `c-in-sws' region. It can be likened to a ladder where
1581 ;; `c-in-sws' marks the bars and `c-is-sws' the rungs.
1582 ;;
1583 ;; o The `c-is-sws' property is put on the simple whitespace chars at
1584 ;; a "rung position" and also maybe on the first following char.
1585 ;; As many characters as can be conveniently found in this range
1586 ;; are marked, but no assumption can be made that the whole range
1587 ;; is marked (it could be clobbered by later changes, for
1588 ;; instance).
1589 ;;
1590 ;; Note that some part of the beginning of a sequence of simple
1591 ;; whitespace might be part of the end of a preceding line comment
1592 ;; or cpp directive and must not be considered part of the "rung".
1593 ;; Such whitespace is some amount of horizontal whitespace followed
1594 ;; by a newline. In the case of cpp directives it could also be
1595 ;; two newlines with horizontal whitespace between them.
1596 ;;
1597 ;; The reason to include the first following char is to cope with
1598 ;; "rung positions" that don't have any ordinary whitespace. If
1599 ;; `c-is-sws' is put on a token character it does not have
1600 ;; `c-in-sws' set simultaneously. That's the only case when that
1601 ;; can occur, and the reason for not extending the `c-in-sws'
1602 ;; region to cover it is that the `c-in-sws' region could then be
1603 ;; accidentally merged with a following one if the token is only
1604 ;; one character long.
1605 ;;
1606 ;; o On buffer changes the `c-in-sws' and `c-is-sws' properties are
1607 ;; removed in the changed region. If the change was inside
1608 ;; syntactic whitespace that means that the "ladder" is broken, but
1609 ;; a later call to `c-forward-sws' or `c-backward-sws' will use the
1610 ;; parts on either side and use an ordinary search only to "repair"
1611 ;; the gap.
1612 ;;
1613 ;; Special care needs to be taken if a region is removed: If there
1614 ;; are `c-in-sws' on both sides of it which do not connect inside
1615 ;; the region then they can't be joined. If e.g. a marked macro is
1616 ;; broken, syntactic whitespace inside the new text might be
1617 ;; marked. If those marks would become connected with the old
1618 ;; `c-in-sws' range around the macro then we could get a ladder
1619 ;; with one end outside the macro and the other at some whitespace
1620 ;; within it.
1621 ;;
1622 ;; The main motivation for this system is to increase the speed in
1623 ;; skipping over the large whitespace regions that can occur at the
1624 ;; top level in e.g. header files that contain a lot of comments and
1625 ;; cpp directives. For small comments inside code it's probably
1626 ;; slower than using `forward-comment' straightforwardly, but speed is
1627 ;; not a significant factor there anyway.
1629 ; (defface c-debug-is-sws-face
1630 ; '((t (:background "GreenYellow")))
1631 ; "Debug face to mark the `c-is-sws' property.")
1632 ; (defface c-debug-in-sws-face
1633 ; '((t (:underline t)))
1634 ; "Debug face to mark the `c-in-sws' property.")
1636 ; (defun c-debug-put-sws-faces ()
1637 ; ;; Put the sws debug faces on all the `c-is-sws' and `c-in-sws'
1638 ; ;; properties in the buffer.
1639 ; (interactive)
1640 ; (save-excursion
1641 ; (c-save-buffer-state (in-face)
1642 ; (goto-char (point-min))
1643 ; (setq in-face (if (get-text-property (point) 'c-is-sws)
1644 ; (point)))
1645 ; (while (progn
1646 ; (goto-char (next-single-property-change
1647 ; (point) 'c-is-sws nil (point-max)))
1648 ; (if in-face
1649 ; (progn
1650 ; (c-debug-add-face in-face (point) 'c-debug-is-sws-face)
1651 ; (setq in-face nil))
1652 ; (setq in-face (point)))
1653 ; (not (eobp))))
1654 ; (goto-char (point-min))
1655 ; (setq in-face (if (get-text-property (point) 'c-in-sws)
1656 ; (point)))
1657 ; (while (progn
1658 ; (goto-char (next-single-property-change
1659 ; (point) 'c-in-sws nil (point-max)))
1660 ; (if in-face
1661 ; (progn
1662 ; (c-debug-add-face in-face (point) 'c-debug-in-sws-face)
1663 ; (setq in-face nil))
1664 ; (setq in-face (point)))
1665 ; (not (eobp)))))))
1668 ;;`(message ,@args)
1669 )
1672 ;; This macro does a hidden buffer change.
1679 ;; This macro does a hidden buffer change.
1686 ;; This macro does a hidden buffer change.
1693 ;; This macro does a hidden buffer change.
1700 ;; This macro does a hidden buffer change.
1708 ;; Called from `after-change-functions'. Note that if
1709 ;; `c-forward-sws' or `c-backward-sws' are used outside
1710 ;; `c-save-buffer-state' or similar then this will remove the cache
1711 ;; properties right after they're added.
1712 ;;
1713 ;; This function does hidden buffer changes.
1716 ;; Adjust the end to remove the properties in any following simple
1717 ;; ws up to and including the next line break, if there is any
1718 ;; after the changed region. This is necessary e.g. when a rung
1719 ;; marked empty line is converted to a line comment by inserting
1720 ;; "//" before the line break. In that case the line break would
1721 ;; keep the rung mark which could make a later `c-backward-sws'
1722 ;; move into the line comment instead of over it.
1732 ;; Ensure that an `c-in-sws' range gets broken. Note that it isn't
1733 ;; safe to keep a range that was continuous before the change. E.g:
1734 ;;
1735 ;; #define foo
1736 ;; \
1737 ;; bar
1738 ;;
1739 ;; There can be a "ladder" between "#" and "b". Now, if the newline
1740 ;; after "foo" is removed then "bar" will become part of the cpp
1741 ;; directive instead of a syntactically relevant token. In that
1742 ;; case there's no longer syntactic ws from "#" to "b".
1749 ;; Used by `c-forward-syntactic-ws' to implement the unbounded search.
1750 ;;
1751 ;; This function might do hidden buffer changes.
1754 ;; unmarked part of the simple ws region.
1756 rung-is-marked next-rung-is-marked simple-ws-end
1757 ;; `safe-start' is set when it's safe to cache the start position.
1758 ;; It's not set if we've initially skipped over comments and line
1759 ;; continuations since we might have gone out through the end of a
1760 ;; macro then. This provision makes `c-forward-sws' not populate the
1761 ;; cache in the majority of cases, but otoh is `c-backward-sws' by far
1762 ;; more common.
1763 safe-start)
1765 ;; Skip simple ws and do a quick check on the following character to see
1766 ;; if it's anything that can't start syntactic ws, so we can bail out
1767 ;; early in the majority of cases when there just are a few ws chars.
1776 ;; Find the last rung position to avoid setting properties in all
1777 ;; the cases when the marked rung is complete.
1778 ;; (`next-single-property-change' is certain to move at least one
1779 ;; step forward.)
1782 ;; Got no marked rung here. Since the simple ws might have started
1783 ;; inside a line comment or cpp directive we must set `rung-pos' as
1784 ;; high as possible.
1790 ;; In the following while form, we move over a "ladder" and
1791 ;; following simple WS each time round the loop, appending the WS
1792 ;; onto the ladder, joining adjacent ladders, and terminating when
1793 ;; there is no more WS or we reach EOB.
1798 ;; The following search is the main reason that `c-in-sws'
1799 ;; and `c-is-sws' aren't combined to one property.
1803 ;; If the `c-in-sws' region extended past the last
1804 ;; `c-is-sws' char we have to go back a bit.
1811 "c-forward-sws cached move %s -> %s (max %s)"
1818 ;; We'll loop here if there is simple ws after the last rung.
1819 ;; That means that there's been some change in it and it's
1820 ;; possible that we've stepped into another ladder, so extend
1821 ;; the previous one to join with it if there is one, and try to
1822 ;; use the cache again.
1824 "c-forward-sws extending rung with [%s..%s] (max %s)"
1827 ;; Remove any `c-in-sws' property from the last char of
1828 ;; the rung before we mark it with `c-is-sws', so that we
1829 ;; won't connect with the remains of a broken "ladder".
1835 last-put-in-sws-pos rung-pos)))
1837 ;; Now move over any comments (x)or a CPP construct.
1843 ;; Skipped over comments. Don't cache at eob in case the buffer
1844 ;; is narrowed.
1855 ;; Skip a preprocessor directive.
1862 ;; Don't cache at eob in case the buffer is narrowed.
1867 ;; Skip over a noise macro.
1872 ;; We've searched over a piece of non-white syntactic ws. See if this
1873 ;; can be cached.
1879 ;; Cache if we haven't skipped comments only, and if we started
1880 ;; either from a marked rung or from a completely uncached
1881 ;; position.
1886 ;; See if there's a marked rung in the encountered simple ws. If
1887 ;; so then we can cache, unless `safe-start' is nil. Even then
1888 ;; we need to do this to check if the cache can be used for the
1889 ;; next step.
1893 safe-start))
1897 "c-forward-sws caching [%s..%s] - [%s..%s] (max %s)"
1901 ;; Remove the properties for any nested ws that might be cached.
1902 ;; Only necessary for `c-is-sws' since `c-in-sws' will be set
1903 ;; anyway.
1911 last-put-in-sws-pos rung-pos))
1913 ;; Remove any `c-in-sws' property from the last char of
1914 ;; the rung before we mark it with `c-is-sws', so that we
1915 ;; won't connect with the remains of a broken "ladder".
1918 rung-end-pos))
1921 "c-forward-sws not caching [%s..%s] - [%s..%s] (max %s)"
1925 ;; Set `rung-pos' for the next rung. It's the same thing here as
1926 ;; initially, except that the rung position is set as early as
1927 ;; possible since we can't be in the ending ws of a line comment or
1928 ;; cpp directive now.
1935 ;; Make sure that the newly marked `c-in-sws' region doesn't connect to
1936 ;; another one after the point (which might occur when editing inside a
1937 ;; comment or macro).
1941 "c-forward-sws clearing at %s for cache separation"
1942 last-put-in-sws-pos)
1946 ;; If at eob we have to clear the last character before the end
1947 ;; instead since the buffer might be narrowed and there might
1948 ;; be a `c-in-sws' after (point-max). In this case it's
1949 ;; necessary to clear both properties.
1951 "c-forward-sws clearing thoroughly at %s for cache separation"
1954 last-put-in-sws-pos))))
1955 ))))
1958 ;; Used by `c-backward-syntactic-ws' to implement the unbounded search.
1959 ;;
1960 ;; This function might do hidden buffer changes.
1963 ;; part of the simple ws region.
1965 rung-is-marked simple-ws-beg cmt-skip-pos)
1967 ;; Skip simple horizontal ws and do a quick check on the preceding
1968 ;; character to see if it's anything that can't end syntactic ws, so we can
1969 ;; bail out early in the majority of cases when there just are a few ws
1970 ;; chars. Newlines are complicated in the backward direction, so we can't
1971 ;; skip over them.
1981 ;; Try to find a rung position in the simple ws preceding point, so that
1982 ;; we can get a cache hit even if the last bit of the simple ws has
1983 ;; changed recently.
1989 ;; `rung-pos' will be the earliest marked position, which means that
1990 ;; there might be later unmarked parts in the simple ws region.
1991 ;; It's not worth the effort to fix that; the last part of the
1992 ;; simple ws is also typically edited often, so it could be wasted.
1999 ;; Each time round the next while form, we move back over a ladder
2000 ;; and append any simple WS preceding it, if possible joining with
2001 ;; the previous ladder.
2007 ;; The following search is the main reason that `c-in-sws'
2008 ;; and `c-is-sws' aren't combined to one property.
2012 ;; If the `c-in-sws' region extended past the first
2013 ;; `c-is-sws' char we have to go forward a bit.
2018 "c-backward-sws cached move %s <- %s (min %s)"
2030 t
2032 nil))
2034 ;; We'll loop here if there is simple ws before the first rung.
2035 ;; That means that there's been some change in it and it's
2036 ;; possible that we've stepped into another ladder, so extend
2037 ;; the previous one to join with it if there is one, and try to
2038 ;; use the cache again.
2040 "c-backward-sws extending rung with [%s..%s] (min %s)"
2043 ;; Remove any `c-in-sws' property from the last char of
2044 ;; the rung before we mark it with `c-is-sws', so that we
2045 ;; won't connect with the remains of a broken "ladder".
2048 rung-pos)
2052 last-put-in-sws-pos rung-pos))
2061 ;; Inside a cpp directive. See if it should be skipped over.
2064 ;; Move back over all line continuations in the region skipped
2065 ;; over by `c-backward-comments'. If we go past it then we
2066 ;; started inside the cpp directive.
2075 ;; Don't move past the cpp directive if we began inside
2076 ;; it. Note that the position at the end of the last line
2077 ;; of the macro is also considered to be within it.
2079 nil)
2081 ;; It's worthwhile to spend a little bit of effort on finding
2082 ;; the end of the macro, to get a good `simple-ws-beg'
2083 ;; position for the cache. Note that `c-backward-comments'
2084 ;; could have stepped over some comments before going into
2085 ;; the macro, and then `simple-ws-beg' must be kept on the
2086 ;; same side of those comments.
2093 ;; Might happen if comments after the macro were skipped
2094 ;; over.
2098 t)))
2103 simple-ws-beg)
2104 ;; Skipped over comments. Must put point at the end of
2105 ;; the simple ws at point since we might be after a line
2106 ;; comment or cpp directive that's been partially
2107 ;; narrowed out, and we can't risk marking the simple ws
2108 ;; at the end of it.
2110 t)
2117 ;; Skipped over a noise macro
2119 t)))
2121 ;; We've searched over a piece of non-white syntactic ws. See if this
2122 ;; can be cached.
2127 ;; Cache if we started either from a marked rung or from a
2128 ;; completely uncached position.
2129 rung-is-marked
2132 ;; Cache if there's a marked rung in the encountered simple ws.
2140 "c-backward-sws caching [%s..%s] - [%s..%s] (min %s)"
2145 ;; Remove the properties for any nested ws that might be cached.
2146 ;; Only necessary for `c-is-sws' since `c-in-sws' will be set
2147 ;; anyway.
2152 ;; Remove any `c-in-sws' property from the last char of
2153 ;; the rung before we mark it with `c-is-sws', so that we
2154 ;; won't connect with the remains of a broken "ladder".
2157 rung-end-pos)
2160 last-put-in-sws-pos simple-ws-beg)
2161 rung-pos)
2166 "c-backward-sws not caching [%s..%s] - [%s..%s] (min %s)"
2172 ))
2174 ;; Make sure that the newly marked `c-in-sws' region doesn't connect to
2175 ;; another one before the point (which might occur when editing inside a
2176 ;; comment or macro).
2180 "c-backward-sws clearing at %s for cache separation"
2183 last-put-in-sws-pos))
2185 ;; If at bob and the buffer is narrowed, we have to clear the
2186 ;; character we're standing on instead since there might be a
2187 ;; `c-in-sws' before (point-min). In this case it's necessary
2188 ;; to clear both properties.
2190 "c-backward-sws clearing thoroughly at %s for cache separation"
2191 last-put-in-sws-pos)
2194 ))))
2196 \f
2197 ;; Other whitespace tools
2199 ;; Is the region (beg end) WS, and is there WS (or BOB/EOB) next to the
2200 ;; region? This is a "heuristic" function. .....
2201 ;;
2202 ;; The motivation for the second bit is to check whether removing this
2203 ;; region would coalesce two symbols.
2204 ;;
2205 ;; FIXME!!! This function doesn't check virtual semicolons in any way. Be
2206 ;; careful about using this function for, e.g. AWK. (2007/3/7)
2215 \f
2216 ;; A system for finding noteworthy parens before the point.
2219 ;; A maximum comfortable scanning distance, e.g. between
2220 ;; `c-state-cache-good-pos' and "HERE" (where we call c-parse-state). When
2221 ;; this distance is exceeded, we take "emergency measures", e.g. by clearing
2222 ;; the cache and starting again from point-min or a beginning of defun. This
2223 ;; value can be tuned for efficiency or set to a lower value for testing.
2227 ;; The state cache used by `c-parse-state' to cut down the amount of
2228 ;; searching. It's the result from some earlier `c-parse-state' call. See
2229 ;; `c-parse-state''s doc string for details of its structure.
2230 ;;
2231 ;; The use of the cached info is more effective if the next
2232 ;; `c-parse-state' call is on a line close by the one the cached state
2233 ;; was made at; the cache can actually slow down a little if the
2234 ;; cached state was made very far back in the buffer. The cache is
2235 ;; most effective if `c-parse-state' is used on each line while moving
2236 ;; forward.
2240 ;; This is a position where `c-state-cache' is known to be correct, or
2241 ;; nil (see below). It's a position inside one of the recorded unclosed
2242 ;; parens or the top level, but not further nested inside any literal or
2243 ;; subparen that is closed before the last recorded position.
2244 ;;
2245 ;; The exact position is chosen to try to be close to yet earlier than
2246 ;; the position where `c-state-cache' will be called next. Right now
2247 ;; the heuristic is to set it to the position after the last found
2248 ;; closing paren (of any type) before the line on which
2249 ;; `c-parse-state' was called. That is chosen primarily to work well
2250 ;; with refontification of the current line.
2251 ;;
2252 ;; 2009-07-28: When `c-state-point-min' and the last position where
2253 ;; `c-parse-state' or for which `c-invalidate-state-cache' was called, are
2254 ;; both in the same literal, there is no such "good position", and
2255 ;; c-state-cache-good-pos is then nil. This is the ONLY circumstance in which
2256 ;; it can be nil. In this case, `c-state-point-min-literal' will be non-nil.
2257 ;;
2258 ;; 2009-06-12: In a brace desert, c-state-cache-good-pos may also be in
2259 ;; the middle of the desert, as long as it is not within a brace pair
2260 ;; recorded in `c-state-cache' or a paren/bracket pair.
2262 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2263 ;; We maintain a simple cache of positions which aren't in a literal, so as to
2264 ;; speed up testing for non-literality.
2266 ;; The approximate interval between entries in `c-state-nonlit-pos-cache'.
2270 ;; A list of buffer positions which are known not to be in a literal or a cpp
2271 ;; construct. This is ordered with higher positions at the front of the list.
2272 ;; Only those which are less than `c-state-nonlit-pos-cache-limit' are valid.
2276 ;; An upper limit on valid entries in `c-state-nonlit-pos-cache'. This is
2277 ;; reduced by buffer changes, and increased by invocations of
2278 ;; `c-state-literal-at'.
2282 ;; A list of buffer positions which are known not to be in a literal. This is
2283 ;; ordered with higher positions at the front of the list. Only those which
2284 ;; are less than `c-state-semi-nonlit-pos-cache-limit' are valid.
2288 ;; An upper limit on valid entries in `c-state-semi-nonlit-pos-cache'. This is
2289 ;; reduced by buffer changes, and increased by invocations of
2290 ;; `c-state-literal-at'. FIXME!!!
2293 ;; Do a parse-partial-sexp from FROM to TO, returning either
2294 ;; (STATE TYPE (BEG . END)) if TO is in a literal; or
2295 ;; (STATE) otherwise,
2296 ;; where STATE is the parsing state at TO, TYPE is the type of the literal
2297 ;; (one of 'c, 'c++, 'string) and (BEG . END) is the boundaries of the literal,
2298 ;; including the delimiters.
2299 ;;
2300 ;; Unless NOT-IN-DELIMITER is non-nil, when TO is inside a two-character
2301 ;; comment opener, this is recognized as being in a comment literal.
2302 ;;
2303 ;; Only elements 3 (in a string), 4 (in a comment), 5 (following a quote),
2304 ;; 7 (comment type) and 8 (start of comment/string) (and possibly 9) of
2305 ;; STATE are valid.
2309 ty co-st)
2317 nil ; TARGETDEPTH
2318 nil ; STOPBEFORE
2319 s ; OLDSTATE
2336 ;; Return a buffer position before HERE which is "safe", i.e. outside any
2337 ;; string, comment, or macro.
2338 ;;
2339 ;; NOTE: This function manipulates `c-state-nonlit-pos-cache'. This cache
2340 ;; MAY NOT contain any positions within macros, since macros are frequently
2341 ;; turned into comments by use of the `c-cpp-delimiter' category properties.
2342 ;; We cannot rely on this mechanism whilst determining a cache pos since
2343 ;; this function is also called from outwith `c-parse-state'.
2348 pos npos high-pos lit macro-beg macro-end)
2349 ;; Trim the cache to take account of buffer changes.
2361 ;; Add an element to `c-state-nonlit-pos-cache' each iteration.
2367 ;; Test for being in a literal. If so, go to after it.
2374 ;; Test for being in a macro. If so, go to after it.
2389 ;; Add one extra element above HERE so as to to avoid the previous
2390 ;; expensive calculation when the next call is close to the current
2391 ;; one. This is especially useful when inside a large macro.
2398 pos))))
2401 ;; Return a buffer position before HERE which is "safe", i.e. outside any
2402 ;; string or comment. It may be in a macro.
2407 pos npos high-pos lit macro-beg macro-end)
2408 ;; Trim the cache to take account of buffer changes.
2420 ;; Add an element to `c-state-semi-nonlit-pos-cache' each iteration.
2424 ;; Test for being in a literal. If so, go to after it.
2437 pos))))
2440 ;; If position HERE is inside a literal, return (START . END), the
2441 ;; boundaries of the literal (which may be outside the accessible bit of the
2442 ;; buffer). Otherwise, return nil.
2443 ;;
2444 ;; This function is almost the same as `c-literal-limits'. Previously, it
2445 ;; differed in that it was a lower level function, and that it rigorously
2446 ;; followed the syntax from BOB. `c-literal-limits' is now (2011-12)
2447 ;; virtually identical to this function.
2455 ;; Return the start of the literal containing POS, or POS itself.
2457 pos))
2460 ;; Return a position outside of a string/comment/macro at or before POS.
2461 ;; STATE is the parse-partial-sexp state at POS.
2465 pos)))
2470 res))))
2472 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2473 ;; Stuff to do with point-min, and coping with any literal there.
2476 ;; This is (point-min) when `c-state-cache' was last calculated. A change of
2477 ;; narrowing is likely to affect the parens that are visible before the point.
2483 ;; These two variables define the literal, if any, containing point-min.
2484 ;; Their values are, respectively, 'string, c, or c++, and the start of the
2485 ;; literal. If there's no literal there, they're both nil.
2489 ;; This is the earliest buffer-pos from which scanning can be done. It is
2490 ;; either the end of the literal containing point-min, or point-min itself.
2491 ;; It becomes nil if the buffer is changed earlier than this point.
2493 ;; Return the lowest valid scanning pos. This will be the end of the
2494 ;; literal enclosing point-min, or point-min itself.
2506 ;; Determine the properties of any literal containing POINT-MIN, setting the
2507 ;; variables `c-state-point-min-lit-type', `c-state-point-min-lit-start',
2508 ;; and `c-state-min-scan-pos' accordingly. The return value is meaningless.
2510 lit)
2525 c-state-point-min-lit-start nil
2526 c-state-min-scan-pos p-min)))))
2529 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2530 ;; A variable which signals a brace dessert - helpful for reducing the number
2531 ;; of fruitless backward scans.
2534 ;; Used only in `c-append-lower-brace-pair-to-state-cache'. It is set when
2535 ;; that defun has searched backwards for a brace pair and not found one. Its
2536 ;; value is either nil or a cons (PA . FROM), where PA is the position of the
2537 ;; enclosing opening paren/brace/bracket which bounds the backwards search (or
2538 ;; nil when at top level) and FROM is where the backward search started. It
2539 ;; is reset to nil in `c-invalidate-state-cache'.
2542 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2543 ;; Lowish level functions/macros which work directly on `c-state-cache', or a
2544 ;; list of like structure.
2546 ;; Return the address of the top left brace/bracket/paren recorded in CACHE
2547 ;; (default `c-state-cache') (or nil).
2554 ;; Return the address of the latest brace/bracket/paren (whether left or
2555 ;; right) recorded in CACHE (default `c-state-cache') or nil.
2562 ;; Return the position just after the latest brace/bracket/paren (whether
2563 ;; left or right) recorded in CACHE (default `c-state-cache') or nil.
2571 ;; From the state-cache, determine the buffer position from which we might
2572 ;; scan forward to HERE to update this cache. This position will be just
2573 ;; after a paren/brace/bracket recorded in the cache, if possible, otherwise
2574 ;; return the earliest position in the accessible region which isn't within
2575 ;; a literal. If the visible portion of the buffer is entirely within a
2576 ;; literal, return NIL.
2578 ;(while (>= (or (c-state-cache-top-lparen c) 1) here)
2594 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2595 ;; Variables which keep track of preprocessor constructs.
2604 ;; These are the limits of the macro containing point at the previous call of
2605 ;; `c-parse-state', or nil.
2607 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2608 ;; Defuns which analyze the buffer, yet don't change `c-state-cache'.
2610 ;; Return a start position for building `c-state-cache' from
2611 ;; scratch. This will be at the top level, 2 defuns back.
2613 ;; Go back 2 bods, but ignore any bogus positions returned by
2614 ;; beginning-of-defun (i.e. open paren in column zero).
2624 ;; Return the position of the opening paren/brace/bracket before HERE- which
2625 ;; matches the outermost close p/b/b between HERE+ and TOP. Except when
2626 ;; there's a macro, HERE- and HERE+ are the same. Like this:
2627 ;;
2628 ;; ............................................
2629 ;; | |
2630 ;; ( [ ( .........#macro.. ) ( ) ] )
2631 ;; ^ ^ ^ ^
2632 ;; | | | |
2633 ;; return HERE- HERE+ TOP
2634 ;;
2635 ;; If there aren't enough opening paren/brace/brackets, return the position
2636 ;; of the outermost one found, or HERE- if there are none. If there are no
2637 ;; closing p/b/bs between HERE+ and TOP, return HERE-. HERE-/+ and TOP
2638 ;; must not be inside literals. Only the accessible portion of the buffer
2639 ;; will be scanned.
2641 ;; PART 1: scan from `here+' up to `top', accumulating ")"s which enclose
2642 ;; `here'. Go round the next loop each time we pass over such a ")". These
2643 ;; probably match "("s before `here-'.
2655 ;; PART 2: Scan back before `here-' searching for the "("s
2656 ;; matching/mismatching the ")"s found above. We only need to direct the
2657 ;; caller to scan when we've encountered unmatched right parens.
2666 pos))
2669 ;; Determine the scanning strategy for adjusting `c-parse-state', attempting
2670 ;; to minimize the amount of scanning. HERE is the pertinent position in
2671 ;; the buffer, GOOD-POS is a position where `c-state-cache' (possibly with
2672 ;; its head trimmed) is known to be good, or nil if there is no such
2673 ;; position.
2674 ;;
2675 ;; The return value is a list, one of the following:
2676 ;;
2677 ;; o - ('forward START-POINT) - scan forward from START-POINT,
2678 ;; which is not less than the highest position in `c-state-cache' below HERE,
2679 ;; which is after GOOD-POS.
2680 ;; o - ('backward nil) - scan backwards (from HERE).
2681 ;; o - ('back-and-forward START-POINT) - like 'forward, but when HERE is earlier
2682 ;; than GOOD-POS.
2683 ;; o - ('BOD START-POINT) - scan forwards from START-POINT, which is at the
2684 ;; top level.
2685 ;; o - ('IN-LIT nil) - point is inside the literal containing point-min.
2687 BOD-pos ; position of 2nd BOD before HERE.
2688 strategy ; 'forward, 'backward, 'BOD, or 'IN-LIT.
2689 start-point
2695 start-point nil
2696 cache-pos nil
2707 start-point cache-pos
2710 ;; Might we be better off starting from the top level, two defuns back,
2711 ;; instead? This heuristic no longer works well in C++, where
2712 ;; declarations inside namespace brace blocks are frequently placed at
2713 ;; column zero. (2015-11-10): Remove the condition on C++ Mode.
2715 open-paren-in-column-0-is-defun-start)
2716 ;; (not (c-major-mode-is 'c++-mode))
2721 start-point BOD-pos)))
2726 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2727 ;; Routines which change `c-state-cache' and associated values.
2729 ;; The region (more precisely, point-min) has changed since we
2730 ;; calculated `c-state-cache'. Amend `c-state-cache' accordingly.
2732 ;; If point-min has MOVED BACKWARDS then we drop the state completely.
2733 ;; It would be possible to do a better job here and recalculate the top
2734 ;; only.
2738 c-state-cache-good-pos c-state-min-scan-pos
2739 c-state-brace-pair-desert nil))
2741 ;; point-min has MOVED FORWARD.
2743 ;; Is the new point-min inside a (different) literal?
2748 ;; Cut off a bit of the tail from `c-state-cache'.
2750 pa)
2759 ; inside a recorded
2760 ; brace pair.
2762 c-state-cache-good-pos c-state-min-scan-pos)
2765 )))
2770 ;; If there is a brace pair preceding FROM in the buffer, at the same level
2771 ;; of nesting (not necessarily immediately preceding), push a cons onto
2772 ;; `c-state-cache' to represent it. FROM must not be inside a literal. If
2773 ;; UPPER-LIM is non-nil, we append the highest brace pair whose "}" is below
2774 ;; UPPER-LIM.
2775 ;;
2776 ;; Return non-nil when this has been done.
2777 ;;
2778 ;; The situation it copes with is this transformation:
2779 ;;
2780 ;; OLD: { (.) {...........}
2781 ;; ^ ^
2782 ;; FROM HERE
2783 ;;
2784 ;; NEW: { {....} (.) {.........
2785 ;; ^ ^ ^
2786 ;; LOWER BRACE PAIR HERE or HERE
2787 ;;
2788 ;; This routine should be fast. Since it can get called a LOT, we maintain
2789 ;; `c-state-brace-pair-desert', a small cache of "failures", such that we
2790 ;; reduce the time wasted in repeated fruitless searches in brace deserts.
2800 ;; Don't start scanning in the middle of a CPP construct unless
2801 ;; it contains HERE - these constructs, in Emacs, are "commented
2802 ;; out" with category properties.
2805 macro-start-or-from
2806 from))
2810 ;; If we're essentially repeating a fruitless search, just give up.
2816 ;; DESERT-LIM. Avoid repeated searching through the cached desert.
2822 ;; CACHE-LIM. This limit will be necessary when an opening
2823 ;; paren at `cache-pos' has just had its matching close paren
2824 ;; inserted into the buffer. `cache-pos' continues to be a
2825 ;; search bound, even though the algorithm below would skip
2826 ;; over the new paren pair.
2835 ;; The top limit is EOB to ensure that `bra' is inside the
2836 ;; accessible part of the buffer at the next scan operation.
2839 ;; In the next pair of nested loops, the inner one moves back past a
2840 ;; pair of (mis-)matching parens or brackets; the outer one moves
2841 ;; back over a sequence of unmatched close brace/paren/bracket each
2842 ;; time round.
2858 ; brace, ignore it.
2861 ;; We've found the desired brace-pair.
2873 ;; We haven't found a brace pair. Record this in the cache.
2876 bra
2881 ;; If BRA+1 is nil, do nothing. Otherwise, BRA+1 is the buffer position
2882 ;; following a {, and that brace has a (mis-)matching } (or ]), and we
2883 ;; "push" "a" brace pair onto `c-state-cache'.
2884 ;;
2885 ;; Here "push" means overwrite the top element if it's itself a brace-pair,
2886 ;; otherwise push it normally.
2887 ;;
2888 ;; The brace pair we push is normally the one surrounding BRA+1, but if the
2889 ;; latter is inside a macro, not being a macro containing
2890 ;; MACRO-START-OR-HERE, we scan backwards through the buffer for a non-macro
2891 ;; base pair. This latter case is assumed to be rare.
2892 ;;
2893 ;; Note: POINT is not preserved in this routine.
2903 c-state-cache)))
2904 ;; N.B. This defsubst codes one method for the simple, normal case,
2905 ;; and a more sophisticated, slower way for the general case. Don't
2906 ;; eliminate this defsubst - it's a speed optimization.
2910 ;; Scan the buffer from FROM to HERE, adding elements into `c-state-cache'
2911 ;; for braces etc. Return a candidate for `c-state-cache-good-pos'.
2912 ;;
2913 ;; FROM must be after the latest brace/paren/bracket in `c-state-cache', if
2914 ;; any. Typically, it is immediately after it. It must not be inside a
2915 ;; literal.
2921 here)))
2924 ; Is actually the pos. to scan for a (/{/[ from,
2925 ; which sometimes is after a silly )/}/].
2928 ; good-pos.
2936 ;; Each time round the following loop, we enter a successively deeper
2937 ;; level of brace/paren nesting. (Except sometimes we "continue at
2938 ;; the existing level".) `pa+1' is a pos inside an opening
2939 ;; brace/paren/bracket, usually just after it.
2942 ;; Each time round the next loop moves forward over an opening then
2943 ;; a closing brace/bracket/paren. This loop is white hot, so it
2944 ;; plays ugly tricks to go fast. DON'T PUT ANYTHING INTO THIS
2945 ;; LOOP WHICH ISN'T ABSOLUTELY NECESSARY!!! It terminates when a
2946 ;; call of `scan-lists' signals an error, which happens when there
2947 ;; are no more b/b/p's to scan.
2958 ;; We've just entered a deeper nesting level.
2960 ;; Insert the brace pair (if present) and the single open
2961 ;; paren/brace/bracket into `c-state-cache' It cannot be
2962 ;; inside a macro, except one around point, because of what
2963 ;; `c-neutralize-syntax-in-CPP' has done.
2965 ;; Insert the opening brace/bracket/paren position.
2967 ;; Clear admin stuff for the next more nested part of the scan.
2971 ;; All open p/b/b's at this nesting level, if any, have probably
2972 ;; been closed by matching/mismatching ones. We're probably
2973 ;; finished - we just need to check for having found an
2974 ;; unmatched )/}/], which we ignore. Such a )/}/] can't be in a
2975 ;; macro, due the action of `c-neutralize-syntax-in-CPP'.
2978 ;; Record the final, innermost, brace-pair if there is one.
2981 ;; Determine a good pos
2989 here-bol))
2998 ;; Remove stale entries from the `c-cache-state', i.e. those which will
2999 ;; not be in it when it is amended for position HERE. This may involve
3000 ;; replacing a CONS element for a brace pair containing HERE with its car.
3001 ;; Additionally, the "outermost" open-brace entry before HERE will be
3002 ;; converted to a cons if the matching close-brace is below HERE.
3003 ;;
3004 ;; START-POINT is a "maximal" "safe position" - there must be no open
3005 ;; parens/braces/brackets between START-POINT and HERE.
3006 ;;
3007 ;; As a second thing, calculate the result of parse-partial-sexp at
3008 ;; PPS-POINT, w.r.t. START-POINT. The motivation here is that
3009 ;; `c-state-cache-good-pos' may become PPS-POINT, but the caller may need to
3010 ;; adjust it to get outside a string/comment. (Sorry about this! The code
3011 ;; needs to be FAST).
3012 ;;
3013 ;; Return a list (GOOD-POS SCAN-BACK-POS CONS-SEPARATED PPS-STATE), where
3014 ;; o - GOOD-POS is a position where the new value `c-state-cache' is known
3015 ;; to be good (we aim for this to be as high as possible);
3016 ;; o - SCAN-BACK-POS, if not nil, indicates there may be a brace pair
3017 ;; preceding POS which needs to be recorded in `c-state-cache'. It is a
3018 ;; position to scan backwards from. It is the position of the "{" of the
3019 ;; last element to be removed from `c-state-cache', when that elt is a
3020 ;; cons, otherwise nil.
3021 ;; o - CONS-SEPARATED is t when a cons element in `c-state-cache' has been
3022 ;; replaced by its car because HERE lies inside the brace pair represented
3023 ;; by the cons.
3024 ;; o - PPS-STATE is the parse-partial-sexp state at PPS-POINT.
3034 ; start-point or nil
3041 ; HERE), or nil.
3047 pps-state ; Will be 9 or 10 elements long.
3048 pos
3049 upper-lim ; ,beyond which `c-state-cache' entries are removed
3050 scan-back-pos
3051 cons-separated
3052 pair-beg pps-point-state target-depth)
3054 ;; Remove entries beyond HERE. Also remove any entries inside
3055 ;; a macro, unless HERE is in the same macro.
3060 here
3066 ;; If `upper-lim' is inside the last recorded brace pair, remove its
3067 ;; RBrace and indicate we'll need to search backwards for a previous
3068 ;; brace pair.
3074 cons-separated t))
3076 ;; The next loop jumps forward out of a nested level of parens each
3077 ;; time round; the corresponding elements in `c-state-cache' are
3078 ;; removed. `pos' is just after the brace-pair or the open paren at
3079 ;; (car c-state-cache). There can be no open parens/braces/brackets
3080 ;; between `start-point'/`start-point-actual-macro-start' and HERE,
3081 ;; due to the interface spec to this function.
3084 in-macro-start)))
3086 ; marked by a `category' text property.
3087 start-point))
3098 ;; Do nothing when we've merely reached pps-point.
3099 )
3101 ;; Scan!
3105 target-depth
3106 nil pps-state))
3116 ;; We've just moved out of the paren pair containing the brace-pair
3117 ;; at (car c-state-cache). `pair-beg' is where the open paren is,
3118 ;; and is potentially where the open brace of a cons in
3119 ;; c-state-cache will be.
3125 ; containing Lparen
3129 ; together with enclosed brace pair.
3130 ;; (t nil) ; Ignore an unmated Rparen.
3131 )))
3136 nil nil ; TARGETDEPTH, STOPBEFORE
3137 pps-state)))
3139 ;; If the last paren pair we moved out of was actually a brace pair,
3140 ;; insert it into `c-state-cache'.
3145 c-state-cache)))
3150 ;; Strip stale elements of `c-state-cache' by moving backwards through the
3151 ;; buffer, and inform the caller of the scenario detected.
3152 ;;
3153 ;; HERE is the position we're setting `c-state-cache' for.
3154 ;; CACHE-POS (a locally bound variable) is just after the latest recorded
3155 ;; position in `c-state-cache' before HERE, or a position at or near
3156 ;; point-min which isn't in a literal.
3157 ;;
3158 ;; This function must only be called only when (> `c-state-cache-good-pos'
3159 ;; HERE). Usually the gap between CACHE-POS and HERE is large. It is thus
3160 ;; optimized to eliminate (or minimize) scanning between these two
3161 ;; positions.
3162 ;;
3163 ;; Return a three element list (GOOD-POS SCAN-BACK-POS FWD-FLAG), where:
3164 ;; o - GOOD-POS is a "good position", where `c-state-cache' is valid, or
3165 ;; could become so after missing elements are inserted into
3166 ;; `c-state-cache'. This is JUST AFTER an opening or closing
3167 ;; brace/paren/bracket which is already in `c-state-cache' or just before
3168 ;; one otherwise. exceptionally (when there's no such b/p/b handy) the BOL
3169 ;; before `here''s line, or the start of the literal containing it.
3170 ;; o - SCAN-BACK-POS, if non-nil, indicates there may be a brace pair
3171 ;; preceding POS which isn't recorded in `c-state-cache'. It is a position
3172 ;; to scan backwards from.
3173 ;; o - FWD-FLAG, if non-nil, indicates there may be parens/braces between
3174 ;; POS and HERE which aren't recorded in `c-state-cache'.
3175 ;;
3176 ;; The comments in this defun use "paren" to mean parenthesis or square
3177 ;; bracket (as contrasted with a brace), and "(" and ")" likewise.
3178 ;;
3179 ;; . {..} (..) (..) ( .. { } ) (...) ( .... . ..)
3180 ;; | | | | | |
3181 ;; CP E here D C good
3184 pa ren ; positions of "(" and ")"
3185 dropped-cons ; whether the last element dropped from `c-state-cache'
3186 ; was a cons (representing a brace-pair)
3187 good-pos ; see above.
3188 lit ; (START . END) of a literal containing some point.
3189 here-lit-start here-lit-end ; bounds of literal containing `here'
3190 ; or `here' itself.
3195 ;; Remove completely irrelevant entries from `c-state-cache'.
3201 ;; At this stage, (>= pos here);
3202 ;; (< (c-state-cache-top-lparen) here) (or is nil).
3207 ;; CASE 1: The top of the cache is a brace pair which now encloses
3208 ;; `here'. As good-pos, return the address. of the "{". Since we've no
3209 ;; knowledge of what's inside these braces, we have no alternative but
3210 ;; to direct the caller to scan the buffer from the opening brace.
3214 ; entry into a { entry, so the caller needs to
3215 ; search for a brace pair before the {.
3217 ;; `here' might be inside a literal. Check for this.
3222 ;; Has `here' just "newly entered" a macro?
3235 ;; `here' might be nested inside any depth of parens (or brackets but
3236 ;; not braces). Scan backwards to find the outermost such opening
3237 ;; paren, if there is one. This will be the scan position to return.
3244 ;; CASE 2: Address of outermost ( or [ which now encloses `here', but
3245 ;; didn't enclose the (previous) `c-state-cache-good-pos'. If there is
3246 ;; a brace pair preceding this, it will already be in `c-state-cache',
3247 ;; unless there was a brace pair after it, i.e. there'll only be one to
3248 ;; scan for if we've just deleted one.
3251 ;; `here' isn't enclosed in a (previously unrecorded) bracket/paren.
3252 ;; Further forward scanning isn't needed, but we still need to find a
3253 ;; GOOD-POS. Step out of all enclosing "("s on HERE's line.
3265 ;; CASE 3: After a }/)/] before `here''s BOL.
3270 ;; CASE 3.5: Just after an existing entry in `c-state-cache' on `here''s
3271 ;; line or the previous line.
3275 ;; CASE 4; Best of a bad job: BOL before `here-bol', or beginning of
3276 ;; literal containing it.
3280 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3281 ;; Externally visible routines.
3285 c-state-cache-good-pos 1
3286 c-state-nonlit-pos-cache nil
3287 c-state-nonlit-pos-cache-limit 1
3288 c-state-semi-nonlit-pos-cache nil
3289 c-state-semi-nonlit-pos-cache-limit 1
3290 c-state-brace-pair-desert nil
3291 c-state-point-min 1
3292 c-state-point-min-lit-type nil
3293 c-state-point-min-lit-start nil
3294 c-state-min-scan-pos 1
3295 c-state-old-cpp-beg nil
3296 c-state-old-cpp-end nil)
3299 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3300 ;; Debugging routines to dump `c-state-cache' in a "replayable" form.
3301 ;; (defmacro c-sc-de (elt) ; "c-state-cache-dump-element"
3302 ;; `(format ,(concat "(setq " (symbol-name elt) " %s) ") ,elt))
3303 ;; (defmacro c-sc-qde (elt) ; "c-state-cache-quote-dump-element"
3304 ;; `(format ,(concat "(setq " (symbol-name elt) " '%s) ") ,elt))
3305 ;; (defun c-state-dump ()
3306 ;; ;; For debugging.
3307 ;; ;(message
3308 ;; (concat
3309 ;; (c-sc-qde c-state-cache)
3310 ;; (c-sc-de c-state-cache-good-pos)
3311 ;; (c-sc-qde c-state-nonlit-pos-cache)
3312 ;; (c-sc-de c-state-nonlit-pos-cache-limit)
3313 ;; (c-sc-qde c-state-brace-pair-desert)
3314 ;; (c-sc-de c-state-point-min)
3315 ;; (c-sc-de c-state-point-min-lit-type)
3316 ;; (c-sc-de c-state-point-min-lit-start)
3317 ;; (c-sc-de c-state-min-scan-pos)
3318 ;; (c-sc-de c-state-old-cpp-beg)
3319 ;; (c-sc-de c-state-old-cpp-end)))
3320 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3323 ;; Invalidate all info on `c-state-cache' that applies to the buffer at HERE
3324 ;; or higher and set `c-state-cache-good-pos' accordingly. The cache is
3325 ;; left in a consistent state.
3326 ;;
3327 ;; This is much like `c-whack-state-after', but it never changes a paren
3328 ;; pair element into an open paren element. Doing that would mean that the
3329 ;; new open paren wouldn't have the required preceding paren pair element.
3330 ;;
3331 ;; This function is called from c-before-change.
3333 ;; The caches of non-literals:
3334 ;; Note that we use "<=" for the possibility of the second char of a two-char
3335 ;; comment opener being typed; this would invalidate any cache position at
3336 ;; HERE.
3342 ;; `c-state-cache':
3343 ;; Case 1: if `here' is in a literal containing point-min, everything
3344 ;; becomes (or is already) nil.
3348 c-state-cache-good-pos nil
3349 c-state-min-scan-pos nil)
3351 ;; Truncate `c-state-cache' and set `c-state-cache-good-pos' to a value
3352 ;; below `here'. To maintain its consistency, we may need to insert a new
3353 ;; brace pair.
3355 too-high-pa ; recorded {/(/[ next above or just below here, or nil.
3356 dropped-cons ; was the last removed element a brace pair?
3357 pa)
3358 ;; The easy bit - knock over-the-top bits off `c-state-cache'.
3365 ;; Do we need to add in an earlier brace pair, having lopped one off?
3372 ;; The brace-pair desert marker:
3380 ;; Find and record all noteworthy parens between some good point earlier in
3381 ;; the file and point. That good point is at least the beginning of the
3382 ;; top-level construct we are in, or the beginning of the preceding
3383 ;; top-level construct if we aren't in one.
3384 ;;
3385 ;; The returned value is a list of the noteworthy parens with the last one
3386 ;; first. If an element in the list is an integer, it's the position of an
3387 ;; open paren (of any type) which has not been closed before the point. If
3388 ;; an element is a cons, it gives the position of a closed BRACE paren
3389 ;; pair[*]; the car is the start brace position and the cdr is the position
3390 ;; following the closing brace. Only the last closed brace paren pair
3391 ;; before each open paren and before the point is recorded, and thus the
3392 ;; state never contains two cons elements in succession. When a close brace
3393 ;; has no matching open brace (e.g., the matching brace is outside the
3394 ;; visible region), it is not represented in the returned value.
3395 ;;
3396 ;; [*] N.B. The close "brace" might be a mismatching close bracket or paren.
3397 ;; This defun explicitly treats mismatching parens/braces/brackets as
3398 ;; matching. It is the open brace which makes it a "brace" pair.
3399 ;;
3400 ;; If POINT is within a macro, open parens and brace pairs within
3401 ;; THIS macro MIGHT be recorded. This depends on whether their
3402 ;; syntactic properties have been suppressed by
3403 ;; `c-neutralize-syntax-in-CPP'. This might need fixing (2008-12-11).
3404 ;;
3405 ;; Currently no characters which are given paren syntax with the
3406 ;; syntax-table property are recorded, i.e. angle bracket arglist
3407 ;; parens are never present here. Note that this might change.
3408 ;;
3409 ;; BUG: This function doesn't cope entirely well with unbalanced
3410 ;; parens in macros. (2008-12-11: this has probably been resolved
3411 ;; by the function `c-neutralize-syntax-in-CPP'.) E.g. in the
3412 ;; following case the brace before the macro isn't balanced with the
3413 ;; one after it:
3414 ;;
3415 ;; {
3416 ;; #define X {
3417 ;; }
3418 ;;
3419 ;; Note to maintainers: this function DOES get called with point
3420 ;; within comments and strings, so don't assume it doesn't!
3421 ;;
3422 ;; This function might do hidden buffer changes.
3425 strategy ; 'forward, 'backward etc..
3426 ;; Candidate positions to start scanning from:
3427 cache-pos ; highest position below HERE already existing in
3428 ; cache (or 1).
3429 good-pos
3430 start-point ; (when scanning forward) a place below HERE where there
3431 ; are no open parens/braces between it and HERE.
3432 bopl-state
3433 res
3434 cons-separated
3436 ;; If POINT-MIN has changed, adjust the cache
3440 ;; Strategy?
3447 c-state-cache-good-pos start-point))
3449 ;; SCAN!
3457 ; start-point)
3467 good-pos)))
3479 good-pos)))
3483 c-state-cache-good-pos nil))))
3485 c-state-cache)
3488 ;; This is a wrapper over `c-invalidate-state-cache-1'.
3489 ;;
3490 ;; It suppresses the syntactic effect of the < and > (template) brackets and
3491 ;; of all parens in preprocessor constructs, except for any such construct
3492 ;; containing point. We can then call `c-invalidate-state-cache-1' without
3493 ;; worrying further about macros and template delimiters.
3495 ;; Emacs
3500 c-state-old-cpp-beg
3501 c-state-old-cpp-end
3505 ;; XEmacs
3509 ;; If PLACE is non-nil, return a marker marking it, otherwise nil.
3510 ;; We (re)use MARKER.
3516 ;; This is a wrapper over `c-parse-state-1'. See that function for a
3517 ;; description of the functionality and return value.
3518 ;;
3519 ;; It suppresses the syntactic effect of the < and > (template) brackets and
3520 ;; of all parens in preprocessor constructs, except for any such construct
3521 ;; containing point. We can then call `c-parse-state-1' without worrying
3522 ;; further about macros and template delimiters.
3529 here-cpp-beg)
3531 ;; FIXME!!! Put in a `condition-case' here to protect the integrity of the
3532 ;; subsystem.
3535 ;; Emacs
3539 here-cpp-beg here-cpp-end
3543 ;; XEmacs
3547 c-state-old-cpp-end
3550 ;; Debug tool to catch cache inconsistencies. This is called from
3551 ;; 000tests.el.
3574 c-state-cache-good-pos
3575 c-state-nonlit-pos-cache
3576 c-state-nonlit-pos-cache-limit
3577 c-state-semi-nonlit-pos-cache
3578 c-state-semi-nonlit-pos-cache-limit
3579 c-state-brace-pair-desert
3580 c-state-point-min
3581 c-state-point-min-lit-type
3582 c-state-point-min-lit-start
3583 c-state-min-scan-pos
3584 c-state-old-cpp-beg
3585 c-state-old-cpp-end
3586 c-parse-state-point))))
3608 conses-not-ok))
3625 ;; The cache can actually go further back due to the ad-hoc way
3626 ;; the first paren is found, so try to whack off a bit of its
3627 ;; start before complaining.
3628 ;; (save-excursion
3629 ;; (goto-char (or (c-least-enclosing-brace res2) (point)))
3630 ;; (c-beginning-of-defun-1)
3631 ;; (while (not (or (bobp) (eq (char-after) ?{)))
3632 ;; (c-beginning-of-defun-1))
3633 ;; (unless (equal (c-whack-state-before (point) res1) res2)
3634 ;; (message (concat "c-parse-state inconsistency at %s: "
3635 ;; "using cache: %s, from scratch: %s")
3636 ;; here res1 res2)))
3639 here res1 res2 min-point)
3645 here res1)
3650 res2 ; res1 correct a cascading series of errors ASAP
3651 ))
3657 'c-debug-parse-state
3665 \f
3667 ;; Whack off any state information from PAREN-STATE which lies
3668 ;; before BUFPOS. Not destructive on PAREN-STATE.
3671 car)
3682 ;; Whack off any state information from PAREN-STATE which lies at or
3683 ;; after BUFPOS. Not destructive on PAREN-STATE.
3688 ;; just check the car, because in a balanced brace
3689 ;; expression, it must be impossible for the corresponding
3690 ;; close brace to be before point, but the open brace to
3691 ;; be after.
3693 nil ; whack it off
3695 ;; its possible that the open brace is before
3696 ;; bufpos, but the close brace is after. In that
3697 ;; case, convert this to a non-cons element. The
3698 ;; rest of the state is before bufpos, so we're
3699 ;; done.
3701 ;; we know that both the open and close braces are
3702 ;; before bufpos, so we also know that everything else
3703 ;; on state is before bufpos.
3706 nil ; whack it off
3707 ;; it's before bufpos, so everything else should too.
3710 nil)))
3713 ;; Return the bufpos of the innermost enclosing open paren before
3714 ;; bufpos, or nil if none was found.
3724 enclosingp))
3727 ;; Return the bufpos of the outermost enclosing open paren, or nil
3728 ;; if none was found.
3735 pos))
3738 ;; Return the closest "safe" position recorded on PAREN-STATE that
3739 ;; is higher up than BUFPOS. Return nil if PAREN-STATE doesn't
3740 ;; contain any. Return nil if BUFPOS is nil, which is useful to
3741 ;; find the closest limit before a given limit that might be nil.
3742 ;;
3743 ;; A "safe" position is a position at or after a recorded open
3744 ;; paren, or after a recorded close paren. The returned position is
3745 ;; thus either the first position after a close brace, or the first
3746 ;; position after an enclosing paren, or at the enclosing paren in
3747 ;; case BUFPOS is immediately after it.
3757 ;; See below.
3760 ;; elem is the position at and not after the opening paren, so
3761 ;; we can go forward one more step unless it's equal to
3762 ;; bufpos. This is useful in some cases avoid an extra paren
3763 ;; level between the safe position and bufpos.
3768 ;; This is used for `font-lock-beginning-of-syntax-function'. It
3769 ;; goes to the closest previous point that is known to be outside
3770 ;; any string literal or comment. `c-state-cache' is used if it has
3771 ;; a position in the vicinity.
3773 elem
3776 ;; Note: Similar code in `c-safe-position'. The
3777 ;; difference is that we accept a safe position at
3778 ;; the point and don't bother to go forward past open
3779 ;; parens.
3794 ;; The position is far back. Try `c-beginning-of-defun-1'
3795 ;; (although we can't be entirely sure it will go to a position
3796 ;; outside a comment or string in current emacsen). FIXME:
3797 ;; Consult `syntax-ppss' here.
3802 \f
3803 ;; Tools for scanning identifiers and other tokens.
3806 "Return non-nil if the point is on or directly after an identifier.
3807 Keywords are recognized and not considered identifiers. If an
3808 identifier is detected, the returned value is its starting position.
3809 If an identifier ends at the point and another begins at it \(can only
3810 happen in Pike) then the point for the preceding one is returned.
3812 Note that this function might do hidden buffer changes. See the
3813 comment at the start of cc-engine.el for more info."
3815 ;; FIXME: Shouldn't this function handle "operator" in C++?
3822 ;; Check for a normal (non-keyword) identifier.
3828 ;; Handle the `<operator> syntax in Pike.
3832 t
3839 ;; Handle the "operator +" syntax in C++.
3856 )))
3859 ;; If the point is at the end of a symbol then skip backward to the
3860 ;; beginning of it. Don't move otherwise. Return non-nil if point
3861 ;; moved.
3862 ;;
3863 ;; This function might do hidden buffer changes.
3866 ;; Handle the `<operator> syntax in Pike.
3872 t
3874 nil)))))
3877 ;; Move to the beginning of the current token. Do not move if not
3878 ;; in the middle of one. BACK-LIMIT may be used to bound the
3879 ;; backward search; if given it's assumed to be at the boundary
3880 ;; between two tokens. Return non-nil if the point is moved, nil
3881 ;; otherwise.
3882 ;;
3883 ;; This function might do hidden buffer changes.
3890 ;; `c-nonsymbol-token-regexp' should always match
3891 ;; since we've skipped backward over punctuation
3892 ;; or paren syntax, but consume one char in case
3893 ;; it doesn't so that we don't leave point before
3894 ;; some earlier incorrect token.
3901 ;; Move to the end of the current token. Do not move if not in the
3902 ;; middle of one. BACK-LIMIT may be used to bound the backward
3903 ;; search; if given it's assumed to be at the boundary between two
3904 ;; tokens. Return non-nil if the point is moved, nil otherwise.
3905 ;;
3906 ;; This function might do hidden buffer changes.
3914 ;; `c-nonsymbol-token-regexp' should always match since
3915 ;; we've skipped backward over punctuation or paren
3916 ;; syntax, but move forward in case it doesn't so that
3917 ;; we don't leave point earlier than we started with.
3933 "Move forward by tokens.
3934 A token is defined as all symbols and identifiers which aren't
3936 treated properly). Point is always either left at the beginning of a
3937 token or not moved at all. COUNT specifies the number of tokens to
3938 move; a negative COUNT moves in the opposite direction. A COUNT of 0
3939 moves to the next token beginning only if not already at one. If
3940 BALANCED is true, move over balanced parens, otherwise move into them.
3941 Also, if BALANCED is true, never move out of an enclosing paren.
3943 LIMIT sets the limit for the movement and defaults to the point limit.
3944 The case when LIMIT is set in the middle of a token, comment or macro
3945 is handled correctly, i.e. the point won't be left there.
3947 Return the number of tokens left to move \(positive or negative). If
3948 BALANCED is true, a move over a balanced paren counts as one. Note
3949 that if COUNT is 0 and no appropriate token beginning is found, 1 will
3950 be returned. Thus, a return value of 0 guarantees that point is at
3951 the requested position and a return value less \(without signs) than
3952 COUNT guarantees that point is at the beginning of some token.
3954 Note that this function might do hidden buffer changes. See the
3955 comment at the start of cc-engine.el for more info."
3962 c-jump-syntax-balanced
3963 c-jump-syntax-unbalanced))
3968 ;; If count is zero we should jump if in the middle of a token.
3975 ;; Skip whitespace. Count this as a move if we did in
3976 ;; fact move.
3980 ;; Moved out of bounds. Make sure the returned count isn't zero.
3985 ;; Use `condition-case' to avoid having the limit tests
3986 ;; inside the loop.
3994 t)
3997 t)
3998 ;; `c-nonsymbol-token-regexp' above should always
3999 ;; match if there are correct tokens. Try to
4000 ;; widen to see if the limit was set in the
4001 ;; middle of one, else fall back to treating
4002 ;; the offending thing as a one character token.
4007 nil)
4010 t))))
4020 count)))
4023 "Move backward by tokens.
4024 See `c-forward-token-2' for details."
4032 c-jump-syntax-balanced
4033 c-jump-syntax-unbalanced))
4037 ;; The count is zero so try to skip to the beginning of the
4038 ;; current token.
4042 ;; The limit is inside the same token, so return 1.
4045 ;; We're not in the middle of a token. If there's
4046 ;; whitespace after the point then we must move backward,
4047 ;; so set count to 1 in that case.
4049 ;; If we're looking at a '#' that might start a cpp
4050 ;; directive then we have to do a more elaborate check.
4063 ;; Use `condition-case' to avoid having to check for buffer
4064 ;; limits in `backward-char', `scan-sexps' and `goto-char' below.
4073 ;; This can be very inefficient if there's a long
4074 ;; sequence of operator tokens without any separation.
4075 ;; That doesn't happen in practice, anyway.
4085 count)))
4088 "Like `c-forward-token-2' but doesn't treat multicharacter operator
4090 characters are jumped over character by character. This function is
4091 for compatibility only; it's only a wrapper over `c-forward-token-2'."
4096 "Like `c-backward-token-2' but doesn't treat multicharacter operator
4098 characters are jumped over character by character. This function is
4099 for compatibility only; it's only a wrapper over `c-backward-token-2'."
4103 \f
4104 ;; Tools for doing searches restricted to syntactically relevant text.
4107 paren-level not-inside-token
4108 lookbehind-submatch)
4109 "Like `re-search-forward', but only report matches that are found
4110 in syntactically significant text. I.e. matches in comments, macros
4111 or string literals are ignored. The start point is assumed to be
4112 outside any comment, macro or string literal, or else the content of
4113 that region is taken as syntactically significant text.
4115 If PAREN-LEVEL is non-nil, an additional restriction is added to
4116 ignore matches in nested paren sexps. The search will also not go
4117 outside the current list sexp, which has the effect that if the point
4118 should be moved to BOUND when no match is found \(i.e. NOERROR is
4119 neither nil nor t), then it will be at the closing paren if the end of
4120 the current list sexp is encountered first.
4122 If NOT-INSIDE-TOKEN is non-nil, matches in the middle of tokens are
4123 ignored. Things like multicharacter operators and special symbols
4125 constants.
4127 If LOOKBEHIND-SUBMATCH is non-nil, it's taken as a number of a
4128 subexpression in REGEXP. The end of that submatch is used as the
4129 position to check for syntactic significance. If LOOKBEHIND-SUBMATCH
4130 isn't used or if that subexpression didn't match then the start
4132 subexpression is never tested before the starting position, so it
4136 subexpression can match the end of nonwhite syntactic whitespace,
4137 i.e. the end of comments or cpp directives. This since the function
4138 skips over such things before resuming the search. It's on the other
4140 matches syntactic whitespace.
4142 Bug: Unbalanced parens inside cpp directives are currently not handled
4143 correctly \(i.e. they don't get ignored as they should) when
4144 PAREN-LEVEL is set.
4146 Note that this function might do hidden buffer changes. See the
4147 comment at the start of cc-engine.el for more info."
4152 ;;(message "c-syntactic-re-search-forward %s %s %S" (point) bound regexp)
4155 tmp
4156 ;; Start position for the last search.
4157 search-pos
4158 ;; The `parse-partial-sexp' state between the start position
4159 ;; and the point.
4160 state
4161 ;; The current position after the last state update. The next
4162 ;; `parse-partial-sexp' continues from here.
4164 ;; The position at which to check the state and the state
4165 ;; there. This is separate from `state-pos' since we might
4166 ;; need to back up before doing the next search round.
4167 check-pos check-state
4168 ;; Last position known to end a token.
4170 ;; Set when a valid match is found.
4171 found)
4189 state-pos check-pos paren-level nil state))
4191 check-state state))
4193 ;; NOTE: If we got a look behind subexpression and get
4194 ;; an insignificant match in something that isn't
4195 ;; syntactic whitespace (i.e. strings or in nested
4196 ;; parentheses), then we can never skip more than a
4197 ;; single character from the match start position
4198 ;; (i.e. `state-pos' here) before continuing the
4199 ;; search. That since the look behind subexpression
4200 ;; might match the end of the insignificant region in
4201 ;; the next search.
4205 ;; Match inside a line comment. Skip to eol. Use
4206 ;; `re-search-forward' instead of `skip-chars-forward' to get
4207 ;; the right bound behavior.
4211 ;; Match inside a block comment. Skip to the '*/'.
4218 ;; Match in the middle of the opener of a block or line
4219 ;; comment.
4224 ;; The last `parse-partial-sexp' above might have
4225 ;; stopped short of the real check position if the end
4226 ;; of the current sexp was encountered in paren-level
4227 ;; mode. The checks above are always false in that
4228 ;; case, and since they can do better skipping in
4229 ;; lookbehind-submatch mode, we do them before
4230 ;; checking the paren level.
4234 ;; Check the paren level first since we're short of the
4235 ;; syntactic checking position if the end of the
4236 ;; current sexp was encountered by `parse-partial-sexp'.
4239 ;; Inside a nested paren sexp.
4241 ;; See the NOTE above.
4243 ;; Skip out of the paren quickly.
4247 ;; Have exited the current paren sexp.
4250 ;; The last `parse-partial-sexp' call above
4251 ;; has left us just after the closing paren
4252 ;; in this case, so we can modify the bound
4253 ;; to leave the point at the right position
4254 ;; upon return.
4256 nil)
4260 ;; Match inside a string.
4263 ;; See the NOTE above.
4265 ;; Skip to the end of the string before continuing.
4274 continue)))
4279 ;; Match inside a macro. Skip to the end of it.
4287 (< check-pos
4293 ;; Inside a token.
4295 ;; See the NOTE above.
4300 ;; A real match.
4302 nil)))
4304 ;; Should loop to search again, but take care to avoid
4305 ;; looping on the same spot.
4309 nil
4312 t))))
4318 ;;(message "c-syntactic-re-search-forward done %s" (or (match-end 0) (point)))
4325 ;; Search failed. Set point as appropriate.
4329 nil)))
4334 ;; Return the start of the literal point is in, or nil.
4335 ;; We read and write the variables `safe-pos', `safe-pos-list', `state'
4336 ;; bound in the caller.
4338 ;; Use `parse-partial-sexp' from a safe position down to the point to check
4339 ;; if it's outside comments and strings.
4342 ;; Pick a safe position as close to the point as possible.
4343 ;;
4344 ;; FIXME: Consult `syntax-ppss' here if our cache doesn't give a good
4345 ;; position.
4357 ;; Cache positions along the way to use if we have to back up more. We
4358 ;; cache every closing paren on the same level. If the paren cache is
4359 ;; relevant in this region then we're typically already on the same
4360 ;; level as the target position. Note that we might cache positions
4361 ;; after opening parens in case safe-pos is in a nested list. That's
4362 ;; both uncommon and harmless.
4370 ;; If the state contains the start of the containing sexp we cache that
4371 ;; position too, so that parse-partial-sexp in the next run has a bigger
4372 ;; chance of starting at the same level as the target position and thus
4373 ;; will get more good safe positions into the list.
4379 ;; Inside string or comment. Continue search at the
4380 ;; beginning of it.
4384 "Like `skip-chars-backward' but only look at syntactically relevant chars,
4385 i.e. don't stop at positions inside syntactic whitespace or string
4386 literals. Preprocessor directives are also ignored, with the exception
4387 of the one that the point starts within, if any. If LIMIT is given,
4388 it's assumed to be at a syntactically relevant position.
4390 If PAREN-LEVEL is non-nil, the function won't stop in nested paren
4391 sexps, and the search will also not go outside the current paren sexp.
4392 However, if LIMIT or the buffer limit is reached inside a nested paren
4393 then the point will be left at the limit.
4395 Non-nil is returned if the point moved, nil otherwise.
4397 Note that this function might do hidden buffer changes. See the
4398 comment at the start of cc-engine.el for more info."
4402 state-2
4403 ;; A list of syntactically relevant positions in descending
4404 ;; order. It's used to avoid scanning repeatedly over
4405 ;; potentially large regions with `parse-partial-sexp' to verify
4406 ;; each position. Used in `c-ssb-lit-begin'
4407 safe-pos-list
4408 ;; The result from `c-beginning-of-macro' at the start position or the
4409 ;; start position itself if it isn't within a macro. Evaluated on
4410 ;; demand.
4411 start-macro-beg
4412 ;; The earliest position after the current one with the same paren
4413 ;; level. Used only when `paren-level' is set.
4414 lit-beg
4419 ;; The next loop "tries" to find the end point each time round,
4420 ;; loops when it hasn't succeeded.
4426 ;; Don't stop inside a literal.
4429 t)))
4441 ;; Not at the right level.
4444 ;; We stop above if we go out of a paren.
4445 ;; Now check whether it precedes or is
4446 ;; nested in the starting sexp.
4450 pps-end-pos paren-level-pos
4451 nil nil state-2))
4454 ;; We've stopped short of the starting position
4455 ;; so the hit was inside a nested list. Go up
4456 ;; until we are at the right level.
4465 nil)
4466 t))
4469 nil))
4471 ;; The hit was outside the list at the start
4472 ;; position. Go to the start of the list and exit.
4474 nil))
4477 ;; Inside a macro.
4485 t
4487 ;; It's inside the same macro we started in so it's
4488 ;; a relevant match.
4490 nil))))))
4494 ;; Skip syntactic ws afterwards so that we don't stop at the
4495 ;; end of a comment if `skip-chars' is something like "^/".
4499 ;; We might want to extend this with more useful return values in
4500 ;; the future.
4503 ;; The following is an alternative implementation of
4504 ;; `c-syntactic-skip-backward' that uses backward movement to keep
4505 ;; track of the syntactic context. It turned out to be generally
4506 ;; slower than the one above which uses forward checks from earlier
4507 ;; safe positions.
4508 ;;
4509 ;;(defconst c-ssb-stop-re
4510 ;; ;; The regexp matching chars `c-syntactic-skip-backward' needs to
4511 ;; ;; stop at to avoid going into comments and literals.
4512 ;; (concat
4513 ;; ;; Match comment end syntax and string literal syntax. Also match
4514 ;; ;; '/' for block comment endings (not covered by comment end
4515 ;; ;; syntax).
4516 ;; "\\s>\\|/\\|\\s\""
4517 ;; (if (memq 'gen-string-delim c-emacs-features)
4518 ;; "\\|\\s|"
4519 ;; "")
4520 ;; (if (memq 'gen-comment-delim c-emacs-features)
4521 ;; "\\|\\s!"
4522 ;; "")))
4523 ;;
4524 ;;(defconst c-ssb-stop-paren-re
4525 ;; ;; Like `c-ssb-stop-re' but also stops at paren chars.
4526 ;; (concat c-ssb-stop-re "\\|\\s(\\|\\s)"))
4527 ;;
4528 ;;(defconst c-ssb-sexp-end-re
4529 ;; ;; Regexp matching the ending syntax of a complex sexp.
4530 ;; (concat c-string-limit-regexp "\\|\\s)"))
4531 ;;
4532 ;;(defun c-syntactic-skip-backward (skip-chars &optional limit paren-level)
4533 ;; "Like `skip-chars-backward' but only look at syntactically relevant chars,
4534 ;;i.e. don't stop at positions inside syntactic whitespace or string
4535 ;;literals. Preprocessor directives are also ignored. However, if the
4536 ;;point is within a comment, string literal or preprocessor directory to
4537 ;;begin with, its contents is treated as syntactically relevant chars.
4538 ;;If LIMIT is given, it limits the backward search and the point will be
4539 ;;left there if no earlier position is found.
4540 ;;
4541 ;;If PAREN-LEVEL is non-nil, the function won't stop in nested paren
4542 ;;sexps, and the search will also not go outside the current paren sexp.
4543 ;;However, if LIMIT or the buffer limit is reached inside a nested paren
4544 ;;then the point will be left at the limit.
4545 ;;
4546 ;;Non-nil is returned if the point moved, nil otherwise.
4547 ;;
4548 ;;Note that this function might do hidden buffer changes. See the
4549 ;;comment at the start of cc-engine.el for more info."
4550 ;;
4551 ;; (save-restriction
4552 ;; (when limit
4553 ;; (narrow-to-region limit (point-max)))
4554 ;;
4555 ;; (let ((start (point)))
4556 ;; (catch 'done
4557 ;; (while (let ((last-pos (point))
4558 ;; (stop-pos (progn
4559 ;; (skip-chars-backward skip-chars)
4560 ;; (point))))
4561 ;;
4562 ;; ;; Skip back over the same region as
4563 ;; ;; `skip-chars-backward' above, but keep to
4564 ;; ;; syntactically relevant positions.
4565 ;; (goto-char last-pos)
4566 ;; (while (and
4567 ;; ;; `re-search-backward' with a single char regexp
4568 ;; ;; should be fast.
4569 ;; (re-search-backward
4570 ;; (if paren-level c-ssb-stop-paren-re c-ssb-stop-re)
4571 ;; stop-pos 'move)
4572 ;;
4573 ;; (progn
4574 ;; (cond
4575 ;; ((looking-at "\\s(")
4576 ;; ;; `paren-level' is set and we've found the
4577 ;; ;; start of the containing paren.
4578 ;; (forward-char)
4579 ;; (throw 'done t))
4580 ;;
4581 ;; ((looking-at c-ssb-sexp-end-re)
4582 ;; ;; We're at the end of a string literal or paren
4583 ;; ;; sexp (if `paren-level' is set).
4584 ;; (forward-char)
4585 ;; (condition-case nil
4586 ;; (c-backward-sexp)
4587 ;; (error
4588 ;; (goto-char limit)
4589 ;; (throw 'done t))))
4590 ;;
4591 ;; (t
4592 ;; (forward-char)
4593 ;; ;; At the end of some syntactic ws or possibly
4594 ;; ;; after a plain '/' operator.
4595 ;; (let ((pos (point)))
4596 ;; (c-backward-syntactic-ws)
4597 ;; (if (= pos (point))
4598 ;; ;; Was a plain '/' operator. Go past it.
4599 ;; (backward-char)))))
4600 ;;
4601 ;; (> (point) stop-pos))))
4602 ;;
4603 ;; ;; Now the point is either at `stop-pos' or at some
4604 ;; ;; position further back if `stop-pos' was at a
4605 ;; ;; syntactically irrelevant place.
4606 ;;
4607 ;; ;; Skip additional syntactic ws so that we don't stop
4608 ;; ;; at the end of a comment if `skip-chars' is
4609 ;; ;; something like "^/".
4610 ;; (c-backward-syntactic-ws)
4611 ;;
4612 ;; (< (point) stop-pos))))
4613 ;;
4614 ;; ;; We might want to extend this with more useful return values
4615 ;; ;; in the future.
4616 ;; (/= (point) start))))
4618 \f
4619 ;; Tools for handling comments and string literals.
4622 "Return the type of literal point is in, if any.
4623 The return value is `c' if in a C-style comment, `c++' if in a C++
4624 style comment, `string' if in a string literal, `pound' if DETECT-CPP
4625 is non-nil and in a preprocessor line, or nil if somewhere else.
4626 Optional LIM is used as the backward limit of the search. If omitted,
4627 or nil, `c-beginning-of-defun' is used.
4629 The last point calculated is cached if the cache is enabled, i.e. if
4630 `c-in-literal-cache' is bound to a two element vector.
4632 Note that this function might do hidden buffer changes. See the
4633 comment at the start of cc-engine.el for more info."
4644 "Return a cons of the beginning and end positions of the comment or
4645 string surrounding point (including both delimiters), or nil if point
4647 to start parsing from. If NEAR is non-nil, then the limits of any
4649 spaces and tabs between point and the literal. The search for such a
4650 literal is done first in forward direction. If NOT-IN-DELIMITER is
4651 non-nil, the case when point is inside a starting delimiter won't be
4652 recognized. This only has effect for comments which have starting
4653 delimiters with more than one character.
4655 Note that this function might do hidden buffer changes. See the
4656 comment at the start of cc-engine.el for more info."
4672 ;; Search forward for a literal.
4683 ;; Search backward.
4694 ;; Block comment. Due to the nature of line
4695 ;; comments, they will always be covered by the
4696 ;; normal case above.
4699 ;; If LIM is bogus, beg will be bogus.
4703 ))))
4705 ;; In case external callers use this; it did have a docstring.
4709 "If the argument is a cons of two buffer positions (such as returned by
4710 `c-literal-limits'), and that range contains a C++ style line comment,
4711 then an extended range is returned that contains all adjacent line
4712 comments (i.e. all comments that starts in the same column with no
4713 empty lines or non-whitespace characters between them). Otherwise the
4714 argument is returned.
4716 Note that this function might do hidden buffer changes. See the
4717 comment at the start of cc-engine.el for more info."
4728 ;; Got to take care in the backward direction to handle
4729 ;; comments which are preceded by code.
4743 range)
4747 "Convenience function that given the result of `c-literal-limits',
4748 returns nil or the type of literal that the range surrounds, one
4749 of the symbols `c', `c++' or `string'. It's much faster than using
4750 `c-in-literal' and is intended to be used when you need both the
4751 type of a literal and its limits.
4753 Note that this function might do hidden buffer changes. See the
4754 comment at the start of cc-engine.el for more info."
4765 range))
4768 ;; Get a "safe place" approximately TRY-SIZE characters before START.
4769 ;; This doesn't preserve point.
4778 ;; Return a buffer position HOW-FAR-BACK non-literal characters from START
4779 ;; (default point). This is done by going back further in the buffer then
4780 ;; searching forward for literals. The position found won't be in a
4781 ;; literal. We start searching for the sought position TRY-SIZE (default
4782 ;; twice HOW-FAR-BACK) bytes back from START. This function must be fast.
4783 ;; :-)
4791 stack elt size
4794 ;; Move forward one literal each time round this loop.
4795 ;; Move forward to the start of a comment or string.
4797 pos
4798 start
4799 nil ; target-depth
4800 nil ; stop-before
4801 s ; state
4804 ;; Gather details of the non-literal-bit - starting pos and size.
4808 pos))
4812 ;; Move forward to the end of the comment/string.
4816 start
4817 nil ; target-depth
4818 nil ; stop-before
4819 s ; state
4823 ;; Now try and find enough non-literal characters recorded on the stack.
4824 ;; Go back one recorded literal each time round this loop.
4826 stack)
4831 ;; Have we found enough yet?
4841 ;; Return a buffer position about HOW-FAR non-literal characters forward
4842 ;; from START-POS (default point), which must not be inside a literal.
4849 ;; Scan over counted characters.
4851 pos
4853 nil ; target-depth
4854 nil ; stop-before
4855 s ; state
4859 ;; Scan over literal characters.
4862 pos
4864 nil ; target-depth
4865 nil ; stop-before
4866 s ; state
4871 \f
4872 ;; `c-find-decl-spots' and accompanying stuff.
4874 ;; Variables used in `c-find-decl-spots' to cache the search done for
4875 ;; the first declaration in the last call. When that function starts,
4876 ;; it needs to back up over syntactic whitespace to look at the last
4877 ;; token before the region being searched. That can sometimes cause
4878 ;; moves back and forth over a quite large region of comments and
4879 ;; macros, which would be repeated for each changed character when
4880 ;; we're called during fontification, since font-lock refontifies the
4881 ;; current line for each change. Thus it's worthwhile to cache the
4882 ;; first match.
4883 ;;
4884 ;; `c-find-decl-syntactic-pos' is a syntactically relevant position in
4885 ;; the syntactic whitespace less or equal to some start position.
4886 ;; There's no cached value if it's nil.
4887 ;;
4888 ;; `c-find-decl-match-pos' is the match position if
4889 ;; `c-find-decl-prefix-search' matched before the syntactic whitespace
4890 ;; at `c-find-decl-syntactic-pos', or nil if there's no such match.
4901 ; (defface c-debug-decl-spot-face
4902 ; '((t (:background "Turquoise")))
4903 ; "Debug face to mark the spots where `c-find-decl-spots' stopped.")
4904 ; (defface c-debug-decl-sws-face
4905 ; '((t (:background "Khaki")))
4906 ; "Debug face to mark the syntactic whitespace between the declaration
4907 ; spots and the preceding token end.")
4923 ;; Macro used inside `c-find-decl-spots'. It ought to be a defun,
4924 ;; but it contains lots of free variables that refer to things
4925 ;; inside `c-find-decl-spots'. The point is left at `cfd-match-pos'
4926 ;; if there is a match, otherwise at `cfd-limit'.
4927 ;;
4928 ;; The macro moves point forward to the next putative start of a declaration
4929 ;; or cfd-limit. This decl start is the next token after a "declaration
4930 ;; prefix". The declaration prefix is the earlier of `cfd-prop-match' and
4931 ;; `cfd-re-match'. `cfd-match-pos' is set to the decl prefix.
4932 ;;
4933 ;; This macro might do hidden buffer changes.
4936 ;; Find the next property match position if we haven't got one already.
4947 ;; Find the next `c-decl-prefix-or-start-re' match if we haven't
4948 ;; got one already.
4954 ;; Each time round, the next `while' moves forward over a pseudo match
4955 ;; of `c-decl-prefix-or-start-re' which is either inside a literal, or
4956 ;; is a ":" not preceded by "public", etc.. `cfd-re-match' and
4957 ;; `cfd-re-match-end' get set.
4964 ;; No match. Finish up and exit the loop.
4966 nil)
4969 ;; Matched the end of a token preceding a decl spot.
4973 ;; Matched a token that start a decl spot.
4976 c-literal-faces)
4977 ;; Pseudo match inside a comment or string literal. Skip out
4978 ;; of comments and string literals.
4990 ;; Found a ":" which isn't part of "public:", etc.
4991 t)
4994 ;; If our match was at the decl start, we have to back up over the
4995 ;; preceding syntactic ws to set `cfd-match-pos' and to catch
4996 ;; any decl spots in the syntactic ws.
5001 ;; Choose whichever match is closer to the start.
5004 cfd-re-match nil)
5006 cfd-prop-match nil))
5011 ;; Skip forward past comments only so we don't skip macros.
5013 ;; Set the position to continue at. We can avoid going over
5014 ;; the comments skipped above a second time, but it's possible
5015 ;; that the comment skipping has taken us past `cfd-prop-match'
5016 ;; since the property might be used inside comments.
5022 ;; Call CFD-FUN for each possible spot for a declaration, cast or
5023 ;; label from the point to CFD-LIMIT.
5024 ;;
5025 ;; CFD-FUN is called with point at the start of the spot. It's passed two
5026 ;; arguments: The first is the end position of the token preceding the spot,
5027 ;; or 0 for the implicit match at bob. The second is a flag that is t when
5028 ;; the match is inside a macro. Point should be moved forward by at least
5029 ;; one token.
5030 ;;
5031 ;; If CFD-FUN adds `c-decl-end' properties somewhere below the current spot,
5032 ;; it should return non-nil to ensure that the next search will find them.
5033 ;;
5034 ;; Such a spot is:
5035 ;; o The first token after bob.
5036 ;; o The first token after the end of submatch 1 in
5037 ;; `c-decl-prefix-or-start-re' when that submatch matches. This
5038 ;; submatch is typically a (L or R) brace or paren, a ;, or a ,.
5039 ;; o The start of each `c-decl-prefix-or-start-re' match when
5040 ;; submatch 1 doesn't match. This is, for example, the keyword
5041 ;; "class" in Pike.
5042 ;; o The start of a previously recognized declaration; "recognized"
5043 ;; means that the last char of the previous token has a `c-type'
5044 ;; text property with the value `c-decl-end'; this only holds
5045 ;; when `c-type-decl-end-used' is set.
5046 ;;
5047 ;; Only a spot that match CFD-DECL-RE and whose face is in the
5048 ;; CFD-FACE-CHECKLIST list causes CFD-FUN to be called. The face
5049 ;; check is disabled if CFD-FACE-CHECKLIST is nil.
5050 ;;
5051 ;; If the match is inside a macro then the buffer is narrowed to the
5052 ;; end of it, so that CFD-FUN can investigate the following tokens
5053 ;; without matching something that begins inside a macro and ends
5054 ;; outside it. It's to avoid this work that the CFD-DECL-RE and
5055 ;; CFD-FACE-CHECKLIST checks exist.
5056 ;;
5057 ;; The spots are visited approximately in order from top to bottom.
5058 ;; It's however the positions where `c-decl-prefix-or-start-re'
5059 ;; matches and where `c-decl-end' properties are found that are in
5060 ;; order. Since the spots often are at the following token, they
5061 ;; might be visited out of order insofar as more spots are reported
5062 ;; later on within the syntactic whitespace between the match
5063 ;; positions and their spots.
5064 ;;
5065 ;; It's assumed that comments and strings are fontified in the
5066 ;; searched range.
5067 ;;
5068 ;; This is mainly used in fontification, and so has an elaborate
5069 ;; cache to handle repeated calls from the same start position; see
5070 ;; the variables above.
5071 ;;
5072 ;; All variables in this function begin with `cfd-' to avoid name
5073 ;; collision with the (dynamically bound) variables used in CFD-FUN.
5074 ;;
5075 ;; This function might do hidden buffer changes.
5079 ;; The end of the token preceding the decl spot last found
5080 ;; with `c-decl-prefix-or-start-re'. `cfd-limit' if there's
5081 ;; no match.
5082 cfd-re-match
5083 ;; The end position of the last `c-decl-prefix-or-start-re'
5084 ;; match. If this is greater than `cfd-continue-pos', the
5085 ;; next regexp search is started here instead.
5087 ;; The end of the last `c-decl-end' found by
5088 ;; `c-find-decl-prefix-search'. `cfd-limit' if there's no
5089 ;; match. If searching for the property isn't needed then we
5090 ;; disable it by setting it to `cfd-limit' directly.
5092 ;; The end of the token preceding the decl spot last found by
5093 ;; `c-find-decl-prefix-search'. 0 for the implicit match at
5094 ;; bob. `cfd-limit' if there's no match. In other words,
5095 ;; this is the minimum of `cfd-re-match' and `cfd-prop-match'.
5097 ;; The position to continue searching at.
5098 cfd-continue-pos
5099 ;; The position of the last "real" token we've stopped at.
5100 ;; This can be greater than `cfd-continue-pos' when we get
5101 ;; hits inside macros or at `c-decl-end' positions inside
5102 ;; comments.
5104 ;; The end position of the last entered macro.
5107 ;; Initialize by finding a syntactically relevant start position
5108 ;; before the point, and do the first `c-decl-prefix-or-start-re'
5109 ;; search unless we're at bob.
5112 ;; Must back up a bit since we look for the end of the previous
5113 ;; statement or declaration, which is earlier than the first
5114 ;; returned match.
5116 ;; This `cond' moves back over any literals or macros. It has special
5117 ;; handling for when the region being searched is entirely within a
5118 ;; macro. It sets `cfd-continue-pos' (unless we've reached
5119 ;; `cfd-limit').
5121 ;; First we need to move to a syntactically relevant position.
5122 ;; Begin by backing out of comment or string literals.
5123 ;;
5124 ;; This arm of the cond actually triggers if we're in a literal,
5125 ;; and cfd-limit is at most at BONL.
5127 ;; This arm of the `and' moves backwards out of a literal when
5128 ;; the face at point is a literal face. In this case, its value
5129 ;; is always non-nil.
5131 ;; Try to use the faces to back up to the start of the
5132 ;; literal. FIXME: What if the point is on a declaration
5133 ;; inside a comment?
5139 ;; XEmacs doesn't fontify the quotes surrounding string
5140 ;; literals.
5149 ;; Don't trust the literal to contain only literal faces
5150 ;; (the font lock package might not have fontified the
5151 ;; start of it at all, for instance) so check that we have
5152 ;; arrived at something that looks like a start or else
5153 ;; resort to `c-literal-limits'.
5160 ;; The start is in a literal. If the limit is in the same
5161 ;; one we don't have to find a syntactic position etc. We
5162 ;; only check that if the limit is at or before bonl to save
5163 ;; time; it covers the by far most common case when font-lock
5164 ;; refontifies the current line only.
5175 ;; Completely inside a literal. Set up variables to trig the
5176 ;; (< cfd-continue-pos cfd-start-pos) case below and it'll
5177 ;; find a suitable start position.
5180 ;; Check if the region might be completely inside a macro, to
5181 ;; optimize that like the completely-inside-literal above.
5188 ;; (Maybe) completely inside a macro. Only need to trig the
5189 ;; (< cfd-continue-pos cfd-start-pos) case below to make it
5190 ;; set things up.
5192 start-in-macro t))
5194 ;; The default arm of the `cond' moves back over any macro we're in
5195 ;; and over any syntactic WS. It sets `c-find-decl-syntactic-pos'.
5197 ;; Back out of any macro so we don't miss any declaration
5198 ;; that could follow after it.
5202 ;; Now we're at a proper syntactically relevant position so we
5203 ;; can use the cache. But first clear it if it applied
5204 ;; further down.
5209 ;; Don't have to do this if the cache is relevant here,
5210 ;; typically if the same line is refontified again. If
5211 ;; we're just some syntactic whitespace further down we can
5212 ;; still use the cache to limit the skipping.
5215 ;; If we hit `c-find-decl-syntactic-pos' and
5216 ;; `c-find-decl-match-pos' is set then we install the cached
5217 ;; values. If we hit `c-find-decl-syntactic-pos' and
5218 ;; `c-find-decl-match-pos' is nil then we know there's no decl
5219 ;; prefix in the whitespace before `c-find-decl-syntactic-pos'
5220 ;; and so we can continue the search from this point. If we
5221 ;; didn't hit `c-find-decl-syntactic-pos' then we're now in
5222 ;; the right spot to begin searching anyway.
5224 c-find-decl-match-pos)
5226 cfd-continue-pos syntactic-pos)
5231 ;; Always consider bob a match to get the first
5232 ;; declaration in the file. Do this separately instead of
5233 ;; letting `c-decl-prefix-or-start-re' match bob, so that
5234 ;; regexp always can consume at least one character to
5235 ;; ensure that we won't get stuck in an infinite loop.
5240 ;; Do an initial search now. In the bob case above it's
5241 ;; only done to search for a `c-decl-end' spot.
5247 ;; Advance `cfd-continue-pos' if it's before the start position.
5248 ;; The closest continue position that might have effect at or
5249 ;; after the start depends on what we started in. This also
5250 ;; finds a suitable start position in the special cases when the
5251 ;; region is completely within a literal or macro.
5256 ;; If we're in a macro then it's the closest preceding token
5257 ;; in the macro. Check this before `start-in-literal',
5258 ;; since if we're inside a literal in a macro, the preceding
5259 ;; token is earlier than any `c-decl-end' spot inside the
5260 ;; literal (comment).
5262 ;; The only syntactic ws in macros are comments.
5268 ;; If we're in a comment it can only be the closest
5269 ;; preceding `c-decl-end' position within that comment, if
5270 ;; any. Go back to the beginning of such a property so that
5271 ;; `c-find-decl-prefix-search' will find the end of it.
5272 ;; (Can't stop at the end and install it directly on
5273 ;; `cfd-prop-match' since that variable might be cleared
5274 ;; after `cfd-fun' below.)
5275 ;;
5276 ;; Note that if the literal is a string then the property
5277 ;; search will simply skip to the beginning of it right
5278 ;; away.
5290 ;; Didn't find any property inside the comment, so we can
5291 ;; skip it entirely. (This won't skip past a string, but
5292 ;; that'll be handled quickly by the next
5293 ;; `c-find-decl-prefix-search' anyway.)
5299 ;; If we started in normal code, the only match that might
5300 ;; apply before the start is what we already got in
5301 ;; `cfd-match-pos' so we can continue at the start position.
5302 ;; (Note that we don't get here if the first match is below
5303 ;; it.)
5306 ;; Delete found matches if they are before our new continue
5307 ;; position, so that `c-find-decl-prefix-search' won't back up
5308 ;; to them later on.
5316 ;; This is the normal case and we got a proper syntactic
5317 ;; position. If there's a match then it's always outside
5318 ;; macros and comments, so advance to the next token and set
5319 ;; `cfd-token-pos'. The loop below will later go back using
5320 ;; `cfd-continue-pos' to fix declarations inside the
5321 ;; syntactic ws.
5329 ;; Have one of the special cases when the region is completely
5330 ;; within a literal or macro. `cfd-continue-pos' is set to a
5331 ;; good start position for the search, so do it.
5334 ;; Now loop, one decl spot per iteration. We already have the first
5335 ;; match in `cfd-match-pos'.
5337 ;; Go forward over "false matches", one per iteration.
5342 ;; Kludge to filter out matches on the "<" that
5343 ;; aren't open parens, for the sake of languages
5344 ;; that got `c-recognize-<>-arglists' set.
5349 ;; If `cfd-continue-pos' is less or equal to
5350 ;; `cfd-token-pos', we've got a hit inside a macro
5351 ;; that's in the syntactic whitespace before the last
5352 ;; "real" declaration we've checked. If they're equal
5353 ;; we've arrived at the declaration a second time, so
5354 ;; there's nothing to do.
5358 ;; If `cfd-continue-pos' is less than `cfd-token-pos'
5359 ;; we're still searching for declarations embedded in
5360 ;; the syntactic whitespace. In that case we need
5361 ;; only to skip comments and not macros, since they
5362 ;; can't be nested, and that's already been done in
5363 ;; `c-find-decl-prefix-search'.
5368 ;; Continue if the following token fails the
5369 ;; CFD-DECL-RE and CFD-FACE-CHECKLIST checks.
5376 t)))
5387 ;; Narrow to the end of the macro if we got a hit inside
5388 ;; one, to avoid recognizing things that start inside the
5389 ;; macro and end outside it.
5391 ;; Not in the same macro as in the previous round.
5402 t
5405 t)
5406 ;; The matched token was the last thing in the macro,
5407 ;; so the whole match is bogus.
5416 ;; Restore limits if we did macro narrowing above.
5423 ; cfd-match-pos, etc.
5425 \f
5426 ;; A cache for found types.
5428 ;; Buffer local variable that contains an obarray with the types we've
5429 ;; found. If a declaration is recognized somewhere we record the
5430 ;; fully qualified identifier in it to recognize it as a type
5431 ;; elsewhere in the file too. This is not accurate since we do not
5432 ;; bother with the scoping rules of the languages, but in practice the
5433 ;; same name is seldom used as both a type and something else in a
5434 ;; file, and we only use this as a last resort in ambiguous cases (see
5435 ;; `c-forward-decl-or-cast-1').
5436 ;;
5437 ;; Not every type need be in this cache. However, things which have
5438 ;; ceased to be types must be removed from it.
5439 ;;
5440 ;; Template types in C++ are added here too but with the template
5441 ;; arglist replaced with "<>" in references or "<" for the one in the
5442 ;; primary type. E.g. the type "Foo<A,B>::Bar<C>" is stored as
5443 ;; "Foo<>::Bar<". This avoids storing very long strings (since C++
5444 ;; template specs can be fairly sized programs in themselves) and
5445 ;; improves the hit ratio (it's a type regardless of the template
5446 ;; args; it's just not the same type, but we're only interested in
5447 ;; recognizing types, not telling distinct types apart). Note that
5448 ;; template types in references are added here too; from the example
5449 ;; above there will also be an entry "Foo<".
5454 ;; Clears `c-found-types'.
5458 ;; Add the given region as a type in `c-found-types'. If the region
5459 ;; doesn't match an existing type but there is a type which is equal
5460 ;; to the given one except that the last character is missing, then
5461 ;; the shorter type is removed. That's done to avoid adding all
5462 ;; prefixes of a type as it's being entered and font locked. This
5463 ;; doesn't cover cases like when characters are removed from a type
5464 ;; or added in the middle. We'd need the position of point when the
5465 ;; font locking is invoked to solve this well.
5466 ;;
5467 ;; This function might do hidden buffer changes.
5474 ;; Remove the "NAME" from c-found-types, if present.
5478 ;; Return non-nil if the given region contains a type in
5479 ;; `c-found-types'.
5480 ;;
5481 ;; This function might do hidden buffer changes.
5483 c-found-types))
5486 ;; Return all the types in `c-found-types' as a sorted list of
5487 ;; strings.
5491 type-list)))
5492 c-found-types)
5495 ;; Shut up the byte compiler.
5499 ;; An after change function which, in conjunction with the info in
5500 ;; c-maybe-stale-found-type (set in c-before-change), removes a type
5501 ;; from `c-found-types', should this type have become stale. For
5502 ;; example, this happens to "foo" when "foo \n bar();" becomes
5503 ;; "foo(); \n bar();". Such stale types, if not removed, foul up
5504 ;; the fontification.
5505 ;;
5506 ;; Have we, perhaps, added non-ws characters to the front/back of a found
5507 ;; type?
5527 ;; Changing the amount of (already existing) whitespace - don't do anything.
5532 ;; The syntactic relationship which defined a "found type" has been
5533 ;; destroyed.
5536 ;; ((eq (car c-maybe-stale-found-type) 'c-decl-type-start) FIXME!!!
5537 )))
5539 \f
5540 ;; Setting and removing syntax properties on < and > in languages (C++
5541 ;; and Java) where they can be template/generic delimiters as well as
5542 ;; their normal meaning of "less/greater than".
5544 ;; Normally, < and > have syntax 'punctuation'. When they are found to
5545 ;; be delimiters, they are marked as such with the category properties
5546 ;; c-<-as-paren-syntax, c->-as-paren-syntax respectively.
5548 ;; STRATEGY:
5549 ;;
5550 ;; It is impossible to determine with certainty whether a <..> pair in
5551 ;; C++ is two comparison operators or is template delimiters, unless
5552 ;; one duplicates a lot of a C++ compiler. For example, the following
5553 ;; code fragment:
5554 ;;
5555 ;; foo (a < b, c > d) ;
5556 ;;
5557 ;; could be a function call with two integer parameters (each a
5558 ;; relational expression), or it could be a constructor for class foo
5559 ;; taking one parameter d of templated type "a < b, c >". They are
5560 ;; somewhat easier to distinguish in Java.
5561 ;;
5562 ;; The strategy now (2010-01) adopted is to mark and unmark < and
5563 ;; > IN MATCHING PAIRS ONLY. [Previously, they were marked
5564 ;; individually when their context so indicated. This gave rise to
5565 ;; intractable problems when one of a matching pair was deleted, or
5566 ;; pulled into a literal.]
5567 ;;
5568 ;; At each buffer change, the syntax-table properties are removed in a
5569 ;; before-change function and reapplied, when needed, in an
5570 ;; after-change function. It is far more important that the
5571 ;; properties get removed when they they are spurious than that they
5572 ;; be present when wanted.
5573 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
5575 ;; POS (default point) is at a < character. If it is marked with
5576 ;; open paren syntax-table text property, remove the property,
5577 ;; together with the close paren property on the matching > (if
5578 ;; any).
5593 ;; POS (default point) is at a > character. If it is marked with
5594 ;; close paren syntax-table property, remove the property, together
5595 ;; with the open paren property on the matching < (if any).
5610 ;; POS (default point) is at a < or > character. If it has an
5611 ;; open/close paren syntax-table property, remove this property both
5612 ;; from the current character and its partner (which will also be
5613 ;; thusly marked).
5623 ;; POS (default point) is at a < character. If it is both marked
5624 ;; with open/close paren syntax-table property, and has a matching >
5625 ;; (also marked) which is after LIM, remove the property both from
5626 ;; the current > and its partner. Return t when this happens, nil
5627 ;; when it doesn't.
5641 t)))
5644 ;; POS (default point) is at a > character. If it is both marked
5645 ;; with open/close paren syntax-table property, and has a matching <
5646 ;; (also marked) which is before LIM, remove the property both from
5647 ;; the current < and its partner. Return t when this happens, nil
5648 ;; when it doesn't.
5662 t)))
5664 ;; Set by c-common-init in cc-mode.el.
5667 ;; Set by c-after-change in cc-mode.el.
5672 ;; Unmark certain pairs of "< .... >" which are currently marked as
5673 ;; template/generic delimiters. (This marking is via syntax-table text
5674 ;; properties), and expand the (c-new-BEG c-new-END) region to include all
5675 ;; unmarked < and > operators within the certain bounds (see below).
5676 ;;
5677 ;; These pairs are those which are in the current "statement" (i.e.,
5678 ;; the region between the {, }, or ; before BEG and the one after
5679 ;; END), and which enclose any part of the interval (BEG END).
5680 ;;
5681 ;; Note that in C++ (?and Java), template/generic parens cannot
5682 ;; enclose a brace or semicolon, so we use these as bounds on the
5683 ;; region we must work on.
5684 ;;
5685 ;; This function is called from before-change-functions (via
5686 ;; c-get-state-before-change-functions). Thus the buffer is widened,
5687 ;; and point is undefined, both at entry and exit.
5688 ;;
5689 ;; FIXME!!! This routine ignores the possibility of macros entirely.
5690 ;; 2010-01-29.
5695 new-beg new-end beg-limit end-limit)
5696 ;; Locate the earliest < after the barrier before the changed region,
5697 ;; which isn't already marked as a paren.
5701 ;; Remove the syntax-table/category properties from each pertinent <...>
5702 ;; pair. Firstly, the ones with the < before beg and > after beg....
5711 ;; ...Then the ones with < before end and > after end.
5722 ;; Extend the fontification region, if needed.
5731 ;; This is called from `after-change-functions' when
5732 ;; c-recognize-<>-arglists' is set. It ensures that no "<" or ">"
5733 ;; chars with paren syntax become part of another operator like "<<"
5734 ;; or ">=".
5735 ;;
5736 ;; This function might do hidden buffer changes.
5769 ;; This function is called as an after-change function. It restores the
5770 ;; category/syntax-table properties on template/generic <..> pairs between
5771 ;; c-new-BEG and c-new-END. It may do hidden buffer changes.
5791 \f
5792 ;; Functions to handle C++ raw strings.
5793 ;;
5794 ;; A valid C++ raw string looks like
5795 ;; R"<id>(<contents>)<id>"
5796 ;; , where <id> is an identifier from 0 to 16 characters long, not containing
5797 ;; spaces, control characters, double quote or left/right paren. <contents>
5798 ;; can include anything which isn't the terminating )<id>", including new
5799 ;; lines, "s, parentheses, etc.
5800 ;;
5801 ;; CC Mode handles C++ raw strings by the use of `syntax-table' text
5802 ;; properties as follows:
5803 ;;
5804 ;; (i) On a validly terminated raw string, no `syntax-table' text properties
5805 ;; are applied to the opening and closing delimiters, but any " in the
5806 ;; contents is given the property value "punctuation" (`(1)') to prevent it
5807 ;; interacting with the "s in the delimiters.
5808 ;;
5809 ;; The font locking routine `c-font-lock-c++-raw-strings' (in cc-fonts.el)
5810 ;; recognizes valid raw strings, and fontifies the delimiters (apart from
5811 ;; the parentheses) with the default face and the parentheses and the
5812 ;; <contents> with font-lock-string-face.
5813 ;;
5814 ;; (ii) A valid, but unterminated, raw string opening delimiter gets the
5815 ;; "punctuation" value (`(1)') of the `syntax-table' text property, and the
5816 ;; open parenthesis gets the "string fence" value (`(15)').
5817 ;;
5818 ;; `c-font-lock-c++-raw-strings' puts c-font-lock-warning-face on the entire
5819 ;; unmatched opening delimiter (from the R up to the open paren), and allows
5820 ;; the rest of the buffer to get font-lock-string-face, caused by the
5821 ;; unmatched "string fence" `syntax-table' text property value.
5822 ;;
5823 ;; (iii) Inside a macro, a valid raw string is handled as in (i). An
5824 ;; unmatched opening delimiter is handled slightly differently. In addition
5825 ;; to the "punctuation" and "string fence" properties on the delimiter,
5826 ;; another "string fence" `syntax-table' property is applied to the last
5827 ;; possible character of the macro before the terminating linefeed (if there
5828 ;; is such a character after the "("). This "last possible" character is
5829 ;; never a backslash escaping the end of line. If the character preceding
5830 ;; this "last possible" character is itself a backslash, this preceding
5831 ;; character gets a "punctuation" `syntax-table' value. If the "(" is
5832 ;; already at the end of the macro, it gets the "punctuaion" value, and no
5833 ;; "string fence"s are used.
5834 ;;
5835 ;; The effect on the fontification of either of these tactics is that rest of
5836 ;; the macro (if any) after the "(" gets font-lock-string-face, but the rest
5837 ;; of the file is fontified normally.
5841 ;; Get POINT's relationship to any containing raw string.
5842 ;; If point isn't in a raw string, return nil.
5843 ;; Otherwise, return the following list:
5844 ;;
5845 ;; (POS B\" B\( E\) E\")
5846 ;;
5847 ;; , where POS is the symbol `open-delim' if point is in the opening
5848 ;; delimiter, the symbol `close-delim' if it's in the closing delimiter, and
5849 ;; nil if it's in the string body. B\", B\(, E\), E\" are the positions of
5850 ;; the opening and closing quotes and parentheses of a correctly terminated
5851 ;; raw string. (N.B.: E\) and E\" are NOT on the "outside" of these
5852 ;; characters.) If the raw string is not terminated, E\) and E\" are set to
5853 ;; nil.
5854 ;;
5855 ;; Note: this routine is dependant upon the correct syntax-table text
5856 ;; properties being set.
5859 open-quote-pos open-paren-pos close-paren-pos close-quote-pos id)
5891 open-quote-pos open-paren-pos close-paren-pos close-quote-pos))))
5894 ;; Point is immediately after a raw string opening delimiter. Remove any
5895 ;; `syntax-table' text properties associated with the delimiter (if it's
5896 ;; unmatched) or the raw string.
5897 ;;
5898 ;; ID, a string, is the delimiter's identifier. OPEN-QUOTE and OPEN-PAREN
5899 ;; are the buffer positions of the delimiter's components. BOUND is the
5900 ;; bound for searching for a matching closing delimiter; it is usually nil,
5901 ;; but if we're inside a macro, it's the end of the macro.
5902 ;;
5903 ;; Point is moved to after the (terminated) raw string, or left after the
5904 ;; unmatched opening delimiter, as the case may be. The return value is of
5905 ;; no significance.
5909 ;; A terminated raw string
5915 ;; An unterminated raw string either not in a macro, or in a macro with
5916 ;; the open parenthesis right up against the end of macro
5920 ;; An unterminated string in a macro, with at least one char after the
5921 ;; open paren
5930 ))))
5933 ;; Remove any `syntax-table' text properties associated with C++ raw strings
5934 ;; contained in the region (START FINISH). Point is undefined at entry and
5935 ;; exit, and the return value has no significance.
5940 c-anchored-cpp-prefix ; 2
5944 finish t))
5948 ;; We've found a raw string
5954 ;; We've found a CPP construct. Search for raw strings within it.
5969 ;; This function clears `syntax-table' text properties from C++ raw strings
5970 ;; in the region (c-new-BEG c-new-END). BEG and END are the standard
5971 ;; arguments supplied to any before-change function.
5972 ;;
5973 ;; Point is undefined on both entry and exit, and the return value has no
5974 ;; significance.
5975 ;;
5976 ;; This function is called as a before-change function solely due to its
5977 ;; membership of the C++ value of `c-get-state-before-change-functions'.
5981 beg
5985 ; Optimize this so that we don't call
5986 ; `c-raw-string-pos' twice when once
5987 ; will do. (2016-06-02).
5989 end
5991 )
6003 ;; Point is immediately after a raw string opening delimiter. Apply any
6004 ;; pertinent `syntax-table' text properties to the delimiter and also the
6005 ;; raw string, should there be a valid matching closing delimiter.
6006 ;;
6007 ;; ID, a string, is the delimiter's identifier. OPEN-QUOTE and OPEN-PAREN
6008 ;; are the buffer positions of the delimiter's components. BOUND is the
6009 ;; bound for searching for a matching closing delimiter; it is usually nil,
6010 ;; but if we're inside a macro, it's the end of the macro.
6011 ;;
6012 ;; Point is moved to after the (terminated) raw string, or left after the
6013 ;; unmatched opening delimiter, as the case may be. The return value is of
6014 ;; no significance.
6027 ;; In a CPP construct, we try to apply a generic-string `syntax-table'
6028 ;; text property to the last possible character in the string, so that
6029 ;; only characters within the macro get "stringed out".
6035 ;; This regular expression matches either an escape pair (which
6036 ;; isn't an escaped NL) (submatch 5) or a non-escaped character
6037 ;; (which isn't itself a backslash) (submatch 10). The long
6038 ;; preambles to these (respectively submatches 2-4 and 6-9)
6039 ;; ensure that we have the correct parity for sequences of
6040 ;; backslashes, etc..
6058 ;; This function applies `syntax-table' text properties to C++ raw strings
6059 ;; beginning in the region (c-new-BEG c-new-END). BEG, END, and OLD-LEN are
6060 ;; the standard arguments supplied to any after-change function.
6061 ;;
6062 ;; Point is undefined on both entry and exit, and the return value has no
6063 ;; significance.
6064 ;;
6065 ;; This function is called as an after-change function solely due to its
6066 ;; membership of the C++ value of `c-before-font-lock-functions'.
6068 ;; If the region (c-new-BEG c-new-END) has expanded, remove
6069 ;; `syntax-table' text-properties from the new piece(s).
6073 c-new-BEG
6076 c-old-BEG))))
6082 c-old-END)
6083 c-new-END)))
6089 c-anchored-cpp-prefix ; 2
6093 c-new-END t))
6097 ;; We've found a raw string.
6103 ;; We've found a CPP construct. Search for raw strings within it.
6117 \f
6118 ;; Handling of small scale constructs like types and names.
6120 ;; Dynamically bound variable that instructs `c-forward-type' to also
6121 ;; treat possible types (i.e. those that it normally returns 'maybe or
6122 ;; 'found for) as actual types (and always return 'found for them).
6123 ;; This means that it records them in `c-record-type-identifiers' if
6124 ;; that is set, and that it adds them to `c-found-types'.
6127 ;; Dynamically bound variable that instructs `c-forward-<>-arglist' to
6128 ;; mark up successfully parsed arglists with paren syntax properties on
6129 ;; the surrounding angle brackets and with `c-<>-arg-sep' in the
6130 ;; `c-type' property of each argument separating comma.
6131 ;;
6132 ;; Setting this variable also makes `c-forward-<>-arglist' recurse into
6133 ;; all arglists for side effects (i.e. recording types), otherwise it
6134 ;; exploits any existing paren syntax properties to quickly jump to the
6135 ;; end of already parsed arglists.
6136 ;;
6137 ;; Marking up the arglists is not the default since doing that correctly
6138 ;; depends on a proper value for `c-restricted-<>-arglists'.
6141 ;; Dynamically bound variable that instructs `c-forward-<>-arglist' to
6142 ;; not accept arglists that contain binary operators.
6143 ;;
6144 ;; This is primarily used to handle C++ template arglists. C++
6145 ;; disambiguates them by checking whether the preceding name is a
6146 ;; template or not. We can't do that, so we assume it is a template
6147 ;; if it can be parsed as one. That usually works well since
6148 ;; comparison expressions on the forms "a < b > c" or "a < b, c > d"
6149 ;; in almost all cases would be pointless.
6150 ;;
6151 ;; However, in function arglists, e.g. in "foo (a < b, c > d)", we
6152 ;; should let the comma separate the function arguments instead. And
6153 ;; in a context where the value of the expression is taken, e.g. in
6154 ;; "if (a < b || c > d)", it's probably not a template.
6157 ;; Dynamically bound variables that instructs
6158 ;; `c-forward-keyword-clause', `c-forward-<>-arglist',
6159 ;; `c-forward-name', `c-forward-type', `c-forward-decl-or-cast-1', and
6160 ;; `c-forward-label' to record the ranges of all the type and
6161 ;; reference identifiers they encounter. They will build lists on
6162 ;; these variables where each element is a cons of the buffer
6163 ;; positions surrounding each identifier. This recording is only
6164 ;; activated when `c-record-type-identifiers' is non-nil.
6165 ;;
6166 ;; All known types that can't be identifiers are recorded, and also
6167 ;; other possible types if `c-promote-possible-types' is set.
6168 ;; Recording is however disabled inside angle bracket arglists that
6169 ;; are encountered inside names and other angle bracket arglists.
6170 ;; Such occurrences are taken care of by `c-font-lock-<>-arglists'
6171 ;; instead.
6172 ;;
6173 ;; Only the names in C++ template style references (e.g. "tmpl" in
6174 ;; "tmpl<a,b>::foo") are recorded as references, other references
6175 ;; aren't handled here.
6176 ;;
6177 ;; `c-forward-label' records the label identifier(s) on
6178 ;; `c-record-ref-identifiers'.
6182 ;; This variable will receive a cons cell of the range of the last
6183 ;; single identifier symbol stepped over by `c-forward-name' if it's
6184 ;; successful. This is the range that should be put on one of the
6185 ;; record lists above by the caller. It's assigned nil if there's no
6186 ;; such symbol in the name.
6191 ;; Always true.
6201 ;; Always true.
6209 ;; Dynamically bound variable that instructs `c-forward-type' to
6210 ;; record the ranges of types that only are found. Behaves otherwise
6211 ;; like `c-record-type-identifiers'.
6215 ;; Used internally in `c-forward-keyword-clause' to move forward
6216 ;; over a type (if TYPE is 'type) or a name (otherwise) which
6217 ;; possibly is prefixed by keywords and their associated clauses.
6218 ;; Try with a type/name first to not trip up on those that begin
6219 ;; with a keyword. Return t if a known or found type is moved
6220 ;; over. The point is clobbered if nil is returned. If range
6221 ;; recording is enabled, the identifier is recorded on as a type
6222 ;; if TYPE is 'type or as a reference if TYPE is 'ref.
6223 ;;
6224 ;; This macro might do hidden buffer changes.
6230 nil
6241 t)))
6244 ;; Used internally in `c-forward-keyword-clause' to move forward
6245 ;; over a comma separated list of types or names using
6246 ;; `c-forward-keyword-prefixed-id'.
6247 ;;
6248 ;; This macro might do hidden buffer changes.
6259 ;; Point is at a c-noise-macro-with-parens-names macro identifier. Go
6260 ;; forward over this name, any parenthesis expression which follows it, and
6261 ;; any syntactic WS, ending up at the next token. If there is an unbalanced
6262 ;; paren expression, leave point at it. Always Return t.
6267 t)
6270 ;; Submatch MATCH in the current match data is assumed to surround a
6271 ;; token. If it's a keyword, move over it and any immediately
6272 ;; following clauses associated with it, stopping at the start of
6273 ;; the next token. t is returned in that case, otherwise the point
6274 ;; stays and nil is returned. The kind of clauses that are
6275 ;; recognized are those specified by `c-type-list-kwds',
6276 ;; `c-ref-list-kwds', `c-colon-type-list-kwds',
6277 ;; `c-paren-nontype-kwds', `c-paren-type-kwds', `c-<>-type-kwds',
6278 ;; and `c-<>-arglist-kwds'.
6279 ;;
6280 ;; This function records identifier ranges on
6281 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6282 ;; `c-record-type-identifiers' is non-nil.
6283 ;;
6284 ;; Note that for `c-colon-type-list-kwds', which doesn't necessary
6285 ;; apply directly after the keyword, the type list is moved over
6286 ;; only when there is no unaccounted token before it (i.e. a token
6287 ;; that isn't moved over due to some other keyword list). The
6288 ;; identifier ranges in the list are still recorded if that should
6289 ;; be done, though.
6290 ;;
6291 ;; This function might do hidden buffer changes.
6294 ;; The call to `c-forward-<>-arglist' below is made after
6295 ;; `c-<>-sexp-kwds' keywords, so we're certain they actually
6296 ;; are angle bracket arglists and `c-restricted-<>-arglists'
6297 ;; should therefore be nil.
6309 ;; There's a type directly after a keyword in `c-type-list-kwds'.
6314 ;; There's a name directly after a keyword in `c-ref-list-kwds'.
6319 ;; There's an open paren after a keyword in `c-paren-any-kwds'.
6326 ;; Use `c-forward-type' on every identifier we can find
6327 ;; inside the paren, to record the types.
6352 ;; If we are at the colon already, we move over the type
6353 ;; list after it.
6359 ;; Not at the colon, so stop here. But the identifier
6360 ;; ranges in the type list later on should still be
6361 ;; recorded.
6364 ;; If a keyword matched both one of the types above and
6365 ;; this one, we match `c-colon-type-list-re' after the
6366 ;; clause matched above.
6373 ;; There's a type after the `c-colon-type-list-re' match
6374 ;; after a keyword in `c-colon-type-list-kwds'.
6378 t)))
6380 ;; cc-mode requires cc-fonts.
6384 ;; The point is assumed to be at a "<". Try to treat it as the open
6385 ;; paren of an angle bracket arglist and move forward to the
6386 ;; corresponding ">". If successful, the point is left after the
6387 ;; ">" and t is returned, otherwise the point isn't moved and nil is
6388 ;; returned. If ALL-TYPES is t then all encountered arguments in
6389 ;; the arglist that might be types are treated as found types.
6390 ;;
6391 ;; The variable `c-parse-and-markup-<>-arglists' controls how this
6392 ;; function handles text properties on the angle brackets and argument
6393 ;; separating commas.
6394 ;;
6395 ;; `c-restricted-<>-arglists' controls how lenient the template
6396 ;; arglist recognition should be.
6397 ;;
6398 ;; This function records identifier ranges on
6399 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6400 ;; `c-record-type-identifiers' is non-nil.
6401 ;;
6402 ;; This function might do hidden buffer changes.
6405 ;; If `c-record-type-identifiers' is set then activate
6406 ;; recording of any found types that constitute an argument in
6407 ;; the arglist.
6415 ;; `nconc' doesn't mind that the tail of
6416 ;; `c-record-found-types' is t.
6418 t)
6421 nil)))
6424 ;; Recursive part of `c-forward-<>-arglist'.
6425 ;;
6426 ;; This function might do hidden buffer changes.
6428 ;; Cover this so that any recorded found type ranges are
6429 ;; automatically lost if it turns out to not be an angle
6430 ;; bracket arglist. It's propagated through the return value
6431 ;; on successful completion.
6433 ;; List that collects the positions after the argument
6434 ;; separating ',' in the arglist.
6435 arg-start-pos)
6436 ;; If the '<' has paren open syntax then we've marked it as an angle
6437 ;; bracket arglist before, so skip to the end.
6445 t
6446 ;; Got unmatched paren angle brackets. We don't clear the paren
6447 ;; syntax properties and retry, on the basis that it's very
6448 ;; unlikely that paren angle brackets become operators by code
6449 ;; manipulation. It's far more likely that it doesn't match due
6450 ;; to narrowing or some temporary change.
6452 nil))
6457 ;; go forward one non-alphanumeric character (group) per iteration of
6458 ;; this loop.
6472 ;; All encountered identifiers are types, so set the
6473 ;; promote flag and parse the type.
6491 ;; Note: These regexps exploit the match order in \| so
6492 ;; that "<>" is matched by "<" rather than "[^>:-]>".
6494 ;; Stop on ',', '|', '&', '+' and '-' to catch
6495 ;; common binary operators that could be between
6496 ;; two comparison expressions "a<b" and "c>d".
6497 ;; 2016-02-11: C++11 templates can now contain arithmetic
6498 ;; expressions, so template detection in C++ is now less
6499 ;; robust than it was.
6500 c-<>-notable-chars-re
6501 nil t t))
6505 ;; Either an operator starting with '>' or the end of
6506 ;; the angle bracket arglist.
6515 ;; The angle bracket arglist is finished.
6527 ;; Either an operator starting with '<' or a nested arglist.
6531 ;; The '<' begins a multi-char operator.
6534 ;; We're at a nested <.....>
6539 ;; There's always an identifier before an angle
6540 ;; bracket arglist, or a keyword in `c-<>-type-kwds'
6541 ;; or `c-<>-arglist-kwds'.
6558 subres)
6559 ;; It was an angle bracket arglist.
6562 ;; Record the identifier before the template as a type
6563 ;; or reference depending on whether the arglist is last
6564 ;; in a qualified identifier.
6574 ;; At a "less than" operator.
6576 ;; (forward-char) ; NO! We've already gone over the <.
6577 )))
6589 ;; Just another argument. Record the position. The
6590 ;; type check stuff that made us stop at it is at
6591 ;; the top of the loop.
6595 ;; Got a character that can't be in an angle bracket
6596 ;; arglist argument. Abort using `throw', since
6597 ;; it's useless to try to find a surrounding arglist
6598 ;; if we're nested.
6604 ;; The point is assumed to be directly after a ">". Try to treat it
6605 ;; as the close paren of an angle bracket arglist and move back to
6606 ;; the corresponding "<". If successful, the point is left at
6607 ;; the "<" and t is returned, otherwise the point isn't moved and
6608 ;; nil is returned. ALL-TYPES is passed on to
6609 ;; `c-forward-<>-arglist'.
6610 ;;
6611 ;; If the optional LIMIT is given, it bounds the backward search.
6612 ;; It's then assumed to be at a syntactically relevant position.
6613 ;;
6614 ;; This is a wrapper around `c-forward-<>-arglist'. See that
6615 ;; function for more details.
6624 t
6625 ;; See corresponding note in `c-forward-<>-arglist'.
6627 nil)
6634 t
6635 ;; Stopped at bob or a char that isn't allowed in an
6636 ;; arglist, so we've failed.
6638 nil)
6643 ;; If we moved then the "<" was part of some
6644 ;; multicharacter token.
6645 t
6651 ;; Matched the arglist. Break the while.
6653 nil)
6655 ;; We started from a non-paren ">" inside an
6656 ;; arglist.
6658 nil)
6660 ;; Matched a shorter arglist. Can be a nested
6661 ;; one so continue looking.
6663 t))
6664 t))))))
6669 ;; Move forward over a complete name if at the beginning of one,
6670 ;; stopping at the next following token. A keyword, as such,
6671 ;; doesn't count as a name. If the point is not at something that
6672 ;; is recognized as a name then it stays put.
6673 ;;
6674 ;; A name could be something as simple as "foo" in C or something as
6675 ;; complex as "X<Y<class A<int>::B, BIT_MAX >> b>, ::operator<> ::
6676 ;; Z<(a>b)> :: operator const X<&foo>::T Q::G<unsigned short
6677 ;; int>::*volatile const" in C++ (this function is actually little
6678 ;; more than a `looking-at' call in all modes except those that,
6679 ;; like C++, have `c-recognize-<>-arglists' set).
6680 ;;
6681 ;; Return
6682 ;; o - nil if no name is found;
6683 ;; o - 'template if it's an identifier ending with an angle bracket
6684 ;; arglist;
6685 ;; o - 'operator of it's an operator identifier;
6686 ;; o - t if it's some other kind of name.
6687 ;;
6688 ;; This function records identifier ranges on
6689 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6690 ;; `c-record-type-identifiers' is non-nil.
6691 ;;
6692 ;; This function might do hidden buffer changes.
6695 ;; Turn off `c-promote-possible-types' here since we might
6696 ;; call `c-forward-<>-arglist' and we don't want it to promote
6697 ;; every suspect thing in the arglist to a type. We're
6698 ;; typically called from `c-forward-type' in this case, and
6699 ;; the caller only wants the top level type that it finds to
6700 ;; be promoted.
6701 c-promote-possible-types)
6707 ;; Check for keyword. We go to the last symbol in
6708 ;; `c-identifier-key' first.
6721 ;; "template" is only valid inside an
6722 ;; identifier if preceded by "::".
6727 t))
6729 ;; Handle a C++ operator or template identifier.
6733 ;; Got "... ::template".
6737 res subres))))
6740 ;; Got a cast operator.
6744 ;; Now we should match a sequence of either
6745 ;; '*', '&' or a name followed by ":: *",
6746 ;; where each can be followed by a sequence
6747 ;; of `c-opt-type-modifier-key'.
6750 t)
6760 t))))
6768 ;; Got some other operator.
6776 nil)
6778 ;; `id-start' is equal to `id-end' if we've jumped over
6779 ;; an identifier that doesn't end with a symbol token.
6780 ;; That can occur e.g. for Java import directives on the
6781 ;; form "foo.bar.*".
6788 res t)))
6798 ;; Got a concatenated identifier. This handles the
6799 ;; cases with tricky syntactic whitespace that aren't
6800 ;; covered in `c-identifier-key'.
6803 t)
6807 ;; Maybe an angle bracket arglist.
6820 ;; Continue if there's an identifier concatenation
6821 ;; operator after the template argument.
6827 t)
6833 nil)))
6834 )))))
6837 res))
6840 ;; Move forward over a type spec if at the beginning of one,
6841 ;; stopping at the next following token. The keyword "typedef"
6842 ;; isn't part of a type spec here.
6843 ;;
6844 ;; BRACE-BLOCK-TOO, when non-nil, means move over the brace block in
6845 ;; constructs like "struct foo {...} bar ;" or "struct {...} bar;".
6846 ;; The current (2009-03-10) intention is to convert all uses of
6847 ;; `c-forward-type' to call with this parameter set, then to
6848 ;; eliminate it.
6849 ;;
6850 ;; Return
6851 ;; o - t if it's a known type that can't be a name or other
6852 ;; expression;
6853 ;; o - 'known if it's an otherwise known type (according to
6854 ;; `*-font-lock-extra-types');
6855 ;; o - 'prefix if it's a known prefix of a type;
6856 ;; o - 'found if it's a type that matches one in `c-found-types';
6857 ;; o - 'maybe if it's an identifier that might be a type;
6858 ;; o - 'decltype if it's a decltype(variable) declaration; - or
6859 ;; o - nil if it can't be a type (the point isn't moved then).
6860 ;;
6861 ;; The point is assumed to be at the beginning of a token.
6862 ;;
6863 ;; Note that this function doesn't skip past the brace definition
6864 ;; that might be considered part of the type, e.g.
6865 ;; "enum {a, b, c} foo".
6866 ;;
6867 ;; This function records identifier ranges on
6868 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6869 ;; `c-record-type-identifiers' is non-nil.
6870 ;;
6871 ;; This function might do hidden buffer changes.
6879 ;; Skip leading type modifiers. If any are found we know it's a
6880 ;; prefix of a type.
6899 ; "typedef".
6915 ;; In many languages the name can be used without the
6916 ;; prefix, so we add it to `c-found-types'.
6919 c-last-identifier-range)
6941 id-range c-last-identifier-range))))
6953 id-end)
6955 ;; Looking at a primitive or known type identifier. We've
6956 ;; checked for a name first so that we don't go here if the
6957 ;; known type match only is a prefix of another name.
6968 ;; There might be more keywords for the type.
6996 ;; A normal identifier.
7006 ;; It's an identifier that has been used as
7007 ;; a type somewhere else.
7008 'found
7009 ;; It's an identifier that might be a type.
7012 ;; A template is sometimes a type.
7018 ;; It's an identifier that has been used as
7019 ;; a type somewhere else.
7020 'found
7021 ;; It's an identifier that might be a type.
7023 t)))
7025 ;; Otherwise it's an operator identifier, which is not a type.
7030 ;; Skip trailing type modifiers. If any are found we know it's
7031 ;; a type.
7038 ;; Step over any type suffix operator. Do not let the existence
7039 ;; of these alter the classification of the found type, since
7040 ;; these operators typically are allowed in normal expressions
7041 ;; too.
7048 ;; Look for a trailing operator that concatenates the type
7049 ;; with a following one, and if so step past that one through
7050 ;; a recursive call. Note that we don't record concatenated
7051 ;; types in `c-found-types' - it's the component types that
7052 ;; are recorded when appropriate.
7055 c-promote-possible-types))
7056 ;; If we can't promote then set `c-record-found-types' so that
7057 ;; we can merge in the types from the second part afterwards if
7058 ;; it turns out to be a known type there.
7061 subres)
7070 ;; If either operand certainly is a type then both are, but we
7071 ;; don't let the existence of the operator itself promote two
7072 ;; uncertain types to a certain one.
7091 ;; Merge in the ranges of any types found by the second
7092 ;; `c-forward-type'.
7094 ;; `nconc' doesn't mind that the tail of
7095 ;; `c-record-found-types' is t.
7097 c-record-type-identifiers))))
7105 ;;(message "c-forward-type %s -> %s: %s" start (point) res)
7107 res))
7110 ;; Used for Java code only at the moment. Assumes point is on the @, moves
7111 ;; forward an annotation and returns t. Leaves point unmoved and returns
7112 ;; nil if there is no annotation at point.
7121 t)
7124 t))
7128 ;; Pull the next open brace from PS (which has the form of paren-state),
7129 ;; skipping over any brace pairs. Returns NIL when PS is exhausted.
7137 ;; Point is putatively just after a "compound identifier", i.e. something
7138 ;; looking (in C++) like this "FQN::of::base::Class". Move to the start of
7139 ;; this construct and return t. If the parsing fails, return nil, leaving
7140 ;; point unchanged.
7142 end
7143 )
7145 nil
7152 c-opt-identifier-concat-key
7159 t)))
7162 ;; Point is just after a closing brace/parenthesis. Try to parse this as a
7163 ;; C++ member initializer list, going back to just after the introducing ":"
7164 ;; and returning t. Otherwise return nil, leaving point unchanged.
7189 res))
7192 ;; Go back over a list of elements, each looking like:
7193 ;; <symbol> (<expression>) ,
7194 ;; or <symbol> {<expression>} ,
7195 ;; when we are putatively immediately after a comma. Stop when we don't see
7196 ;; a comma. If either of <symbol> or bracketed <expression> is missing,
7197 ;; throw nil to 'level. If the terminating } or ) is unmatched, throw nil
7198 ;; to 'done. This is not a general purpose macro!
7212 ;; Test whether we are in a C++ member initializer list, and if so, go back
7213 ;; to the introducing ":", returning the position of the opening paren of
7214 ;; the function's arglist. Otherwise return nil, leaving point unchanged.
7217 pos level-plausible at-top-level res)
7218 ;; Assume tentatively that we're at the top level. Try to go back to the
7219 ;; colon we seek.
7257 res))
7259 \f
7260 ;; Handling of large scale constructs like statements and declarations.
7262 ;; Macro used inside `c-forward-decl-or-cast-1'. It ought to be a
7263 ;; defsubst or perhaps even a defun, but it contains lots of free
7264 ;; variables that refer to things inside `c-forward-decl-or-cast-1'.
7266 ;; `c-forward-decl-or-cast-1' can consume an arbitrary length list
7267 ;; of types when parsing a declaration, which means that it
7268 ;; sometimes consumes the identifier in the declaration as a type.
7269 ;; This is used to "backtrack" and make the last type be treated as
7270 ;; an identifier instead.
7273 ;; These identifiers are bound only in the inner let.
7275 identifier-start type-start
7276 got-parens nil
7277 got-identifier t
7278 got-suffix t
7279 got-suffix-after-parens id-start
7283 t
7284 backup-at-type))
7286 id-start backup-id-start)
7288 id-start start-pos))
7290 ;; When these flags already are set we've found specifiers that
7291 ;; unconditionally signal these attributes - backtracking doesn't
7292 ;; change that. So keep them set in that case.
7299 ;; This identifier is bound only in the inner let.
7303 ;; Assuming point is at the start of a declarator, move forward over it,
7304 ;; leaving point at the next token after it (e.g. a ) or a ; or a ,).
7305 ;;
7306 ;; Return a list (ID-START ID-END BRACKETS-AFTER-ID GOT-INIT), where ID-START and
7307 ;; ID-END are the bounds of the declarator's identifier, and
7308 ;; BRACKETS-AFTER-ID is non-nil if a [...] pair is present after the id.
7309 ;; GOT-INIT is non-nil when the declarator is followed by "=" or "(".
7310 ;;
7311 ;; If ACCEPT-ANON is non-nil, move forward over any "anonymous declarator",
7312 ;; i.e. something like the (*) in int (*), such as might be found in a
7313 ;; declaration. In such a case ID-START and ID-END in the return value are
7314 ;; both set to nil. A "null" "anonymous declarator" gives a non-nil result.
7315 ;;
7316 ;; If no declarator is found, leave point unmoved and return nil. LIMIT is
7317 ;; an optional limit for forward searching.
7318 ;;
7319 ;; Note that the global variable `c-last-identifier-range' is written to, so
7320 ;; the caller should bind it if necessary.
7322 ;; Inside the following "condition form", we move forward over the
7323 ;; declarator's identifier up as far as any opening bracket (for array
7324 ;; size) or paren (for parameters of function-type) or brace (for
7325 ;; array/struct initialization) or "=" or terminating delimiter
7326 ;; (e.g. "," or ";" or "}").
7328 id-start id-end brackets-after-id paren-depth)
7333 ;; The following form moves forward over the declarator's
7334 ;; identifier (and what precedes it), returning t. If there
7335 ;; wasn't one, it returns nil.
7338 ;; Skip over type decl prefix operators, one for each iteration
7339 ;; of the while. These are, e.g. "*" in "int *foo" or "(" and
7340 ;; "*" in "int (*foo) (void)" (Note similar code in
7341 ;; `c-forward-decl-or-cast-1'.)
7352 ;; If the third submatch matches in C++ then
7353 ;; we're looking at an identifier that's a
7354 ;; prefix only if it specifies a member pointer.
7359 ;; We only check for a trailing "::" and
7360 ;; let the "*" that should follow be
7361 ;; matched in the next round.
7362 t
7363 ;; It turned out to be the real identifier,
7364 ;; so flag that and stop.
7366 nil))
7367 t))
7374 t)))
7376 ;; If we haven't passed the identifier already, do it now.
7387 t)
7390 ;; Skip out of the parens surrounding the identifier. If closing
7391 ;; parens are missing, this form returns nil.
7397 ;; Skip over any trailing bit, such as "__attribute__".
7407 ;; Search syntactically to the end of the declarator (";",
7408 ;; ",", a closing paren, eob etc) or to the beginning of an
7409 ;; initializer or function prototype ("=" or "\\s\(").
7410 ;; Note that square brackets are now not also treated as
7411 ;; initializers, since this broke when there were also
7412 ;; initializing brace lists.
7421 found))
7425 nil)))
7428 ;; Move forward over a declaration or a cast if at the start of one.
7429 ;; The point is assumed to be at the start of some token. Nil is
7430 ;; returned if no declaration or cast is recognized, and the point
7431 ;; is clobbered in that case.
7432 ;;
7433 ;; If a declaration is parsed:
7434 ;;
7435 ;; The point is left at the first token after the first complete
7436 ;; declarator, if there is one. The return value is a list of 4 elements,
7437 ;; where the first is the position of the first token in the declarator.
7438 ;; (See below for the other three.)
7439 ;; Some examples:
7440 ;;
7441 ;; void foo (int a, char *b) stuff ...
7442 ;; car ^ ^ point
7443 ;; float (*a)[], b;
7444 ;; car ^ ^ point
7445 ;; unsigned int a = c_style_initializer, b;
7446 ;; car ^ ^ point
7447 ;; unsigned int a (cplusplus_style_initializer), b;
7448 ;; car ^ ^ point (might change)
7449 ;; class Foo : public Bar {}
7450 ;; car ^ ^ point
7451 ;; class PikeClass (int a, string b) stuff ...
7452 ;; car ^ ^ point
7453 ;; enum bool;
7454 ;; car ^ ^ point
7455 ;; enum bool flag;
7456 ;; car ^ ^ point
7457 ;; void cplusplus_function (int x) throw (Bad);
7458 ;; car ^ ^ point
7459 ;; Foo::Foo (int b) : Base (b) {}
7460 ;; car ^ ^ point
7461 ;;
7462 ;; auto foo = 5;
7463 ;; car ^ ^ point
7464 ;; auto cplusplus_11 (int a, char *b) -> decltype (bar):
7465 ;; car ^ ^ point
7466 ;;
7467 ;;
7468 ;;
7469 ;; The second element of the return value is non-nil when a
7470 ;; `c-typedef-decl-kwds' specifier is found in the declaration.
7471 ;; Specifically it is a dotted pair (A . B) where B is t when a
7472 ;; `c-typedef-kwds' ("typedef") is present, and A is t when some
7473 ;; other `c-typedef-decl-kwds' (e.g. class, struct, enum)
7474 ;; specifier is present. I.e., (some of) the declared
7475 ;; identifier(s) are types.
7476 ;;
7477 ;; The third element of the return value is non-nil when the declaration
7478 ;; parsed might be an expression. The fourth element is the position of
7479 ;; the start of the type identifier.
7480 ;;
7481 ;; If a cast is parsed:
7482 ;;
7483 ;; The point is left at the first token after the closing paren of
7484 ;; the cast. The return value is `cast'. Note that the start
7485 ;; position must be at the first token inside the cast parenthesis
7486 ;; to recognize it.
7487 ;;
7488 ;; PRECEDING-TOKEN-END is the first position after the preceding
7489 ;; token, i.e. on the other side of the syntactic ws from the point.
7490 ;; Use a value less than or equal to (point-min) if the point is at
7491 ;; the first token in (the visible part of) the buffer.
7492 ;;
7493 ;; CONTEXT is a symbol that describes the context at the point:
7494 ;; 'decl In a comma-separated declaration context (typically
7495 ;; inside a function declaration arglist).
7496 ;; '<> In an angle bracket arglist.
7497 ;; 'arglist Some other type of arglist.
7498 ;; nil Some other context or unknown context. Includes
7499 ;; within the parens of an if, for, ... construct.
7500 ;;
7501 ;; LAST-CAST-END is the first token after the closing paren of a
7502 ;; preceding cast, or nil if none is known. If
7503 ;; `c-forward-decl-or-cast-1' is used in succession, it should be
7504 ;; the position after the closest preceding call where a cast was
7505 ;; matched. In that case it's used to discover chains of casts like
7506 ;; "(a) (b) c".
7507 ;;
7508 ;; This function records identifier ranges on
7509 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
7510 ;; `c-record-type-identifiers' is non-nil.
7511 ;;
7512 ;; This function might do hidden buffer changes.
7515 ;; first type, i.e. after any leading specifiers. It might
7516 ;; also point at the beginning of the preceding syntactic
7517 ;; whitespace.
7519 ;; Set to the result of `c-forward-type'.
7520 at-type
7521 ;; The position of the first token in what we currently
7522 ;; believe is the type in the declaration or cast, after any
7523 ;; specifiers and their associated clauses.
7524 type-start
7525 ;; The position of the first token in what we currently
7526 ;; believe is the declarator for the first identifier. Set
7527 ;; when the type is found, and moved forward over any
7528 ;; `c-decl-hangon-kwds' and their associated clauses that
7529 ;; occurs after the type.
7530 id-start
7531 ;; These store `at-type', `type-start' and `id-start' of the
7532 ;; identifier before the one in those variables. The previous
7533 ;; identifier might turn out to be the real type in a
7534 ;; declaration if the last one has to be the declarator in it.
7535 ;; If `backup-at-type' is nil then the other variables have
7536 ;; undefined values.
7537 backup-at-type backup-type-start backup-id-start
7538 ;; This stores `kwd-sym' of the symbol before the current one.
7539 ;; This is needed to distinguish the C++11 version of "auto" from
7540 ;; the pre C++11 meaning.
7541 backup-kwd-sym
7542 ;; Set if we've found a specifier (apart from "typedef") that makes
7543 ;; the defined identifier(s) types.
7544 at-type-decl
7545 ;; Set if we've a "typedef" keyword.
7546 at-typedef
7547 ;; Set if we've found a specifier that can start a declaration
7548 ;; where there's no type.
7549 maybe-typeless
7550 ;; Save the value of kwd-sym between loops of the "Check for a
7551 ;; type" loop. Needed to distinguish a C++11 "auto" from a pre
7552 ;; C++11 one.
7553 prev-kwd-sym
7554 ;; If a specifier is found that also can be a type prefix,
7555 ;; these flags are set instead of those above. If we need to
7556 ;; back up an identifier, they are copied to the real flag
7557 ;; variables. Thus they only take effect if we fail to
7558 ;; interpret it as a type.
7559 backup-at-type-decl backup-maybe-typeless
7560 ;; Whether we've found a declaration or a cast. We might know
7561 ;; this before we've found the type in it. It's 'ids if we've
7562 ;; found two consecutive identifiers (usually a sure sign, but
7563 ;; we should allow that in labels too), and t if we've found a
7564 ;; specifier keyword (a 100% sure sign).
7565 at-decl-or-cast
7566 ;; Set when we need to back up to parse this as a declaration
7567 ;; but not as a cast.
7568 backup-if-not-cast
7569 ;; For casts, the return position.
7570 cast-end
7571 ;; Have we got a new-style C++11 "auto"?
7572 new-style-auto
7573 ;; Set when the symbol before `preceding-token-end' is known to
7574 ;; terminate the previous construct, or when we're at point-min.
7575 at-decl-start
7576 ;; Save `c-record-type-identifiers' and
7577 ;; `c-record-ref-identifiers' since ranges are recorded
7578 ;; speculatively and should be thrown away if it turns out
7579 ;; that it isn't a declaration or cast.
7582 ;; Set when we parse a declaration which might also be an expression,
7583 ;; such as "a *b". See CASE 16 and CASE 17.
7584 maybe-expression)
7593 c-pre-start-tokens)))))
7598 ;; Check for a type. Unknown symbols are treated as possible
7599 ;; types, but they could also be specifiers disguised through
7600 ;; macros like __INLINE__, so we recognize both types and known
7601 ;; specifiers after them too.
7606 ;; Look for a specifier keyword clause.
7624 ;; Found a known or possible type or a prefix of a known type.
7633 ;; Got two identifiers with nothing but whitespace
7634 ;; between them. That can only happen in declarations.
7638 ;; If the previous identifier is a found type we
7639 ;; record it as a real one; it might be some sort of
7640 ;; alias for a prefix like "unsigned".
7647 backup-type-start type-start
7648 backup-id-start id-start
7649 backup-kwd-sym kwd-sym
7650 at-type found-type
7651 type-start start
7653 ;; The previous ambiguous specifier/type turned out
7654 ;; to be a type since we've parsed another one after
7655 ;; it, so clear these backup flags.
7656 backup-at-type-decl nil
7657 backup-maybe-typeless nil))
7661 ;; Handle known specifier keywords and
7662 ;; `c-decl-hangon-kwds' which can occur after known
7663 ;; types.
7666 noise-start)
7667 ;; It's a hang-on keyword or noise clause that can occur
7668 ;; anywhere.
7671 ;; Move the identifier start position if
7672 ;; we've passed a type.
7674 ;; Otherwise treat this as a specifier and
7675 ;; move the fallback position.
7679 ;; It's an ordinary specifier so we know that
7680 ;; anything before this can't be the type.
7682 start-pos kwd-clause-end)
7685 ;; It's ambiguous whether this keyword is a
7686 ;; specifier or a type prefix, so set the backup
7687 ;; flags. (It's assumed that `c-forward-type'
7688 ;; moved further than `c-forward-keyword-clause'.)
7696 ;; This test only happens after we've scanned a type.
7697 ;; So, with valid syntax, kwd-sym can't be 'typedef.
7702 ;; Haven't matched a type so it's an unambiguous
7703 ;; specifier keyword and we know we're in a
7704 ;; declaration.
7710 ;; If the type isn't known we continue so that we'll jump
7711 ;; over all specifiers and type identifiers. The reason
7712 ;; to do this for a known type prefix is to make things
7713 ;; like "unsigned INT16" work.
7718 ;; If a known type was found, we still need to skip over any
7719 ;; hangon keyword clauses after it. Otherwise it has already
7720 ;; been done in the loop above.
7730 ;; A prefix type is itself a primitive type when it's not
7731 ;; followed by another type.
7735 ;; Got no type but set things up to continue anyway to handle
7736 ;; the various cases when a declaration doesn't start with a
7737 ;; type.
7742 ;; If it's C++ then check if the last "type" ends on the form
7743 ;; "foo::foo" or "foo::~foo", i.e. if it's the name of a
7744 ;; (con|de)structor.
7755 ;; Cheating in the handling of syntactic ws below.
7762 name))
7763 ;; It is a (con|de)structor name. In that case the
7764 ;; declaration is typeless so zap out any preceding
7765 ;; identifier(s) that we might have taken as types.
7768 backup-at-type nil
7769 id-start type-start))))))
7771 ;; Check for and step over a type decl expression after the thing
7772 ;; that is or might be a type. This can't be skipped since we
7773 ;; need the correct end position of the declarator for
7774 ;; `max-type-decl-end-*'.
7776 ;; True if there's a non-open-paren match of
7777 ;; `c-type-decl-prefix-key'.
7778 got-prefix
7779 ;; True if the declarator is surrounded by a parenthesis pair.
7780 got-parens
7781 ;; True if there is an identifier in the declarator.
7782 got-identifier
7783 ;; True if there's a non-close-paren match of
7784 ;; `c-type-decl-suffix-key'.
7785 got-suffix
7786 ;; True if there's a prefix match outside the outermost
7787 ;; paren pair that surrounds the declarator.
7788 got-prefix-before-parens
7789 ;; True if there's a suffix match outside the outermost
7790 ;; paren pair that surrounds the declarator. The value is
7791 ;; the position of the first suffix match.
7792 got-suffix-after-parens
7793 ;; True if we've parsed the type decl to a token that is
7794 ;; known to end declarations in this context.
7795 at-decl-end
7796 ;; The earlier values of `at-type' and `type-start' if we've
7797 ;; shifted the type backwards.
7798 identifier-type identifier-start
7799 ;; If `c-parse-and-markup-<>-arglists' is set we need to
7800 ;; turn it off during the name skipping below to avoid
7801 ;; getting `c-type' properties that might be bogus. That
7802 ;; can happen since we don't know if
7803 ;; `c-restricted-<>-arglists' will be correct inside the
7804 ;; arglist paren that gets entered.
7805 c-parse-and-markup-<>-arglists
7806 ;; Start of the identifier for which `got-identifier' was set.
7807 name-start)
7811 ;; Skip over type decl prefix operators. (Note similar code in
7812 ;; `c-forward-declarator'.)
7822 ;; If the third submatch matches in C++ then
7823 ;; we're looking at an identifier that's a
7824 ;; prefix only if it specifies a member pointer.
7829 ;; We only check for a trailing "::" and
7830 ;; let the "*" that should follow be
7831 ;; matched in the next round.
7833 ;; It turned out to be the real identifier,
7834 ;; so stop.
7835 nil))
7836 t))
7850 ;; Skip over an identifier.
7857 ;; Skip over type decl suffix operators and trailing noise macros.
7869 t)
7873 t)
7880 ;; No suffix matched. We might have matched the
7881 ;; identifier as a type and the open paren of a
7882 ;; function arglist as a type decl prefix. In that
7883 ;; case we should "backtrack": Reinterpret the last
7884 ;; type as the identifier, move out of the arglist and
7885 ;; continue searching for suffix operators.
7886 ;;
7887 ;; Do this even if there's no preceding type, to cope
7888 ;; with old style function declarations in K&R C,
7889 ;; (con|de)structors in C++ and `c-typeless-decl-kwds'
7890 ;; style declarations. That isn't applicable in an
7891 ;; arglist context, though.
7896 maybe-typeless
7897 backup-maybe-typeless
7904 t)))
7913 at-type))
7914 ;; Have found no identifier but `c-typeless-decl-kwds' has
7915 ;; matched so we know we're inside a declaration. The
7916 ;; preceding type must be the identifier instead.
7919 ;; Prepare the "-> type;" for fontification later on.
7929 at-decl-or-cast
7932 ;; CASE 1
7934 ;; Encountered something inside parens that isn't matched by
7935 ;; the `c-type-decl-*' regexps, so it's not a type decl
7936 ;; expression. Try to skip out to the same paren depth to
7937 ;; not confuse the cast check below.
7939 ;; If we've found a specifier keyword then it's a
7940 ;; declaration regardless.
7948 ;; Now we've collected info about various characteristics of
7949 ;; the construct we're looking at. Below follows a decision
7950 ;; tree based on that. It's ordered to check more certain
7951 ;; signs before less certain ones.
7956 ;; CASE 2
7959 ;; Got another identifier directly after the type, so it's a
7960 ;; declaration.
7965 ;; (not got-suffix-after-parens)
7967 maybe-typeless
7968 backup-maybe-typeless
7970 ;; Check whether we have "bar (gnu);" where we
7971 ;; are directly inside a class (etc.) called "bar".
7981 type-start
7987 ;; Got a declaration of the form "foo bar (gnu);" or "bar
7988 ;; (gnu);" where we've recognized "bar" as the type and "gnu"
7989 ;; as the declarator, and in the latter case, checked that
7990 ;; "bar (gnu)" appears directly inside the class "bar". In
7991 ;; this case it's however more likely that "bar" is the
7992 ;; declarator and "gnu" a function argument or initializer
7993 ;; (if `c-recognize-paren-inits' is set), since the parens
7994 ;; around "gnu" would be superfluous if it's a declarator.
7995 ;; Shift the type one step backward.
7998 ;; Found no identifier.
8003 ;; CASE 3
8005 ;; Got a plain list of identifiers. If a colon follows it's
8006 ;; a valid label, or maybe a bitfield. Otherwise the last
8007 ;; one probably is the declared identifier and we should
8008 ;; back up to the previous type, providing it isn't a cast.
8012 ;; If we've found a specifier keyword then it's a
8013 ;; declaration regardless.
8024 ;; CASE 4
8028 ;; Got a plain list of identifiers followed by some suffix.
8029 ;; If this isn't a cast then the last identifier probably is
8030 ;; the declared one and we should back up to the previous
8031 ;; type.
8035 ;; CASE 5
8037 ;; If the type is known we know that there can't be any
8038 ;; identifier somewhere else, and it's only in declarations in
8039 ;; e.g. function prototypes and in casts that the identifier may
8040 ;; be left out.
8044 ;; Only got a single identifier (parsed as a type so far).
8045 ;; CASE 6
8047 ;; Check that the identifier isn't at the start of an
8048 ;; expression.
8049 at-decl-end
8052 ;; Inside an arglist that contains declarations. If K&R
8053 ;; style declarations and parenthesis style initializers
8054 ;; aren't allowed then the single identifier must be a
8055 ;; type, else we require that it's known or found
8056 ;; (primitive types are handled above).
8061 ;; Inside a template arglist. Accept known and found
8062 ;; types; other identifiers could just as well be
8063 ;; constants in C++.
8066 ;; CASE 7
8067 ;; Can't be a valid declaration or cast, but if we've found a
8068 ;; specifier it can't be anything else either, so treat it as
8069 ;; an invalid/unfinished declaration or cast.
8077 maybe-typeless
8078 backup-maybe-typeless
8082 c-after-suffixed-type-maybe-decl-key))))))
8083 ;; Got an empty paren pair and a preceding type that probably
8084 ;; really is the identifier. Shift the type backwards to make
8085 ;; the last one the identifier. This is analogous to the
8086 ;; "backtracking" done inside the `c-type-decl-suffix-key' loop
8087 ;; above.
8088 ;;
8089 ;; Exception: In addition to the conditions in that
8090 ;; "backtracking" code, do not shift backward if we're not
8091 ;; looking at either `c-after-suffixed-type-decl-key' or "[;,]".
8092 ;; Since there's no preceding type, the shift would mean that
8093 ;; the declaration is typeless. But if the regexp doesn't match
8094 ;; then we will simply fall through in the tests below and not
8095 ;; recognize it at all, so it's better to try it as an abstract
8096 ;; declarator instead.
8099 ;; Still no identifier.
8100 ;; CASE 8
8102 ;; Require `got-prefix' together with either `got-parens' or
8103 ;; `got-suffix' to recognize it as an abstract declarator:
8104 ;; `got-parens' only is probably an empty function call.
8105 ;; `got-suffix' only can build an ordinary expression together
8106 ;; with the preceding identifier which we've taken as a type.
8107 ;; We could actually accept on `got-prefix' only, but that can
8108 ;; easily occur temporarily while writing an expression so we
8109 ;; avoid that case anyway. We could do a better job if we knew
8110 ;; the point when the fontification was invoked.
8113 ;; CASE 9
8117 got-suffix-after-parens
8119 ;; Got a type, no declarator but a paren suffix. I.e. it's a
8120 ;; normal function call after all (or perhaps a C++ style object
8121 ;; instantiation expression).
8124 ;; CASE 10
8126 ;; By now we've located the type in the declaration that we know
8127 ;; we're in.
8130 ;; CASE 11
8138 ;; Shift the type backward in the case that there's a
8139 ;; single identifier inside parens. That can only
8140 ;; occur in K&R style function declarations so it's
8141 ;; more likely that it really is a function call.
8142 ;; Therefore we only do this after
8143 ;; `c-after-suffixed-type-decl-key' has matched.
8145 got-suffix-after-parens))
8146 ;; A declaration according to `c-after-suffixed-type-decl-key'.
8149 ;; CASE 12
8152 ;; It's a declaration if a known type precedes it and it can't be a
8153 ;; function call.
8156 ;; If we get here we can't tell if this is a type decl or a normal
8157 ;; expression by looking at it alone. (That's under the assumption
8158 ;; that normal expressions always can look like type decl expressions,
8159 ;; which isn't really true but the cases where it doesn't hold are so
8160 ;; uncommon (e.g. some placements of "const" in C++) it's not worth
8161 ;; the effort to look for them.)
8163 ;;; 2008-04-16: commented out the next form, to allow the function to recognize
8164 ;;; "foo (int bar)" in CC (an implicit type (in class foo) without a semicolon)
8165 ;;; as a(n almost complete) declaration, enabling it to be fontified.
8166 ;; CASE 13
8167 ;; (unless (or at-decl-end (looking-at "=[^=]"))
8168 ;; If this is a declaration it should end here or its initializer(*)
8169 ;; should start here, so check for allowed separation tokens. Note
8170 ;; that this rule doesn't work e.g. with a K&R arglist after a
8171 ;; function header.
8172 ;;
8173 ;; *) Don't check for C++ style initializers using parens
8174 ;; since those already have been matched as suffixes.
8175 ;;
8176 ;; If `at-decl-or-cast' is then we've found some other sign that
8177 ;; it's a declaration or cast, so then it's probably an
8178 ;; invalid/unfinished one.
8179 ;; (throw 'at-decl-or-cast at-decl-or-cast))
8181 ;; Below are tests that only should be applied when we're certain to
8182 ;; not have parsed halfway through an expression.
8184 ;; CASE 14
8186 ;; The expression starts with a known type so treat it as a
8187 ;; declaration.
8190 ;; CASE 15
8192 ;; In C++ we check if the identifier is a known type, since
8193 ;; (con|de)structors use the class name as identifier.
8194 ;; We've always shifted over the identifier as a type and
8195 ;; then backed up again in this case.
8196 identifier-type
8199 ;; `at-type' probably won't be 'found for
8200 ;; destructors since the "~" is then part of the
8201 ;; type name being checked against the list of
8202 ;; known types, so do a check without that
8203 ;; operator.
8208 c-identifier-syntax-table
8212 ;; We have already parsed the type earlier,
8213 ;; so it'd be possible to cache the end
8214 ;; position instead of redoing it here, but
8215 ;; then we'd need to keep track of another
8216 ;; position everywhere.
8224 ;; CASE 16
8226 at-type
8230 at-decl-start))
8231 ;; Got something like "foo * bar;". Since we're not inside
8232 ;; an arglist it would be a meaningless expression because
8233 ;; the result isn't used. We therefore choose to recognize
8234 ;; it as a declaration. We only allow a suffix (which makes
8235 ;; the construct look like a function call) when
8236 ;; `at-decl-start' provides additional evidence that we do
8237 ;; have a declaration.
8241 ;; CASE 17
8246 ;; Got something like "a (*b) (c);" or "a (b) = c;". It could
8247 ;; be an odd expression or it could be a declaration. Treat
8248 ;; it as a declaration if "a" has been used as a type
8249 ;; somewhere else (if it's a known type we won't get here).
8253 ;; CASE 18
8259 ;; Got a type followed by an abstract declarator. If `got-prefix'
8260 ;; is set it's something like "a *" without anything after it. If
8261 ;; `got-parens' or `got-suffix' is set it's "a()", "a[]", "a()[]",
8262 ;; or similar, which we accept only if the context rules out
8263 ;; expressions.
8266 ;; If we had a complete symbol table here (which rules out
8267 ;; `c-found-types') we should return t due to the disambiguation rule
8268 ;; (in at least C++) that anything that can be parsed as a declaration
8269 ;; is a declaration. Now we're being more defensive and prefer to
8270 ;; highlight things like "foo (bar);" as a declaration only if we're
8271 ;; inside an arglist that contains declarations.
8272 ;; CASE 19
8275 ;; The point is now after the type decl expression.
8278 ;; Check for a cast.
8281 c-cast-parens
8283 ;; Should be the first type/identifier in a cast paren.
8287 ;; The closing paren should follow.
8292 ;; There should be a primary expression after it.
8301 ;; Check if the expression begins with a prefix keyword.
8304 ;; Expression begins with an ambiguous operator. Treat
8305 ;; it as a cast if it's a type decl or if we've
8306 ;; recognized the type somewhere else.
8309 ;; Unless it's a keyword, it's the beginning of a primary
8310 ;; expression.
8312 ;; If `c-primary-expr-regexp' matched a nonsymbol token, check
8313 ;; that it matched a whole one so that we don't e.g. confuse
8314 ;; the operator '-' with '->'. It's ok if it matches further,
8315 ;; though, since it e.g. can match the float '.5' while the
8316 ;; operator regexp only matches '.'.
8320 ;; There should either be a cast before it or something that isn't an
8321 ;; identifier or close paren.
8329 ;; It's a symbol. Accept it only if it's one of the
8330 ;; keywords that can precede an expression (without
8331 ;; surrounding parens).
8334 ;; Check that it isn't a close paren (block close is ok,
8335 ;; though).
8337 ;; Check that it isn't a nonsymbol identifier.
8340 ;; Handle the cast.
8350 ;; We're at a declaration. Highlight the type and the following
8351 ;; declarators.
8357 ;; Make sure to propagate the `c-decl-arg-start' property to
8358 ;; the next argument if it's set in this one, to cope with
8359 ;; interactive refontification.
8362 ;; Record the type's coordinates in `c-record-type-identifiers' for
8363 ;; later fontification.
8365 ;; There seems no reason to exclude a token from
8366 ;; fontification just because it's "a known type that can't
8367 ;; be a name or other expression". 2013-09-18.
8368 )
8377 maybe-expression
8378 type-start))
8381 ;; False alarm. Restore the recorded ranges.
8383 c-record-ref-identifiers save-rec-ref-ids)
8384 nil))))
8387 ;; Assuming that point is at the beginning of a token, check if it starts a
8388 ;; label and if so move over it and return non-nil (t in default situations,
8389 ;; specific symbols (see below) for interesting situations), otherwise don't
8390 ;; move and return nil. "Label" here means "most things with a colon".
8391 ;;
8392 ;; More precisely, a "label" is regarded as one of:
8393 ;; (i) a goto target like "foo:" - returns the symbol `goto-target';
8394 ;; (ii) A case label - either the entire construct "case FOO:", or just the
8395 ;; bare "case", should the colon be missing. We return t;
8396 ;; (iii) a keyword which needs a colon, like "default:" or "private:"; We
8397 ;; return t;
8398 ;; (iv) One of QT's "extended" C++ variants of
8399 ;; "private:"/"protected:"/"public:"/"more:" looking like "public slots:".
8400 ;; Returns the symbol `qt-2kwds-colon'.
8401 ;; (v) QT's construct "signals:". Returns the symbol `qt-1kwd-colon'.
8402 ;; (vi) One of the keywords matched by `c-opt-extra-label-key' (without any
8403 ;; colon). Currently (2006-03), this applies only to Objective C's
8404 ;; keywords "@private", "@protected", and "@public". Returns t.
8405 ;;
8406 ;; One of the things which will NOT be recognized as a label is a bit-field
8407 ;; element of a struct, something like "int foo:5".
8408 ;;
8409 ;; The end of the label is taken to be just after the colon, or the end of
8410 ;; the first submatch in `c-opt-extra-label-key'. The point is directly
8411 ;; after the end on return. The terminating char gets marked with
8412 ;; `c-decl-end' to improve recognition of the following declaration or
8413 ;; statement.
8414 ;;
8415 ;; If ASSUME-MARKUP is non-nil, it's assumed that the preceding
8416 ;; label, if any, has already been marked up like that.
8417 ;;
8418 ;; If PRECEDING-TOKEN-END is given, it should be the first position
8419 ;; after the preceding token, i.e. on the other side of the
8420 ;; syntactic ws from the point. Use a value less than or equal to
8421 ;; (point-min) if the point is at the first token in (the visible
8422 ;; part of) the buffer.
8423 ;;
8424 ;; The optional LIMIT limits the forward scan for the colon.
8425 ;;
8426 ;; This function records the ranges of the label symbols on
8427 ;; `c-record-ref-identifiers' if `c-record-type-identifiers' (!) is
8428 ;; non-nil.
8429 ;;
8430 ;; This function might do hidden buffer changes.
8433 label-end
8434 qt-symbol-idx
8435 macro-start ; if we're in one.
8436 label-type
8437 kwd)
8439 ;; "case" or "default" (Doesn't apply to AWK).
8442 ;; Record only the keyword itself for fontification, since in
8443 ;; case labels the following is a constant expression and not
8444 ;; a label.
8448 ;; Find the label end.
8452 ;; Stop on chars that aren't allowed in expressions,
8453 ;; and on operator chars that would be meaningless
8454 ;; there. FIXME: This doesn't cope with ?: operators.
8462 t)
8464 ;; It's an unfinished label. We consider the keyword enough
8465 ;; to recognize it as a label, so that it gets fontified.
8466 ;; Leave the point at the end of it, but don't put any
8467 ;; `c-decl-end' marker.
8469 t))))
8471 ;; @private, @protected, @public, in Objective C, or similar.
8474 ;; For a `c-opt-extra-label-key' match, we record the whole
8475 ;; thing for fontification. That's to get the leading '@' in
8476 ;; Objective-C protection labels fontified.
8483 ;; All other cases of labels.
8486 ;; A colon label must have something before the colon.
8489 ;; Check that we're not after a token that can't precede a label.
8491 ;; Trivially succeeds when there's no preceding token.
8492 ;; Succeeds when we're at a virtual semicolon.
8501 ;; Check if we're after a label, if we're after a closing
8502 ;; paren that belong to statement, and with
8503 ;; `c-label-prefix-re'. It's done in different order
8504 ;; depending on `assume-markup' since the checks have
8505 ;; different expensiveness.
8532 ;; Might be after another label, so check it recursively.
8536 ;; Essentially the same as the
8537 ;; `c-syntactic-re-search-forward' regexp below.
8543 ;; Note: the following should work instead of the
8544 ;; narrow-to-region above. Investigate why not,
8545 ;; sometime. ACM, 2006-03-31.
8546 ;; (c-syntactic-skip-backward "^-]:?;}=*/%&|,<>!@+"
8547 ;; macro-start t)
8549 ;; If the caller turned on recording for us,
8550 ;; it shouldn't apply when we check the
8551 ;; preceding label.
8552 c-record-type-identifiers)
8553 ;; A label can't start at a cpp directive. Check for
8554 ;; this, since c-forward-syntactic-ws would foul up on it.
8559 ;; Point is still at the beginning of the possible label construct.
8560 ;;
8561 ;; Check that the next nonsymbol token is ":", or that we're in one
8562 ;; of QT's "slots" declarations. Allow '(' for the sake of macro
8563 ;; arguments. FIXME: Should build this regexp from the language
8564 ;; constants.
8566 ;; public: protected: private:
8576 ;; QT double keyword like "protected slots:" or goto target.
8595 'qt-1kwd-colon
8607 ;; Check that `c-nonlabel-token-key' doesn't match anywhere.
8617 t)
8620 ;; Record the identifiers in the label for fontification, unless
8621 ;; it begins with `c-label-kwds' in which case the following
8622 ;; identifiers are part of a (constant) expression that
8623 ;; shouldn't be fontified.
8635 ;; Not a label.
8637 label-type))
8640 ;; Assuming the point is at the beginning of a token, try to move
8641 ;; forward to the end of the Objective-C directive that starts
8642 ;; there. Return t if a directive was fully recognized, otherwise
8643 ;; the point is moved as far as one could be successfully parsed and
8644 ;; nil is returned.
8645 ;;
8646 ;; This function records identifier ranges on
8647 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
8648 ;; `c-record-type-identifiers' is non-nil.
8649 ;;
8650 ;; This function might do hidden buffer changes.
8653 start-char
8655 lim
8656 ;; Turn off recognition of angle bracket arglists while parsing
8657 ;; types here since the protocol reference list might then be
8658 ;; considered part of the preceding name or superclass-name.
8669 t)
8678 ;; Handle the name of the class itself.
8680 ;; (c-forward-token-2) ; 2006/1/13 This doesn't move if the token's
8681 ;; at EOB.
8688 ;; Look for ": superclass-name" or "( category-name )".
8699 ;; Look for a protocol reference list.
8705 t))))
8711 t)
8714 nil)))
8717 ;; Go to the first non-whitespace after the colon that starts a
8718 ;; multiple inheritance introduction. Optional LIM is the farthest
8719 ;; back we should search.
8720 ;;
8721 ;; This function might do hidden buffer changes.
8729 ;; Return nil if we aren't in a method definition, otherwise the
8730 ;; position of the initial [+-].
8731 ;;
8732 ;; This function might do hidden buffer changes.
8738 ))
8740 ;; Contributed by Kevin Ryde <user42@zip.com.au>.
8742 ;; Return non-nil if point is within a gcc \"asm\" block.
8743 ;;
8744 ;; This should be called with point inside an argument list.
8745 ;;
8746 ;; Only one level of enclosing parentheses is considered, so for
8747 ;; instance nil is returned when in a function call within an asm
8748 ;; operand.
8749 ;;
8750 ;; This function might do hidden buffer changes.
8762 a function.
8764 More precisely, being at the top-level means that point is either
8765 outside any enclosing block (such as a function definition), or
8766 directly inside a class, namespace or other block that contains
8767 another declaration level.
8769 If point is not at the top-level (e.g. it is inside a method
8770 definition), then nil is returned. Otherwise, if point is at a
8771 top-level not enclosed within a class definition, t is returned.
8772 Otherwise, a 2-vector is returned where the zeroth element is the
8773 buffer position of the start of the class declaration, and the first
8774 element is the buffer position of the enclosing class's opening
8775 brace.
8777 Note that this function might do hidden buffer changes. See the
8778 comment at the start of cc-engine.el for more info."
8779 ;; Note to maintainers: this function consumes a great mass of CPU cycles.
8780 ;; Its use should thus be minimized as far as possible.
8786 ;; Return non-nil if the point is in the region after the argument
8787 ;; list of a function and its opening brace (or semicolon in case it
8788 ;; got no body). If there are K&R style argument declarations in
8789 ;; that region, the point has to be inside the first one for this
8790 ;; function to recognize it.
8791 ;;
8792 ;; If successful, the point is moved to the first token after the
8793 ;; function header (see `c-forward-decl-or-cast-1' for details) and
8794 ;; the position of the opening paren of the function arglist is
8795 ;; returned.
8796 ;;
8797 ;; The point is clobbered if not successful.
8798 ;;
8799 ;; LIM is used as bound for backward buffer searches.
8800 ;;
8801 ;; This function might do hidden buffer changes.
8814 ;; There should not be a '=' or ',' between beg and the
8815 ;; start of the declaration since that means we were in the
8816 ;; "expression part" of the declaration.
8821 ;; Check that there's an arglist paren in the
8822 ;; declaration.
8825 ;; The declarator is a paren expression, so skip past it
8826 ;; so that we don't get stuck on that instead of the
8827 ;; function arglist.
8831 ;; Don't trip up on "operator ()".
8838 ;; Return the position of the first argument declaration if point is
8839 ;; inside a K&R style argument declaration list, nil otherwise.
8840 ;; `c-recognize-knr-p' is not checked. If LIM is non-nil, it's a
8841 ;; position that bounds the backward search for the argument list. This
8842 ;; function doesn't move point.
8843 ;;
8844 ;; Point must be within a possible K&R region, e.g. just before a top-level
8845 ;; "{". It must be outside of parens and brackets. The test can return
8846 ;; false positives otherwise.
8847 ;;
8848 ;; This function might do hidden buffer changes.
8851 ;; If we're in a macro, our search range is restricted to it. Narrow to
8852 ;; the searchable range.
8856 before-lparen after-rparen
8859 ; we give up.
8860 ids ; List of identifiers in the parenthesized list.
8861 id-start after-prec-token decl-or-cast decl-res
8862 c-last-identifier-range identifier-ok)
8865 ;; Search backwards for the defun's argument list. We give up if we
8866 ;; encounter a "}" (end of a previous defun) an "=" (which can't be in
8867 ;; a knr region) or BOB.
8868 ;;
8869 ;; The criterion for a paren structure being the arg list is:
8870 ;; o - there is non-WS stuff after it but before any "{"; AND
8871 ;; o - the token after it isn't a ";" AND
8872 ;; o - it is preceded by either an identifier (the function name) or
8873 ;; a macro expansion like "DEFUN (...)"; AND
8874 ;; o - its content is a non-empty comma-separated list of identifiers
8875 ;; (an empty arg list won't have a knr region).
8876 ;;
8877 ;; The following snippet illustrates these rules:
8878 ;; int foo (bar, baz, yuk)
8879 ;; int bar [] ;
8880 ;; int (*baz) (my_type) ;
8881 ;; int (*(* yuk) (void)) (void) ;
8882 ;; {
8883 ;;
8884 ;; Additionally, for a knr list to be recognized:
8885 ;; o - The identifier of each declarator up to and including the
8886 ;; one "near" point must be contained in the arg list.
8897 ; parens/brackets.
8901 ;; We're inside a paren. Could it be our argument list....?
8907 ;; FIXME!!! What about macros between the parens? 2007/01/20
8910 ;; It can't be the arg list if next token is ; or {
8915 ;; Is the thing preceding the list an identifier (the
8916 ;; function name), or a macro expansion?
8926 ;; Have we got a non-empty list of comma-separated
8927 ;; identifiers?
8940 ids)
8948 ;; Are all the identifiers in the k&r list up to the
8949 ;; current one also in the argument list?
8957 after-prec-token
8958 nil ; Or 'arglist ???
8959 nil)))
8964 nil))
8972 ids))
8978 identifier-ok))
8979 ;; ...Yes. We've identified the function's argument list.
8984 ;; ...No. The current parens aren't the function's arg list.
8991 ;; skip forward over conditional at point, including any predicate
8992 ;; statements in parentheses. No error checking is performed.
8993 ;;
8994 ;; This function might do hidden buffer changes.
8996 ;; else if()
9001 ;; do, else, try, finally
9006 ;; for, if, while, switch, catch, synchronized, foreach
9010 ;; If looking at the token after a conditional then return the
9011 ;; position of its start, otherwise return nil.
9012 ;;
9013 ;; This function might do hidden buffer changes.
9024 ;; If the point is after an operator identifier that isn't handled
9025 ;; like an ordinary symbol (i.e. like "operator =" in C++) then the
9026 ;; position of the start of that identifier is returned. nil is
9027 ;; returned otherwise. The point may be anywhere in the syntactic
9028 ;; whitespace after the last token of the operator identifier.
9029 ;;
9030 ;; This function might do hidden buffer changes.
9042 ;; Assuming point is at a brace that opens a statement block of some
9043 ;; kind, move to the proper anchor point for that block. It might
9044 ;; need to be adjusted further by c-add-stmt-syntax, but the
9045 ;; position at return is suitable as start position for that
9046 ;; function.
9047 ;;
9048 ;; This function might do hidden buffer changes.
9055 ;; Assuming point is at a brace that opens the block of a top level
9056 ;; declaration of some kind, move to the proper anchor point for
9057 ;; that block.
9058 ;;
9059 ;; This function might do hidden buffer changes.
9064 ;; Search forward for the end of the "header" of the current
9065 ;; declaration. That's the position where the definition body
9066 ;; starts, or the first variable initializer, or the ending
9067 ;; semicolon. I.e. search forward for the closest following
9068 ;; (syntactically relevant) '{', '=' or ';' token. Point is left
9069 ;; _after_ the first found token, or at point-max if none is found.
9070 ;;
9071 ;; This function might do hidden buffer changes.
9076 ;; In C++ we need to take special care to handle operator
9077 ;; tokens and those pesky template brackets.
9082 ;; Handle operator identifiers, i.e. ignore any
9083 ;; operator token preceded by "operator".
9090 t
9092 nil)))))
9101 ;; Go to the beginning of the current declaration, or the beginning
9102 ;; of the previous one if already at the start of it. Point won't
9103 ;; be moved out of any surrounding paren. Return a cons cell of the
9104 ;; form (MOVE . KNR-POS). MOVE is like the return value from
9105 ;; `c-beginning-of-statement-1'. If point skipped over some K&R
9106 ;; style argument declarations (and they are to be recognized) then
9107 ;; KNR-POS is set to the start of the first such argument
9108 ;; declaration, otherwise KNR-POS is nil. If LIM is non-nil, it's a
9109 ;; position that bounds the backward search.
9110 ;;
9111 ;; NB: Cases where the declaration continues after the block, as in
9112 ;; "struct foo { ... } bar;", are currently recognized as two
9113 ;; declarations, e.g. "struct foo { ... }" and "bar;" in this case.
9114 ;;
9115 ;; This function might do hidden buffer changes.
9121 ;; `c-beginning-of-statement-1' stops at a block start, but we
9122 ;; want to continue if the block doesn't begin a top level
9123 ;; construct, i.e. if it isn't preceded by ';', '}', ':', bob,
9124 ;; or an open paren.
9126 ;; Go back one "statement" each time round the loop until we're just
9127 ;; after a ;, }, or :, or at BOB or the start of a macro or start of
9128 ;; an ObjC method. This will move over a multiple declaration whose
9129 ;; components are comma separated.
9131 ;; Must check with c-opt-method-key in ObjC mode.
9141 ;; Check that we don't move from the first thing in a
9142 ;; macro to its header.
9148 move tentative-move))
9153 ;; Handle K&R argdecls. Back up after the "statement" jumped
9154 ;; over by `c-beginning-of-statement-1', unless it was the
9155 ;; function body, in which case we're sitting on the opening
9156 ;; brace now. Then test if we're in a K&R argdecl region and
9157 ;; that we started at the other side of the first argdecl in
9158 ;; it.
9168 'previous
9170 knr-argdecl-start))
9173 ;; `c-beginning-of-statement-1' counts each brace block as a separate
9174 ;; statement, so the result will be 'previous if we've moved over any.
9175 ;; So change our result back to 'same if necessary.
9176 ;;
9177 ;; If they were brace list initializers we might not have moved over a
9178 ;; declaration boundary though, so change it to 'same if we've moved
9179 ;; past a '=' before '{', but not ';'. (This ought to be integrated
9180 ;; into `c-beginning-of-statement-1', so we avoid this extra pass which
9181 ;; potentially can search over a large amount of text.). Take special
9182 ;; pains not to get mislead by C++'s "operator=", and the like.
9185 c++-template-syntax-table
9191 ; no more, or get to one which isn't an "operator ="
9194 c-overloadable-operators-regexp
9195 c-opt-op-identifier-prefix
9210 ;; Assuming point is at the start of a declaration (as detected by
9211 ;; e.g. `c-beginning-of-decl-1'), go to the end of it. Unlike
9212 ;; `c-beginning-of-decl-1', this function handles the case when a
9213 ;; block is followed by identifiers in e.g. struct declarations in C
9214 ;; or C++. If a proper end was found then t is returned, otherwise
9215 ;; point is moved as far as possible within the current sexp and nil
9216 ;; is returned. This function doesn't handle macros; use
9217 ;; `c-end-of-macro' instead in those cases.
9218 ;;
9219 ;; This function might do hidden buffer changes.
9222 c++-template-syntax-table
9230 ;; Stopped at the ';' in a K&R argdecl section which is
9231 ;; detected using the same criteria as in
9232 ;; `c-beginning-of-decl-1'. Move to the following block
9233 ;; start.
9237 ;; Encountered a block in the declaration. Jump over it.
9248 ;; Check for `c-opt-block-decls-with-vars-key'
9249 ;; before the first paren.
9252 c-opt-block-decls-with-vars-key
9254 lim t t t)
9257 ;; Check that the first following paren is
9258 ;; the block.
9260 lim t t t)
9262 ;; The declaration doesn't have any of the
9263 ;; `c-opt-block-decls-with-vars' keywords in the
9264 ;; beginning, so it ends here at the end of the block.
9272 nil)))
9275 ;; Assuming the point is at an open brace, check if it starts a
9276 ;; block that contains another declaration level, i.e. that isn't a
9277 ;; statement block or a brace list, and if so return non-nil.
9278 ;;
9279 ;; If the check is successful, the return value is the start of the
9280 ;; keyword that tells what kind of construct it is, i.e. typically
9281 ;; what `c-decl-block-key' matched. Also, if GOTO-START is set then
9282 ;; the point will be at the start of the construct, before any
9283 ;; leading specifiers, otherwise it's at the returned position.
9284 ;;
9285 ;; The point is clobbered if the check is unsuccessful.
9286 ;;
9287 ;; CONTAINING-SEXP is the position of the open of the surrounding
9288 ;; paren, or nil if none.
9289 ;;
9290 ;; The optional LIMIT limits the backward search for the start of
9291 ;; the construct. It's assumed to be at a syntactically relevant
9292 ;; position.
9293 ;;
9294 ;; If any template arglists are found in the searched region before
9295 ;; the open brace, they get marked with paren syntax.
9296 ;;
9297 ;; This function might do hidden buffer changes.
9304 ;; Could be at the end of a template arglist.
9312 ;; Skip back over noise clauses.
9314 c-opt-cpp-prefix
9324 t)
9326 nil))))
9328 ;; Note: Can't get bogus hits inside template arglists below since they
9329 ;; have gotten paren syntax above.
9331 ;; If `goto-start' is set we begin by searching for the
9332 ;; first possible position of a leading specifier list.
9333 ;; The `c-decl-block-key' search continues from there since
9334 ;; we know it can't match earlier.
9337 open-brace t t)
9339 t)
9340 t)
9346 ;; Exclude cases where we matched what would ordinarily
9347 ;; be a block declaration keyword, except where it's not
9348 ;; legal because it's part of a "compound keyword" like
9349 ;; "enum class". Of course, if c-after-brace-list-key
9350 ;; is nil, we can skip the test.
9360 ;; Found a keyword that can't be a type?
9363 ;; Can be a type too, in which case it's the return type of a
9364 ;; function (under the assumption that no declaration level
9365 ;; block construct starts with a type).
9368 ;; Jumped over a type, but it could be a declaration keyword
9369 ;; followed by the declared identifier that we've jumped over
9370 ;; instead (e.g. in "class Foo {"). If it indeed is a type
9371 ;; then we should be at the declarator now, so check for a
9372 ;; valid declarator start.
9373 ;;
9374 ;; Note: This doesn't cope with the case when a declared
9375 ;; identifier is followed by e.g. '(' in a language where '('
9376 ;; also might be part of a declarator expression. Currently
9377 ;; there's no such language.
9381 ;; In Pike a list of modifiers may be followed by a brace
9382 ;; to make them apply to many identifiers. Note that the
9383 ;; match data will be empty on return in this case.
9389 ;; Use this variant to avoid yet another special regexp.
9393 t)))
9395 ;; Got a match.
9398 ;; Back up over any preceding specifiers and their clauses
9399 ;; by going forward from `first-specifier-pos', which is the
9400 ;; earliest possible position where the specifier list can
9401 ;; start.
9407 ;; Accept any plain symbol token on the ground that
9408 ;; it's a specifier masked through a macro (just
9409 ;; like `c-forward-decl-or-cast-1' skip forward over
9410 ;; such tokens).
9411 ;;
9412 ;; Could be more restrictive wrt invalid keywords,
9413 ;; but that'd only occur in invalid code so there's
9414 ;; no use spending effort on it.
9420 ;; Can't parse a declaration preamble and is still
9421 ;; before `kwd-start'. That means `first-specifier-pos'
9422 ;; was in some earlier construct. Search again.
9426 ;; Got no preamble before the block declaration keyword.
9432 kwd-start)))
9435 ;; Check whether point is directly inside a brace block which is the brace
9436 ;; block of a class, struct, or union which is called NAME, a string.
9439 )
9443 ; *c-looking-at-decl-block
9444 ; containing-sexp goto-start &optional
9445 ; limit)
9448 nil)
9455 ;; Check if the closest containing paren sexp is a declaration
9456 ;; block, returning a 2 element vector in that case. Aref 0
9457 ;; contains the bufpos at boi of the class key line, and aref 1
9458 ;; contains the bufpos of the open brace. This function is an
9459 ;; obsolete wrapper for `c-looking-at-decl-block'.
9460 ;;
9461 ;; This function might do hidden buffer changes.
9469 nil))
9474 ;; Return the buffer position of the most enclosing decl-block brace (in the
9475 ;; sense of c-looking-at-decl-block) in the PAREN-STATE structure, or nil if
9476 ;; none was found.
9485 open-brace))
9488 ;; Return the position of the L-brace if point is inside a brace list
9489 ;; initialization of an array, etc. This is an approximate function,
9490 ;; designed for speed over accuracy. It will not find every bracelist, but
9491 ;; a non-nil result is reliable. We simply search for "= {" (naturally with
9492 ;; syntactic whitespace allowed). PAREN-STATE is the normal thing that it
9493 ;; is everywhere else.
9502 b-pos)))
9505 ;; We're at a "{" which might be the opening brace of a enum which is
9506 ;; strongly typed (by a ":" followed by a type). If this is the case, leave
9507 ;; point before the colon and return t. Otherwise leave point unchanged and return nil.
9508 ;; Match data will be clobbered.
9528 nil)
9530 t)
9532 t)
9536 t)))
9539 ;; We're at a "{". Move back to the enum-like keyword that starts this
9540 ;; declaration and return t, otherwise don't move and return nil.
9542 up-sexp-pos before-identifier)
9558 t)
9570 t)
9576 ;; return the buffer position of the beginning of the brace list
9577 ;; statement if we're inside a brace list, otherwise return nil.
9578 ;; CONTAINING-SEXP is the buffer pos of the innermost containing
9579 ;; paren. PAREN-STATE is the remainder of the state of enclosing
9580 ;; braces
9581 ;;
9582 ;; N.B.: This algorithm can potentially get confused by cpp macros
9583 ;; placed in inconvenient locations. It's a trade-off we make for
9584 ;; speed.
9585 ;;
9586 ;; This function might do hidden buffer changes.
9588 ;; This will pick up brace list declarations.
9592 ;; this will pick up array/aggregate init lists, even if they are nested.
9595 ;; Pike can have class definitions anywhere, so we must
9596 ;; check for the class key here.
9598 c-decl-block-key))
9599 bufpos braceassignp lim next-containing macro-start)
9601 containing-sexp)
9612 ;; We're in an in-expression block of some kind. Do not
9613 ;; check nesting. We deliberately set the limit to the
9614 ;; containing sexp, so that c-looking-at-inexpr-block
9615 ;; doesn't check for an identifier before it.
9617 ;; see if the open brace is preceded by = or [...] in
9618 ;; this statement, but watch out for operator=
9621 ;; Checks to do only on the first sexp before the brace.
9624 ;; In Java, an initialization brace list may follow
9625 ;; directly after "new Foo[]", so check for a "new"
9626 ;; earlier.
9632 ;; Carry on looking if this is an
9633 ;; identifier (may contain "." in Java)
9634 ;; or another "[]" sexp.
9637 ;; Checks to do on all sexps before the brace, up to the
9638 ;; beginning of the statement.
9646 ;; We've seen a =, but must check earlier tokens so
9647 ;; that it isn't something that should be ignored.
9653 ;; Check for operator =
9656 nil)
9657 ;; Check for `<opchar>= in Pike.
9660 ;; Special case for Pikes
9661 ;; `[]=, since '[' is not in
9662 ;; the punctuation class.
9665 nil)
9667 ;; make sure we're not in a C++ template
9668 ;; argument assignment
9680 ))))
9681 nil)
9688 ;; We've hit the beginning of the aggregate list.
9693 ;; Brace lists can't contain a semicolon, so we're done.
9698 ;; We've a macro whose expansion starts with the '{'.
9699 ;; Heuristically, if we have a ';' in it we've not got a
9700 ;; brace list, otherwise we have.
9707 containing-sexp nil)
9710 ;; Go up one level
9712 lim nil
9713 next-containing nil)))))
9715 bufpos))
9716 ))
9719 ;; If we're looking at the start of a pike-style list, i.e., `({Â })',
9720 ;; `([Â ])', `(<Â >)', etc., a cons of a cons of its starting and ending
9721 ;; positions and its entry in c-special-brace-lists is returned, nil
9722 ;; otherwise. The ending position is nil if the list is still open.
9723 ;; LIM is the limit for forward search. The point may either be at
9724 ;; the `(' or at the following paren character. Tries to check the
9725 ;; matching closer, but assumes it's correct if no balanced paren is
9726 ;; found (i.e. the case `({ ... } ... )' is detected as _not_ being
9727 ;; a special brace list).
9728 ;;
9729 ;; This function might do hidden buffer changes.
9734 inner-beg end type)
9749 nil)))))
9759 ;; Check balancing of the inner paren
9760 ;; below.
9763 t)
9764 ;; If the inner char isn't a paren then
9765 ;; we can't check balancing, so just
9766 ;; check the char before the outer
9767 ;; closing paren.
9782 ;; Return non-nil if between two statements or declarations, assuming
9783 ;; point is not inside a literal or comment.
9784 ;;
9785 ;; Obsolete - `c-at-statement-start-p' or `c-at-expression-start-p'
9786 ;; are recommended instead.
9787 ;;
9788 ;; This function might do hidden buffer changes.
9793 ;; Return non-nil if we're looking at the beginning of a block
9794 ;; inside an expression. The value returned is actually a cons of
9795 ;; either 'inlambda, 'inexpr-statement or 'inexpr-class and the
9796 ;; position of the beginning of the construct.
9797 ;;
9798 ;; LIM limits the backward search. CONTAINING-SEXP is the start
9799 ;; position of the closest containing list. If it's nil, the
9800 ;; containing paren isn't used to decide whether we're inside an
9801 ;; expression or not. If both LIM and CONTAINING-SEXP are used, LIM
9802 ;; needs to be farther back.
9803 ;;
9804 ;; If CHECK-AT-END is non-nil then extra checks at the end of the
9805 ;; brace block might be done. It should only be used when the
9806 ;; construct can be assumed to be complete, i.e. when the original
9807 ;; starting position was further down than that.
9808 ;;
9809 ;; This function might do hidden buffer changes.
9814 ;; Look at the character after point only as a last resort
9815 ;; when we can't disambiguate.
9835 ;; If the class definition is at the start of
9836 ;; a statement, we don't consider it an
9837 ;; in-expression class.
9845 ;; Also, in Pike we treat it as an
9846 ;; in-expression class if it's used in an
9847 ;; object clone expression.
9863 nil)
9871 ;; Accept several square bracket sexps for
9872 ;; Java array initializations.
9880 block-follows
9881 containing-sexp
9895 nil
9898 res))))
9901 ;; Returns non-nil if we're looking at the end of an in-expression
9902 ;; block, otherwise the same as `c-looking-at-inexpr-block'.
9903 ;; PAREN-STATE is the paren state relevant at the current position.
9904 ;;
9905 ;; This function might do hidden buffer changes.
9907 ;; We currently only recognize a block.
9910 containing-sexp)
9919 paren-state)
9920 containing-sexp)))))
9923 ;; Is there a "virtual semicolon" at POS or point?
9924 ;; (See cc-defs.el for full details of "virtual semicolons".)
9925 ;;
9926 ;; This is true when point is at the last non syntactic WS position on the
9927 ;; line, there is a macro call last on the line, and this particular macro's
9928 ;; name is defined by the regexp `c-vs-macro-regexp' as not needing a
9929 ;; semicolon.
9937 c-macro-with-semi-re
9940 ;; Check we've got nothing after this except comments and empty lines
9941 ;; joined by escaped EOLs.
9954 nil)
9962 ;; Check for one of the listed macros being before point.
9966 t))
9974 \f
9975 ;; `c-guess-basic-syntax' and the functions that precedes it below
9976 ;; implements the main decision tree for determining the syntactic
9977 ;; analysis of the current line of code.
9979 ;; Dynamically bound to t when `c-guess-basic-syntax' is called during
9980 ;; auto newline analysis.
9984 ;; BRACEPOS is the position of a brace in a construct like "namespace
9985 ;; Bar {". Return the anchor point in this construct; this is the
9986 ;; earliest symbol on the brace's line which isn't earlier than
9987 ;; "namespace".
9988 ;;
9989 ;; Currently (2007-08-17), "like namespace" means "matches
9990 ;; c-other-block-decl-kwds". It doesn't work with "class" or "struct"
9991 ;; or anything like that.
10001 ;; A simple function to prepend a new syntax element to
10002 ;; `c-syntactic-context'. Using `setq' on it is unsafe since it
10003 ;; should always be dynamically bound but since we read it first
10004 ;; we'll fail properly anyway if this function is misused.
10006 c-syntactic-context)))
10009 ;; Like `c-add-syntax' but appends to the end of the syntax list.
10010 ;; (Normally not necessary.)
10015 syntax-extra-args
10016 stop-at-boi-only
10017 containing-sexp
10018 paren-state)
10019 ;; Add the indicated SYNTAX-SYMBOL to `c-syntactic-context', extending it as
10020 ;; needed with further syntax elements of the types `substatement',
10021 ;; `inexpr-statement', `arglist-cont-nonempty', `statement-block-intro', and
10022 ;; `defun-block-intro'.
10023 ;;
10024 ;; Do the generic processing to anchor the given syntax symbol on
10025 ;; the preceding statement: Skip over any labels and containing
10026 ;; statements on the same line, and then search backward until we
10027 ;; find a statement or block start that begins at boi without a
10028 ;; label or comment.
10029 ;;
10030 ;; Point is assumed to be at the prospective anchor point for the
10031 ;; given SYNTAX-SYMBOL. More syntax entries are added if we need to
10032 ;; skip past open parens and containing statements. Most of the added
10033 ;; syntax elements will get the same anchor point - the exception is
10034 ;; for an anchor in a construct like "namespace"[*] - this is as early
10035 ;; as possible in the construct but on the same line as the {.
10036 ;;
10037 ;; [*] i.e. with a keyword matching c-other-block-decl-kwds.
10038 ;;
10039 ;; SYNTAX-EXTRA-ARGS are a list of the extra arguments for the
10040 ;; syntax symbol. They are appended after the anchor point.
10041 ;;
10042 ;; If STOP-AT-BOI-ONLY is nil, we can stop in the middle of the line
10043 ;; if the current statement starts there.
10044 ;;
10045 ;; Note: It's not a problem if PAREN-STATE "overshoots"
10046 ;; CONTAINING-SEXP, i.e. contains info about parens further down.
10047 ;;
10048 ;; This function might do hidden buffer changes.
10051 ;; This is by far the most common case, so let's give it special
10052 ;; treatment.
10057 ;; Set when we're on a label, so that we don't stop there.
10058 ;; FIXME: To be complete we should check if we're on a label
10059 ;; now at the start.
10060 on-label)
10062 ;; Use point as the anchor point for "namespace", "extern", etc.
10066 syntax-extra-args)
10068 ;; Loop while we have to back out of containing blocks.
10073 ;; Loop while we have to back up statements.
10075 on-label
10078 ;; Skip past any comments that stands between the
10079 ;; statement start and boi.
10087 ;; Skip to the beginning of this statement or backward
10088 ;; another one.
10096 ;; If we didn't move we're at the start of a block and
10097 ;; have to continue outside it.
10106 ;; Special case to avoid deeper and deeper indentation
10107 ;; of "else if" clauses.
10108 )
10113 ;; If stop-at-boi-only is nil, we shouldn't back up
10114 ;; over previous or containing statements to try to
10115 ;; reach boi, so go back to the last position and
10116 ;; exit.
10123 ;; If we've moved into another statement then we
10124 ;; should no longer try to stop in the middle of a
10125 ;; line.
10128 ;; Record this as a substatement if we skipped up one
10129 ;; level.
10132 )))
10134 containing-sexp)
10136 ;; Now we have to go out of this block.
10139 ;; Don't stop in the middle of a special brace list opener
10140 ;; like "({".
10152 ;; Analyze the construct in front of the block we've stepped out
10153 ;; from and add the right syntactic element for it.
10156 step-type)
10159 ;; Stepped out of a parenthesis block, so we're in an
10160 ;; expression now.
10172 ;; Stepped out of an in-expression statement. This
10173 ;; syntactic element won't get an anchor pos.
10176 ;; A parenthesis normally belongs to an arglist.
10184 on-label nil))
10186 ;; Stepped out of a brace block.
10198 containing-sexp)))
10200 'defun-block-intro
10202 nil))
10206 c-other-decl-block-key-in-symbols-alist))
10213 ;; Always done if the open brace was at boi. The
10214 ;; c-beginning-of-statement-1 call above is necessary
10215 ;; anyway, to decide the type of block-intro to add.
10218 ))
10220 ;; Fill in the current point as the anchor for all the symbols
10221 ;; added above.
10230 )))
10233 containing-decl-open
10234 containing-decl-start
10235 containing-decl-kwd
10236 paren-state)
10237 ;; The inclass and class-close syntactic symbols are added in
10238 ;; several places and some work is needed to fix everything.
10239 ;; Therefore it's collected here.
10240 ;;
10241 ;; This function might do hidden buffer changes.
10246 containing-decl-open)
10248 ;; Ought to use `c-add-stmt-syntax' instead of backing up to boi
10249 ;; here, but we have to do like this for compatibility.
10259 char-after-ip
10260 beg-of-same-or-containing-stmt
10261 containing-sexp
10262 paren-state)
10263 ;; This function contains the decision tree reached through both
10264 ;; cases 18 and 10. It's a continued statement or top level
10265 ;; construct of some kind.
10266 ;;
10267 ;; This function might do hidden buffer changes.
10274 ;; (CASE A removed.)
10275 ;; CASE B: open braces for class or brace-lists
10282 ;; CASE B.1: class-open
10289 ;; CASE B.2: brace-list-open
10294 indent-point t t t)))
10295 ;; The most semantically accurate symbol here is
10296 ;; brace-list-open, but we normally report it simply as a
10297 ;; statement-cont. The reason is that one normally adjusts
10298 ;; brace-list-open for brace lists as top-level constructs,
10299 ;; and brace lists inside statements is a completely different
10300 ;; context. C.f. case 5A.3.
10303 ;; Turn off the dwim above when we're
10304 ;; analyzing the nature of the brace
10305 ;; for the auto newline feature.
10306 'brace-list-open
10308 nil nil
10309 containing-sexp paren-state))
10311 ;; CASE B.3: The body of a function declared inside a normal
10312 ;; block. Can occur e.g. in Pike and when using gcc
10313 ;; extensions, but watch out for macros followed by blocks.
10314 ;; C.f. cases E, 16F and 17G.
10320 ;; Turn off recognition of constructs that lacks a
10321 ;; type in this case, since that's more likely to be
10322 ;; a macro followed by a block.
10325 containing-sexp paren-state))
10327 ;; CASE B.4: Continued statement with block open. The most
10328 ;; accurate analysis is perhaps `statement-cont' together with
10329 ;; `block-open' but we play DWIM and use `substatement-open'
10330 ;; instead. The rationale is that this typically is a macro
10331 ;; followed by a block which makes it very similar to a
10332 ;; statement with a substatement block.
10335 containing-sexp paren-state))
10336 ))
10338 ;; CASE C: iostream insertion or extraction operator
10342 ;; If there is no preceding streamop in the statement
10343 ;; then indent this line as a normal statement-cont.
10347 t))))
10349 ;; CASE E: In the "K&R region" of a function declared inside a
10350 ;; normal block. C.f. case B.3.
10352 ;; Check that the next token is a '{'. This works as
10353 ;; long as no language that allows nested function
10354 ;; definitions allows stuff like member init lists, K&R
10355 ;; declarations or throws clauses there.
10356 ;;
10357 ;; Note that we do a forward search for something ahead
10358 ;; of the indentation line here. That's not good since
10359 ;; the user might not have typed it yet. Unfortunately
10360 ;; it's exceedingly tricky to recognize a function
10361 ;; prototype in a code block without resorting to this.
10369 ;; Turn off recognition of constructs that lacks a
10370 ;; type in this case, since that's more likely to be
10371 ;; a macro followed by a block.
10374 containing-sexp paren-state))
10376 ;;CASE F: continued statement and the only preceding items are
10377 ;;annotations.
10385 t)
10392 ;; CASE G: a template list continuation?
10393 ;; Mostly a duplication of case 5D.3 to fix templates-19:
10411 ;; In a nested template arglist.
10417 ;; FIXME: Should use c-add-stmt-syntax, but it's not yet
10418 ;; template aware.
10421 ;; CASE D: continued statement.
10425 containing-sexp paren-state))
10426 )))
10428 ;; The next autoload was added by RMS on 2005/8/9 - don't know why (ACM,
10429 ;; 2005/11/29).
10430 ;;;###autoload
10432 "Return the syntactic context of the current line."
10438 ;; A whole ugly bunch of various temporary variables. Have
10439 ;; to declare them here since it's not possible to declare
10440 ;; a variable with only the scope of a cond test and the
10441 ;; following result clauses, and most of this function is a
10442 ;; single gigantic cond. :P
10443 literal char-before-ip before-ws-ip char-after-ip macro-start
10444 in-macro-expr c-syntactic-context placeholder c-in-literal-cache
10445 step-type tmpsymbol keyword injava-inher special-brace-list tmp-pos
10446 containing-<
10447 ;; The following record some positions for the containing
10448 ;; declaration block if we're directly within one:
10449 ;; `containing-decl-open' is the position of the open
10450 ;; brace. `containing-decl-start' is the start of the
10451 ;; declaration. `containing-decl-kwd' is the keyword
10452 ;; symbol of the keyword that tells what kind of block it
10453 ;; is.
10454 containing-decl-open
10455 containing-decl-start
10456 containing-decl-kwd
10457 ;; The open paren of the closest surrounding sexp or nil if
10458 ;; there is none.
10459 containing-sexp
10460 ;; The position after the closest preceding brace sexp
10461 ;; (nested sexps are ignored), or the position after
10462 ;; `containing-sexp' if there is none, or (point-min) if
10463 ;; `containing-sexp' is nil.
10464 lim
10465 ;; The paren state outside `containing-sexp', or at
10466 ;; `indent-point' if `containing-sexp' is nil.
10468 ;; There's always at most one syntactic element which got
10469 ;; an anchor pos. It's stored in syntactic-relpos.
10470 syntactic-relpos
10473 ;; Check if we're directly inside an enclosing declaration
10474 ;; level block.
10483 containing-sexp)
10484 t)))
10487 containing-sexp nil)
10492 ;; Init some position variables.
10505 ;; Ignore balanced paren. The next entry
10506 ;; can't be another one.
10509 ;; If there is no surrounding open paren then
10510 ;; put the last balanced pair back on paren-state.
10512 containing-sexp nil)))
10516 ;; If we're in a parenthesis list then ',' delimits the
10517 ;; "statements" rather than being an operator (with the
10518 ;; exception of the "for" clause). This difference is
10519 ;; typically only noticeable when statements are used in macro
10520 ;; arglists.
10524 ;; cache char before and after indent point, and move point to
10525 ;; the most likely position to perform the majority of tests
10534 ;; are we in a literal?
10537 ;; now figure out syntactic qualities of the current line
10540 ;; CASE 1: in a string.
10544 ;; CASE 2: in a C or C++ style comment.
10546 ;; This is a kludge for XEmacs where we use
10547 ;; `buffer-syntactic-context', which doesn't correctly
10548 ;; recognize "\*/" to end a block comment.
10549 ;; `parse-partial-sexp' which is used by
10550 ;; `c-literal-limits' will however do that in most
10551 ;; versions, which results in that we get nil from
10552 ;; `c-literal-limits' even when `c-in-literal' claims
10553 ;; we're inside a comment.
10557 ;; CASE 3: in a cpp preprocessor macro continuation.
10567 ;; If at the beginning of the body of a #define
10568 ;; directive then analyze as cpp-define-intro
10569 ;; only. Go on with the syntactic analysis
10570 ;; otherwise. in-macro-expr is set if we're in a
10571 ;; cpp expression, i.e. before the #define body
10572 ;; or anywhere in a non-#define directive.
10579 nil)))))
10583 ;; CASE 11: an else clause?
10587 containing-sexp paren-state))
10589 ;; CASE 12: while closure of a do/while construct?
10597 containing-sexp paren-state))
10599 ;; CASE 13: A catch or finally clause? This case is simpler
10600 ;; than if-else and do-while, because a block is required
10601 ;; after every try, catch and finally.
10609 t)
10613 t)
10616 t))
10621 containing-sexp paren-state))
10623 ;; CASE 18: A substatement we can recognize by keyword.
10633 ;; Ought to cache the result from the
10634 ;; c-beginning-of-statement-1 calls here.
10644 ;; Step up to the containing statement if we
10645 ;; stayed in the same one.
10653 ;; There was no containing statement after all.
10655 placeholder))
10657 ;; Require a parenthesis after these keywords.
10658 ;; Necessary to catch e.g. synchronized in Java,
10659 ;; which can be used both as statement and
10660 ;; modifier.
10666 ;; CASE 18A: Simple substatement.
10672 containing-sexp paren-state))
10678 containing-sexp paren-state))
10681 containing-sexp paren-state))))
10683 ;; CASE 18B: Some other substatement. This is shared
10684 ;; with case 10.
10686 char-after-ip
10687 placeholder
10688 lim
10689 paren-state)))
10691 ;; CASE 14: A case or default label
10696 containing-sexp
10709 containing-sexp))
10712 ;; Got a bogus label at the top level. In lack of better
10713 ;; alternatives, anchor it on (point-min).
10716 ;; CASE 15: any other label
10724 containing-decl-open
10725 containing-decl-start
10726 containing-decl-kwd
10727 paren-state))
10728 ;; Append access-label with the same anchor point as
10729 ;; inclass gets.
10735 containing-sexp))
10740 ;; If the surrounding statement is a switch then
10741 ;; let's analyze all labels as switch labels, so
10742 ;; that they get lined up consistently.
10743 'case-label
10749 ;; A label on the top level. Treat it as a class
10750 ;; context. (point-min) is the closest we get to the
10751 ;; class open brace.
10754 ;; CASE 4: In-expression statement. C.f. cases 7B, 16A and
10755 ;; 17E.
10758 containing-sexp
10759 ;; Have to turn on the heuristics after
10760 ;; the point even though it doesn't work
10761 ;; very well. C.f. test case class-16.pike.
10762 t))
10767 ;; It's a statement block or an anonymous class.
10769 ;; It's a Pike lambda. Check whether we are between the
10770 ;; lambda keyword and the argument list or at the defun
10771 ;; opener.
10773 'inline-open
10779 paren-state)
10783 ;; CASE 5: Line is inside a declaration level block or at top level.
10787 ;; CASE 5A: we are looking at a defun, brace list, class,
10788 ;; or inline-inclass method opening brace
10795 ;; CASE 5A.1: Non-class declaration block open.
10810 ;; Special case for extern-lang-open.
10811 'extern-lang-open
10813 nil t containing-sexp paren-state))
10815 ;; CASE 5A.2: we are looking at a class opening brace
10824 ;; CASE 5A.3: brace list open
10852 ))))
10856 ;; We're in Java and have found that the open brace
10857 ;; belongs to a "new Foo[]" initialization list,
10858 ;; which means the brace list is part of an
10859 ;; expression and not a top level definition. We
10860 ;; therefore treat it as any topmost continuation
10861 ;; even though the semantically correct symbol still
10862 ;; is brace-list-open, on the same grounds as in
10863 ;; case B.2.
10869 ;; CASE 5A.4: inline defun open
10875 containing-decl-open
10876 containing-decl-start
10877 containing-decl-kwd
10878 paren-state))
10880 ;; CASE 5A.5: ordinary defun open
10891 ;; Bogus to use bol here, but it's the legacy. (Resolved,
10892 ;; 2007-11-09)
10893 ))))
10895 ;; CASE 5R: Member init list. (Used to be part of CASE 5B.1)
10896 ;; Note there is no limit on the backward search here, since member
10897 ;; init lists can, in practice, be very large.
10904 ;; There is no preceding member init clause.
10905 ;; Indent relative to the beginning of indentation
10906 ;; for the topmost-intro line that contains the
10907 ;; prototype's open paren.
10910 ;; Indent relative to the first member init clause.
10915 ;; CASE 5B: After a function header but before the body (or
10916 ;; the ending semicolon if there's no body).
10923 ;; CASE 5B.1: Member init list.
10925 ;; There is no preceding member init clause.
10926 ;; Indent relative to the beginning of indentation
10927 ;; for the topmost-intro line that contains the
10928 ;; prototype's open paren.
10932 ;; CASE 5B.2: K&R arg decl intro
10939 containing-decl-open
10940 containing-decl-start
10941 containing-decl-kwd
10942 paren-state)))
10944 ;; CASE 5B.4: Nether region after a C++ or Java func
10945 ;; decl, which could include a `throws' declaration.
10949 )))
10951 ;; CASE 5C: inheritance line. could be first inheritance
10952 ;; line, or continuation of a multiple inheritance
10960 ;; watch out for scope operator
10965 )))
10974 ;; for Java
10979 cont done)
10984 done t))
10988 )
10990 injava-inher)
10993 ))
10996 ;; CASE 5C.1: non-hanging colon on an inher intro
11000 ;; don't add inclass symbol since relative point already
11001 ;; contains any class offset
11002 )
11004 ;; CASE 5C.2: hanging colon on an inher intro
11010 containing-decl-open
11011 containing-decl-start
11012 containing-decl-kwd
11013 paren-state)))
11015 ;; CASE 5C.3: in a Java implements/extends
11029 )))
11031 ;; CASE 5C.4: a continued inheritance line
11035 ;; don't add inclass symbol since relative point already
11036 ;; contains any class offset
11037 )))
11039 ;; CASE 5P: AWK pattern or function or continuation
11040 ;; thereof.
11046 'topmost-intro-cont
11048 nil nil
11049 containing-sexp paren-state))
11051 ;; CASE 5D: this could be a top-level initialization, a
11052 ;; member init list continuation, or a template argument
11053 ;; list continuation.
11055 ;; Note: We use the fact that lim is always after any
11056 ;; preceding brace sexp.
11066 t))
11071 t)
11077 nil)
11078 t))
11080 ;; NB: No c-after-special-operator-id stuff in this
11081 ;; clause - we assume only C++ needs it.
11086 ;; CASE 5D.3: perhaps a template list continuation?
11101 ;; In a nested template arglist.
11107 ;; FIXME: Should use c-add-stmt-syntax, but it's not yet
11108 ;; template aware.
11111 ;; CASE 5D.4: perhaps a multiple inheritance line?
11123 t)
11128 ;; CASE 5D.5: Continuation of the "expression part" of a
11129 ;; top level construct. Or, perhaps, an unrecognized construct.
11141 ;; A preceding comma at the top level means that a
11142 ;; new variable declaration starts here. Use
11143 ;; topmost-intro-cont for it, for consistency with
11144 ;; the first variable declaration. C.f. case 5N.
11147 nil nil containing-sexp paren-state))
11148 ))
11150 ;; CASE 5F: Close of a non-class declaration level block.
11154 ;; This is inconsistent: Should use `containing-decl-open'
11155 ;; here if it's at boi, like in case 5J.
11159 ;; Special case for compatibility with the
11160 ;; extern-lang syntactic symbols.
11161 'extern-lang-close
11164 nil t
11166 paren-state))
11168 ;; CASE 5G: we are looking at the brace which closes the
11169 ;; enclosing nested class decl
11174 containing-decl-open
11175 containing-decl-start
11176 containing-decl-kwd
11177 paren-state))
11179 ;; CASE 5H: we could be looking at subsequent knr-argdecls
11186 ;; Do an extra check to avoid tripping up on
11187 ;; statements that occur in invalid contexts
11188 ;; (e.g. in macro bodies where we don't really
11189 ;; know the context of what we're looking at).
11196 ;; CASE 5I: ObjC method definition.
11201 ;; Handle the case when it's the first (non-comment)
11202 ;; thing in the buffer. Can't look for a 'same return
11203 ;; value from cbos1 since ObjC directives currently
11204 ;; aren't recognized fully, so that we get 'same
11205 ;; instead of 'previous if it moved over a preceding
11206 ;; directive.
11210 ;; CASE 5N: At a variable declaration that follows a class
11211 ;; definition or some other block declaration that doesn't
11212 ;; end at the closing '}'. C.f. case 5D.5.
11221 ;; Speed up the backward search a bit.
11226 ;; The '}' is unbalanced.
11227 nil
11232 containing-sexp paren-state))
11234 ;; NOTE: The point is at the end of the previous token here.
11236 ;; CASE 5J: we are at the topmost level, make
11237 ;; sure we skip back past any access specifiers
11239 ;; A macro continuation line is never at top level.
11261 nil)))))
11262 ;; For historic reasons we anchor at bol of the last
11263 ;; line of the previous declaration. That's clearly
11264 ;; highly bogus and useless, and it makes our lives hard
11265 ;; to remain compatible. :P
11276 ;; Special case for compatibility with the
11277 ;; extern-lang syntactic symbols.
11278 'inextern-lang
11281 nil t
11283 paren-state))
11285 containing-decl-open
11286 containing-decl-start
11287 containing-decl-kwd
11288 paren-state)))
11290 macro-start
11295 ;; CASE 5K: we are at an ObjC method definition
11296 ;; continuation line.
11305 ;; CASE 5L: we are at the first argument of a template
11306 ;; arglist that begins on the previous line.
11314 ;; CASE 5Q: we are at a statement within a macro.
11319 ;;CASE 5N: We are at a topmost continuation line and the only
11320 ;;preceding items are annotations.
11327 t)
11333 ;; CASE 5M: we are at a topmost continuation line
11344 ))
11346 ;; (CASE 6 has been removed.)
11348 ;; CASE 7: line is an expression, not a statement. Most
11349 ;; likely we are either in a function prototype or a function
11350 ;; call argument list
11358 ;; CASE 7A: we are looking at the arglist closing paren.
11359 ;; C.f. case 7F.
11371 paren-state))
11373 ;; CASE 7B: Looking at the opening brace of an
11374 ;; in-expression block or brace list. C.f. cases 4, 16A
11375 ;; and 17E.
11379 paren-state))
11383 placeholder
11386 paren-state)
11387 containing-sexp)))
11388 ;; placeholder is nil if it's a block directly in
11389 ;; a function arglist. That makes us skip out of
11390 ;; this case.
11391 )))
11396 paren-state)
11400 ;; CASE 7C: we are looking at the first argument in an empty
11401 ;; argument list. Use arglist-close if we're actually
11402 ;; looking at a close paren or bracket.
11414 paren-state))
11416 ;; CASE 7D: we are inside a conditional test clause. treat
11417 ;; these things as statements
11427 ))
11429 ;; CASE 7E: maybe a continued ObjC method call. This is the
11430 ;; case when we are inside a [] bracketed exp, and what
11431 ;; precede the opening bracket is not an identifier.
11439 )))
11441 ;; CASE 7F: we are looking at an arglist continuation line,
11442 ;; but the preceding argument is on the same line as the
11443 ;; opening paren. This case includes multi-line
11444 ;; mathematical paren groupings, but we could be on a
11445 ;; for-list continuation line. C.f. case 7A.
11462 paren-state))
11464 ;; CASE 7G: we are looking at just a normal arglist
11465 ;; continuation line
11468 ))
11470 ;; CASE 8: func-local multi-inheritance line
11480 ;; CASE 8A: non-hanging colon on an inher intro
11485 ;; CASE 8B: hanging colon on an inher intro
11489 ;; CASE 8C: a continued inheritance line
11493 )))
11495 ;; CASE 9: we are inside a brace-list
11505 ;; CASE 9A: In the middle of a special brace list opener.
11528 ;; CASE 9B: brace-list-close brace
11530 ;; Check special brace list closer.
11537 ;; We were between the special close char and the `)'.
11540 ;; We were before the special close char.
11544 ;; Normal brace list check.
11555 ;; Prepare for the rest of the cases below by going to the
11556 ;; token following the opening brace
11569 ;; CASE 9C: we're looking at the first line in a brace-list
11580 ;; CASE 9D: this is just a later brace-list-entry or
11581 ;; brace-entry-open
11590 ))
11591 ))))
11593 ;; CASE 10: A continued statement or top level construct.
11603 ;; This is shared with case 18.
11605 char-after-ip
11606 placeholder
11607 containing-sexp
11608 paren-state))
11610 ;; CASE 16: block close brace, possibly closing the defun or
11611 ;; the class
11613 ;; From here on we have the next containing sexp in lim.
11618 ;; CASE 16E: Closing a statement block? This catches
11619 ;; cases where it's preceded by a statement keyword,
11620 ;; which works even when used in an "invalid" context,
11621 ;; e.g. a macro argument.
11626 ;; CASE 16A: closing a lambda defun or an in-expression
11627 ;; block? C.f. cases 4, 7B and 17E.
11630 nil))
11632 'inline-close
11642 paren-state)
11646 ;; CASE 16B: does this close an inline or a function in
11647 ;; a non-class declaration level block?
11654 nil))
11664 ;; CASE 16F: Can be a defun-close of a function declared
11665 ;; in a statement block, e.g. in Pike or when using gcc
11666 ;; extensions, but watch out for macros followed by
11667 ;; blocks. Let it through to be handled below.
11668 ;; C.f. cases B.3 and 17G.
11674 ;; Turn off recognition of constructs that
11675 ;; lacks a type in this case, since that's more
11676 ;; likely to be a macro followed by a block.
11683 ;; CASE 16C: If there is an enclosing brace then this is
11684 ;; a block close since defun closes inside declaration
11685 ;; level blocks have been handled above.
11687 ;; If the block is preceded by a case/switch label on
11688 ;; the same line, we anchor at the first preceding label
11689 ;; at boi. The default handling in c-add-stmt-syntax
11690 ;; really fixes it better, but we do like this to keep
11691 ;; the indentation compatible with version 5.28 and
11692 ;; earlier. C.f. case 17H.
11699 ;; c-backward-to-block-anchor not necessary here; those
11700 ;; situations are handled in case 16E above.
11703 ;; CASE 16D: Only top level defun close left.
11709 paren-state))
11710 ))
11712 ;; CASE 19: line is an expression, not a statement, and is directly
11713 ;; contained by a template delimiter. Most likely, we are in a
11714 ;; template arglist within a statement. This case is based on CASE
11715 ;; 7. At some point in the future, we may wish to create more
11716 ;; syntactic symbols such as `template-intro',
11717 ;; `template-cont-nonempty', etc., and distinguish between them as we
11718 ;; do for `arglist-intro' etc. (2009-12-07).
11724 ; '<') before indent-point.
11732 paren-state))
11734 ;; CASE 17: Statement or defun catchall.
11737 ;; Back up statements until we find one that starts at boi.
11740 containing-sexp)))
11744 nil)
11749 ;; CASE 17B: continued statement
11753 containing-sexp paren-state))
11755 ;; CASE 17A: After a case/default label?
11763 'statement-case-open
11765 nil t containing-sexp paren-state))
11767 ;; CASE 17D: any old statement
11774 containing-sexp paren-state)
11778 ;; CASE 17I: Inside a substatement block.
11780 ;; The following tests are all based on containing-sexp.
11782 ;; From here on we have the next containing sexp in lim.
11787 lim paren-state)
11791 ;; CASE 17E: first statement in an in-expression block.
11792 ;; C.f. cases 4, 7B and 16A.
11795 nil))
11797 'defun-block-intro
11806 paren-state)
11812 ;; CASE 17F: first statement in an inline, or first
11813 ;; statement in a top-level defun. we can tell this is it
11814 ;; if there are no enclosing braces that haven't been
11815 ;; narrowed out by a class (i.e. don't use bod here).
11818 paren-state)))
11824 nil))))
11829 ;; CASE 17G: First statement in a function declared inside
11830 ;; a normal block. This can occur in Pike and with
11831 ;; e.g. the gcc extensions, but watch out for macros
11832 ;; followed by blocks. C.f. cases B.3 and 16F.
11838 ;; Turn off recognition of constructs that lacks
11839 ;; a type in this case, since that's more likely
11840 ;; to be a macro followed by a block.
11846 lim paren-state))
11848 ;; CASE 17H: First statement in a block.
11850 ;; If the block is preceded by a case/switch label on the
11851 ;; same line, we anchor at the first preceding label at
11852 ;; boi. The default handling in c-add-stmt-syntax is
11853 ;; really fixes it better, but we do like this to keep the
11854 ;; indentation compatible with version 5.28 and earlier.
11855 ;; C.f. case 16C.
11862 ;; c-backward-to-block-anchor not necessary here; those
11863 ;; situations are handled in case 17I above.
11865 lim paren-state))
11868 ))
11869 )
11871 ;; now we need to look at any modifiers
11875 ;; are we looking at a comment only line?
11880 ;; we might want to give additional offset to friends (in C++).
11885 ;; Set syntactic-relpos.
11891 nil)
11892 t))
11895 ;; Start of or a continuation of a preprocessor directive?
11910 ;; If inside a cpp expression, i.e. anywhere in a
11911 ;; cpp directive except a #define body, we only let
11912 ;; through the syntactic analysis that is internal
11913 ;; in the expression. That means the arglist
11914 ;; elements, if they are anchored inside the cpp
11915 ;; expression.
11924 ;; Inside a #define body and the syntactic analysis is
11925 ;; anchored on the start of the #define. In this case
11926 ;; we add cpp-define-intro to get the extra
11927 ;; indentation of the #define body.
11930 ;; return the syntax
11931 c-syntactic-context)))
11933 \f
11934 ;; Indentation calculation.
11937 ;; offset can be a number, a function, a variable, a list, or one of
11938 ;; the symbols + or -
11939 ;;
11940 ;; This function might do hidden buffer changes.
11959 langelem symbol))
11965 offset symbol)
11966 nil)
11980 Error evaluating offset %S for %s: \
11981 Cannot combine absolute offset %S with relative %S in `%s' method"
11987 Error evaluating offset %S for %s: \
11988 Cannot combine relative offset %S with absolute %S in `%s' method"
11993 res))
12011 Error evaluating offset %S for %s: \
12012 Cannot combine absolute offsets %S and %S in `add' method"
12016 res))
12025 res))))
12032 nil))))
12036 res
12038 offset symbol res)
12039 nil)))
12042 ;; Get offset from LANGELEM which is a list beginning with the
12043 ;; syntactic symbol and followed by any analysis data it provides.
12044 ;; That data may be zero or more elements, but if at least one is
12045 ;; given then the first is the anchor position (or nil). The symbol
12046 ;; is matched against `c-offsets-alist' and the offset calculated
12047 ;; from that is returned.
12048 ;;
12049 ;; This function might do hidden buffer changes.
12059 offset
12063 ))
12066 ;; This is a compatibility wrapper for `c-calc-offset' in case
12067 ;; someone is calling it directly. It takes an old style syntactic
12068 ;; element on the form (SYMBOL . ANCHOR-POS) and converts it to the
12069 ;; new list form.
12070 ;;
12071 ;; This function might do hidden buffer changes.
12078 ;; Calculate the syntactic indentation from a syntactic description
12079 ;; as returned by `c-guess-syntax'.
12080 ;;
12081 ;; Note that topmost-intro always has an anchor position at bol, for
12082 ;; historical reasons. It's often used together with other symbols
12083 ;; that has more sane positions. Since we always use the first
12084 ;; found anchor position, we rely on that these other symbols always
12085 ;; precede topmost-intro in the LANGELEMS list.
12086 ;;
12087 ;; This function might do hidden buffer changes.
12095 ;; Got an absolute column that overrides any indentation
12096 ;; we've collected so far, but not the relative
12097 ;; indentation we might get for the nested structures
12098 ;; further down the langelems list.
12102 ;; Got a relative change of the current calculated
12103 ;; indentation.
12106 ;; Use the anchor position from the first syntactic
12107 ;; element with one.
12117 indent)))
12119 \f
12122 ;; Local Variables:
12123 ;; indent-tabs-mode: t
12124 ;; tab-width: 8
12125 ;; End:
12126 ;;; cc-engine.el ends here