| blob | a388b4276f938d0bb409f6ec22c2ca064908d314 |
1 ;;; cc-engine.el --- core syntax guessing engine for CC mode -*- coding: utf-8 -*-
3 ;; Copyright (C) 1985, 1987, 1992-2014 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, and
87 ;; to "hide" obtrusive characters in preprocessor lines.
88 ;;
89 ;; This property is used on single characters and is therefore
90 ;; always treated as front and rear nonsticky (or start and end open
91 ;; in XEmacs vocabulary). It's therefore installed on
92 ;; `text-property-default-nonsticky' if that variable exists (Emacs
93 ;; >= 21).
94 ;;
95 ;; 'c-is-sws and 'c-in-sws
96 ;; Used by `c-forward-syntactic-ws' and `c-backward-syntactic-ws' to
97 ;; speed them up. See the comment blurb before `c-put-is-sws'
98 ;; below for further details.
99 ;;
100 ;; 'c-type
101 ;; This property is used on single characters to mark positions with
102 ;; special syntactic relevance of various sorts. Its primary use is
103 ;; to avoid glitches when multiline constructs are refontified
104 ;; interactively (on font lock decoration level 3). It's cleared in
105 ;; a region before it's fontified and is then put on relevant chars
106 ;; in that region as they are encountered during the fontification.
107 ;; The value specifies the kind of position:
108 ;;
109 ;; 'c-decl-arg-start
110 ;; Put on the last char of the token preceding each declaration
111 ;; inside a declaration style arglist (typically in a function
112 ;; prototype).
113 ;;
114 ;; 'c-decl-end
115 ;; Put on the last char of the token preceding a declaration.
116 ;; This is used in cases where declaration boundaries can't be
117 ;; recognized simply by looking for a token like ";" or "}".
118 ;; `c-type-decl-end-used' must be set if this is used (see also
119 ;; `c-find-decl-spots').
120 ;;
121 ;; 'c-<>-arg-sep
122 ;; Put on the commas that separate arguments in angle bracket
123 ;; arglists like C++ template arglists.
124 ;;
125 ;; 'c-decl-id-start and 'c-decl-type-start
126 ;; Put on the last char of the token preceding each declarator
127 ;; in the declarator list of a declaration. They are also used
128 ;; between the identifiers cases like enum declarations.
129 ;; 'c-decl-type-start is used when the declarators are types,
130 ;; 'c-decl-id-start otherwise.
131 ;;
132 ;; 'c-awk-NL-prop
133 ;; Used in AWK mode to mark the various kinds of newlines. See
134 ;; cc-awk.el.
136 ;;; Code:
143 load-path)))
152 \f
153 ;; Make declarations for all the `c-lang-defvar' variables in cc-langs.
165 \f
166 ;;; Internal state variables.
168 ;; Internal state of hungry delete key feature
172 ;; The electric flag (toggled by `c-toggle-electric-state').
173 ;; If t, electric actions (like automatic reindentation, and (if
174 ;; c-auto-newline is also set) auto newlining) will happen when an electric
175 ;; key like `{' is pressed (or an electric keyword like `else').
179 ;; Internal state of auto newline feature.
183 ;; Included in the mode line to indicate the active submodes.
184 ;; (defvar c-submode-indicators nil)
185 ;; (make-variable-buffer-local 'c-submode-indicators)
188 ;; Calculate the new state of PREVSTATE, t or nil, based on arg. If
189 ;; arg is nil or zero, toggle the state. If arg is negative, turn
190 ;; the state off, and if arg is positive, turn the state on
196 \f
197 ;; Basic handling of preprocessor directives.
199 ;; This is a dynamically bound cache used together with
200 ;; `c-query-macro-start' and `c-query-and-set-macro-start'. It only
201 ;; works as long as point doesn't cross a macro boundary.
210 c-macro-start))
218 c-macro-start))
220 ;; One element macro cache to cope with continual movement within very large
221 ;; CPP macros.
224 ;; Nil or cons of the bounds of the most recent CPP form probed by
225 ;; `c-beginning-of-macro', `c-end-of-macro' or `c-syntactic-end-of-macro'.
226 ;; The cdr will be nil if we know only the start of the CPP form.
229 ;; The starting position from where we determined `c-macro-cache'.
232 ;; non-nil iff `c-macro-cache' has both elements set AND the cdr is at a
233 ;; syntactic end of macro, not merely an apparent one.
236 ;; Called from a before-change function. If the change region is before or
237 ;; in the macro characterized by `c-macro-cache' etc., nullify it
238 ;; appropriately. BEG and END are the standard before-change-functions
239 ;; parameters. END isn't used.
244 c-macro-cache-start-pos nil
245 c-macro-cache-syntactic nil))
250 c-macro-cache-syntactic nil))))
253 ;; Check that the ostensible CPP construct at point is a real one. In
254 ;; particular, if point is on the first line of a narrowed buffer, make sure
255 ;; that the "#" isn't, say, the second character of a "##" operator. Return
256 ;; t when the macro is real, nil otherwise.
267 t)
271 "Go to the beginning of a preprocessor directive.
272 Leave point at the beginning of the directive and return t if in one,
273 otherwise return nil and leave point unchanged.
275 Note that this function might do hidden buffer changes. See the
276 comment at the start of cc-engine.el for more info."
288 t))
290 c-macro-cache-start-pos nil
291 c-macro-cache-syntactic nil)
304 c-macro-cache-start-pos here)
305 t)
307 nil))))))
310 "Go to the end of a preprocessor directive.
311 More accurately, move the point to the end of the closest following
312 line that doesn't end with a line continuation backslash - no check is
313 done that the point is inside a cpp directive to begin with.
315 Note that this function might do hidden buffer changes. See the
316 comment at the start of cc-engine.el for more info."
325 c-macro-cache-start-pos nil
326 c-macro-cache-syntactic nil))
332 t)))
337 ;; Go to the end of a CPP directive, or a "safe" pos just before.
338 ;;
339 ;; This is normally the end of the next non-escaped line. A "safe"
340 ;; position is one not within a string or comment. (The EOL on a line
341 ;; comment is NOT "safe").
342 ;;
343 ;; This function must only be called from the beginning of a CPP construct.
344 ;;
345 ;; Note that this function might do hidden buffer changes. See the comment
346 ;; at the start of cc-engine.el for more info.
349 s)
361 ;; Assuming point is at the "#" that introduces a preprocessor
362 ;; directive, it's moved forward to the end of the identifier which is
363 ;; "#define"d (or whatever c-opt-cpp-macro-define specifies). Non-nil
364 ;; is returned in this case, in all other cases nil is returned and
365 ;; point isn't moved.
366 ;;
367 ;; This function might do hidden buffer changes.
373 ;; Assuming point is at the "#" that introduces a preprocessor
374 ;; directive, it's moved forward to the start of the definition body
375 ;; if it's a "#define" (or whatever c-opt-cpp-macro-define
376 ;; specifies). Non-nil is returned in this case, in all other cases
377 ;; nil is returned and point isn't moved.
378 ;;
379 ;; This function might do hidden buffer changes.
385 \f
386 ;;; Basic utility functions.
389 ;; Return the given region as a string where all syntactic
390 ;; whitespace is removed or, where necessary, replaced with a single
391 ;; space. If PAREN-LEVEL is given then all parens in the region are
392 ;; collapsed to "()", "[]" etc.
393 ;;
394 ;; This function might do hidden buffer changes.
438 ;; Shift the indentation of the current line with the specified
439 ;; amount (positive inwards). The buffer is modified only if
440 ;; SHIFT-AMT isn't equal to zero.
443 tmp-char-inserted)
445 nil
446 ;; If we're on an empty line inside a macro, we take the point
447 ;; to be at the current indentation and shift it to the
448 ;; appropriate column. This way we don't treat the extra
449 ;; whitespace out to the line continuation as indentation.
465 ;; If initial point was within line's indentation and we're not on
466 ;; a line with a line continuation in a macro, position after the
467 ;; indentation. Else stay at same point in text.
475 ;; Return non-nil if the string KEYWORD is a known keyword. More
476 ;; precisely, the value is the symbol for the keyword in
477 ;; `c-keywords-obarray'.
481 ;; Return non-nil if the symbol KEYWORD-SYM, as returned by
482 ;; `c-keyword-sym', is a member of LANG-CONSTANT, which is the name
483 ;; of a language constant that ends with "-kwds". If KEYWORD-SYM is
484 ;; nil then the result is nil.
487 ;; String syntax chars, suitable for skip-syntax-(forward|backward).
492 ;; Regexp matching string limit syntax.
497 ;; Regexp matching WS followed by string limit syntax.
501 ;; Holds formatted error strings for the few cases where parse errors
502 ;; are reported.
509 c-parsing-error)
511 ;; Faces given to comments and string literals. This is used in some
512 ;; situations to speed up recognition; it isn't mandatory that font
513 ;; locking is in use. This variable is extended with the face in
514 ;; `c-doc-face-name' when fontification is activated in cc-fonts.el.
518 ;; New in Emacs 22.
522 ;; Put a c-type property with the given value at POS.
526 ;; Remove all occurrences of the c-type property that has the given
527 ;; value in the region between FROM and TO. VALUE is assumed to not
528 ;; be nil.
529 ;;
530 ;; Note: This assumes that c-type is put on single chars only; it's
531 ;; very inefficient if matching properties cover large regions.
540 \f
541 ;; Some debug tools to visualize various special positions. This
542 ;; debug code isn't as portable as the rest of CC Mode.
578 \f
579 ;; `c-beginning-of-statement-1' and accompanying stuff.
581 ;; KLUDGE ALERT: c-maybe-labelp is used to pass information between
582 ;; c-crosses-statement-barrier-p and c-beginning-of-statement-1. A
583 ;; better way should be implemented, but this will at least shut up
584 ;; the byte compiler.
587 ;; New awk-compatible version of c-beginning-of-statement-1, ACM 2002/6/22
589 ;; Macros used internally in c-beginning-of-statement-1 for the
590 ;; automaton actions.
593 stack)))
598 t
599 ,do-if-done
604 ;; Throw nil if stack is empty, else throw non-nil.
628 noerror comma-delim)
629 "Move to the start of the current statement or declaration, or to
630 the previous one if already at the beginning of one. Only
631 statements/declarations on the same level are considered, i.e. don't
632 move into or out of sexps (not even normal expression parentheses).
634 If point is already at the earliest statement within braces or parens,
635 this function doesn't move back into any whitespace preceding it; it
636 returns 'same in this case.
640 is within the continuation. If starting at such a token, move to the
641 corresponding statement start. If at the beginning of a statement,
642 move to the closest containing statement if there is any. This might
643 also stop at a continuation clause.
645 Labels are treated as part of the following statements if
646 IGNORE-LABELS is non-nil. (FIXME: Doesn't work if we stop at a known
647 statement start keyword.) Otherwise, each label is treated as a
648 separate statement.
650 Macros are ignored \(i.e. skipped over) unless point is within one, in
651 which case the content of the macro is treated as normal code. Aside
652 from any normal statement starts found in it, stop at the first token
655 macros before leaving them.
657 Return:
659 'same if stopped at the beginning of the current statement;
660 'up if stepped to a containing statement;
661 'previous if stepped to a preceding statement;
662 'beginning if stepped from a statement continuation clause to
663 its start clause; or
664 'macro if stepped to a macro start.
665 Note that 'same and not 'label is returned if stopped at the same
666 label without crossing the colon character.
668 LIM may be given to limit the search. If the search hits the limit,
669 point will be left at the closest following token, or at the start
670 position if that is less ('same is returned in this case).
672 NOERROR turns off error logging to `c-parsing-error'.
674 Normally only ';' and virtual semicolons are considered to delimit
675 statements, but if COMMA-DELIM is non-nil then ',' is treated
676 as a delimiter too.
678 Note that this function might do hidden buffer changes. See the
679 comment at the start of cc-engine.el for more info."
681 ;; The bulk of this function is a pushdown automaton that looks at statement
682 ;; boundaries and the tokens (such as "while") in c-opt-block-stmt-key. Its
683 ;; purpose is to keep track of nested statements, ensuring that such
684 ;; statements are skipped over in their entirety (somewhat akin to what C-M-p
685 ;; does with nested braces/brackets/parentheses).
686 ;;
687 ;; Note: The position of a boundary is the following token.
688 ;;
689 ;; Beginning with the current token (the one following point), move back one
690 ;; sexp at a time (where a sexp is, more or less, either a token or the
691 ;; entire contents of a brace/bracket/paren pair). Each time a statement
692 ;; boundary is crossed or a "while"-like token is found, update the state of
693 ;; the PDA. Stop at the beginning of a statement when the stack (holding
694 ;; nested statement info) is empty and the position has been moved.
695 ;;
696 ;; The following variables constitute the PDA:
697 ;;
698 ;; sym: This is either the "while"-like token (e.g. 'for) we've just
699 ;; scanned back over, 'boundary if we've just gone back over a
700 ;; statement boundary, or nil otherwise.
701 ;; state: takes one of the values (nil else else-boundary while
702 ;; while-boundary catch catch-boundary).
703 ;; nil means "no "while"-like token yet scanned".
704 ;; 'else, for example, means "just gone back over an else".
705 ;; 'else-boundary means "just gone back over a statement boundary
706 ;; immediately after having gone back over an else".
707 ;; saved-pos: A vector of either saved positions (tok ptok pptok, etc.) or
708 ;; of error reporting information.
709 ;; stack: The stack onto which the PDA pushes its state. Each entry
710 ;; consists of a saved value of state and saved-pos. An entry is
711 ;; pushed when we move back over a "continuation" token (e.g. else)
712 ;; and popped when we encounter the corresponding opening token
713 ;; (e.g. if).
714 ;;
715 ;;
716 ;; The following diagram briefly outlines the PDA.
717 ;;
718 ;; Common state:
719 ;; "else": Push state, goto state `else'.
720 ;; "while": Push state, goto state `while'.
721 ;; "catch" or "finally": Push state, goto state `catch'.
722 ;; boundary: Pop state.
723 ;; other: Do nothing special.
724 ;;
725 ;; State `else':
726 ;; boundary: Goto state `else-boundary'.
727 ;; other: Error, pop state, retry token.
728 ;;
729 ;; State `else-boundary':
730 ;; "if": Pop state.
731 ;; boundary: Error, pop state.
732 ;; other: See common state.
733 ;;
734 ;; State `while':
735 ;; boundary: Save position, goto state `while-boundary'.
736 ;; other: Pop state, retry token.
737 ;;
738 ;; State `while-boundary':
739 ;; "do": Pop state.
740 ;; boundary: Restore position if it's not at start, pop state. [*see below]
741 ;; other: See common state.
742 ;;
743 ;; State `catch':
744 ;; boundary: Goto state `catch-boundary'.
745 ;; other: Error, pop state, retry token.
746 ;;
747 ;; State `catch-boundary':
748 ;; "try": Pop state.
749 ;; "catch": Goto state `catch'.
750 ;; boundary: Error, pop state.
751 ;; other: See common state.
752 ;;
753 ;; [*] In the `while-boundary' state, we had pushed a 'while state, and were
754 ;; searching for a "do" which would have opened a do-while. If we didn't
755 ;; find it, we discard the analysis done since the "while", go back to this
756 ;; token in the buffer and restart the scanning there, this time WITHOUT
757 ;; pushing the 'while state onto the stack.
758 ;;
759 ;; In addition to the above there is some special handling of labels
760 ;; and macros.
764 macro-start
767 c-stmt-delim-chars-with-comma
768 c-stmt-delim-chars))
769 c-in-literal-cache c-maybe-labelp after-case:-pos saved
770 ;; Current position.
771 pos
772 ;; Position of last stmt boundary character (e.g. ;).
773 boundary-pos
774 ;; The position of the last sexp or bound that follows the
775 ;; first found colon, i.e. the start of the nonlabel part of
776 ;; the statement. It's `start' if a colon is found just after
777 ;; the start.
778 after-labels-pos
779 ;; Like `after-labels-pos', but the first such position inside
780 ;; a label, i.e. the start of the last label before the start
781 ;; of the nonlabel part of the statement.
782 last-label-pos
783 ;; The last position where a label is possible provided the
784 ;; statement started there. It's nil as long as no invalid
785 ;; label content has been found (according to
786 ;; `c-nonlabel-token-key'). It's `start' if no valid label
787 ;; content was found in the label. Note that we might still
788 ;; regard it a label if it starts with `c-label-kwds'.
789 label-good-pos
790 ;; Putative positions of the components of a bitfield declaration,
791 ;; e.g. "int foo : NUM_FOO_BITS ;"
792 bitfield-type-pos bitfield-id-pos bitfield-size-pos
793 ;; Symbol just scanned back over (e.g. 'while or 'boundary).
794 ;; See above.
795 sym
796 ;; Current state in the automaton. See above.
797 state
798 ;; Current saved positions. See above.
799 saved-pos
800 ;; Stack of conses (state . saved-pos).
801 stack
802 ;; Regexp which matches "for", "if", etc.
805 ;; Return value.
807 ;; Positions of the last three sexps or bounds we've stopped at.
808 tok ptok pptok)
818 ;; Try to skip back over unary operator characters, to register
819 ;; that we've moved.
823 ;; Protect post-++/-- operators just before a virtual semicolon.
827 ;; Skip back over any semicolon here. If it was a bare semicolon, we're
828 ;; done. Later on we ignore the boundaries for statements that don't
829 ;; contain any sexp. The only thing that is affected is that the error
830 ;; checking is a little less strict, and we really don't bother.
840 pos saved)
842 ;; Begin at start and not pos to detect macros if we stand
843 ;; directly after the #.
846 ;; Record this as the first token if not starting inside it.
849 ;; The following while loop goes back one sexp (balanced parens,
850 ;; etc. with contents, or symbol or suchlike) each iteration. This
851 ;; movement is accomplished with a call to c-backward-sexp approx 170
852 ;; lines below.
853 ;;
854 ;; The loop is exited only by throwing nil to the (catch 'loop ...):
855 ;; 1. On reaching the start of a macro;
856 ;; 2. On having passed a stmt boundary with the PDA stack empty;
857 ;; 3. On reaching the start of an Objective C method def;
858 ;; 4. From macro `c-bos-pop-state'; when the stack is empty;
859 ;; 5. From macro `c-bos-pop-state-and-retry' when the stack is empty.
863 ;; Are we in a macro, just after the opening #?
878 ;; Stop at the first token in the content of the macro.
882 ret 'macro
883 ignore-labels t))
886 ;; Do a round through the automaton if we've just passed a
887 ;; statement boundary or passed a "while"-like token.
895 ;; The PDA state handling.
896 ;;
897 ;; Refer to the description of the PDA in the opening
898 ;; comments. In the following OR form, the first leaf
899 ;; attempts to handles one of the specific actions detailed
900 ;; (e.g., finding token "if" whilst in state `else-boundary').
901 ;; We drop through to the second leaf (which handles common
902 ;; state) if no specific handler is found in the first cond.
903 ;; If a parsing error is detected (e.g. an "else" with no
904 ;; preceding "if"), we throw to the enclosing catch.
905 ;;
906 ;; Note that the (eq state 'else) means
907 ;; "we've just passed an else", NOT "we're looking for an
908 ;; else".
925 ;; Since this can cause backtracking we do a
926 ;; little more careful analysis to avoid it:
927 ;; If there's a label in front of the while
928 ;; it can't be part of a do-while.
957 ;; This is state common. We get here when the previous
958 ;; cond statement found no particular state handler.
960 ;; If we have a boundary at the start
961 ;; position we push a frame to go to the
962 ;; previous statement.
971 ;; Is this a real while, or a do-while?
972 ;; The next `when' triggers unless we are SURE that
973 ;; the `while' is not the tail end of a `do-while'.
976 ;; The following kludge is to prevent
977 ;; infinite recursion when called from
978 ;; c-awk-after-if-for-while-condition-p,
979 ;; or the like.
983 ;; Since this can cause backtracking we do a
984 ;; little more careful analysis to avoid it: If
985 ;; the while isn't followed by a (possibly
986 ;; virtual) semicolon it can't be a do-while.
995 ;; We're either past a statement boundary or at the
996 ;; start of a statement, so throw away any label data
997 ;; for the previous one.
999 last-label-pos nil
1000 c-maybe-labelp nil))))
1002 ;; Step to the previous sexp, but not if we crossed a
1003 ;; boundary, since that doesn't consume an sexp.
1007 ;; HERE IS THE SINGLE PLACE INSIDE THE PDA LOOP WHERE WE MOVE
1008 ;; BACKWARDS THROUGH THE SOURCE.
1012 ;; The end position of the area to search for statement
1013 ;; barriers in this round.
1016 ;; Go back over exactly one logical sexp, taking proper
1017 ;; account of macros and escaped EOLs.
1021 ;; Give up if we hit an unbalanced block. Since the
1022 ;; stack won't be empty the code below will report a
1023 ;; suitable error.
1026 ;; Have we moved into a macro?
1029 ;; Have we crossed a statement boundary? If not,
1030 ;; keep going back until we find one or a "real" sexp.
1037 ;; Have we just gone back over an escaped NL? This
1038 ;; doesn't count as a sexp.
1041 ;; Have we crossed a statement boundary?
1044 ;; Are we at a macro beginning?
1046 c-opt-cpp-prefix
1052 ;; Just gone back over a brace block?
1061 ;; Just gone back over some paren block?
1065 before-sws-pos)))
1068 ;; Just gone back over an ordinary symbol of some sort?
1074 ptok tok
1075 tok boundary-pos
1077 ;; Like a C "continue". Analyze the next sexp.
1080 ;; ObjC method def?
1087 ;; Might we have a bitfield declaration, "<type> <id> : <size>"?
1090 ;; The : <size> and <id> fields?
1100 ;; The <type> field?
1108 bitfield-id-pos nil)))))
1110 ;; Handle labels.
1113 ;; `c-crosses-statement-barrier-p' has found a colon, so we
1114 ;; might be in a label now. Have we got a real label
1115 ;; (including a case label) or something like C++'s "public:"?
1116 ;; A case label might use an expression rather than a token.
1119 ;; Catch C++'s inheritance construct "class foo : bar".
1133 ; been found.
1135 ;; We're in a potential label and it's the first
1136 ;; time we've found something that isn't allowed in
1137 ;; one.
1140 ;; We've moved back by a sexp, so update the token positions.
1142 pptok ptok
1143 ptok tok
1149 ;; If the stack isn't empty there might be errors to report.
1158 ;; Need to investigate closer whether we've crossed
1159 ;; between a substatement and its containing statement.
1163 pptok)
1165 ptok)
1173 after-labels-pos
1180 last-label-pos
1181 pos))
1183 ;; We're in a label. Maybe we should step to the statement
1184 ;; after it.
1189 ;; Might have jumped over several labels. Go to the last one.
1192 ;; Have we got "case <expression>:"?
1202 ;; Skip over the unary operators that can start the statement.
1205 ;; protect AWK post-inc/decrement operators, etc.
1210 ret)))
1213 "Return non-nil if there is a non-comment non-macro punctuation character
1214 between FROM and TO. FROM must not be in a string or comment. The returned
1215 value is the position of the first such character."
1226 "Return non-nil if buffer positions FROM to TO cross one or more
1227 statement or declaration boundaries. The returned value is actually
1228 the position of the earliest boundary char. FROM must not be within
1229 a string or comment.
1231 The variable `c-maybe-labelp' is set to the position of the first `:' that
1232 might start a label (i.e. not part of `::' and not preceded by `?'). If a
1233 single `?' is found, then `c-maybe-labelp' is cleared.
1235 For AWK, a statement which is terminated by an EOL (not a \; or a }) is
1237 the line. If this virtual semicolon is _at_ from, the function recognizes it.
1239 Note that this function might do hidden buffer changes. See the
1240 comment at the start of cc-engine.el for more info."
1242 ;; If the current language has CPP macros, insert # into skip-chars.
1245 c-opt-cpp-symbol ; usually "#"
1247 c-stmt-delim-chars))
1250 lit-range vsemi-pos)
1257 skip-chars
1261 ;; Virtual semicolon?
1271 ;; In a string/comment?
1278 ;; Ignore scope operators.
1282 ;; A question mark. Can't be a label, so stop
1283 ;; looking for more : and ?.
1286 ;; At a CPP construct or a "#" or "##" operator?
1297 ;; In trailing space after an as yet undetected virtual semicolon?
1300 ; unterminated string/regexp.
1305 nil))))))
1308 "Return non-nil if the point is at the first token in a statement
1309 or somewhere in the syntactic whitespace before it.
1312 Any kind of declaration-like construct that occur outside function
1315 Note that this function might do hidden buffer changes. See the
1316 comment at the start of cc-engine.el for more info."
1320 c-maybe-labelp)
1331 "Return non-nil if the point is at the first token in an expression or
1332 statement, or somewhere in the syntactic whitespace before it.
1335 grammar sense: It's any sequence of expression tokens except commas,
1336 unless they are enclosed inside parentheses of some kind. Also, an
1337 expression never continues past an enclosing parenthesis, but it might
1338 contain parenthesis pairs of any sort except braces.
1340 Since expressions never cross statement boundaries, this function also
1341 recognizes statement beginnings, just like `c-at-statement-start-p'.
1343 Note that this function might do hidden buffer changes. See the
1344 comment at the start of cc-engine.el for more info."
1349 c-maybe-labelp)
1357 \f
1358 ;; A set of functions that covers various idiosyncrasies in
1359 ;; implementations of `forward-comment'.
1361 ;; Note: Some emacsen considers incorrectly that any line comment
1362 ;; ending with a backslash continues to the next line. I can't think
1363 ;; of any way to work around that in a reliable way without changing
1364 ;; the buffer, though. Suggestions welcome. ;) (No, temporarily
1365 ;; changing the syntax for backslash doesn't work since we must treat
1366 ;; escapes in string literals correctly.)
1369 "Move forward past whitespace and the closest following comment, if any.
1370 Return t if a comment was found, nil otherwise. In either case, the
1371 point is moved past the following whitespace. Line continuations,
1372 i.e. a backslashes followed by line breaks, are treated as whitespace.
1373 The line breaks that end line comments are considered to be the
1374 comment enders, so the point will be put on the beginning of the next
1375 line if it moved past a line comment.
1377 This function does not do any hidden buffer changes."
1385 ;; Some emacsen (e.g. XEmacs 21) return t when moving
1386 ;; forwards at eob.
1387 nil
1389 ;; Emacs includes the ending newline in a b-style (c++)
1390 ;; comment, but XEmacs doesn't. We depend on the Emacs
1391 ;; behavior (which also is symmetric).
1395 t))))
1398 "Move forward past all following whitespace and comments.
1399 Line continuations, i.e. a backslashes followed by line breaks, are
1400 treated as whitespace.
1402 Note that this function might do hidden buffer changes. See the
1403 comment at the start of cc-engine.el for more info."
1406 ;; If forward-comment in at least XEmacs 21 is given a large
1407 ;; positive value, it'll loop all the way through if it hits
1408 ;; eob.
1410 ;; Some emacsen (e.g. XEmacs 21) return t when moving
1411 ;; forwards at eob.
1416 t))))
1419 "Move backward past whitespace and the closest preceding comment, if any.
1420 Return t if a comment was found, nil otherwise. In either case, the
1421 point is moved past the preceding whitespace. Line continuations,
1422 i.e. a backslashes followed by line breaks, are treated as whitespace.
1423 The line breaks that end line comments are considered to be the
1424 comment enders, so the point cannot be at the end of the same line to
1425 move over a line comment.
1427 This function does not do any hidden buffer changes."
1430 ;; When we got newline terminated comments, forward-comment in all
1431 ;; supported emacsen so far will stop at eol of each line not
1432 ;; ending with a comment when moving backwards. This corrects for
1433 ;; that, and at the same time handles line continuations.
1441 ;; Some emacsen (e.g. Emacs 19.34) return t when moving
1442 ;; backwards at bob.
1443 nil
1445 ;; Leave point after the closest following newline if we've
1446 ;; backed up over any above, since forward-comment won't move
1447 ;; backward over a line comment if point is at the end of the
1448 ;; same line.
1453 ;; If forward-comment above succeeded and we're at eol
1454 ;; then the newline we moved over above didn't end a
1455 ;; line comment, so we give it another go.
1458 t))
1460 ;; Emacs <= 20 and XEmacs move back over the closer of a
1461 ;; block comment that lacks an opener.
1464 t)))))
1467 "Move backward past all preceding whitespace and comments.
1468 Line continuations, i.e. a backslashes followed by line breaks, are
1469 treated as whitespace. The line breaks that end line comments are
1470 considered to be the comment enders, so the point cannot be at the end
1471 of the same line to move over a line comment. Unlike
1472 c-backward-syntactic-ws, this function doesn't move back over
1473 preprocessor directives.
1475 Note that this function might do hidden buffer changes. See the
1476 comment at the start of cc-engine.el for more info."
1480 ;; `forward-comment' in some emacsen (e.g. XEmacs 21.4)
1481 ;; return t when moving backwards at bob.
1487 ;; Cope specifically with ^M^J here -
1488 ;; forward-comment sometimes gets stuck after ^Ms,
1489 ;; sometimes after ^M^J.
1493 t)
1497 t))))
1498 moved-comment)
1500 ;; Emacs <= 20 and XEmacs move back over the
1501 ;; closer of a block comment that lacks an opener.
1503 t)
1505 ;; XEmacs treats line continuations as whitespace but
1506 ;; only in the backward direction, which seems a bit
1507 ;; odd. Anyway, this is necessary for Emacs.
1512 t))))))
1514 \f
1515 ;; Tools for skipping over syntactic whitespace.
1517 ;; The following functions use text properties to cache searches over
1518 ;; large regions of syntactic whitespace. It works as follows:
1519 ;;
1520 ;; o If a syntactic whitespace region contains anything but simple
1521 ;; whitespace (i.e. space, tab and line breaks), the text property
1522 ;; `c-in-sws' is put over it. At places where we have stopped
1523 ;; within that region there's also a `c-is-sws' text property.
1524 ;; That since there typically are nested whitespace inside that
1525 ;; must be handled separately, e.g. whitespace inside a comment or
1526 ;; cpp directive. Thus, from one point with `c-is-sws' it's safe
1527 ;; to jump to another point with that property within the same
1528 ;; `c-in-sws' region. It can be likened to a ladder where
1529 ;; `c-in-sws' marks the bars and `c-is-sws' the rungs.
1530 ;;
1531 ;; o The `c-is-sws' property is put on the simple whitespace chars at
1532 ;; a "rung position" and also maybe on the first following char.
1533 ;; As many characters as can be conveniently found in this range
1534 ;; are marked, but no assumption can be made that the whole range
1535 ;; is marked (it could be clobbered by later changes, for
1536 ;; instance).
1537 ;;
1538 ;; Note that some part of the beginning of a sequence of simple
1539 ;; whitespace might be part of the end of a preceding line comment
1540 ;; or cpp directive and must not be considered part of the "rung".
1541 ;; Such whitespace is some amount of horizontal whitespace followed
1542 ;; by a newline. In the case of cpp directives it could also be
1543 ;; two newlines with horizontal whitespace between them.
1544 ;;
1545 ;; The reason to include the first following char is to cope with
1546 ;; "rung positions" that doesn't have any ordinary whitespace. If
1547 ;; `c-is-sws' is put on a token character it does not have
1548 ;; `c-in-sws' set simultaneously. That's the only case when that
1549 ;; can occur, and the reason for not extending the `c-in-sws'
1550 ;; region to cover it is that the `c-in-sws' region could then be
1551 ;; accidentally merged with a following one if the token is only
1552 ;; one character long.
1553 ;;
1554 ;; o On buffer changes the `c-in-sws' and `c-is-sws' properties are
1555 ;; removed in the changed region. If the change was inside
1556 ;; syntactic whitespace that means that the "ladder" is broken, but
1557 ;; a later call to `c-forward-sws' or `c-backward-sws' will use the
1558 ;; parts on either side and use an ordinary search only to "repair"
1559 ;; the gap.
1560 ;;
1561 ;; Special care needs to be taken if a region is removed: If there
1562 ;; are `c-in-sws' on both sides of it which do not connect inside
1563 ;; the region then they can't be joined. If e.g. a marked macro is
1564 ;; broken, syntactic whitespace inside the new text might be
1565 ;; marked. If those marks would become connected with the old
1566 ;; `c-in-sws' range around the macro then we could get a ladder
1567 ;; with one end outside the macro and the other at some whitespace
1568 ;; within it.
1569 ;;
1570 ;; The main motivation for this system is to increase the speed in
1571 ;; skipping over the large whitespace regions that can occur at the
1572 ;; top level in e.g. header files that contain a lot of comments and
1573 ;; cpp directives. For small comments inside code it's probably
1574 ;; slower than using `forward-comment' straightforwardly, but speed is
1575 ;; not a significant factor there anyway.
1577 ; (defface c-debug-is-sws-face
1578 ; '((t (:background "GreenYellow")))
1579 ; "Debug face to mark the `c-is-sws' property.")
1580 ; (defface c-debug-in-sws-face
1581 ; '((t (:underline t)))
1582 ; "Debug face to mark the `c-in-sws' property.")
1584 ; (defun c-debug-put-sws-faces ()
1585 ; ;; Put the sws debug faces on all the `c-is-sws' and `c-in-sws'
1586 ; ;; properties in the buffer.
1587 ; (interactive)
1588 ; (save-excursion
1589 ; (c-save-buffer-state (in-face)
1590 ; (goto-char (point-min))
1591 ; (setq in-face (if (get-text-property (point) 'c-is-sws)
1592 ; (point)))
1593 ; (while (progn
1594 ; (goto-char (next-single-property-change
1595 ; (point) 'c-is-sws nil (point-max)))
1596 ; (if in-face
1597 ; (progn
1598 ; (c-debug-add-face in-face (point) 'c-debug-is-sws-face)
1599 ; (setq in-face nil))
1600 ; (setq in-face (point)))
1601 ; (not (eobp))))
1602 ; (goto-char (point-min))
1603 ; (setq in-face (if (get-text-property (point) 'c-in-sws)
1604 ; (point)))
1605 ; (while (progn
1606 ; (goto-char (next-single-property-change
1607 ; (point) 'c-in-sws nil (point-max)))
1608 ; (if in-face
1609 ; (progn
1610 ; (c-debug-add-face in-face (point) 'c-debug-in-sws-face)
1611 ; (setq in-face nil))
1612 ; (setq in-face (point)))
1613 ; (not (eobp)))))))
1616 ;;`(message ,@args)
1617 )
1620 ;; This macro does a hidden buffer change.
1627 ;; This macro does a hidden buffer change.
1634 ;; This macro does a hidden buffer change.
1641 ;; This macro does a hidden buffer change.
1648 ;; This macro does a hidden buffer change.
1656 ;; Called from `after-change-functions'. Note that if
1657 ;; `c-forward-sws' or `c-backward-sws' are used outside
1658 ;; `c-save-buffer-state' or similar then this will remove the cache
1659 ;; properties right after they're added.
1660 ;;
1661 ;; This function does hidden buffer changes.
1664 ;; Adjust the end to remove the properties in any following simple
1665 ;; ws up to and including the next line break, if there is any
1666 ;; after the changed region. This is necessary e.g. when a rung
1667 ;; marked empty line is converted to a line comment by inserting
1668 ;; "//" before the line break. In that case the line break would
1669 ;; keep the rung mark which could make a later `c-backward-sws'
1670 ;; move into the line comment instead of over it.
1680 ;; Ensure that an `c-in-sws' range gets broken. Note that it isn't
1681 ;; safe to keep a range that was continuous before the change. E.g:
1682 ;;
1683 ;; #define foo
1684 ;; \
1685 ;; bar
1686 ;;
1687 ;; There can be a "ladder" between "#" and "b". Now, if the newline
1688 ;; after "foo" is removed then "bar" will become part of the cpp
1689 ;; directive instead of a syntactically relevant token. In that
1690 ;; case there's no longer syntactic ws from "#" to "b".
1697 ;; Used by `c-forward-syntactic-ws' to implement the unbounded search.
1698 ;;
1699 ;; This function might do hidden buffer changes.
1702 ;; unmarked part of the simple ws region.
1704 rung-is-marked next-rung-is-marked simple-ws-end
1705 ;; `safe-start' is set when it's safe to cache the start position.
1706 ;; It's not set if we've initially skipped over comments and line
1707 ;; continuations since we might have gone out through the end of a
1708 ;; macro then. This provision makes `c-forward-sws' not populate the
1709 ;; cache in the majority of cases, but otoh is `c-backward-sws' by far
1710 ;; more common.
1711 safe-start)
1713 ;; Skip simple ws and do a quick check on the following character to see
1714 ;; if it's anything that can't start syntactic ws, so we can bail out
1715 ;; early in the majority of cases when there just are a few ws chars.
1722 ;; Find the last rung position to avoid setting properties in all
1723 ;; the cases when the marked rung is complete.
1724 ;; (`next-single-property-change' is certain to move at least one
1725 ;; step forward.)
1728 ;; Got no marked rung here. Since the simple ws might have started
1729 ;; inside a line comment or cpp directive we must set `rung-pos' as
1730 ;; high as possible.
1740 ;; The following search is the main reason that `c-in-sws'
1741 ;; and `c-is-sws' aren't combined to one property.
1745 ;; If the `c-in-sws' region extended past the last
1746 ;; `c-is-sws' char we have to go back a bit.
1753 "c-forward-sws cached move %s -> %s (max %s)"
1760 ;; We'll loop here if there is simple ws after the last rung.
1761 ;; That means that there's been some change in it and it's
1762 ;; possible that we've stepped into another ladder, so extend
1763 ;; the previous one to join with it if there is one, and try to
1764 ;; use the cache again.
1766 "c-forward-sws extending rung with [%s..%s] (max %s)"
1769 ;; Remove any `c-in-sws' property from the last char of
1770 ;; the rung before we mark it with `c-is-sws', so that we
1771 ;; won't connect with the remains of a broken "ladder".
1777 last-put-in-sws-pos rung-pos)))
1784 ;; Skipped over comments. Don't cache at eob in case the buffer
1785 ;; is narrowed.
1796 ;; Skip a preprocessor directive.
1803 ;; Don't cache at eob in case the buffer is narrowed.
1806 ;; We've searched over a piece of non-white syntactic ws. See if this
1807 ;; can be cached.
1813 ;; Cache if we haven't skipped comments only, and if we started
1814 ;; either from a marked rung or from a completely uncached
1815 ;; position.
1820 ;; See if there's a marked rung in the encountered simple ws. If
1821 ;; so then we can cache, unless `safe-start' is nil. Even then
1822 ;; we need to do this to check if the cache can be used for the
1823 ;; next step.
1827 safe-start))
1831 "c-forward-sws caching [%s..%s] - [%s..%s] (max %s)"
1835 ;; Remove the properties for any nested ws that might be cached.
1836 ;; Only necessary for `c-is-sws' since `c-in-sws' will be set
1837 ;; anyway.
1845 last-put-in-sws-pos rung-pos))
1847 ;; Remove any `c-in-sws' property from the last char of
1848 ;; the rung before we mark it with `c-is-sws', so that we
1849 ;; won't connect with the remains of a broken "ladder".
1852 rung-end-pos))
1855 "c-forward-sws not caching [%s..%s] - [%s..%s] (max %s)"
1859 ;; Set `rung-pos' for the next rung. It's the same thing here as
1860 ;; initially, except that the rung position is set as early as
1861 ;; possible since we can't be in the ending ws of a line comment or
1862 ;; cpp directive now.
1869 ;; Make sure that the newly marked `c-in-sws' region doesn't connect to
1870 ;; another one after the point (which might occur when editing inside a
1871 ;; comment or macro).
1875 "c-forward-sws clearing at %s for cache separation"
1876 last-put-in-sws-pos)
1880 ;; If at eob we have to clear the last character before the end
1881 ;; instead since the buffer might be narrowed and there might
1882 ;; be a `c-in-sws' after (point-max). In this case it's
1883 ;; necessary to clear both properties.
1885 "c-forward-sws clearing thoroughly at %s for cache separation"
1888 last-put-in-sws-pos))))
1889 ))))
1892 ;; Used by `c-backward-syntactic-ws' to implement the unbounded search.
1893 ;;
1894 ;; This function might do hidden buffer changes.
1897 ;; part of the simple ws region.
1899 rung-is-marked simple-ws-beg cmt-skip-pos)
1901 ;; Skip simple horizontal ws and do a quick check on the preceding
1902 ;; character to see if it's anything that can't end syntactic ws, so we can
1903 ;; bail out early in the majority of cases when there just are a few ws
1904 ;; chars. Newlines are complicated in the backward direction, so we can't
1905 ;; skip over them.
1912 ;; Try to find a rung position in the simple ws preceding point, so that
1913 ;; we can get a cache hit even if the last bit of the simple ws has
1914 ;; changed recently.
1920 ;; `rung-pos' will be the earliest marked position, which means that
1921 ;; there might be later unmarked parts in the simple ws region.
1922 ;; It's not worth the effort to fix that; the last part of the
1923 ;; simple ws is also typically edited often, so it could be wasted.
1935 ;; The following search is the main reason that `c-in-sws'
1936 ;; and `c-is-sws' aren't combined to one property.
1940 ;; If the `c-in-sws' region extended past the first
1941 ;; `c-is-sws' char we have to go forward a bit.
1946 "c-backward-sws cached move %s <- %s (min %s)"
1958 t
1960 nil))
1962 ;; We'll loop here if there is simple ws before the first rung.
1963 ;; That means that there's been some change in it and it's
1964 ;; possible that we've stepped into another ladder, so extend
1965 ;; the previous one to join with it if there is one, and try to
1966 ;; use the cache again.
1968 "c-backward-sws extending rung with [%s..%s] (min %s)"
1971 ;; Remove any `c-in-sws' property from the last char of
1972 ;; the rung before we mark it with `c-is-sws', so that we
1973 ;; won't connect with the remains of a broken "ladder".
1976 rung-pos)
1980 last-put-in-sws-pos rung-pos))
1989 ;; Inside a cpp directive. See if it should be skipped over.
1992 ;; Move back over all line continuations in the region skipped
1993 ;; over by `c-backward-comments'. If we go past it then we
1994 ;; started inside the cpp directive.
2003 ;; Don't move past the cpp directive if we began inside
2004 ;; it. Note that the position at the end of the last line
2005 ;; of the macro is also considered to be within it.
2007 nil)
2009 ;; It's worthwhile to spend a little bit of effort on finding
2010 ;; the end of the macro, to get a good `simple-ws-beg'
2011 ;; position for the cache. Note that `c-backward-comments'
2012 ;; could have stepped over some comments before going into
2013 ;; the macro, and then `simple-ws-beg' must be kept on the
2014 ;; same side of those comments.
2021 ;; Might happen if comments after the macro were skipped
2022 ;; over.
2026 t)))
2031 simple-ws-beg)
2032 ;; Skipped over comments. Must put point at the end of
2033 ;; the simple ws at point since we might be after a line
2034 ;; comment or cpp directive that's been partially
2035 ;; narrowed out, and we can't risk marking the simple ws
2036 ;; at the end of it.
2038 t)))
2040 ;; We've searched over a piece of non-white syntactic ws. See if this
2041 ;; can be cached.
2046 ;; Cache if we started either from a marked rung or from a
2047 ;; completely uncached position.
2048 rung-is-marked
2051 ;; Cache if there's a marked rung in the encountered simple ws.
2059 "c-backward-sws caching [%s..%s] - [%s..%s] (min %s)"
2064 ;; Remove the properties for any nested ws that might be cached.
2065 ;; Only necessary for `c-is-sws' since `c-in-sws' will be set
2066 ;; anyway.
2071 ;; Remove any `c-in-sws' property from the last char of
2072 ;; the rung before we mark it with `c-is-sws', so that we
2073 ;; won't connect with the remains of a broken "ladder".
2076 rung-end-pos)
2079 last-put-in-sws-pos simple-ws-beg)
2080 rung-pos)
2085 "c-backward-sws not caching [%s..%s] - [%s..%s] (min %s)"
2091 ))
2093 ;; Make sure that the newly marked `c-in-sws' region doesn't connect to
2094 ;; another one before the point (which might occur when editing inside a
2095 ;; comment or macro).
2099 "c-backward-sws clearing at %s for cache separation"
2102 last-put-in-sws-pos))
2104 ;; If at bob and the buffer is narrowed, we have to clear the
2105 ;; character we're standing on instead since there might be a
2106 ;; `c-in-sws' before (point-min). In this case it's necessary
2107 ;; to clear both properties.
2109 "c-backward-sws clearing thoroughly at %s for cache separation"
2110 last-put-in-sws-pos)
2113 ))))
2115 \f
2116 ;; Other whitespace tools
2118 ;; Is the region (beg end) WS, and is there WS (or BOB/EOB) next to the
2119 ;; region? This is a "heuristic" function. .....
2120 ;;
2121 ;; The motivation for the second bit is to check whether removing this
2122 ;; region would coalesce two symbols.
2123 ;;
2124 ;; FIXME!!! This function doesn't check virtual semicolons in any way. Be
2125 ;; careful about using this function for, e.g. AWK. (2007/3/7)
2134 \f
2135 ;; A system for finding noteworthy parens before the point.
2138 ;; A maximum comfortable scanning distance, e.g. between
2139 ;; `c-state-cache-good-pos' and "HERE" (where we call c-parse-state). When
2140 ;; this distance is exceeded, we take "emergency measures", e.g. by clearing
2141 ;; the cache and starting again from point-min or a beginning of defun. This
2142 ;; value can be tuned for efficiency or set to a lower value for testing.
2146 ;; The state cache used by `c-parse-state' to cut down the amount of
2147 ;; searching. It's the result from some earlier `c-parse-state' call. See
2148 ;; `c-parse-state''s doc string for details of its structure.
2149 ;;
2150 ;; The use of the cached info is more effective if the next
2151 ;; `c-parse-state' call is on a line close by the one the cached state
2152 ;; was made at; the cache can actually slow down a little if the
2153 ;; cached state was made very far back in the buffer. The cache is
2154 ;; most effective if `c-parse-state' is used on each line while moving
2155 ;; forward.
2159 ;; This is a position where `c-state-cache' is known to be correct, or
2160 ;; nil (see below). It's a position inside one of the recorded unclosed
2161 ;; parens or the top level, but not further nested inside any literal or
2162 ;; subparen that is closed before the last recorded position.
2163 ;;
2164 ;; The exact position is chosen to try to be close to yet earlier than
2165 ;; the position where `c-state-cache' will be called next. Right now
2166 ;; the heuristic is to set it to the position after the last found
2167 ;; closing paren (of any type) before the line on which
2168 ;; `c-parse-state' was called. That is chosen primarily to work well
2169 ;; with refontification of the current line.
2170 ;;
2171 ;; 2009-07-28: When `c-state-point-min' and the last position where
2172 ;; `c-parse-state' or for which `c-invalidate-state-cache' was called, are
2173 ;; both in the same literal, there is no such "good position", and
2174 ;; c-state-cache-good-pos is then nil. This is the ONLY circumstance in which
2175 ;; it can be nil. In this case, `c-state-point-min-literal' will be non-nil.
2176 ;;
2177 ;; 2009-06-12: In a brace desert, c-state-cache-good-pos may also be in
2178 ;; the middle of the desert, as long as it is not within a brace pair
2179 ;; recorded in `c-state-cache' or a paren/bracket pair.
2181 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2182 ;; We maintain a simple cache of positions which aren't in a literal, so as to
2183 ;; speed up testing for non-literality.
2185 ;; The approximate interval between entries in `c-state-nonlit-pos-cache'.
2189 ;; A list of buffer positions which are known not to be in a literal or a cpp
2190 ;; construct. This is ordered with higher positions at the front of the list.
2191 ;; Only those which are less than `c-state-nonlit-pos-cache-limit' are valid.
2195 ;; An upper limit on valid entries in `c-state-nonlit-pos-cache'. This is
2196 ;; reduced by buffer changes, and increased by invocations of
2197 ;; `c-state-literal-at'.
2201 ;; A list of buffer positions which are known not to be in a literal. This is
2202 ;; ordered with higher positions at the front of the list. Only those which
2203 ;; are less than `c-state-semi-nonlit-pos-cache-limit' are valid.
2207 ;; An upper limit on valid entries in `c-state-semi-nonlit-pos-cache'. This is
2208 ;; reduced by buffer changes, and increased by invocations of
2209 ;; `c-state-literal-at'. FIXME!!!
2212 ;; Do a parse-partial-sexp from FROM to TO, returning either
2213 ;; (STATE TYPE (BEG . END)) if TO is in a literal; or
2214 ;; (STATE) otherwise,
2215 ;; where STATE is the parsing state at TO, TYPE is the type of the literal
2216 ;; (one of 'c, 'c++, 'string) and (BEG . END) is the boundaries of the literal.
2217 ;;
2218 ;; Unless NOT-IN-DELIMITER is non-nil, when TO is inside a two-character
2219 ;; comment opener, this is recognized as being in a comment literal.
2220 ;;
2221 ;; Only elements 3 (in a string), 4 (in a comment), 5 (following a quote),
2222 ;; 7 (comment type) and 8 (start of comment/string) (and possibly 9) of
2223 ;; STATE are valid.
2226 ty co-st)
2234 nil ; TARGETDEPTH
2235 nil ; STOPBEFORE
2236 s ; OLDSTATE
2253 ;; Return a buffer position before HERE which is "safe", i.e. outside any
2254 ;; string, comment, or macro.
2255 ;;
2256 ;; NOTE: This function manipulates `c-state-nonlit-pos-cache'. This cache
2257 ;; MAY NOT contain any positions within macros, since macros are frequently
2258 ;; turned into comments by use of the `c-cpp-delimiter' category properties.
2259 ;; We cannot rely on this mechanism whilst determining a cache pos since
2260 ;; this function is also called from outwith `c-parse-state'.
2265 pos npos high-pos lit macro-beg macro-end)
2266 ;; Trim the cache to take account of buffer changes.
2278 ;; Add an element to `c-state-nonlit-pos-cache' each iteration.
2282 ;; Test for being in a literal. If so, go to after it.
2289 ;; Test for being in a macro. If so, go to after it.
2304 ;; Add one extra element above HERE so as to to avoid the previous
2305 ;; expensive calculation when the next call is close to the current
2306 ;; one. This is especially useful when inside a large macro.
2311 pos))))
2314 ;; Return a buffer position before HERE which is "safe", i.e. outside any
2315 ;; string or comment. It may be in a macro.
2320 pos npos high-pos lit macro-beg macro-end)
2321 ;; Trim the cache to take account of buffer changes.
2333 ;; Add an element to `c-state-semi-nonlit-pos-cache' each iteration.
2337 ;; Test for being in a literal. If so, go to after it.
2350 pos))))
2353 ;; If position HERE is inside a literal, return (START . END), the
2354 ;; boundaries of the literal (which may be outside the accessible bit of the
2355 ;; buffer). Otherwise, return nil.
2356 ;;
2357 ;; This function is almost the same as `c-literal-limits'. Previously, it
2358 ;; differed in that it was a lower level function, and that it rigorously
2359 ;; followed the syntax from BOB. `c-literal-limits' is now (2011-12)
2360 ;; virtually identical to this function.
2368 ;; Return the start of the literal containing POS, or POS itself.
2370 pos))
2373 ;; Return a position outside of a string/comment/macro at or before POS.
2374 ;; STATE is the parse-partial-sexp state at POS.
2378 pos)))
2383 res))))
2385 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2386 ;; Stuff to do with point-min, and coping with any literal there.
2389 ;; This is (point-min) when `c-state-cache' was last calculated. A change of
2390 ;; narrowing is likely to affect the parens that are visible before the point.
2396 ;; These two variables define the literal, if any, containing point-min.
2397 ;; Their values are, respectively, 'string, c, or c++, and the start of the
2398 ;; literal. If there's no literal there, they're both nil.
2402 ;; This is the earliest buffer-pos from which scanning can be done. It is
2403 ;; either the end of the literal containing point-min, or point-min itself.
2404 ;; It becomes nil if the buffer is changed earlier than this point.
2406 ;; Return the lowest valid scanning pos. This will be the end of the
2407 ;; literal enclosing point-min, or point-min itself.
2419 ;; Determine the properties of any literal containing POINT-MIN, setting the
2420 ;; variables `c-state-point-min-lit-type', `c-state-point-min-lit-start',
2421 ;; and `c-state-min-scan-pos' accordingly. The return value is meaningless.
2423 lit)
2438 c-state-point-min-lit-start nil
2439 c-state-min-scan-pos p-min)))))
2442 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2443 ;; A variable which signals a brace dessert - helpful for reducing the number
2444 ;; of fruitless backward scans.
2447 ;; Used only in `c-append-lower-brace-pair-to-state-cache'. It is set when
2448 ;; that defun has searched backwards for a brace pair and not found one. Its
2449 ;; value is either nil or a cons (PA . FROM), where PA is the position of the
2450 ;; enclosing opening paren/brace/bracket which bounds the backwards search (or
2451 ;; nil when at top level) and FROM is where the backward search started. It
2452 ;; is reset to nil in `c-invalidate-state-cache'.
2455 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2456 ;; Lowish level functions/macros which work directly on `c-state-cache', or a
2457 ;; list of like structure.
2459 ;; Return the address of the top left brace/bracket/paren recorded in CACHE
2460 ;; (default `c-state-cache') (or nil).
2467 ;; Return the address of the latest brace/bracket/paren (whether left or
2468 ;; right) recorded in CACHE (default `c-state-cache') or nil.
2475 ;; Return the position just after the latest brace/bracket/paren (whether
2476 ;; left or right) recorded in CACHE (default `c-state-cache') or nil.
2484 ;; From the state-cache, determine the buffer position from which we might
2485 ;; scan forward to HERE to update this cache. This position will be just
2486 ;; after a paren/brace/bracket recorded in the cache, if possible, otherwise
2487 ;; return the earliest position in the accessible region which isn't within
2488 ;; a literal. If the visible portion of the buffer is entirely within a
2489 ;; literal, return NIL.
2491 ;(while (>= (or (c-state-cache-top-lparen c) 1) here)
2507 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2508 ;; Variables which keep track of preprocessor constructs.
2517 ;; These are the limits of the macro containing point at the previous call of
2518 ;; `c-parse-state', or nil.
2520 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2521 ;; Defuns which analyze the buffer, yet don't change `c-state-cache'.
2523 ;; Return the position of the opening paren/brace/bracket before HERE- which
2524 ;; matches the outermost close p/b/b between HERE+ and TOP. Except when
2525 ;; there's a macro, HERE- and HERE+ are the same. Like this:
2526 ;;
2527 ;; ............................................
2528 ;; | |
2529 ;; ( [ ( .........#macro.. ) ( ) ] )
2530 ;; ^ ^ ^ ^
2531 ;; | | | |
2532 ;; return HERE- HERE+ TOP
2533 ;;
2534 ;; If there aren't enough opening paren/brace/brackets, return the position
2535 ;; of the outermost one found, or HERE- if there are none. If there are no
2536 ;; closing p/b/bs between HERE+ and TOP, return HERE-. HERE-/+ and TOP
2537 ;; must not be inside literals. Only the accessible portion of the buffer
2538 ;; will be scanned.
2540 ;; PART 1: scan from `here+' up to `top', accumulating ")"s which enclose
2541 ;; `here'. Go round the next loop each time we pass over such a ")". These
2542 ;; probably match "("s before `here-'.
2554 ;; PART 2: Scan back before `here-' searching for the "("s
2555 ;; matching/mismatching the ")"s found above. We only need to direct the
2556 ;; caller to scan when we've encountered unmatched right parens.
2565 pos))
2568 ;; Determine the scanning strategy for adjusting `c-parse-state', attempting
2569 ;; to minimize the amount of scanning. HERE is the pertinent position in
2570 ;; the buffer, GOOD-POS is a position where `c-state-cache' (possibly with
2571 ;; its head trimmed) is known to be good, or nil if there is no such
2572 ;; position.
2573 ;;
2574 ;; The return value is a list, one of the following:
2575 ;;
2576 ;; o - ('forward START-POINT) - scan forward from START-POINT,
2577 ;; which is not less than the highest position in `c-state-cache' below HERE,
2578 ;; which is after GOOD-POS.
2579 ;; o - ('backward nil) - scan backwards (from HERE).
2580 ;; o - ('back-and-forward START-POINT) - like 'forward, but when HERE is earlier
2581 ;; than GOOD-POS.
2582 ;; o - ('IN-LIT nil) - point is inside the literal containing point-min.
2584 strategy ; 'forward, 'backward, or 'IN-LIT.
2585 start-point)
2597 start-point cache-pos)))
2601 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
2602 ;; Routines which change `c-state-cache' and associated values.
2604 ;; The region (more precisely, point-min) has changed since we
2605 ;; calculated `c-state-cache'. Amend `c-state-cache' accordingly.
2607 ;; If point-min has MOVED BACKWARDS then we drop the state completely.
2608 ;; It would be possible to do a better job here and recalculate the top
2609 ;; only.
2613 c-state-cache-good-pos c-state-min-scan-pos
2614 c-state-brace-pair-desert nil))
2616 ;; point-min has MOVED FORWARD.
2618 ;; Is the new point-min inside a (different) literal?
2623 ;; Cut off a bit of the tail from `c-state-cache'.
2625 pa)
2633 c-state-cache-good-pos c-state-min-scan-pos)
2636 )))
2641 ;; If there is a brace pair preceding FROM in the buffer, at the same level
2642 ;; of nesting (not necessarily immediately preceding), push a cons onto
2643 ;; `c-state-cache' to represent it. FROM must not be inside a literal. If
2644 ;; UPPER-LIM is non-nil, we append the highest brace pair whose "}" is below
2645 ;; UPPER-LIM.
2646 ;;
2647 ;; Return non-nil when this has been done.
2648 ;;
2649 ;; The situation it copes with is this transformation:
2650 ;;
2651 ;; OLD: { (.) {...........}
2652 ;; ^ ^
2653 ;; FROM HERE
2654 ;;
2655 ;; NEW: { {....} (.) {.........
2656 ;; ^ ^ ^
2657 ;; LOWER BRACE PAIR HERE or HERE
2658 ;;
2659 ;; This routine should be fast. Since it can get called a LOT, we maintain
2660 ;; `c-state-brace-pair-desert', a small cache of "failures", such that we
2661 ;; reduce the time wasted in repeated fruitless searches in brace deserts.
2671 ;; Don't start scanning in the middle of a CPP construct unless
2672 ;; it contains HERE - these constructs, in Emacs, are "commented
2673 ;; out" with category properties.
2676 macro-start-or-from
2677 from))
2681 ;; If we're essentially repeating a fruitless search, just give up.
2687 ;; DESERT-LIM. Avoid repeated searching through the cached desert.
2693 ;; CACHE-LIM. This limit will be necessary when an opening
2694 ;; paren at `cache-pos' has just had its matching close paren
2695 ;; inserted into the buffer. `cache-pos' continues to be a
2696 ;; search bound, even though the algorithm below would skip
2697 ;; over the new paren pair.
2706 ;; The top limit is EOB to ensure that `bra' is inside the
2707 ;; accessible part of the buffer at the next scan operation.
2710 ;; In the next pair of nested loops, the inner one moves back past a
2711 ;; pair of (mis-)matching parens or brackets; the outer one moves
2712 ;; back over a sequence of unmatched close brace/paren/bracket each
2713 ;; time round.
2729 ; brace, ignore it.
2732 ;; We've found the desired brace-pair.
2744 ;; We haven't found a brace pair. Record this in the cache.
2747 bra
2752 ;; If BRA+1 is nil, do nothing. Otherwise, BRA+1 is the buffer position
2753 ;; following a {, and that brace has a (mis-)matching } (or ]), and we
2754 ;; "push" "a" brace pair onto `c-state-cache'.
2755 ;;
2756 ;; Here "push" means overwrite the top element if it's itself a brace-pair,
2757 ;; otherwise push it normally.
2758 ;;
2759 ;; The brace pair we push is normally the one surrounding BRA+1, but if the
2760 ;; latter is inside a macro, not being a macro containing
2761 ;; MACRO-START-OR-HERE, we scan backwards through the buffer for a non-macro
2762 ;; base pair. This latter case is assumed to be rare.
2763 ;;
2764 ;; Note: POINT is not preserved in this routine.
2774 c-state-cache)))
2775 ;; N.B. This defsubst codes one method for the simple, normal case,
2776 ;; and a more sophisticated, slower way for the general case. Don't
2777 ;; eliminate this defsubst - it's a speed optimization.
2781 ;; Scan the buffer from FROM to HERE, adding elements into `c-state-cache'
2782 ;; for braces etc. Return a candidate for `c-state-cache-good-pos'.
2783 ;;
2784 ;; FROM must be after the latest brace/paren/bracket in `c-state-cache', if
2785 ;; any. Typically, it is immediately after it. It must not be inside a
2786 ;; literal.
2792 here)))
2795 ; Is actually the pos. to scan for a (/{/[ from,
2796 ; which sometimes is after a silly )/}/].
2799 ; good-pos.
2807 ;; Each time round the following loop, we enter a successively deeper
2808 ;; level of brace/paren nesting. (Except sometimes we "continue at
2809 ;; the existing level".) `pa+1' is a pos inside an opening
2810 ;; brace/paren/bracket, usually just after it.
2813 ;; Each time round the next loop moves forward over an opening then
2814 ;; a closing brace/bracket/paren. This loop is white hot, so it
2815 ;; plays ugly tricks to go fast. DON'T PUT ANYTHING INTO THIS
2816 ;; LOOP WHICH ISN'T ABSOLUTELY NECESSARY!!! It terminates when a
2817 ;; call of `scan-lists' signals an error, which happens when there
2818 ;; are no more b/b/p's to scan.
2829 ;; We've just entered a deeper nesting level.
2831 ;; Insert the brace pair (if present) and the single open
2832 ;; paren/brace/bracket into `c-state-cache' It cannot be
2833 ;; inside a macro, except one around point, because of what
2834 ;; `c-neutralize-syntax-in-CPP' has done.
2836 ;; Insert the opening brace/bracket/paren position.
2838 ;; Clear admin stuff for the next more nested part of the scan.
2842 ;; All open p/b/b's at this nesting level, if any, have probably
2843 ;; been closed by matching/mismatching ones. We're probably
2844 ;; finished - we just need to check for having found an
2845 ;; unmatched )/}/], which we ignore. Such a )/}/] can't be in a
2846 ;; macro, due the action of `c-neutralize-syntax-in-CPP'.
2849 ;; Record the final, innermost, brace-pair if there is one.
2852 ;; Determine a good pos
2860 here-bol))
2869 ;; Remove stale entries from the `c-cache-state', i.e. those which will
2870 ;; not be in it when it is amended for position HERE. This may involve
2871 ;; replacing a CONS element for a brace pair containing HERE with its car.
2872 ;; Additionally, the "outermost" open-brace entry before HERE will be
2873 ;; converted to a cons if the matching close-brace is below HERE.
2874 ;;
2875 ;; START-POINT is a "maximal" "safe position" - there must be no open
2876 ;; parens/braces/brackets between START-POINT and HERE.
2877 ;;
2878 ;; As a second thing, calculate the result of parse-partial-sexp at
2879 ;; PPS-POINT, w.r.t. START-POINT. The motivation here is that
2880 ;; `c-state-cache-good-pos' may become PPS-POINT, but the caller may need to
2881 ;; adjust it to get outside a string/comment. (Sorry about this! The code
2882 ;; needs to be FAST).
2883 ;;
2884 ;; Return a list (GOOD-POS SCAN-BACK-POS CONS-SEPARATED PPS-STATE), where
2885 ;; o - GOOD-POS is a position where the new value `c-state-cache' is known
2886 ;; to be good (we aim for this to be as high as possible);
2887 ;; o - SCAN-BACK-POS, if not nil, indicates there may be a brace pair
2888 ;; preceding POS which needs to be recorded in `c-state-cache'. It is a
2889 ;; position to scan backwards from. It is the position of the "{" of the
2890 ;; last element to be removed from `c-state-cache', when that elt is a
2891 ;; cons, otherwise nil.
2892 ;; o - CONS-SEPARATED is t when a cons element in `c-state-cache' has been
2893 ;; replaced by its car because HERE lies inside the brace pair represented
2894 ;; by the cons.
2895 ;; o - PPS-STATE is the parse-partial-sexp state at PPS-POINT.
2905 ; start-point or nil
2912 ; HERE), or nil.
2918 pps-state ; Will be 9 or 10 elements long.
2919 pos
2920 upper-lim ; ,beyond which `c-state-cache' entries are removed
2921 scan-back-pos
2922 cons-separated
2923 pair-beg pps-point-state target-depth)
2925 ;; Remove entries beyond HERE. Also remove any entries inside
2926 ;; a macro, unless HERE is in the same macro.
2931 here
2937 ;; If `upper-lim' is inside the last recorded brace pair, remove its
2938 ;; RBrace and indicate we'll need to search backwards for a previous
2939 ;; brace pair.
2945 cons-separated t))
2947 ;; The next loop jumps forward out of a nested level of parens each
2948 ;; time round; the corresponding elements in `c-state-cache' are
2949 ;; removed. `pos' is just after the brace-pair or the open paren at
2950 ;; (car c-state-cache). There can be no open parens/braces/brackets
2951 ;; between `start-point'/`start-point-actual-macro-start' and HERE,
2952 ;; due to the interface spec to this function.
2955 in-macro-start)))
2957 ; marked by a `category' text property.
2958 start-point))
2969 ;; Do nothing when we've merely reached pps-point.
2970 )
2972 ;; Scan!
2976 target-depth
2977 nil pps-state))
2987 ;; We've just moved out of the paren pair containing the brace-pair
2988 ;; at (car c-state-cache). `pair-beg' is where the open paren is,
2989 ;; and is potentially where the open brace of a cons in
2990 ;; c-state-cache will be.
2996 ; containing Lparen
3000 ; together with enclosed brace pair.
3001 ;; (t nil) ; Ignore an unmated Rparen.
3002 )))
3006 nil nil ; TARGETDEPTH, STOPBEFORE
3007 pps-state)))
3009 ;; If the last paren pair we moved out of was actually a brace pair,
3010 ;; insert it into `c-state-cache'.
3015 c-state-cache)))
3020 ;; Strip stale elements of `c-state-cache' by moving backwards through the
3021 ;; buffer, and inform the caller of the scenario detected.
3022 ;;
3023 ;; HERE is the position we're setting `c-state-cache' for.
3024 ;; CACHE-POS (a locally bound variable) is just after the latest recorded
3025 ;; position in `c-state-cache' before HERE, or a position at or near
3026 ;; point-min which isn't in a literal.
3027 ;;
3028 ;; This function must only be called only when (> `c-state-cache-good-pos'
3029 ;; HERE). Usually the gap between CACHE-POS and HERE is large. It is thus
3030 ;; optimized to eliminate (or minimize) scanning between these two
3031 ;; positions.
3032 ;;
3033 ;; Return a three element list (GOOD-POS SCAN-BACK-POS FWD-FLAG), where:
3034 ;; o - GOOD-POS is a "good position", where `c-state-cache' is valid, or
3035 ;; could become so after missing elements are inserted into
3036 ;; `c-state-cache'. This is JUST AFTER an opening or closing
3037 ;; brace/paren/bracket which is already in `c-state-cache' or just before
3038 ;; one otherwise. exceptionally (when there's no such b/p/b handy) the BOL
3039 ;; before `here''s line, or the start of the literal containing it.
3040 ;; o - SCAN-BACK-POS, if non-nil, indicates there may be a brace pair
3041 ;; preceding POS which isn't recorded in `c-state-cache'. It is a position
3042 ;; to scan backwards from.
3043 ;; o - FWD-FLAG, if non-nil, indicates there may be parens/braces between
3044 ;; POS and HERE which aren't recorded in `c-state-cache'.
3045 ;;
3046 ;; The comments in this defun use "paren" to mean parenthesis or square
3047 ;; bracket (as contrasted with a brace), and "(" and ")" likewise.
3048 ;;
3049 ;; . {..} (..) (..) ( .. { } ) (...) ( .... . ..)
3050 ;; | | | | | |
3051 ;; CP E here D C good
3054 pa ren ; positions of "(" and ")"
3055 dropped-cons ; whether the last element dropped from `c-state-cache'
3056 ; was a cons (representing a brace-pair)
3057 good-pos ; see above.
3058 lit ; (START . END) of a literal containing some point.
3059 here-lit-start here-lit-end ; bounds of literal containing `here'
3060 ; or `here' itself.
3065 ;; Remove completely irrelevant entries from `c-state-cache'.
3071 ;; At this stage, (> pos here);
3072 ;; (< (c-state-cache-top-lparen) here) (or is nil).
3077 ;; CASE 1: The top of the cache is a brace pair which now encloses
3078 ;; `here'. As good-pos, return the address. of the "{". Since we've no
3079 ;; knowledge of what's inside these braces, we have no alternative but
3080 ;; to direct the caller to scan the buffer from the opening brace.
3084 ; entry into a { entry, so the caller needs to
3085 ; search for a brace pair before the {.
3087 ;; `here' might be inside a literal. Check for this.
3092 ;; Has `here' just "newly entered" a macro?
3105 ;; `here' might be nested inside any depth of parens (or brackets but
3106 ;; not braces). Scan backwards to find the outermost such opening
3107 ;; paren, if there is one. This will be the scan position to return.
3114 ;; CASE 2: Address of outermost ( or [ which now encloses `here', but
3115 ;; didn't enclose the (previous) `c-state-cache-good-pos'. If there is
3116 ;; a brace pair preceding this, it will already be in `c-state-cache',
3117 ;; unless there was a brace pair after it, i.e. there'll only be one to
3118 ;; scan for if we've just deleted one.
3121 ;; `here' isn't enclosed in a (previously unrecorded) bracket/paren.
3122 ;; Further forward scanning isn't needed, but we still need to find a
3123 ;; GOOD-POS. Step out of all enclosing "("s on HERE's line.
3133 ;; CASE 3: After a }/)/] before `here''s BOL.
3137 ;; CASE 4; Best of a bad job: BOL before `here-bol', or beginning of
3138 ;; literal containing it.
3143 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3144 ;; Externally visible routines.
3148 c-state-cache-good-pos 1
3149 c-state-nonlit-pos-cache nil
3150 c-state-nonlit-pos-cache-limit 1
3151 c-state-semi-nonlit-pos-cache nil
3152 c-state-semi-nonlit-pos-cache-limit 1
3153 c-state-brace-pair-desert nil
3154 c-state-point-min 1
3155 c-state-point-min-lit-type nil
3156 c-state-point-min-lit-start nil
3157 c-state-min-scan-pos 1
3158 c-state-old-cpp-beg nil
3159 c-state-old-cpp-end nil)
3162 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3163 ;; Debugging routines to dump `c-state-cache' in a "replayable" form.
3164 ;; (defmacro c-sc-de (elt) ; "c-state-cache-dump-element"
3165 ;; `(format ,(concat "(setq " (symbol-name elt) " %s) ") ,elt))
3166 ;; (defmacro c-sc-qde (elt) ; "c-state-cache-quote-dump-element"
3167 ;; `(format ,(concat "(setq " (symbol-name elt) " '%s) ") ,elt))
3168 ;; (defun c-state-dump ()
3169 ;; ;; For debugging.
3170 ;; ;(message
3171 ;; (concat
3172 ;; (c-sc-qde c-state-cache)
3173 ;; (c-sc-de c-state-cache-good-pos)
3174 ;; (c-sc-qde c-state-nonlit-pos-cache)
3175 ;; (c-sc-de c-state-nonlit-pos-cache-limit)
3176 ;; (c-sc-qde c-state-brace-pair-desert)
3177 ;; (c-sc-de c-state-point-min)
3178 ;; (c-sc-de c-state-point-min-lit-type)
3179 ;; (c-sc-de c-state-point-min-lit-start)
3180 ;; (c-sc-de c-state-min-scan-pos)
3181 ;; (c-sc-de c-state-old-cpp-beg)
3182 ;; (c-sc-de c-state-old-cpp-end)))
3183 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
3186 ;; Invalidate all info on `c-state-cache' that applies to the buffer at HERE
3187 ;; or higher and set `c-state-cache-good-pos' accordingly. The cache is
3188 ;; left in a consistent state.
3189 ;;
3190 ;; This is much like `c-whack-state-after', but it never changes a paren
3191 ;; pair element into an open paren element. Doing that would mean that the
3192 ;; new open paren wouldn't have the required preceding paren pair element.
3193 ;;
3194 ;; This function is called from c-after-change.
3196 ;; The caches of non-literals:
3197 ;; Note that we use "<=" for the possibility of the second char of a two-char
3198 ;; comment opener being typed; this would invalidate any cache position at
3199 ;; HERE.
3205 ;; `c-state-cache':
3206 ;; Case 1: if `here' is in a literal containing point-min, everything
3207 ;; becomes (or is already) nil.
3211 c-state-cache-good-pos nil
3212 c-state-min-scan-pos nil)
3214 ;; Truncate `c-state-cache' and set `c-state-cache-good-pos' to a value
3215 ;; below `here'. To maintain its consistency, we may need to insert a new
3216 ;; brace pair.
3219 too-high-pa ; recorded {/(/[ next above here, or nil.
3220 dropped-cons ; was the last removed element a brace pair?
3221 pa)
3222 ;; The easy bit - knock over-the-top bits off `c-state-cache'.
3229 ;; Do we need to add in an earlier brace pair, having lopped one off?
3236 ;; The brace-pair desert marker:
3244 ;; Find and record all noteworthy parens between some good point earlier in
3245 ;; the file and point. That good point is at least the beginning of the
3246 ;; top-level construct we are in, or the beginning of the preceding
3247 ;; top-level construct if we aren't in one.
3248 ;;
3249 ;; The returned value is a list of the noteworthy parens with the last one
3250 ;; first. If an element in the list is an integer, it's the position of an
3251 ;; open paren (of any type) which has not been closed before the point. If
3252 ;; an element is a cons, it gives the position of a closed BRACE paren
3253 ;; pair[*]; the car is the start brace position and the cdr is the position
3254 ;; following the closing brace. Only the last closed brace paren pair
3255 ;; before each open paren and before the point is recorded, and thus the
3256 ;; state never contains two cons elements in succession. When a close brace
3257 ;; has no matching open brace (e.g., the matching brace is outside the
3258 ;; visible region), it is not represented in the returned value.
3259 ;;
3260 ;; [*] N.B. The close "brace" might be a mismatching close bracket or paren.
3261 ;; This defun explicitly treats mismatching parens/braces/brackets as
3262 ;; matching. It is the open brace which makes it a "brace" pair.
3263 ;;
3264 ;; If POINT is within a macro, open parens and brace pairs within
3265 ;; THIS macro MIGHT be recorded. This depends on whether their
3266 ;; syntactic properties have been suppressed by
3267 ;; `c-neutralize-syntax-in-CPP'. This might need fixing (2008-12-11).
3268 ;;
3269 ;; Currently no characters which are given paren syntax with the
3270 ;; syntax-table property are recorded, i.e. angle bracket arglist
3271 ;; parens are never present here. Note that this might change.
3272 ;;
3273 ;; BUG: This function doesn't cope entirely well with unbalanced
3274 ;; parens in macros. (2008-12-11: this has probably been resolved
3275 ;; by the function `c-neutralize-syntax-in-CPP'.) E.g. in the
3276 ;; following case the brace before the macro isn't balanced with the
3277 ;; one after it:
3278 ;;
3279 ;; {
3280 ;; #define X {
3281 ;; }
3282 ;;
3283 ;; Note to maintainers: this function DOES get called with point
3284 ;; within comments and strings, so don't assume it doesn't!
3285 ;;
3286 ;; This function might do hidden buffer changes.
3289 open-paren-in-column-0-is-defun-start
3290 strategy ; 'forward, 'backward etc..
3291 ;; Candidate positions to start scanning from:
3292 cache-pos ; highest position below HERE already existing in
3293 ; cache (or 1).
3294 good-pos
3295 start-point ; (when scanning forward) a place below HERE where there
3296 ; are no open parens/braces between it and HERE.
3297 bopl-state
3298 res
3299 cons-separated
3301 ;; If POINT-MIN has changed, adjust the cache
3305 ;; Strategy?
3310 ;; SCAN!
3318 ; start-point)
3328 good-pos)))
3340 good-pos)))
3344 c-state-cache-good-pos nil))))
3346 c-state-cache)
3349 ;; This is a wrapper over `c-invalidate-state-cache-1'.
3350 ;;
3351 ;; It suppresses the syntactic effect of the < and > (template) brackets and
3352 ;; of all parens in preprocessor constructs, except for any such construct
3353 ;; containing point. We can then call `c-invalidate-state-cache-1' without
3354 ;; worrying further about macros and template delimiters.
3359 c-state-old-cpp-beg
3366 ;; If PLACE is non-nil, return a marker marking it, otherwise nil.
3367 ;; We (re)use MARKER.
3373 ;; This is a wrapper over `c-parse-state-1'. See that function for a
3374 ;; description of the functionality and return value.
3375 ;;
3376 ;; It suppresses the syntactic effect of the < and > (template) brackets and
3377 ;; of all parens in preprocessor constructs, except for any such construct
3378 ;; containing point. We can then call `c-parse-state-1' without worrying
3379 ;; further about macros and template delimiters.
3386 here-cpp-beg)
3388 ;; FIXME!!! Put in a `condition-case' here to protect the integrity of the
3389 ;; subsystem.
3394 here-cpp-beg here-cpp-end
3400 c-state-old-cpp-end
3403 ;; Debug tool to catch cache inconsistencies. This is called from
3404 ;; 000tests.el.
3422 val))))
3424 c-state-cache-good-pos
3425 c-state-nonlit-pos-cache
3426 c-state-nonlit-pos-cache-limit
3427 c-state-semi-nonlit-pos-cache
3428 c-state-semi-nonlit-pos-cache-limit
3429 c-state-brace-pair-desert
3430 c-state-point-min
3431 c-state-point-min-lit-type
3432 c-state-point-min-lit-start
3433 c-state-min-scan-pos
3434 c-state-old-cpp-beg
3435 c-state-old-cpp-end
3436 c-parse-state-point))))
3454 conses-not-ok))
3471 ;; The cache can actually go further back due to the ad-hoc way
3472 ;; the first paren is found, so try to whack off a bit of its
3473 ;; start before complaining.
3474 ;; (save-excursion
3475 ;; (goto-char (or (c-least-enclosing-brace res2) (point)))
3476 ;; (c-beginning-of-defun-1)
3477 ;; (while (not (or (bobp) (eq (char-after) ?{)))
3478 ;; (c-beginning-of-defun-1))
3479 ;; (unless (equal (c-whack-state-before (point) res1) res2)
3480 ;; (message (concat "c-parse-state inconsistency at %s: "
3481 ;; "using cache: %s, from scratch: %s")
3482 ;; here res1 res2)))
3485 here res1 res2)
3491 here res1)
3496 res2 ; res1 correct a cascading series of errors ASAP
3497 ))
3503 'c-debug-parse-state
3511 \f
3513 ;; Whack off any state information from PAREN-STATE which lies
3514 ;; before BUFPOS. Not destructive on PAREN-STATE.
3517 car)
3528 ;; Whack off any state information from PAREN-STATE which lies at or
3529 ;; after BUFPOS. Not destructive on PAREN-STATE.
3534 ;; just check the car, because in a balanced brace
3535 ;; expression, it must be impossible for the corresponding
3536 ;; close brace to be before point, but the open brace to
3537 ;; be after.
3539 nil ; whack it off
3541 ;; its possible that the open brace is before
3542 ;; bufpos, but the close brace is after. In that
3543 ;; case, convert this to a non-cons element. The
3544 ;; rest of the state is before bufpos, so we're
3545 ;; done.
3547 ;; we know that both the open and close braces are
3548 ;; before bufpos, so we also know that everything else
3549 ;; on state is before bufpos.
3552 nil ; whack it off
3553 ;; it's before bufpos, so everything else should too.
3556 nil)))
3559 ;; Return the bufpos of the innermost enclosing open paren before
3560 ;; bufpos, or nil if none was found.
3570 enclosingp))
3573 ;; Return the bufpos of the outermost enclosing open paren, or nil
3574 ;; if none was found.
3581 pos))
3584 ;; Return the closest "safe" position recorded on PAREN-STATE that
3585 ;; is higher up than BUFPOS. Return nil if PAREN-STATE doesn't
3586 ;; contain any. Return nil if BUFPOS is nil, which is useful to
3587 ;; find the closest limit before a given limit that might be nil.
3588 ;;
3589 ;; A "safe" position is a position at or after a recorded open
3590 ;; paren, or after a recorded close paren. The returned position is
3591 ;; thus either the first position after a close brace, or the first
3592 ;; position after an enclosing paren, or at the enclosing paren in
3593 ;; case BUFPOS is immediately after it.
3603 ;; See below.
3606 ;; elem is the position at and not after the opening paren, so
3607 ;; we can go forward one more step unless it's equal to
3608 ;; bufpos. This is useful in some cases avoid an extra paren
3609 ;; level between the safe position and bufpos.
3614 ;; This is used for `font-lock-beginning-of-syntax-function'. It
3615 ;; goes to the closest previous point that is known to be outside
3616 ;; any string literal or comment. `c-state-cache' is used if it has
3617 ;; a position in the vicinity.
3619 elem
3622 ;; Note: Similar code in `c-safe-position'. The
3623 ;; difference is that we accept a safe position at
3624 ;; the point and don't bother to go forward past open
3625 ;; parens.
3640 ;; The position is far back. Try `c-beginning-of-defun-1'
3641 ;; (although we can't be entirely sure it will go to a position
3642 ;; outside a comment or string in current emacsen). FIXME:
3643 ;; Consult `syntax-ppss' here.
3648 \f
3649 ;; Tools for scanning identifiers and other tokens.
3652 "Return non-nil if the point is on or directly after an identifier.
3653 Keywords are recognized and not considered identifiers. If an
3654 identifier is detected, the returned value is its starting position.
3655 If an identifier ends at the point and another begins at it \(can only
3656 happen in Pike) then the point for the preceding one is returned.
3658 Note that this function might do hidden buffer changes. See the
3659 comment at the start of cc-engine.el for more info."
3661 ;; FIXME: Shouldn't this function handle "operator" in C++?
3668 ;; Check for a normal (non-keyword) identifier.
3674 ;; Handle the `<operator> syntax in Pike.
3678 t
3685 ;; Handle the "operator +" syntax in C++.
3702 )))
3705 ;; If the point is at the end of a symbol then skip backward to the
3706 ;; beginning of it. Don't move otherwise. Return non-nil if point
3707 ;; moved.
3708 ;;
3709 ;; This function might do hidden buffer changes.
3712 ;; Handle the `<operator> syntax in Pike.
3718 t
3720 nil)))))
3723 ;; Move to the beginning of the current token. Do not move if not
3724 ;; in the middle of one. BACK-LIMIT may be used to bound the
3725 ;; backward search; if given it's assumed to be at the boundary
3726 ;; between two tokens. Return non-nil if the point is moved, nil
3727 ;; otherwise.
3728 ;;
3729 ;; This function might do hidden buffer changes.
3736 ;; `c-nonsymbol-token-regexp' should always match
3737 ;; since we've skipped backward over punctuation
3738 ;; or paren syntax, but consume one char in case
3739 ;; it doesn't so that we don't leave point before
3740 ;; some earlier incorrect token.
3747 ;; Move to the end of the current token. Do not move if not in the
3748 ;; middle of one. BACK-LIMIT may be used to bound the backward
3749 ;; search; if given it's assumed to be at the boundary between two
3750 ;; tokens. Return non-nil if the point is moved, nil otherwise.
3751 ;;
3752 ;; This function might do hidden buffer changes.
3760 ;; `c-nonsymbol-token-regexp' should always match since
3761 ;; we've skipped backward over punctuation or paren
3762 ;; syntax, but move forward in case it doesn't so that
3763 ;; we don't leave point earlier than we started with.
3779 "Move forward by tokens.
3780 A token is defined as all symbols and identifiers which aren't
3782 treated properly). Point is always either left at the beginning of a
3783 token or not moved at all. COUNT specifies the number of tokens to
3784 move; a negative COUNT moves in the opposite direction. A COUNT of 0
3785 moves to the next token beginning only if not already at one. If
3786 BALANCED is true, move over balanced parens, otherwise move into them.
3787 Also, if BALANCED is true, never move out of an enclosing paren.
3789 LIMIT sets the limit for the movement and defaults to the point limit.
3790 The case when LIMIT is set in the middle of a token, comment or macro
3791 is handled correctly, i.e. the point won't be left there.
3793 Return the number of tokens left to move \(positive or negative). If
3794 BALANCED is true, a move over a balanced paren counts as one. Note
3795 that if COUNT is 0 and no appropriate token beginning is found, 1 will
3796 be returned. Thus, a return value of 0 guarantees that point is at
3797 the requested position and a return value less \(without signs) than
3798 COUNT guarantees that point is at the beginning of some token.
3800 Note that this function might do hidden buffer changes. See the
3801 comment at the start of cc-engine.el for more info."
3808 c-jump-syntax-balanced
3809 c-jump-syntax-unbalanced))
3814 ;; If count is zero we should jump if in the middle of a token.
3821 ;; Skip whitespace. Count this as a move if we did in
3822 ;; fact move.
3826 ;; Moved out of bounds. Make sure the returned count isn't zero.
3831 ;; Use `condition-case' to avoid having the limit tests
3832 ;; inside the loop.
3840 t)
3843 t)
3844 ;; `c-nonsymbol-token-regexp' above should always
3845 ;; match if there are correct tokens. Try to
3846 ;; widen to see if the limit was set in the
3847 ;; middle of one, else fall back to treating
3848 ;; the offending thing as a one character token.
3853 nil)
3856 t))))
3866 count)))
3869 "Move backward by tokens.
3870 See `c-forward-token-2' for details."
3878 c-jump-syntax-balanced
3879 c-jump-syntax-unbalanced))
3883 ;; The count is zero so try to skip to the beginning of the
3884 ;; current token.
3888 ;; The limit is inside the same token, so return 1.
3891 ;; We're not in the middle of a token. If there's
3892 ;; whitespace after the point then we must move backward,
3893 ;; so set count to 1 in that case.
3895 ;; If we're looking at a '#' that might start a cpp
3896 ;; directive then we have to do a more elaborate check.
3909 ;; Use `condition-case' to avoid having to check for buffer
3910 ;; limits in `backward-char', `scan-sexps' and `goto-char' below.
3919 ;; This can be very inefficient if there's a long
3920 ;; sequence of operator tokens without any separation.
3921 ;; That doesn't happen in practice, anyway.
3931 count)))
3934 "Like `c-forward-token-2' but doesn't treat multicharacter operator
3936 characters are jumped over character by character. This function is
3937 for compatibility only; it's only a wrapper over `c-forward-token-2'."
3942 "Like `c-backward-token-2' but doesn't treat multicharacter operator
3944 characters are jumped over character by character. This function is
3945 for compatibility only; it's only a wrapper over `c-backward-token-2'."
3949 \f
3950 ;; Tools for doing searches restricted to syntactically relevant text.
3953 paren-level not-inside-token
3954 lookbehind-submatch)
3955 "Like `re-search-forward', but only report matches that are found
3956 in syntactically significant text. I.e. matches in comments, macros
3957 or string literals are ignored. The start point is assumed to be
3958 outside any comment, macro or string literal, or else the content of
3959 that region is taken as syntactically significant text.
3961 If PAREN-LEVEL is non-nil, an additional restriction is added to
3962 ignore matches in nested paren sexps. The search will also not go
3963 outside the current list sexp, which has the effect that if the point
3964 should be moved to BOUND when no match is found \(i.e. NOERROR is
3965 neither nil nor t), then it will be at the closing paren if the end of
3966 the current list sexp is encountered first.
3968 If NOT-INSIDE-TOKEN is non-nil, matches in the middle of tokens are
3969 ignored. Things like multicharacter operators and special symbols
3971 constants.
3973 If LOOKBEHIND-SUBMATCH is non-nil, it's taken as a number of a
3974 subexpression in REGEXP. The end of that submatch is used as the
3975 position to check for syntactic significance. If LOOKBEHIND-SUBMATCH
3976 isn't used or if that subexpression didn't match then the start
3978 subexpression is never tested before the starting position, so it
3982 subexpression can match the end of nonwhite syntactic whitespace,
3983 i.e. the end of comments or cpp directives. This since the function
3984 skips over such things before resuming the search. It's on the other
3986 matches syntactic whitespace.
3988 Bug: Unbalanced parens inside cpp directives are currently not handled
3989 correctly \(i.e. they don't get ignored as they should) when
3990 PAREN-LEVEL is set.
3992 Note that this function might do hidden buffer changes. See the
3993 comment at the start of cc-engine.el for more info."
3998 ;;(message "c-syntactic-re-search-forward %s %s %S" (point) bound regexp)
4001 tmp
4002 ;; Start position for the last search.
4003 search-pos
4004 ;; The `parse-partial-sexp' state between the start position
4005 ;; and the point.
4006 state
4007 ;; The current position after the last state update. The next
4008 ;; `parse-partial-sexp' continues from here.
4010 ;; The position at which to check the state and the state
4011 ;; there. This is separate from `state-pos' since we might
4012 ;; need to back up before doing the next search round.
4013 check-pos check-state
4014 ;; Last position known to end a token.
4016 ;; Set when a valid match is found.
4017 found)
4035 state-pos check-pos paren-level nil state))
4037 check-state state))
4039 ;; NOTE: If we got a look behind subexpression and get
4040 ;; an insignificant match in something that isn't
4041 ;; syntactic whitespace (i.e. strings or in nested
4042 ;; parentheses), then we can never skip more than a
4043 ;; single character from the match start position
4044 ;; (i.e. `state-pos' here) before continuing the
4045 ;; search. That since the look behind subexpression
4046 ;; might match the end of the insignificant region in
4047 ;; the next search.
4051 ;; Match inside a line comment. Skip to eol. Use
4052 ;; `re-search-forward' instead of `skip-chars-forward' to get
4053 ;; the right bound behavior.
4057 ;; Match inside a block comment. Skip to the '*/'.
4064 ;; Match in the middle of the opener of a block or line
4065 ;; comment.
4070 ;; The last `parse-partial-sexp' above might have
4071 ;; stopped short of the real check position if the end
4072 ;; of the current sexp was encountered in paren-level
4073 ;; mode. The checks above are always false in that
4074 ;; case, and since they can do better skipping in
4075 ;; lookbehind-submatch mode, we do them before
4076 ;; checking the paren level.
4080 ;; Check the paren level first since we're short of the
4081 ;; syntactic checking position if the end of the
4082 ;; current sexp was encountered by `parse-partial-sexp'.
4085 ;; Inside a nested paren sexp.
4087 ;; See the NOTE above.
4089 ;; Skip out of the paren quickly.
4093 ;; Have exited the current paren sexp.
4096 ;; The last `parse-partial-sexp' call above
4097 ;; has left us just after the closing paren
4098 ;; in this case, so we can modify the bound
4099 ;; to leave the point at the right position
4100 ;; upon return.
4102 nil)
4106 ;; Match inside a string.
4109 ;; See the NOTE above.
4111 ;; Skip to the end of the string before continuing.
4120 continue)))
4125 ;; Match inside a macro. Skip to the end of it.
4133 (< check-pos
4139 ;; Inside a token.
4141 ;; See the NOTE above.
4146 ;; A real match.
4148 nil)))
4150 ;; Should loop to search again, but take care to avoid
4151 ;; looping on the same spot.
4155 nil
4158 t))))
4164 ;;(message "c-syntactic-re-search-forward done %s" (or (match-end 0) (point)))
4171 ;; Search failed. Set point as appropriate.
4175 nil)))
4180 ;; Return the start of the literal point is in, or nil.
4181 ;; We read and write the variables `safe-pos', `safe-pos-list', `state'
4182 ;; bound in the caller.
4184 ;; Use `parse-partial-sexp' from a safe position down to the point to check
4185 ;; if it's outside comments and strings.
4188 ;; Pick a safe position as close to the point as possible.
4189 ;;
4190 ;; FIXME: Consult `syntax-ppss' here if our cache doesn't give a good
4191 ;; position.
4204 ;; Cache positions along the way to use if we have to back up more. We
4205 ;; cache every closing paren on the same level. If the paren cache is
4206 ;; relevant in this region then we're typically already on the same
4207 ;; level as the target position. Note that we might cache positions
4208 ;; after opening parens in case safe-pos is in a nested list. That's
4209 ;; both uncommon and harmless.
4217 ;; If the state contains the start of the containing sexp we cache that
4218 ;; position too, so that parse-partial-sexp in the next run has a bigger
4219 ;; chance of starting at the same level as the target position and thus
4220 ;; will get more good safe positions into the list.
4226 ;; Inside string or comment. Continue search at the
4227 ;; beginning of it.
4231 "Like `skip-chars-backward' but only look at syntactically relevant chars,
4232 i.e. don't stop at positions inside syntactic whitespace or string
4233 literals. Preprocessor directives are also ignored, with the exception
4234 of the one that the point starts within, if any. If LIMIT is given,
4235 it's assumed to be at a syntactically relevant position.
4237 If PAREN-LEVEL is non-nil, the function won't stop in nested paren
4238 sexps, and the search will also not go outside the current paren sexp.
4239 However, if LIMIT or the buffer limit is reached inside a nested paren
4240 then the point will be left at the limit.
4242 Non-nil is returned if the point moved, nil otherwise.
4244 Note that this function might do hidden buffer changes. See the
4245 comment at the start of cc-engine.el for more info."
4248 state-2
4249 ;; A list of syntactically relevant positions in descending
4250 ;; order. It's used to avoid scanning repeatedly over
4251 ;; potentially large regions with `parse-partial-sexp' to verify
4252 ;; each position. Used in `c-ssb-lit-begin'
4253 safe-pos-list
4254 ;; The result from `c-beginning-of-macro' at the start position or the
4255 ;; start position itself if it isn't within a macro. Evaluated on
4256 ;; demand.
4257 start-macro-beg
4258 ;; The earliest position after the current one with the same paren
4259 ;; level. Used only when `paren-level' is set.
4260 lit-beg
4265 ;; The next loop "tries" to find the end point each time round,
4266 ;; loops when it hasn't succeeded.
4272 ;; Don't stop inside a literal.
4275 t)))
4287 ;; Not at the right level.
4290 ;; We stop above if we go out of a paren.
4291 ;; Now check whether it precedes or is
4292 ;; nested in the starting sexp.
4296 pps-end-pos paren-level-pos
4297 nil nil state-2))
4300 ;; We've stopped short of the starting position
4301 ;; so the hit was inside a nested list. Go up
4302 ;; until we are at the right level.
4311 nil)
4312 t))
4315 nil))
4317 ;; The hit was outside the list at the start
4318 ;; position. Go to the start of the list and exit.
4320 nil))
4323 ;; Inside a macro.
4331 t
4333 ;; It's inside the same macro we started in so it's
4334 ;; a relevant match.
4336 nil))))))
4340 ;; Skip syntactic ws afterwards so that we don't stop at the
4341 ;; end of a comment if `skip-chars' is something like "^/".
4345 ;; We might want to extend this with more useful return values in
4346 ;; the future.
4349 ;; The following is an alternative implementation of
4350 ;; `c-syntactic-skip-backward' that uses backward movement to keep
4351 ;; track of the syntactic context. It turned out to be generally
4352 ;; slower than the one above which uses forward checks from earlier
4353 ;; safe positions.
4354 ;;
4355 ;;(defconst c-ssb-stop-re
4356 ;; ;; The regexp matching chars `c-syntactic-skip-backward' needs to
4357 ;; ;; stop at to avoid going into comments and literals.
4358 ;; (concat
4359 ;; ;; Match comment end syntax and string literal syntax. Also match
4360 ;; ;; '/' for block comment endings (not covered by comment end
4361 ;; ;; syntax).
4362 ;; "\\s>\\|/\\|\\s\""
4363 ;; (if (memq 'gen-string-delim c-emacs-features)
4364 ;; "\\|\\s|"
4365 ;; "")
4366 ;; (if (memq 'gen-comment-delim c-emacs-features)
4367 ;; "\\|\\s!"
4368 ;; "")))
4369 ;;
4370 ;;(defconst c-ssb-stop-paren-re
4371 ;; ;; Like `c-ssb-stop-re' but also stops at paren chars.
4372 ;; (concat c-ssb-stop-re "\\|\\s(\\|\\s)"))
4373 ;;
4374 ;;(defconst c-ssb-sexp-end-re
4375 ;; ;; Regexp matching the ending syntax of a complex sexp.
4376 ;; (concat c-string-limit-regexp "\\|\\s)"))
4377 ;;
4378 ;;(defun c-syntactic-skip-backward (skip-chars &optional limit paren-level)
4379 ;; "Like `skip-chars-backward' but only look at syntactically relevant chars,
4380 ;;i.e. don't stop at positions inside syntactic whitespace or string
4381 ;;literals. Preprocessor directives are also ignored. However, if the
4382 ;;point is within a comment, string literal or preprocessor directory to
4383 ;;begin with, its contents is treated as syntactically relevant chars.
4384 ;;If LIMIT is given, it limits the backward search and the point will be
4385 ;;left there if no earlier position is found.
4386 ;;
4387 ;;If PAREN-LEVEL is non-nil, the function won't stop in nested paren
4388 ;;sexps, and the search will also not go outside the current paren sexp.
4389 ;;However, if LIMIT or the buffer limit is reached inside a nested paren
4390 ;;then the point will be left at the limit.
4391 ;;
4392 ;;Non-nil is returned if the point moved, nil otherwise.
4393 ;;
4394 ;;Note that this function might do hidden buffer changes. See the
4395 ;;comment at the start of cc-engine.el for more info."
4396 ;;
4397 ;; (save-restriction
4398 ;; (when limit
4399 ;; (narrow-to-region limit (point-max)))
4400 ;;
4401 ;; (let ((start (point)))
4402 ;; (catch 'done
4403 ;; (while (let ((last-pos (point))
4404 ;; (stop-pos (progn
4405 ;; (skip-chars-backward skip-chars)
4406 ;; (point))))
4407 ;;
4408 ;; ;; Skip back over the same region as
4409 ;; ;; `skip-chars-backward' above, but keep to
4410 ;; ;; syntactically relevant positions.
4411 ;; (goto-char last-pos)
4412 ;; (while (and
4413 ;; ;; `re-search-backward' with a single char regexp
4414 ;; ;; should be fast.
4415 ;; (re-search-backward
4416 ;; (if paren-level c-ssb-stop-paren-re c-ssb-stop-re)
4417 ;; stop-pos 'move)
4418 ;;
4419 ;; (progn
4420 ;; (cond
4421 ;; ((looking-at "\\s(")
4422 ;; ;; `paren-level' is set and we've found the
4423 ;; ;; start of the containing paren.
4424 ;; (forward-char)
4425 ;; (throw 'done t))
4426 ;;
4427 ;; ((looking-at c-ssb-sexp-end-re)
4428 ;; ;; We're at the end of a string literal or paren
4429 ;; ;; sexp (if `paren-level' is set).
4430 ;; (forward-char)
4431 ;; (condition-case nil
4432 ;; (c-backward-sexp)
4433 ;; (error
4434 ;; (goto-char limit)
4435 ;; (throw 'done t))))
4436 ;;
4437 ;; (t
4438 ;; (forward-char)
4439 ;; ;; At the end of some syntactic ws or possibly
4440 ;; ;; after a plain '/' operator.
4441 ;; (let ((pos (point)))
4442 ;; (c-backward-syntactic-ws)
4443 ;; (if (= pos (point))
4444 ;; ;; Was a plain '/' operator. Go past it.
4445 ;; (backward-char)))))
4446 ;;
4447 ;; (> (point) stop-pos))))
4448 ;;
4449 ;; ;; Now the point is either at `stop-pos' or at some
4450 ;; ;; position further back if `stop-pos' was at a
4451 ;; ;; syntactically irrelevant place.
4452 ;;
4453 ;; ;; Skip additional syntactic ws so that we don't stop
4454 ;; ;; at the end of a comment if `skip-chars' is
4455 ;; ;; something like "^/".
4456 ;; (c-backward-syntactic-ws)
4457 ;;
4458 ;; (< (point) stop-pos))))
4459 ;;
4460 ;; ;; We might want to extend this with more useful return values
4461 ;; ;; in the future.
4462 ;; (/= (point) start))))
4464 \f
4465 ;; Tools for handling comments and string literals.
4468 "Return the type of literal point is in, if any.
4469 The return value is `c' if in a C-style comment, `c++' if in a C++
4470 style comment, `string' if in a string literal, `pound' if DETECT-CPP
4471 is non-nil and in a preprocessor line, or nil if somewhere else.
4472 Optional LIM is used as the backward limit of the search. If omitted,
4473 or nil, `c-beginning-of-defun' is used.
4475 The last point calculated is cached if the cache is enabled, i.e. if
4476 `c-in-literal-cache' is bound to a two element vector.
4478 Note that this function might do hidden buffer changes. See the
4479 comment at the start of cc-engine.el for more info."
4490 "Return a cons of the beginning and end positions of the comment or
4491 string surrounding point (including both delimiters), or nil if point
4493 to start parsing from. If NEAR is non-nil, then the limits of any
4495 spaces and tabs between point and the literal. The search for such a
4496 literal is done first in forward direction. If NOT-IN-DELIMITER is
4497 non-nil, the case when point is inside a starting delimiter won't be
4498 recognized. This only has effect for comments which have starting
4499 delimiters with more than one character.
4501 Note that this function might do hidden buffer changes. See the
4502 comment at the start of cc-engine.el for more info."
4518 ;; Search forward for a literal.
4529 ;; Search backward.
4540 ;; Block comment. Due to the nature of line
4541 ;; comments, they will always be covered by the
4542 ;; normal case above.
4545 ;; If LIM is bogus, beg will be bogus.
4549 ))))
4551 ;; In case external callers use this; it did have a docstring.
4555 "If the argument is a cons of two buffer positions (such as returned by
4556 `c-literal-limits'), and that range contains a C++ style line comment,
4557 then an extended range is returned that contains all adjacent line
4558 comments (i.e. all comments that starts in the same column with no
4559 empty lines or non-whitespace characters between them). Otherwise the
4560 argument is returned.
4562 Note that this function might do hidden buffer changes. See the
4563 comment at the start of cc-engine.el for more info."
4574 ;; Got to take care in the backward direction to handle
4575 ;; comments which are preceded by code.
4589 range)
4593 "Convenience function that given the result of `c-literal-limits',
4594 returns nil or the type of literal that the range surrounds, one
4595 of the symbols 'c, 'c++ or 'string. It's much faster than using
4596 `c-in-literal' and is intended to be used when you need both the
4597 type of a literal and its limits.
4599 Note that this function might do hidden buffer changes. See the
4600 comment at the start of cc-engine.el for more info."
4611 range))
4614 ;; Get a "safe place" approximately TRY-SIZE characters before START.
4615 ;; This doesn't preserve point.
4624 ;; Return a buffer position HOW-FAR-BACK non-literal characters from START
4625 ;; (default point). This is done by going back further in the buffer then
4626 ;; searching forward for literals. The position found won't be in a
4627 ;; literal. We start searching for the sought position TRY-SIZE (default
4628 ;; twice HOW-FAR-BACK) bytes back from START. This function must be fast.
4629 ;; :-)
4637 stack elt size
4640 ;; Move forward one literal each time round this loop.
4641 ;; Move forward to the start of a comment or string.
4643 pos
4644 start
4645 nil ; target-depth
4646 nil ; stop-before
4647 s ; state
4650 ;; Gather details of the non-literal-bit - starting pos and size.
4654 pos))
4658 ;; Move forward to the end of the comment/string.
4662 start
4663 nil ; target-depth
4664 nil ; stop-before
4665 s ; state
4669 ;; Now try and find enough non-literal characters recorded on the stack.
4670 ;; Go back one recorded literal each time round this loop.
4672 stack)
4677 ;; Have we found enough yet?
4687 ;; Return a buffer position about HOW-FAR non-literal characters forward
4688 ;; from START-POS (default point), which must not be inside a literal.
4695 ;; Scan over counted characters.
4697 pos
4699 nil ; target-depth
4700 nil ; stop-before
4701 s ; state
4705 ;; Scan over literal characters.
4708 pos
4710 nil ; target-depth
4711 nil ; stop-before
4712 s ; state
4717 \f
4718 ;; `c-find-decl-spots' and accompanying stuff.
4720 ;; Variables used in `c-find-decl-spots' to cache the search done for
4721 ;; the first declaration in the last call. When that function starts,
4722 ;; it needs to back up over syntactic whitespace to look at the last
4723 ;; token before the region being searched. That can sometimes cause
4724 ;; moves back and forth over a quite large region of comments and
4725 ;; macros, which would be repeated for each changed character when
4726 ;; we're called during fontification, since font-lock refontifies the
4727 ;; current line for each change. Thus it's worthwhile to cache the
4728 ;; first match.
4729 ;;
4730 ;; `c-find-decl-syntactic-pos' is a syntactically relevant position in
4731 ;; the syntactic whitespace less or equal to some start position.
4732 ;; There's no cached value if it's nil.
4733 ;;
4734 ;; `c-find-decl-match-pos' is the match position if
4735 ;; `c-find-decl-prefix-search' matched before the syntactic whitespace
4736 ;; at `c-find-decl-syntactic-pos', or nil if there's no such match.
4747 ; (defface c-debug-decl-spot-face
4748 ; '((t (:background "Turquoise")))
4749 ; "Debug face to mark the spots where `c-find-decl-spots' stopped.")
4750 ; (defface c-debug-decl-sws-face
4751 ; '((t (:background "Khaki")))
4752 ; "Debug face to mark the syntactic whitespace between the declaration
4753 ; spots and the preceding token end.")
4769 ;; Macro used inside `c-find-decl-spots'. It ought to be a defun,
4770 ;; but it contains lots of free variables that refer to things
4771 ;; inside `c-find-decl-spots'. The point is left at `cfd-match-pos'
4772 ;; if there is a match, otherwise at `cfd-limit'.
4773 ;;
4774 ;; The macro moves point forward to the next putative start of a declaration
4775 ;; or cfd-limit. This decl start is the next token after a "declaration
4776 ;; prefix". The declaration prefix is the earlier of `cfd-prop-match' and
4777 ;; `cfd-re-match'. `cfd-match-pos' is set to the decl prefix.
4778 ;;
4779 ;; This macro might do hidden buffer changes.
4782 ;; Find the next property match position if we haven't got one already.
4793 ;; Find the next `c-decl-prefix-or-start-re' match if we haven't
4794 ;; got one already.
4800 ;; Each time round, the next `while' moves forward over a pseudo match
4801 ;; of `c-decl-prefix-or-start-re' which is either inside a literal, or
4802 ;; is a ":" not preceded by "public", etc.. `cfd-re-match' and
4803 ;; `cfd-re-match-end' get set.
4810 ;; No match. Finish up and exit the loop.
4812 nil)
4815 ;; Matched the end of a token preceding a decl spot.
4819 ;; Matched a token that start a decl spot.
4822 c-literal-faces)
4823 ;; Pseudo match inside a comment or string literal. Skip out
4824 ;; of comments and string literals.
4836 ;; Found a ":" which isn't part of "public:", etc.
4837 t)
4840 ;; If our match was at the decl start, we have to back up over the
4841 ;; preceding syntactic ws to set `cfd-match-pos' and to catch
4842 ;; any decl spots in the syntactic ws.
4847 ;; Choose whichever match is closer to the start.
4850 cfd-re-match nil)
4852 cfd-prop-match nil))
4857 ;; Skip forward past comments only so we don't skip macros.
4859 ;; Set the position to continue at. We can avoid going over
4860 ;; the comments skipped above a second time, but it's possible
4861 ;; that the comment skipping has taken us past `cfd-prop-match'
4862 ;; since the property might be used inside comments.
4868 ;; Call CFD-FUN for each possible spot for a declaration, cast or
4869 ;; label from the point to CFD-LIMIT.
4870 ;;
4871 ;; CFD-FUN is called with point at the start of the spot. It's passed two
4872 ;; arguments: The first is the end position of the token preceding the spot,
4873 ;; or 0 for the implicit match at bob. The second is a flag that is t when
4874 ;; the match is inside a macro. Point should be moved forward by at least
4875 ;; one token.
4876 ;;
4877 ;; If CFD-FUN adds `c-decl-end' properties somewhere below the current spot,
4878 ;; it should return non-nil to ensure that the next search will find them.
4879 ;;
4880 ;; Such a spot is:
4881 ;; o The first token after bob.
4882 ;; o The first token after the end of submatch 1 in
4883 ;; `c-decl-prefix-or-start-re' when that submatch matches. This
4884 ;; submatch is typically a (L or R) brace or paren, a ;, or a ,.
4885 ;; o The start of each `c-decl-prefix-or-start-re' match when
4886 ;; submatch 1 doesn't match. This is, for example, the keyword
4887 ;; "class" in Pike.
4888 ;; o The start of a previously recognized declaration; "recognized"
4889 ;; means that the last char of the previous token has a `c-type'
4890 ;; text property with the value `c-decl-end'; this only holds
4891 ;; when `c-type-decl-end-used' is set.
4892 ;;
4893 ;; Only a spot that match CFD-DECL-RE and whose face is in the
4894 ;; CFD-FACE-CHECKLIST list causes CFD-FUN to be called. The face
4895 ;; check is disabled if CFD-FACE-CHECKLIST is nil.
4896 ;;
4897 ;; If the match is inside a macro then the buffer is narrowed to the
4898 ;; end of it, so that CFD-FUN can investigate the following tokens
4899 ;; without matching something that begins inside a macro and ends
4900 ;; outside it. It's to avoid this work that the CFD-DECL-RE and
4901 ;; CFD-FACE-CHECKLIST checks exist.
4902 ;;
4903 ;; The spots are visited approximately in order from top to bottom.
4904 ;; It's however the positions where `c-decl-prefix-or-start-re'
4905 ;; matches and where `c-decl-end' properties are found that are in
4906 ;; order. Since the spots often are at the following token, they
4907 ;; might be visited out of order insofar as more spots are reported
4908 ;; later on within the syntactic whitespace between the match
4909 ;; positions and their spots.
4910 ;;
4911 ;; It's assumed that comments and strings are fontified in the
4912 ;; searched range.
4913 ;;
4914 ;; This is mainly used in fontification, and so has an elaborate
4915 ;; cache to handle repeated calls from the same start position; see
4916 ;; the variables above.
4917 ;;
4918 ;; All variables in this function begin with `cfd-' to avoid name
4919 ;; collision with the (dynamically bound) variables used in CFD-FUN.
4920 ;;
4921 ;; This function might do hidden buffer changes.
4925 ;; The end of the token preceding the decl spot last found
4926 ;; with `c-decl-prefix-or-start-re'. `cfd-limit' if there's
4927 ;; no match.
4928 cfd-re-match
4929 ;; The end position of the last `c-decl-prefix-or-start-re'
4930 ;; match. If this is greater than `cfd-continue-pos', the
4931 ;; next regexp search is started here instead.
4933 ;; The end of the last `c-decl-end' found by
4934 ;; `c-find-decl-prefix-search'. `cfd-limit' if there's no
4935 ;; match. If searching for the property isn't needed then we
4936 ;; disable it by setting it to `cfd-limit' directly.
4938 ;; The end of the token preceding the decl spot last found by
4939 ;; `c-find-decl-prefix-search'. 0 for the implicit match at
4940 ;; bob. `cfd-limit' if there's no match. In other words,
4941 ;; this is the minimum of `cfd-re-match' and `cfd-prop-match'.
4943 ;; The position to continue searching at.
4944 cfd-continue-pos
4945 ;; The position of the last "real" token we've stopped at.
4946 ;; This can be greater than `cfd-continue-pos' when we get
4947 ;; hits inside macros or at `c-decl-end' positions inside
4948 ;; comments.
4950 ;; The end position of the last entered macro.
4953 ;; Initialize by finding a syntactically relevant start position
4954 ;; before the point, and do the first `c-decl-prefix-or-start-re'
4955 ;; search unless we're at bob.
4958 ;; Must back up a bit since we look for the end of the previous
4959 ;; statement or declaration, which is earlier than the first
4960 ;; returned match.
4962 ;; This `cond' moves back over any literals or macros. It has special
4963 ;; handling for when the region being searched is entirely within a
4964 ;; macro. It sets `cfd-continue-pos' (unless we've reached
4965 ;; `cfd-limit').
4967 ;; First we need to move to a syntactically relevant position.
4968 ;; Begin by backing out of comment or string literals.
4969 ;;
4970 ;; This arm of the cond actually triggers if we're in a literal,
4971 ;; and cfd-limit is at most at BONL.
4973 ;; This arm of the `and' moves backwards out of a literal when
4974 ;; the face at point is a literal face. In this case, its value
4975 ;; is always non-nil.
4977 ;; Try to use the faces to back up to the start of the
4978 ;; literal. FIXME: What if the point is on a declaration
4979 ;; inside a comment?
4985 ;; XEmacs doesn't fontify the quotes surrounding string
4986 ;; literals.
4995 ;; Don't trust the literal to contain only literal faces
4996 ;; (the font lock package might not have fontified the
4997 ;; start of it at all, for instance) so check that we have
4998 ;; arrived at something that looks like a start or else
4999 ;; resort to `c-literal-limits'.
5006 ;; The start is in a literal. If the limit is in the same
5007 ;; one we don't have to find a syntactic position etc. We
5008 ;; only check that if the limit is at or before bonl to save
5009 ;; time; it covers the by far most common case when font-lock
5010 ;; refontifies the current line only.
5021 ;; Completely inside a literal. Set up variables to trig the
5022 ;; (< cfd-continue-pos cfd-start-pos) case below and it'll
5023 ;; find a suitable start position.
5026 ;; Check if the region might be completely inside a macro, to
5027 ;; optimize that like the completely-inside-literal above.
5034 ;; (Maybe) completely inside a macro. Only need to trig the
5035 ;; (< cfd-continue-pos cfd-start-pos) case below to make it
5036 ;; set things up.
5038 start-in-macro t))
5040 ;; The default arm of the `cond' moves back over any macro we're in
5041 ;; and over any syntactic WS. It sets `c-find-decl-syntactic-pos'.
5043 ;; Back out of any macro so we don't miss any declaration
5044 ;; that could follow after it.
5048 ;; Now we're at a proper syntactically relevant position so we
5049 ;; can use the cache. But first clear it if it applied
5050 ;; further down.
5055 ;; Don't have to do this if the cache is relevant here,
5056 ;; typically if the same line is refontified again. If
5057 ;; we're just some syntactic whitespace further down we can
5058 ;; still use the cache to limit the skipping.
5061 ;; If we hit `c-find-decl-syntactic-pos' and
5062 ;; `c-find-decl-match-pos' is set then we install the cached
5063 ;; values. If we hit `c-find-decl-syntactic-pos' and
5064 ;; `c-find-decl-match-pos' is nil then we know there's no decl
5065 ;; prefix in the whitespace before `c-find-decl-syntactic-pos'
5066 ;; and so we can continue the search from this point. If we
5067 ;; didn't hit `c-find-decl-syntactic-pos' then we're now in
5068 ;; the right spot to begin searching anyway.
5070 c-find-decl-match-pos)
5072 cfd-continue-pos syntactic-pos)
5077 ;; Always consider bob a match to get the first
5078 ;; declaration in the file. Do this separately instead of
5079 ;; letting `c-decl-prefix-or-start-re' match bob, so that
5080 ;; regexp always can consume at least one character to
5081 ;; ensure that we won't get stuck in an infinite loop.
5086 ;; Do an initial search now. In the bob case above it's
5087 ;; only done to search for a `c-decl-end' spot.
5093 ;; Advance `cfd-continue-pos' if it's before the start position.
5094 ;; The closest continue position that might have effect at or
5095 ;; after the start depends on what we started in. This also
5096 ;; finds a suitable start position in the special cases when the
5097 ;; region is completely within a literal or macro.
5102 ;; If we're in a macro then it's the closest preceding token
5103 ;; in the macro. Check this before `start-in-literal',
5104 ;; since if we're inside a literal in a macro, the preceding
5105 ;; token is earlier than any `c-decl-end' spot inside the
5106 ;; literal (comment).
5108 ;; The only syntactic ws in macros are comments.
5114 ;; If we're in a comment it can only be the closest
5115 ;; preceding `c-decl-end' position within that comment, if
5116 ;; any. Go back to the beginning of such a property so that
5117 ;; `c-find-decl-prefix-search' will find the end of it.
5118 ;; (Can't stop at the end and install it directly on
5119 ;; `cfd-prop-match' since that variable might be cleared
5120 ;; after `cfd-fun' below.)
5121 ;;
5122 ;; Note that if the literal is a string then the property
5123 ;; search will simply skip to the beginning of it right
5124 ;; away.
5136 ;; Didn't find any property inside the comment, so we can
5137 ;; skip it entirely. (This won't skip past a string, but
5138 ;; that'll be handled quickly by the next
5139 ;; `c-find-decl-prefix-search' anyway.)
5145 ;; If we started in normal code, the only match that might
5146 ;; apply before the start is what we already got in
5147 ;; `cfd-match-pos' so we can continue at the start position.
5148 ;; (Note that we don't get here if the first match is below
5149 ;; it.)
5152 ;; Delete found matches if they are before our new continue
5153 ;; position, so that `c-find-decl-prefix-search' won't back up
5154 ;; to them later on.
5162 ;; This is the normal case and we got a proper syntactic
5163 ;; position. If there's a match then it's always outside
5164 ;; macros and comments, so advance to the next token and set
5165 ;; `cfd-token-pos'. The loop below will later go back using
5166 ;; `cfd-continue-pos' to fix declarations inside the
5167 ;; syntactic ws.
5175 ;; Have one of the special cases when the region is completely
5176 ;; within a literal or macro. `cfd-continue-pos' is set to a
5177 ;; good start position for the search, so do it.
5180 ;; Now loop, one decl spot per iteration. We already have the first
5181 ;; match in `cfd-match-pos'.
5183 ;; Go forward over "false matches", one per iteration.
5188 ;; Kludge to filter out matches on the "<" that
5189 ;; aren't open parens, for the sake of languages
5190 ;; that got `c-recognize-<>-arglists' set.
5195 ;; If `cfd-continue-pos' is less or equal to
5196 ;; `cfd-token-pos', we've got a hit inside a macro
5197 ;; that's in the syntactic whitespace before the last
5198 ;; "real" declaration we've checked. If they're equal
5199 ;; we've arrived at the declaration a second time, so
5200 ;; there's nothing to do.
5204 ;; If `cfd-continue-pos' is less than `cfd-token-pos'
5205 ;; we're still searching for declarations embedded in
5206 ;; the syntactic whitespace. In that case we need
5207 ;; only to skip comments and not macros, since they
5208 ;; can't be nested, and that's already been done in
5209 ;; `c-find-decl-prefix-search'.
5214 ;; Continue if the following token fails the
5215 ;; CFD-DECL-RE and CFD-FACE-CHECKLIST checks.
5222 t)))
5233 ;; Narrow to the end of the macro if we got a hit inside
5234 ;; one, to avoid recognizing things that start inside the
5235 ;; macro and end outside it.
5237 ;; Not in the same macro as in the previous round.
5248 t
5251 t)
5252 ;; The matched token was the last thing in the macro,
5253 ;; so the whole match is bogus.
5262 ;; Restore limits if we did macro narrowing above.
5269 ; cfd-match-pos, etc.
5271 \f
5272 ;; A cache for found types.
5274 ;; Buffer local variable that contains an obarray with the types we've
5275 ;; found. If a declaration is recognized somewhere we record the
5276 ;; fully qualified identifier in it to recognize it as a type
5277 ;; elsewhere in the file too. This is not accurate since we do not
5278 ;; bother with the scoping rules of the languages, but in practice the
5279 ;; same name is seldom used as both a type and something else in a
5280 ;; file, and we only use this as a last resort in ambiguous cases (see
5281 ;; `c-forward-decl-or-cast-1').
5282 ;;
5283 ;; Not every type need be in this cache. However, things which have
5284 ;; ceased to be types must be removed from it.
5285 ;;
5286 ;; Template types in C++ are added here too but with the template
5287 ;; arglist replaced with "<>" in references or "<" for the one in the
5288 ;; primary type. E.g. the type "Foo<A,B>::Bar<C>" is stored as
5289 ;; "Foo<>::Bar<". This avoids storing very long strings (since C++
5290 ;; template specs can be fairly sized programs in themselves) and
5291 ;; improves the hit ratio (it's a type regardless of the template
5292 ;; args; it's just not the same type, but we're only interested in
5293 ;; recognizing types, not telling distinct types apart). Note that
5294 ;; template types in references are added here too; from the example
5295 ;; above there will also be an entry "Foo<".
5300 ;; Clears `c-found-types'.
5304 ;; Add the given region as a type in `c-found-types'. If the region
5305 ;; doesn't match an existing type but there is a type which is equal
5306 ;; to the given one except that the last character is missing, then
5307 ;; the shorter type is removed. That's done to avoid adding all
5308 ;; prefixes of a type as it's being entered and font locked. This
5309 ;; doesn't cover cases like when characters are removed from a type
5310 ;; or added in the middle. We'd need the position of point when the
5311 ;; font locking is invoked to solve this well.
5312 ;;
5313 ;; This function might do hidden buffer changes.
5320 ;; Remove the "NAME" from c-found-types, if present.
5324 ;; Return non-nil if the given region contains a type in
5325 ;; `c-found-types'.
5326 ;;
5327 ;; This function might do hidden buffer changes.
5329 c-found-types))
5332 ;; Return all the types in `c-found-types' as a sorted list of
5333 ;; strings.
5337 type-list)))
5338 c-found-types)
5341 ;; Shut up the byte compiler.
5345 ;; An after change function which, in conjunction with the info in
5346 ;; c-maybe-stale-found-type (set in c-before-change), removes a type
5347 ;; from `c-found-types', should this type have become stale. For
5348 ;; example, this happens to "foo" when "foo \n bar();" becomes
5349 ;; "foo(); \n bar();". Such stale types, if not removed, foul up
5350 ;; the fontification.
5351 ;;
5352 ;; Have we, perhaps, added non-ws characters to the front/back of a found
5353 ;; type?
5373 ;; Changing the amount of (already existing) whitespace - don't do anything.
5378 ;; The syntactic relationship which defined a "found type" has been
5379 ;; destroyed.
5382 ;; ((eq (car c-maybe-stale-found-type) 'c-decl-type-start) FIXME!!!
5383 )))
5385 \f
5386 ;; Setting and removing syntax properties on < and > in languages (C++
5387 ;; and Java) where they can be template/generic delimiters as well as
5388 ;; their normal meaning of "less/greater than".
5390 ;; Normally, < and > have syntax 'punctuation'. When they are found to
5391 ;; be delimiters, they are marked as such with the category properties
5392 ;; c-<-as-paren-syntax, c->-as-paren-syntax respectively.
5394 ;; STRATEGY:
5395 ;;
5396 ;; It is impossible to determine with certainty whether a <..> pair in
5397 ;; C++ is two comparison operators or is template delimiters, unless
5398 ;; one duplicates a lot of a C++ compiler. For example, the following
5399 ;; code fragment:
5400 ;;
5401 ;; foo (a < b, c > d) ;
5402 ;;
5403 ;; could be a function call with two integer parameters (each a
5404 ;; relational expression), or it could be a constructor for class foo
5405 ;; taking one parameter d of templated type "a < b, c >". They are
5406 ;; somewhat easier to distinguish in Java.
5407 ;;
5408 ;; The strategy now (2010-01) adopted is to mark and unmark < and
5409 ;; > IN MATCHING PAIRS ONLY. [Previously, they were marked
5410 ;; individually when their context so indicated. This gave rise to
5411 ;; intractable problems when one of a matching pair was deleted, or
5412 ;; pulled into a literal.]
5413 ;;
5414 ;; At each buffer change, the syntax-table properties are removed in a
5415 ;; before-change function and reapplied, when needed, in an
5416 ;; after-change function. It is far more important that the
5417 ;; properties get removed when they they are spurious than that they
5418 ;; be present when wanted.
5419 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
5421 ;; POS (default point) is at a < character. If it is marked with
5422 ;; open paren syntax-table text property, remove the property,
5423 ;; together with the close paren property on the matching > (if
5424 ;; any).
5439 ;; POS (default point) is at a > character. If it is marked with
5440 ;; close paren syntax-table property, remove the property, together
5441 ;; with the open paren property on the matching < (if any).
5456 ;; POS (default point) is at a < or > character. If it has an
5457 ;; open/close paren syntax-table property, remove this property both
5458 ;; from the current character and its partner (which will also be
5459 ;; thusly marked).
5469 ;; POS (default point) is at a < character. If it is both marked
5470 ;; with open/close paren syntax-table property, and has a matching >
5471 ;; (also marked) which is after LIM, remove the property both from
5472 ;; the current > and its partner. Return t when this happens, nil
5473 ;; when it doesn't.
5487 t)))
5490 ;; POS (default point) is at a > character. If it is both marked
5491 ;; with open/close paren syntax-table property, and has a matching <
5492 ;; (also marked) which is before LIM, remove the property both from
5493 ;; the current < and its partner. Return t when this happens, nil
5494 ;; when it doesn't.
5508 t)))
5510 ;; Set by c-common-init in cc-mode.el.
5515 ;; Unmark certain pairs of "< .... >" which are currently marked as
5516 ;; template/generic delimiters. (This marking is via syntax-table
5517 ;; text properties).
5518 ;;
5519 ;; These pairs are those which are in the current "statement" (i.e.,
5520 ;; the region between the {, }, or ; before BEG and the one after
5521 ;; END), and which enclose any part of the interval (BEG END).
5522 ;;
5523 ;; Note that in C++ (?and Java), template/generic parens cannot
5524 ;; enclose a brace or semicolon, so we use these as bounds on the
5525 ;; region we must work on.
5526 ;;
5527 ;; This function is called from before-change-functions (via
5528 ;; c-get-state-before-change-functions). Thus the buffer is widened,
5529 ;; and point is undefined, both at entry and exit.
5530 ;;
5531 ;; FIXME!!! This routine ignores the possibility of macros entirely.
5532 ;; 2010-01-29.
5536 new-beg new-end need-new-beg need-new-end)
5537 ;; Locate the barrier before the changed region
5542 ;; Remove the syntax-table properties from each pertinent <...> pair.
5543 ;; Firsly, the ones with the < before beg and > after beg.
5548 ;; Locate the barrier after END.
5553 ;; Remove syntax-table properties from the remaining pertinent <...>
5554 ;; pairs, those with a > after end and < before end.
5559 ;; Extend the fontification region, if needed.
5569 ;; This is called from `after-change-functions' when
5570 ;; c-recognize-<>-arglists' is set. It ensures that no "<" or ">"
5571 ;; chars with paren syntax become part of another operator like "<<"
5572 ;; or ">=".
5573 ;;
5574 ;; This function might do hidden buffer changes.
5607 \f
5608 ;; Handling of small scale constructs like types and names.
5610 ;; Dynamically bound variable that instructs `c-forward-type' to also
5611 ;; treat possible types (i.e. those that it normally returns 'maybe or
5612 ;; 'found for) as actual types (and always return 'found for them).
5613 ;; This means that it records them in `c-record-type-identifiers' if
5614 ;; that is set, and that it adds them to `c-found-types'.
5617 ;; Dynamically bound variable that instructs `c-forward-<>-arglist' to
5618 ;; mark up successfully parsed arglists with paren syntax properties on
5619 ;; the surrounding angle brackets and with `c-<>-arg-sep' in the
5620 ;; `c-type' property of each argument separating comma.
5621 ;;
5622 ;; Setting this variable also makes `c-forward-<>-arglist' recurse into
5623 ;; all arglists for side effects (i.e. recording types), otherwise it
5624 ;; exploits any existing paren syntax properties to quickly jump to the
5625 ;; end of already parsed arglists.
5626 ;;
5627 ;; Marking up the arglists is not the default since doing that correctly
5628 ;; depends on a proper value for `c-restricted-<>-arglists'.
5631 ;; Dynamically bound variable that instructs `c-forward-<>-arglist' to
5632 ;; not accept arglists that contain binary operators.
5633 ;;
5634 ;; This is primarily used to handle C++ template arglists. C++
5635 ;; disambiguates them by checking whether the preceding name is a
5636 ;; template or not. We can't do that, so we assume it is a template
5637 ;; if it can be parsed as one. That usually works well since
5638 ;; comparison expressions on the forms "a < b > c" or "a < b, c > d"
5639 ;; in almost all cases would be pointless.
5640 ;;
5641 ;; However, in function arglists, e.g. in "foo (a < b, c > d)", we
5642 ;; should let the comma separate the function arguments instead. And
5643 ;; in a context where the value of the expression is taken, e.g. in
5644 ;; "if (a < b || c > d)", it's probably not a template.
5647 ;; Dynamically bound variables that instructs
5648 ;; `c-forward-keyword-clause', `c-forward-<>-arglist',
5649 ;; `c-forward-name', `c-forward-type', `c-forward-decl-or-cast-1', and
5650 ;; `c-forward-label' to record the ranges of all the type and
5651 ;; reference identifiers they encounter. They will build lists on
5652 ;; these variables where each element is a cons of the buffer
5653 ;; positions surrounding each identifier. This recording is only
5654 ;; activated when `c-record-type-identifiers' is non-nil.
5655 ;;
5656 ;; All known types that can't be identifiers are recorded, and also
5657 ;; other possible types if `c-promote-possible-types' is set.
5658 ;; Recording is however disabled inside angle bracket arglists that
5659 ;; are encountered inside names and other angle bracket arglists.
5660 ;; Such occurrences are taken care of by `c-font-lock-<>-arglists'
5661 ;; instead.
5662 ;;
5663 ;; Only the names in C++ template style references (e.g. "tmpl" in
5664 ;; "tmpl<a,b>::foo") are recorded as references, other references
5665 ;; aren't handled here.
5666 ;;
5667 ;; `c-forward-label' records the label identifier(s) on
5668 ;; `c-record-ref-identifiers'.
5672 ;; This variable will receive a cons cell of the range of the last
5673 ;; single identifier symbol stepped over by `c-forward-name' if it's
5674 ;; successful. This is the range that should be put on one of the
5675 ;; record lists above by the caller. It's assigned nil if there's no
5676 ;; such symbol in the name.
5681 ;; Always true.
5691 ;; Always true.
5699 ;; Dynamically bound variable that instructs `c-forward-type' to
5700 ;; record the ranges of types that only are found. Behaves otherwise
5701 ;; like `c-record-type-identifiers'.
5705 ;; Used internally in `c-forward-keyword-clause' to move forward
5706 ;; over a type (if TYPE is 'type) or a name (otherwise) which
5707 ;; possibly is prefixed by keywords and their associated clauses.
5708 ;; Try with a type/name first to not trip up on those that begin
5709 ;; with a keyword. Return t if a known or found type is moved
5710 ;; over. The point is clobbered if nil is returned. If range
5711 ;; recording is enabled, the identifier is recorded on as a type
5712 ;; if TYPE is 'type or as a reference if TYPE is 'ref.
5713 ;;
5714 ;; This macro might do hidden buffer changes.
5719 nil
5726 t)))
5729 ;; Used internally in `c-forward-keyword-clause' to move forward
5730 ;; over a comma separated list of types or names using
5731 ;; `c-forward-keyword-prefixed-id'.
5732 ;;
5733 ;; This macro might do hidden buffer changes.
5744 ;; Submatch MATCH in the current match data is assumed to surround a
5745 ;; token. If it's a keyword, move over it and any immediately
5746 ;; following clauses associated with it, stopping at the start of
5747 ;; the next token. t is returned in that case, otherwise the point
5748 ;; stays and nil is returned. The kind of clauses that are
5749 ;; recognized are those specified by `c-type-list-kwds',
5750 ;; `c-ref-list-kwds', `c-colon-type-list-kwds',
5751 ;; `c-paren-nontype-kwds', `c-paren-type-kwds', `c-<>-type-kwds',
5752 ;; and `c-<>-arglist-kwds'.
5753 ;;
5754 ;; This function records identifier ranges on
5755 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
5756 ;; `c-record-type-identifiers' is non-nil.
5757 ;;
5758 ;; Note that for `c-colon-type-list-kwds', which doesn't necessary
5759 ;; apply directly after the keyword, the type list is moved over
5760 ;; only when there is no unaccounted token before it (i.e. a token
5761 ;; that isn't moved over due to some other keyword list). The
5762 ;; identifier ranges in the list are still recorded if that should
5763 ;; be done, though.
5764 ;;
5765 ;; This function might do hidden buffer changes.
5768 ;; The call to `c-forward-<>-arglist' below is made after
5769 ;; `c-<>-sexp-kwds' keywords, so we're certain they actually
5770 ;; are angle bracket arglists and `c-restricted-<>-arglists'
5771 ;; should therefore be nil.
5783 ;; There's a type directly after a keyword in `c-type-list-kwds'.
5788 ;; There's a name directly after a keyword in `c-ref-list-kwds'.
5793 ;; There's an open paren after a keyword in `c-paren-any-kwds'.
5800 ;; Use `c-forward-type' on every identifier we can find
5801 ;; inside the paren, to record the types.
5826 ;; If we are at the colon already, we move over the type
5827 ;; list after it.
5833 ;; Not at the colon, so stop here. But the identifier
5834 ;; ranges in the type list later on should still be
5835 ;; recorded.
5838 ;; If a keyword matched both one of the types above and
5839 ;; this one, we match `c-colon-type-list-re' after the
5840 ;; clause matched above.
5847 ;; There's a type after the `c-colon-type-list-re' match
5848 ;; after a keyword in `c-colon-type-list-kwds'.
5852 t)))
5854 ;; cc-mode requires cc-fonts.
5858 ;; The point is assumed to be at a "<". Try to treat it as the open
5859 ;; paren of an angle bracket arglist and move forward to the
5860 ;; corresponding ">". If successful, the point is left after the
5861 ;; ">" and t is returned, otherwise the point isn't moved and nil is
5862 ;; returned. If ALL-TYPES is t then all encountered arguments in
5863 ;; the arglist that might be types are treated as found types.
5864 ;;
5865 ;; The variable `c-parse-and-markup-<>-arglists' controls how this
5866 ;; function handles text properties on the angle brackets and argument
5867 ;; separating commas.
5868 ;;
5869 ;; `c-restricted-<>-arglists' controls how lenient the template
5870 ;; arglist recognition should be.
5871 ;;
5872 ;; This function records identifier ranges on
5873 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
5874 ;; `c-record-type-identifiers' is non-nil.
5875 ;;
5876 ;; This function might do hidden buffer changes.
5879 ;; If `c-record-type-identifiers' is set then activate
5880 ;; recording of any found types that constitute an argument in
5881 ;; the arglist.
5889 ;; `nconc' doesn't mind that the tail of
5890 ;; `c-record-found-types' is t.
5893 t)
5896 nil)))
5899 ;; Recursive part of `c-forward-<>-arglist'.
5900 ;;
5901 ;; This function might do hidden buffer changes.
5903 ;; Cover this so that any recorded found type ranges are
5904 ;; automatically lost if it turns out to not be an angle
5905 ;; bracket arglist. It's propagated through the return value
5906 ;; on successful completion.
5908 ;; List that collects the positions after the argument
5909 ;; separating ',' in the arglist.
5910 arg-start-pos)
5911 ;; If the '<' has paren open syntax then we've marked it as an angle
5912 ;; bracket arglist before, so skip to the end.
5920 t
5921 ;; Got unmatched paren angle brackets. We don't clear the paren
5922 ;; syntax properties and retry, on the basis that it's very
5923 ;; unlikely that paren angle brackets become operators by code
5924 ;; manipulation. It's far more likely that it doesn't match due
5925 ;; to narrowing or some temporary change.
5927 nil))
5932 ;; go forward one non-alphanumeric character (group) per iteration of
5933 ;; this loop.
5940 ;; All encountered identifiers are types, so set the
5941 ;; promote flag and parse the type.
5964 ;; Note: These regexps exploit the match order in \| so
5965 ;; that "<>" is matched by "<" rather than "[^>:-]>".
5967 ;; Stop on ',', '|', '&', '+' and '-' to catch
5968 ;; common binary operators that could be between
5969 ;; two comparison expressions "a<b" and "c>d".
5971 nil t t))
5975 ;; Either an operator starting with '>' or the end of
5976 ;; the angle bracket arglist.
5983 ;; The angle bracket arglist is finished.
5995 ;; Either an operator starting with '<' or a nested arglist.
5999 ;; The '<' begins a multi-char operator.
6003 ;; We're at a nested <.....>
6009 ;; There's always an identifier before an angle
6010 ;; bracket arglist, or a keyword in `c-<>-type-kwds'
6011 ;; or `c-<>-arglist-kwds'.
6027 ;; It was an angle bracket arglist.
6030 ;; Record the identifier before the template as a type
6031 ;; or reference depending on whether the arglist is last
6032 ;; in a qualified identifier.
6042 ;; At a "less than" operator.
6045 )))
6052 ;; Just another argument. Record the position. The
6053 ;; type check stuff that made us stop at it is at
6054 ;; the top of the loop.
6058 ;; Got a character that can't be in an angle bracket
6059 ;; arglist argument. Abort using `throw', since
6060 ;; it's useless to try to find a surrounding arglist
6061 ;; if we're nested.
6067 ;; The point is assumed to be directly after a ">". Try to treat it
6068 ;; as the close paren of an angle bracket arglist and move back to
6069 ;; the corresponding "<". If successful, the point is left at
6070 ;; the "<" and t is returned, otherwise the point isn't moved and
6071 ;; nil is returned. ALL-TYPES is passed on to
6072 ;; `c-forward-<>-arglist'.
6073 ;;
6074 ;; If the optional LIMIT is given, it bounds the backward search.
6075 ;; It's then assumed to be at a syntactically relevant position.
6076 ;;
6077 ;; This is a wrapper around `c-forward-<>-arglist'. See that
6078 ;; function for more details.
6087 t
6088 ;; See corresponding note in `c-forward-<>-arglist'.
6090 nil)
6097 t
6098 ;; Stopped at bob or a char that isn't allowed in an
6099 ;; arglist, so we've failed.
6101 nil)
6106 ;; If we moved then the "<" was part of some
6107 ;; multicharacter token.
6108 t
6114 ;; Matched the arglist. Break the while.
6116 nil)
6118 ;; We started from a non-paren ">" inside an
6119 ;; arglist.
6121 nil)
6123 ;; Matched a shorter arglist. Can be a nested
6124 ;; one so continue looking.
6126 t))
6127 t))))))
6132 ;; Move forward over a complete name if at the beginning of one,
6133 ;; stopping at the next following token. A keyword, as such,
6134 ;; doesn't count as a name. If the point is not at something that
6135 ;; is recognized as a name then it stays put.
6136 ;;
6137 ;; A name could be something as simple as "foo" in C or something as
6138 ;; complex as "X<Y<class A<int>::B, BIT_MAX >> b>, ::operator<> ::
6139 ;; Z<(a>b)> :: operator const X<&foo>::T Q::G<unsigned short
6140 ;; int>::*volatile const" in C++ (this function is actually little
6141 ;; more than a `looking-at' call in all modes except those that,
6142 ;; like C++, have `c-recognize-<>-arglists' set).
6143 ;;
6144 ;; Return
6145 ;; o - nil if no name is found;
6146 ;; o - 'template if it's an identifier ending with an angle bracket
6147 ;; arglist;
6148 ;; o - 'operator of it's an operator identifier;
6149 ;; o - t if it's some other kind of name.
6150 ;;
6151 ;; This function records identifier ranges on
6152 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6153 ;; `c-record-type-identifiers' is non-nil.
6154 ;;
6155 ;; This function might do hidden buffer changes.
6158 ;; Turn off `c-promote-possible-types' here since we might
6159 ;; call `c-forward-<>-arglist' and we don't want it to promote
6160 ;; every suspect thing in the arglist to a type. We're
6161 ;; typically called from `c-forward-type' in this case, and
6162 ;; the caller only wants the top level type that it finds to
6163 ;; be promoted.
6164 c-promote-possible-types)
6170 ;; Check for keyword. We go to the last symbol in
6171 ;; `c-identifier-key' first.
6184 ;; "template" is only valid inside an
6185 ;; identifier if preceded by "::".
6190 t))
6192 ;; Handle a C++ operator or template identifier.
6196 ;; Got "... ::template".
6200 res subres))))
6203 ;; Got a cast operator.
6207 ;; Now we should match a sequence of either
6208 ;; '*', '&' or a name followed by ":: *",
6209 ;; where each can be followed by a sequence
6210 ;; of `c-opt-type-modifier-key'.
6213 t)
6223 t))))
6231 ;; Got some other operator.
6239 nil)
6241 ;; `id-start' is equal to `id-end' if we've jumped over
6242 ;; an identifier that doesn't end with a symbol token.
6243 ;; That can occur e.g. for Java import directives on the
6244 ;; form "foo.bar.*".
6251 res t)))
6261 ;; Got a concatenated identifier. This handles the
6262 ;; cases with tricky syntactic whitespace that aren't
6263 ;; covered in `c-identifier-key'.
6266 t)
6270 ;; Maybe an angle bracket arglist.
6278 c-last-identifier-range nil)
6283 ;; Continue if there's an identifier concatenation
6284 ;; operator after the template argument.
6290 t)
6295 nil)))
6296 )))))
6299 res))
6302 ;; Move forward over a type spec if at the beginning of one,
6303 ;; stopping at the next following token. The keyword "typedef"
6304 ;; isn't part of a type spec here.
6305 ;;
6306 ;; BRACE-BLOCK-TOO, when non-nil, means move over the brace block in
6307 ;; constructs like "struct foo {...} bar ;" or "struct {...} bar;".
6308 ;; The current (2009-03-10) intention is to convert all uses of
6309 ;; `c-forward-type' to call with this parameter set, then to
6310 ;; eliminate it.
6311 ;;
6312 ;; Return
6313 ;; o - t if it's a known type that can't be a name or other
6314 ;; expression;
6315 ;; o - 'known if it's an otherwise known type (according to
6316 ;; `*-font-lock-extra-types');
6317 ;; o - 'prefix if it's a known prefix of a type;
6318 ;; o - 'found if it's a type that matches one in `c-found-types';
6319 ;; o - 'maybe if it's an identifier that might be a type;
6320 ;; o - 'decltype if it's a decltype(variable) declaration; - or
6321 ;; o - nil if it can't be a type (the point isn't moved then).
6322 ;;
6323 ;; The point is assumed to be at the beginning of a token.
6324 ;;
6325 ;; Note that this function doesn't skip past the brace definition
6326 ;; that might be considered part of the type, e.g.
6327 ;; "enum {a, b, c} foo".
6328 ;;
6329 ;; This function records identifier ranges on
6330 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6331 ;; `c-record-type-identifiers' is non-nil.
6332 ;;
6333 ;; This function might do hidden buffer changes.
6341 ;; Skip leading type modifiers. If any are found we know it's a
6342 ;; prefix of a type.
6361 ; "typedef".
6369 ;; In many languages the name can be used without the
6370 ;; prefix, so we add it to `c-found-types'.
6373 c-last-identifier-range)
6395 id-range c-last-identifier-range))))
6407 id-end)
6409 ;; Looking at a primitive or known type identifier. We've
6410 ;; checked for a name first so that we don't go here if the
6411 ;; known type match only is a prefix of another name.
6422 ;; There might be more keywords for the type.
6450 ;; A normal identifier.
6460 ;; It's an identifier that has been used as
6461 ;; a type somewhere else.
6462 'found
6463 ;; It's an identifier that might be a type.
6466 ;; A template is a type.
6470 ;; Otherwise it's an operator identifier, which is not a type.
6475 ;; Skip trailing type modifiers. If any are found we know it's
6476 ;; a type.
6482 ;; Step over any type suffix operator. Do not let the existence
6483 ;; of these alter the classification of the found type, since
6484 ;; these operators typically are allowed in normal expressions
6485 ;; too.
6492 ;; Look for a trailing operator that concatenates the type
6493 ;; with a following one, and if so step past that one through
6494 ;; a recursive call. Note that we don't record concatenated
6495 ;; types in `c-found-types' - it's the component types that
6496 ;; are recorded when appropriate.
6499 c-promote-possible-types))
6500 ;; If we can't promote then set `c-record-found-types' so that
6501 ;; we can merge in the types from the second part afterwards if
6502 ;; it turns out to be a known type there.
6505 subres)
6514 ;; If either operand certainly is a type then both are, but we
6515 ;; don't let the existence of the operator itself promote two
6516 ;; uncertain types to a certain one.
6535 ;; Merge in the ranges of any types found by the second
6536 ;; `c-forward-type'.
6538 ;; `nconc' doesn't mind that the tail of
6539 ;; `c-record-found-types' is t.
6541 c-record-type-identifiers))))
6549 ;;(message "c-forward-type %s -> %s: %s" start (point) res)
6551 res))
6554 ;; Used for Java code only at the moment. Assumes point is on the
6555 ;; @, moves forward an annotation. returns nil if there is no
6556 ;; annotation at point.
6563 t)))
6566 ;; Pull the next open brace from PS (which has the form of paren-state),
6567 ;; skipping over any brace pairs. Returns NIL when PS is exhausted.
6575 ;; Test whether we are in a C++ member initializer list, and if so, go back
6576 ;; to the introducing ":", returning the position of the opening paren of
6577 ;; the function's arglist. Otherwise return nil, leaving point unchanged.
6580 res)
6618 res))
6620 \f
6621 ;; Handling of large scale constructs like statements and declarations.
6623 ;; Macro used inside `c-forward-decl-or-cast-1'. It ought to be a
6624 ;; defsubst or perhaps even a defun, but it contains lots of free
6625 ;; variables that refer to things inside `c-forward-decl-or-cast-1'.
6627 ;; `c-forward-decl-or-cast-1' can consume an arbitrary length list
6628 ;; of types when parsing a declaration, which means that it
6629 ;; sometimes consumes the identifier in the declaration as a type.
6630 ;; This is used to "backtrack" and make the last type be treated as
6631 ;; an identifier instead.
6634 ;; These identifiers are bound only in the inner let.
6636 identifier-start type-start
6637 got-parens nil
6638 got-identifier t
6639 got-suffix t
6640 got-suffix-after-parens id-start
6644 t
6645 backup-at-type))
6647 id-start backup-id-start)
6649 id-start start-pos))
6651 ;; When these flags already are set we've found specifiers that
6652 ;; unconditionally signal these attributes - backtracking doesn't
6653 ;; change that. So keep them set in that case.
6660 ;; This identifier is bound only in the inner let.
6664 ;; Move forward over a declaration or a cast if at the start of one.
6665 ;; The point is assumed to be at the start of some token. Nil is
6666 ;; returned if no declaration or cast is recognized, and the point
6667 ;; is clobbered in that case.
6668 ;;
6669 ;; If a declaration is parsed:
6670 ;;
6671 ;; The point is left at the first token after the first complete
6672 ;; declarator, if there is one. The return value is a cons where
6673 ;; the car is the position of the first token in the declarator. (See
6674 ;; below for the cdr.)
6675 ;; Some examples:
6676 ;;
6677 ;; void foo (int a, char *b) stuff ...
6678 ;; car ^ ^ point
6679 ;; float (*a)[], b;
6680 ;; car ^ ^ point
6681 ;; unsigned int a = c_style_initializer, b;
6682 ;; car ^ ^ point
6683 ;; unsigned int a (cplusplus_style_initializer), b;
6684 ;; car ^ ^ point (might change)
6685 ;; class Foo : public Bar {}
6686 ;; car ^ ^ point
6687 ;; class PikeClass (int a, string b) stuff ...
6688 ;; car ^ ^ point
6689 ;; enum bool;
6690 ;; car ^ ^ point
6691 ;; enum bool flag;
6692 ;; car ^ ^ point
6693 ;; void cplusplus_function (int x) throw (Bad);
6694 ;; car ^ ^ point
6695 ;; Foo::Foo (int b) : Base (b) {}
6696 ;; car ^ ^ point
6697 ;;
6698 ;; auto foo = 5;
6699 ;; car ^ ^ point
6700 ;; auto cplusplus_11 (int a, char *b) -> decltype (bar):
6701 ;; car ^ ^ point
6702 ;;
6703 ;;
6704 ;;
6705 ;; The cdr of the return value is non-nil when a
6706 ;; `c-typedef-decl-kwds' specifier is found in the declaration.
6707 ;; Specifically it is a dotted pair (A . B) where B is t when a
6708 ;; `c-typedef-kwds' ("typedef") is present, and A is t when some
6709 ;; other `c-typedef-decl-kwds' (e.g. class, struct, enum)
6710 ;; specifier is present. I.e., (some of) the declared
6711 ;; identifier(s) are types.
6712 ;;
6713 ;; If a cast is parsed:
6714 ;;
6715 ;; The point is left at the first token after the closing paren of
6716 ;; the cast. The return value is `cast'. Note that the start
6717 ;; position must be at the first token inside the cast parenthesis
6718 ;; to recognize it.
6719 ;;
6720 ;; PRECEDING-TOKEN-END is the first position after the preceding
6721 ;; token, i.e. on the other side of the syntactic ws from the point.
6722 ;; Use a value less than or equal to (point-min) if the point is at
6723 ;; the first token in (the visible part of) the buffer.
6724 ;;
6725 ;; CONTEXT is a symbol that describes the context at the point:
6726 ;; 'decl In a comma-separated declaration context (typically
6727 ;; inside a function declaration arglist).
6728 ;; '<> In an angle bracket arglist.
6729 ;; 'arglist Some other type of arglist.
6730 ;; nil Some other context or unknown context. Includes
6731 ;; within the parens of an if, for, ... construct.
6732 ;;
6733 ;; LAST-CAST-END is the first token after the closing paren of a
6734 ;; preceding cast, or nil if none is known. If
6735 ;; `c-forward-decl-or-cast-1' is used in succession, it should be
6736 ;; the position after the closest preceding call where a cast was
6737 ;; matched. In that case it's used to discover chains of casts like
6738 ;; "(a) (b) c".
6739 ;;
6740 ;; This function records identifier ranges on
6741 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
6742 ;; `c-record-type-identifiers' is non-nil.
6743 ;;
6744 ;; This function might do hidden buffer changes.
6747 ;; first type, i.e. after any leading specifiers. It might
6748 ;; also point at the beginning of the preceding syntactic
6749 ;; whitespace.
6751 ;; Set to the result of `c-forward-type'.
6752 at-type
6753 ;; The position of the first token in what we currently
6754 ;; believe is the type in the declaration or cast, after any
6755 ;; specifiers and their associated clauses.
6756 type-start
6757 ;; The position of the first token in what we currently
6758 ;; believe is the declarator for the first identifier. Set
6759 ;; when the type is found, and moved forward over any
6760 ;; `c-decl-hangon-kwds' and their associated clauses that
6761 ;; occurs after the type.
6762 id-start
6763 ;; These store `at-type', `type-start' and `id-start' of the
6764 ;; identifier before the one in those variables. The previous
6765 ;; identifier might turn out to be the real type in a
6766 ;; declaration if the last one has to be the declarator in it.
6767 ;; If `backup-at-type' is nil then the other variables have
6768 ;; undefined values.
6769 backup-at-type backup-type-start backup-id-start
6770 ;; This stores `kwd-sym' of the symbol before the current one.
6771 ;; This is needed to distinguish the C++11 version of "auto" from
6772 ;; the pre C++11 meaning.
6773 backup-kwd-sym
6774 ;; Set if we've found a specifier (apart from "typedef") that makes
6775 ;; the defined identifier(s) types.
6776 at-type-decl
6777 ;; Set if we've a "typedef" keyword.
6778 at-typedef
6779 ;; Set if we've found a specifier that can start a declaration
6780 ;; where there's no type.
6781 maybe-typeless
6782 ;; Save the value of kwd-sym between loops of the "Check for a
6783 ;; type" loop. Needed to distinguish a C++11 "auto" from a pre
6784 ;; C++11 one.
6785 prev-kwd-sym
6786 ;; If a specifier is found that also can be a type prefix,
6787 ;; these flags are set instead of those above. If we need to
6788 ;; back up an identifier, they are copied to the real flag
6789 ;; variables. Thus they only take effect if we fail to
6790 ;; interpret it as a type.
6791 backup-at-type-decl backup-maybe-typeless
6792 ;; Whether we've found a declaration or a cast. We might know
6793 ;; this before we've found the type in it. It's 'ids if we've
6794 ;; found two consecutive identifiers (usually a sure sign, but
6795 ;; we should allow that in labels too), and t if we've found a
6796 ;; specifier keyword (a 100% sure sign).
6797 at-decl-or-cast
6798 ;; Set when we need to back up to parse this as a declaration
6799 ;; but not as a cast.
6800 backup-if-not-cast
6801 ;; For casts, the return position.
6802 cast-end
6803 ;; Have we got a new-style C++11 "auto"?
6804 new-style-auto
6805 ;; Save `c-record-type-identifiers' and
6806 ;; `c-record-ref-identifiers' since ranges are recorded
6807 ;; speculatively and should be thrown away if it turns out
6808 ;; that it isn't a declaration or cast.
6815 ;; Check for a type. Unknown symbols are treated as possible
6816 ;; types, but they could also be specifiers disguised through
6817 ;; macros like __INLINE__, so we recognize both types and known
6818 ;; specifiers after them too.
6822 ;; Look for a specifier keyword clause.
6835 ;; Found a known or possible type or a prefix of a known type.
6844 ;; Got two identifiers with nothing but whitespace
6845 ;; between them. That can only happen in declarations.
6849 ;; If the previous identifier is a found type we
6850 ;; record it as a real one; it might be some sort of
6851 ;; alias for a prefix like "unsigned".
6858 backup-type-start type-start
6859 backup-id-start id-start
6860 backup-kwd-sym kwd-sym
6861 at-type found-type
6862 type-start start
6864 ;; The previous ambiguous specifier/type turned out
6865 ;; to be a type since we've parsed another one after
6866 ;; it, so clear these backup flags.
6867 backup-at-type-decl nil
6868 backup-maybe-typeless nil))
6872 ;; Handle known specifier keywords and
6873 ;; `c-decl-hangon-kwds' which can occur after known
6874 ;; types.
6877 ;; It's a hang-on keyword that can occur anywhere.
6881 ;; Move the identifier start position if
6882 ;; we've passed a type.
6884 ;; Otherwise treat this as a specifier and
6885 ;; move the fallback position.
6889 ;; It's an ordinary specifier so we know that
6890 ;; anything before this can't be the type.
6892 start-pos kwd-clause-end)
6895 ;; It's ambiguous whether this keyword is a
6896 ;; specifier or a type prefix, so set the backup
6897 ;; flags. (It's assumed that `c-forward-type'
6898 ;; moved further than `c-forward-keyword-clause'.)
6906 ;; This test only happens after we've scanned a type.
6907 ;; So, with valid syntax, kwd-sym can't be 'typedef.
6912 ;; Haven't matched a type so it's an unambiguous
6913 ;; specifier keyword and we know we're in a
6914 ;; declaration.
6920 ;; If the type isn't known we continue so that we'll jump
6921 ;; over all specifiers and type identifiers. The reason
6922 ;; to do this for a known type prefix is to make things
6923 ;; like "unsigned INT16" work.
6928 ;; If a known type was found, we still need to skip over any
6929 ;; hangon keyword clauses after it. Otherwise it has already
6930 ;; been done in the loop above.
6936 ;; A prefix type is itself a primitive type when it's not
6937 ;; followed by another type.
6941 ;; Got no type but set things up to continue anyway to handle
6942 ;; the various cases when a declaration doesn't start with a
6943 ;; type.
6948 ;; If it's C++ then check if the last "type" ends on the form
6949 ;; "foo::foo" or "foo::~foo", i.e. if it's the name of a
6950 ;; (con|de)structor.
6961 ;; Cheating in the handling of syntactic ws below.
6968 name))
6969 ;; It is a (con|de)structor name. In that case the
6970 ;; declaration is typeless so zap out any preceding
6971 ;; identifier(s) that we might have taken as types.
6974 backup-at-type nil
6975 id-start type-start))))))
6977 ;; Check for and step over a type decl expression after the thing
6978 ;; that is or might be a type. This can't be skipped since we
6979 ;; need the correct end position of the declarator for
6980 ;; `max-type-decl-end-*'.
6982 ;; True if there's a non-open-paren match of
6983 ;; `c-type-decl-prefix-key'.
6984 got-prefix
6985 ;; True if the declarator is surrounded by a parenthesis pair.
6986 got-parens
6987 ;; True if there is an identifier in the declarator.
6988 got-identifier
6989 ;; True if there's a non-close-paren match of
6990 ;; `c-type-decl-suffix-key'.
6991 got-suffix
6992 ;; True if there's a prefix match outside the outermost
6993 ;; paren pair that surrounds the declarator.
6994 got-prefix-before-parens
6995 ;; True if there's a suffix match outside the outermost
6996 ;; paren pair that surrounds the declarator. The value is
6997 ;; the position of the first suffix match.
6998 got-suffix-after-parens
6999 ;; True if we've parsed the type decl to a token that is
7000 ;; known to end declarations in this context.
7001 at-decl-end
7002 ;; The earlier values of `at-type' and `type-start' if we've
7003 ;; shifted the type backwards.
7004 identifier-type identifier-start
7005 ;; If `c-parse-and-markup-<>-arglists' is set we need to
7006 ;; turn it off during the name skipping below to avoid
7007 ;; getting `c-type' properties that might be bogus. That
7008 ;; can happen since we don't know if
7009 ;; `c-restricted-<>-arglists' will be correct inside the
7010 ;; arglist paren that gets entered.
7011 c-parse-and-markup-<>-arglists
7012 ;; Start of the identifier for which `got-identifier' was set.
7013 name-start)
7017 ;; Skip over type decl prefix operators. (Note similar code in
7018 ;; `c-font-lock-declarators'.)
7028 ;; If the third submatch matches in C++ then
7029 ;; we're looking at an identifier that's a
7030 ;; prefix only if it specifies a member pointer.
7035 ;; We only check for a trailing "::" and
7036 ;; let the "*" that should follow be
7037 ;; matched in the next round.
7039 ;; It turned out to be the real identifier,
7040 ;; so stop.
7041 nil))
7042 t))
7056 ;; Skip over an identifier.
7063 ;; Skip over type decl suffix operators.
7070 t)
7074 t)
7080 ;; No suffix matched. We might have matched the
7081 ;; identifier as a type and the open paren of a
7082 ;; function arglist as a type decl prefix. In that
7083 ;; case we should "backtrack": Reinterpret the last
7084 ;; type as the identifier, move out of the arglist and
7085 ;; continue searching for suffix operators.
7086 ;;
7087 ;; Do this even if there's no preceding type, to cope
7088 ;; with old style function declarations in K&R C,
7089 ;; (con|de)structors in C++ and `c-typeless-decl-kwds'
7090 ;; style declarations. That isn't applicable in an
7091 ;; arglist context, though.
7096 maybe-typeless
7097 backup-maybe-typeless
7104 t))
7113 at-type))
7114 ;; Have found no identifier but `c-typeless-decl-kwds' has
7115 ;; matched so we know we're inside a declaration. The
7116 ;; preceding type must be the identifier instead.
7119 ;; Prepare the "-> type;" for fontification later on.
7129 at-decl-or-cast
7132 ;; CASE 1
7134 ;; Encountered something inside parens that isn't matched by
7135 ;; the `c-type-decl-*' regexps, so it's not a type decl
7136 ;; expression. Try to skip out to the same paren depth to
7137 ;; not confuse the cast check below.
7139 ;; If we've found a specifier keyword then it's a
7140 ;; declaration regardless.
7148 ;; Now we've collected info about various characteristics of
7149 ;; the construct we're looking at. Below follows a decision
7150 ;; tree based on that. It's ordered to check more certain
7151 ;; signs before less certain ones.
7156 ;; CASE 2
7159 ;; Got another identifier directly after the type, so it's a
7160 ;; declaration.
7165 ;; (not got-suffix-after-parens)
7167 maybe-typeless
7168 backup-maybe-typeless
7173 ;; Got a declaration of the form "foo bar (gnu);" or "bar
7174 ;; (gnu);" where we've recognized "bar" as the type and "gnu"
7175 ;; as the declarator. In this case it's however more likely
7176 ;; that "bar" is the declarator and "gnu" a function argument
7177 ;; or initializer (if `c-recognize-paren-inits' is set),
7178 ;; since the parens around "gnu" would be superfluous if it's
7179 ;; a declarator. Shift the type one step backward.
7182 ;; Found no identifier.
7187 ;; CASE 3
7189 ;; Got a plain list of identifiers. If a colon follows it's
7190 ;; a valid label, or maybe a bitfield. Otherwise the last
7191 ;; one probably is the declared identifier and we should
7192 ;; back up to the previous type, providing it isn't a cast.
7196 ;; If we've found a specifier keyword then it's a
7197 ;; declaration regardless.
7208 ;; CASE 4
7212 ;; Got a plain list of identifiers followed by some suffix.
7213 ;; If this isn't a cast then the last identifier probably is
7214 ;; the declared one and we should back up to the previous
7215 ;; type.
7219 ;; CASE 5
7221 ;; If the type is known we know that there can't be any
7222 ;; identifier somewhere else, and it's only in declarations in
7223 ;; e.g. function prototypes and in casts that the identifier may
7224 ;; be left out.
7228 ;; Only got a single identifier (parsed as a type so far).
7229 ;; CASE 6
7231 ;; Check that the identifier isn't at the start of an
7232 ;; expression.
7233 at-decl-end
7236 ;; Inside an arglist that contains declarations. If K&R
7237 ;; style declarations and parenthesis style initializers
7238 ;; aren't allowed then the single identifier must be a
7239 ;; type, else we require that it's known or found
7240 ;; (primitive types are handled above).
7245 ;; Inside a template arglist. Accept known and found
7246 ;; types; other identifiers could just as well be
7247 ;; constants in C++.
7250 ;; CASE 7
7251 ;; Can't be a valid declaration or cast, but if we've found a
7252 ;; specifier it can't be anything else either, so treat it as
7253 ;; an invalid/unfinished declaration or cast.
7261 maybe-typeless
7262 backup-maybe-typeless
7266 c-after-suffixed-type-maybe-decl-key))))))
7267 ;; Got an empty paren pair and a preceding type that probably
7268 ;; really is the identifier. Shift the type backwards to make
7269 ;; the last one the identifier. This is analogous to the
7270 ;; "backtracking" done inside the `c-type-decl-suffix-key' loop
7271 ;; above.
7272 ;;
7273 ;; Exception: In addition to the conditions in that
7274 ;; "backtracking" code, do not shift backward if we're not
7275 ;; looking at either `c-after-suffixed-type-decl-key' or "[;,]".
7276 ;; Since there's no preceding type, the shift would mean that
7277 ;; the declaration is typeless. But if the regexp doesn't match
7278 ;; then we will simply fall through in the tests below and not
7279 ;; recognize it at all, so it's better to try it as an abstract
7280 ;; declarator instead.
7283 ;; Still no identifier.
7284 ;; CASE 8
7286 ;; Require `got-prefix' together with either `got-parens' or
7287 ;; `got-suffix' to recognize it as an abstract declarator:
7288 ;; `got-parens' only is probably an empty function call.
7289 ;; `got-suffix' only can build an ordinary expression together
7290 ;; with the preceding identifier which we've taken as a type.
7291 ;; We could actually accept on `got-prefix' only, but that can
7292 ;; easily occur temporarily while writing an expression so we
7293 ;; avoid that case anyway. We could do a better job if we knew
7294 ;; the point when the fontification was invoked.
7297 ;; CASE 9
7301 got-suffix-after-parens
7303 ;; Got a type, no declarator but a paren suffix. I.e. it's a
7304 ;; normal function call after all (or perhaps a C++ style object
7305 ;; instantiation expression).
7308 ;; CASE 10
7310 ;; By now we've located the type in the declaration that we know
7311 ;; we're in.
7314 ;; CASE 11
7322 ;; Shift the type backward in the case that there's a
7323 ;; single identifier inside parens. That can only
7324 ;; occur in K&R style function declarations so it's
7325 ;; more likely that it really is a function call.
7326 ;; Therefore we only do this after
7327 ;; `c-after-suffixed-type-decl-key' has matched.
7329 got-suffix-after-parens))
7330 ;; A declaration according to `c-after-suffixed-type-decl-key'.
7333 ;; CASE 12
7336 ;; It's a declaration if a known type precedes it and it can't be a
7337 ;; function call.
7340 ;; If we get here we can't tell if this is a type decl or a normal
7341 ;; expression by looking at it alone. (That's under the assumption
7342 ;; that normal expressions always can look like type decl expressions,
7343 ;; which isn't really true but the cases where it doesn't hold are so
7344 ;; uncommon (e.g. some placements of "const" in C++) it's not worth
7345 ;; the effort to look for them.)
7347 ;;; 2008-04-16: commented out the next form, to allow the function to recognize
7348 ;;; "foo (int bar)" in CC (an implicit type (in class foo) without a semicolon)
7349 ;;; as a(n almost complete) declaration, enabling it to be fontified.
7350 ;; CASE 13
7351 ;; (unless (or at-decl-end (looking-at "=[^=]"))
7352 ;; If this is a declaration it should end here or its initializer(*)
7353 ;; should start here, so check for allowed separation tokens. Note
7354 ;; that this rule doesn't work e.g. with a K&R arglist after a
7355 ;; function header.
7356 ;;
7357 ;; *) Don't check for C++ style initializers using parens
7358 ;; since those already have been matched as suffixes.
7359 ;;
7360 ;; If `at-decl-or-cast' is then we've found some other sign that
7361 ;; it's a declaration or cast, so then it's probably an
7362 ;; invalid/unfinished one.
7363 ;; (throw 'at-decl-or-cast at-decl-or-cast))
7365 ;; Below are tests that only should be applied when we're certain to
7366 ;; not have parsed halfway through an expression.
7368 ;; CASE 14
7370 ;; The expression starts with a known type so treat it as a
7371 ;; declaration.
7374 ;; CASE 15
7376 ;; In C++ we check if the identifier is a known type, since
7377 ;; (con|de)structors use the class name as identifier.
7378 ;; We've always shifted over the identifier as a type and
7379 ;; then backed up again in this case.
7380 identifier-type
7383 ;; `at-type' probably won't be 'found for
7384 ;; destructors since the "~" is then part of the
7385 ;; type name being checked against the list of
7386 ;; known types, so do a check without that
7387 ;; operator.
7392 c-identifier-syntax-table
7396 ;; We have already parsed the type earlier,
7397 ;; so it'd be possible to cache the end
7398 ;; position instead of redoing it here, but
7399 ;; then we'd need to keep track of another
7400 ;; position everywhere.
7408 ;; CASE 16
7410 at-type
7414 ;; Got something like "foo * bar;". Since we're not inside an
7415 ;; arglist it would be a meaningless expression because the
7416 ;; result isn't used. We therefore choose to recognize it as
7417 ;; a declaration. Do not allow a suffix since it could then
7418 ;; be a function call.
7421 ;; CASE 17
7426 ;; Got something like "a (*b) (c);" or "a (b) = c;". It could
7427 ;; be an odd expression or it could be a declaration. Treat
7428 ;; it as a declaration if "a" has been used as a type
7429 ;; somewhere else (if it's a known type we won't get here).
7432 ;; CASE 18
7438 ;; Got a type followed by an abstract declarator. If `got-prefix'
7439 ;; is set it's something like "a *" without anything after it. If
7440 ;; `got-parens' or `got-suffix' is set it's "a()", "a[]", "a()[]",
7441 ;; or similar, which we accept only if the context rules out
7442 ;; expressions.
7445 ;; If we had a complete symbol table here (which rules out
7446 ;; `c-found-types') we should return t due to the disambiguation rule
7447 ;; (in at least C++) that anything that can be parsed as a declaration
7448 ;; is a declaration. Now we're being more defensive and prefer to
7449 ;; highlight things like "foo (bar);" as a declaration only if we're
7450 ;; inside an arglist that contains declarations.
7451 ;; CASE 19
7454 ;; The point is now after the type decl expression.
7457 ;; Check for a cast.
7460 c-cast-parens
7462 ;; Should be the first type/identifier in a cast paren.
7466 ;; The closing paren should follow.
7471 ;; There should be a primary expression after it.
7480 ;; Check if the expression begins with a prefix keyword.
7483 ;; Expression begins with an ambiguous operator. Treat
7484 ;; it as a cast if it's a type decl or if we've
7485 ;; recognized the type somewhere else.
7488 ;; Unless it's a keyword, it's the beginning of a primary
7489 ;; expression.
7491 ;; If `c-primary-expr-regexp' matched a nonsymbol token, check
7492 ;; that it matched a whole one so that we don't e.g. confuse
7493 ;; the operator '-' with '->'. It's ok if it matches further,
7494 ;; though, since it e.g. can match the float '.5' while the
7495 ;; operator regexp only matches '.'.
7499 ;; There should either be a cast before it or something that isn't an
7500 ;; identifier or close paren.
7508 ;; It's a symbol. Accept it only if it's one of the
7509 ;; keywords that can precede an expression (without
7510 ;; surrounding parens).
7513 ;; Check that it isn't a close paren (block close is ok,
7514 ;; though).
7516 ;; Check that it isn't a nonsymbol identifier.
7519 ;; Handle the cast.
7529 ;; We're at a declaration. Highlight the type and the following
7530 ;; declarators.
7536 ;; Make sure to propagate the `c-decl-arg-start' property to
7537 ;; the next argument if it's set in this one, to cope with
7538 ;; interactive refontification.
7541 ;; Record the type's coordinates in `c-record-type-identifiers' for
7542 ;; later fontification.
7544 ;; There seems no reason to exclude a token from
7545 ;; fontification just because it's "a known type that can't
7546 ;; be a name or other expression". 2013-09-18.
7547 )
7558 ;; False alarm. Restore the recorded ranges.
7560 c-record-ref-identifiers save-rec-ref-ids)
7561 nil))))
7564 ;; Assuming that point is at the beginning of a token, check if it starts a
7565 ;; label and if so move over it and return non-nil (t in default situations,
7566 ;; specific symbols (see below) for interesting situations), otherwise don't
7567 ;; move and return nil. "Label" here means "most things with a colon".
7568 ;;
7569 ;; More precisely, a "label" is regarded as one of:
7570 ;; (i) a goto target like "foo:" - returns the symbol `goto-target';
7571 ;; (ii) A case label - either the entire construct "case FOO:", or just the
7572 ;; bare "case", should the colon be missing. We return t;
7573 ;; (iii) a keyword which needs a colon, like "default:" or "private:"; We
7574 ;; return t;
7575 ;; (iv) One of QT's "extended" C++ variants of
7576 ;; "private:"/"protected:"/"public:"/"more:" looking like "public slots:".
7577 ;; Returns the symbol `qt-2kwds-colon'.
7578 ;; (v) QT's construct "signals:". Returns the symbol `qt-1kwd-colon'.
7579 ;; (vi) One of the keywords matched by `c-opt-extra-label-key' (without any
7580 ;; colon). Currently (2006-03), this applies only to Objective C's
7581 ;; keywords "@private", "@protected", and "@public". Returns t.
7582 ;;
7583 ;; One of the things which will NOT be recognized as a label is a bit-field
7584 ;; element of a struct, something like "int foo:5".
7585 ;;
7586 ;; The end of the label is taken to be just after the colon, or the end of
7587 ;; the first submatch in `c-opt-extra-label-key'. The point is directly
7588 ;; after the end on return. The terminating char gets marked with
7589 ;; `c-decl-end' to improve recognition of the following declaration or
7590 ;; statement.
7591 ;;
7592 ;; If ASSUME-MARKUP is non-nil, it's assumed that the preceding
7593 ;; label, if any, has already been marked up like that.
7594 ;;
7595 ;; If PRECEDING-TOKEN-END is given, it should be the first position
7596 ;; after the preceding token, i.e. on the other side of the
7597 ;; syntactic ws from the point. Use a value less than or equal to
7598 ;; (point-min) if the point is at the first token in (the visible
7599 ;; part of) the buffer.
7600 ;;
7601 ;; The optional LIMIT limits the forward scan for the colon.
7602 ;;
7603 ;; This function records the ranges of the label symbols on
7604 ;; `c-record-ref-identifiers' if `c-record-type-identifiers' (!) is
7605 ;; non-nil.
7606 ;;
7607 ;; This function might do hidden buffer changes.
7610 label-end
7611 qt-symbol-idx
7612 macro-start ; if we're in one.
7613 label-type
7614 kwd)
7616 ;; "case" or "default" (Doesn't apply to AWK).
7619 ;; Record only the keyword itself for fontification, since in
7620 ;; case labels the following is a constant expression and not
7621 ;; a label.
7625 ;; Find the label end.
7629 ;; Stop on chars that aren't allowed in expressions,
7630 ;; and on operator chars that would be meaningless
7631 ;; there. FIXME: This doesn't cope with ?: operators.
7639 t)
7641 ;; It's an unfinished label. We consider the keyword enough
7642 ;; to recognize it as a label, so that it gets fontified.
7643 ;; Leave the point at the end of it, but don't put any
7644 ;; `c-decl-end' marker.
7646 t))))
7648 ;; @private, @protected, @public, in Objective C, or similar.
7651 ;; For a `c-opt-extra-label-key' match, we record the whole
7652 ;; thing for fontification. That's to get the leading '@' in
7653 ;; Objective-C protection labels fontified.
7660 ;; All other cases of labels.
7663 ;; A colon label must have something before the colon.
7666 ;; Check that we're not after a token that can't precede a label.
7668 ;; Trivially succeeds when there's no preceding token.
7669 ;; Succeeds when we're at a virtual semicolon.
7678 ;; Check if we're after a label, if we're after a closing
7679 ;; paren that belong to statement, and with
7680 ;; `c-label-prefix-re'. It's done in different order
7681 ;; depending on `assume-markup' since the checks have
7682 ;; different expensiveness.
7709 ;; Might be after another label, so check it recursively.
7713 ;; Essentially the same as the
7714 ;; `c-syntactic-re-search-forward' regexp below.
7720 ;; Note: the following should work instead of the
7721 ;; narrow-to-region above. Investigate why not,
7722 ;; sometime. ACM, 2006-03-31.
7723 ;; (c-syntactic-skip-backward "^-]:?;}=*/%&|,<>!@+"
7724 ;; macro-start t)
7726 ;; If the caller turned on recording for us,
7727 ;; it shouldn't apply when we check the
7728 ;; preceding label.
7729 c-record-type-identifiers)
7730 ;; A label can't start at a cpp directive. Check for
7731 ;; this, since c-forward-syntactic-ws would foul up on it.
7736 ;; Point is still at the beginning of the possible label construct.
7737 ;;
7738 ;; Check that the next nonsymbol token is ":", or that we're in one
7739 ;; of QT's "slots" declarations. Allow '(' for the sake of macro
7740 ;; arguments. FIXME: Should build this regexp from the language
7741 ;; constants.
7743 ;; public: protected: private:
7753 ;; QT double keyword like "protected slots:" or goto target.
7772 'qt-1kwd-colon
7784 ;; Check that `c-nonlabel-token-key' doesn't match anywhere.
7794 t)
7797 ;; Record the identifiers in the label for fontification, unless
7798 ;; it begins with `c-label-kwds' in which case the following
7799 ;; identifiers are part of a (constant) expression that
7800 ;; shouldn't be fontified.
7812 ;; Not a label.
7814 label-type))
7817 ;; Assuming the point is at the beginning of a token, try to move
7818 ;; forward to the end of the Objective-C directive that starts
7819 ;; there. Return t if a directive was fully recognized, otherwise
7820 ;; the point is moved as far as one could be successfully parsed and
7821 ;; nil is returned.
7822 ;;
7823 ;; This function records identifier ranges on
7824 ;; `c-record-type-identifiers' and `c-record-ref-identifiers' if
7825 ;; `c-record-type-identifiers' is non-nil.
7826 ;;
7827 ;; This function might do hidden buffer changes.
7830 start-char
7832 lim
7833 ;; Turn off recognition of angle bracket arglists while parsing
7834 ;; types here since the protocol reference list might then be
7835 ;; considered part of the preceding name or superclass-name.
7846 t)
7855 ;; Handle the name of the class itself.
7857 ;; (c-forward-token-2) ; 2006/1/13 This doesn't move if the token's
7858 ;; at EOB.
7865 ;; Look for ": superclass-name" or "( category-name )".
7876 ;; Look for a protocol reference list.
7882 t))))
7888 t)
7891 nil)))
7894 ;; Go to the first non-whitespace after the colon that starts a
7895 ;; multiple inheritance introduction. Optional LIM is the farthest
7896 ;; back we should search.
7897 ;;
7898 ;; This function might do hidden buffer changes.
7906 ;; Return nil if we aren't in a method definition, otherwise the
7907 ;; position of the initial [+-].
7908 ;;
7909 ;; This function might do hidden buffer changes.
7915 ))
7917 ;; Contributed by Kevin Ryde <user42@zip.com.au>.
7919 ;; Return non-nil if point is within a gcc \"asm\" block.
7920 ;;
7921 ;; This should be called with point inside an argument list.
7922 ;;
7923 ;; Only one level of enclosing parentheses is considered, so for
7924 ;; instance `nil' is returned when in a function call within an asm
7925 ;; operand.
7926 ;;
7927 ;; This function might do hidden buffer changes.
7939 a function.
7941 More precisely, being at the top-level means that point is either
7942 outside any enclosing block (such as a function definition), or
7943 directly inside a class, namespace or other block that contains
7944 another declaration level.
7946 If point is not at the top-level (e.g. it is inside a method
7947 definition), then nil is returned. Otherwise, if point is at a
7948 top-level not enclosed within a class definition, t is returned.
7949 Otherwise, a 2-vector is returned where the zeroth element is the
7950 buffer position of the start of the class declaration, and the first
7951 element is the buffer position of the enclosing class's opening
7952 brace.
7954 Note that this function might do hidden buffer changes. See the
7955 comment at the start of cc-engine.el for more info."
7961 ;; Return non-nil if the point is in the region after the argument
7962 ;; list of a function and its opening brace (or semicolon in case it
7963 ;; got no body). If there are K&R style argument declarations in
7964 ;; that region, the point has to be inside the first one for this
7965 ;; function to recognize it.
7966 ;;
7967 ;; If successful, the point is moved to the first token after the
7968 ;; function header (see `c-forward-decl-or-cast-1' for details) and
7969 ;; the position of the opening paren of the function arglist is
7970 ;; returned.
7971 ;;
7972 ;; The point is clobbered if not successful.
7973 ;;
7974 ;; LIM is used as bound for backward buffer searches.
7975 ;;
7976 ;; This function might do hidden buffer changes.
7989 ;; There should not be a '=' or ',' between beg and the
7990 ;; start of the declaration since that means we were in the
7991 ;; "expression part" of the declaration.
7996 ;; Check that there's an arglist paren in the
7997 ;; declaration.
8000 ;; The declarator is a paren expression, so skip past it
8001 ;; so that we don't get stuck on that instead of the
8002 ;; function arglist.
8006 ;; Don't trip up on "operator ()".
8013 ;; Return the position of the first argument declaration if point is
8014 ;; inside a K&R style argument declaration list, nil otherwise.
8015 ;; `c-recognize-knr-p' is not checked. If LIM is non-nil, it's a
8016 ;; position that bounds the backward search for the argument list.
8017 ;;
8018 ;; Point must be within a possible K&R region, e.g. just before a top-level
8019 ;; "{". It must be outside of parens and brackets. The test can return
8020 ;; false positives otherwise.
8021 ;;
8022 ;; This function might do hidden buffer changes.
8026 ;; If we're in a macro, our search range is restricted to it. Narrow to
8027 ;; the searchable range.
8031 before-lparen after-rparen
8033 ; we give up
8036 ;; Search backwards for the defun's argument list. We give up if we
8037 ;; encounter a "}" (end of a previous defun) an "=" (which can't be in
8038 ;; a knr region) or BOB.
8039 ;;
8040 ;; The criterion for a paren structure being the arg list is:
8041 ;; o - there is non-WS stuff after it but before any "{"; AND
8042 ;; o - the token after it isn't a ";" AND
8043 ;; o - it is preceded by either an identifier (the function name) or
8044 ;; a macro expansion like "DEFUN (...)"; AND
8045 ;; o - its content is a non-empty comma-separated list of identifiers
8046 ;; (an empty arg list won't have a knr region).
8047 ;;
8048 ;; The following snippet illustrates these rules:
8049 ;; int foo (bar, baz, yuk)
8050 ;; int bar [] ;
8051 ;; int (*baz) (my_type) ;
8052 ;; int (*) (void) (*yuk) (void) ;
8053 ;; {
8064 ; parens/brackets.
8068 ;; We're inside a paren. Could it be our argument list....?
8074 ;; FIXME!!! What about macros between the parens? 2007/01/20
8077 ;; It can't be the arg list if next token is ; or {
8082 ;; Is the thing preceding the list an identifier (the
8083 ;; function name), or a macro expansion?
8093 ;; Have we got a non-empty list of comma-separated
8094 ;; identifiers?
8108 ;; ...Yes. We've identified the function's argument list.
8114 ;; ...No. The current parens aren't the function's arg list.
8121 ;; skip forward over conditional at point, including any predicate
8122 ;; statements in parentheses. No error checking is performed.
8123 ;;
8124 ;; This function might do hidden buffer changes.
8126 ;; else if()
8131 ;; do, else, try, finally
8136 ;; for, if, while, switch, catch, synchronized, foreach
8140 ;; If looking at the token after a conditional then return the
8141 ;; position of its start, otherwise return nil.
8142 ;;
8143 ;; This function might do hidden buffer changes.
8154 ;; If the point is after an operator identifier that isn't handled
8155 ;; like an ordinary symbol (i.e. like "operator =" in C++) then the
8156 ;; position of the start of that identifier is returned. nil is
8157 ;; returned otherwise. The point may be anywhere in the syntactic
8158 ;; whitespace after the last token of the operator identifier.
8159 ;;
8160 ;; This function might do hidden buffer changes.
8172 ;; Assuming point is at a brace that opens a statement block of some
8173 ;; kind, move to the proper anchor point for that block. It might
8174 ;; need to be adjusted further by c-add-stmt-syntax, but the
8175 ;; position at return is suitable as start position for that
8176 ;; function.
8177 ;;
8178 ;; This function might do hidden buffer changes.
8185 ;; Assuming point is at a brace that opens the block of a top level
8186 ;; declaration of some kind, move to the proper anchor point for
8187 ;; that block.
8188 ;;
8189 ;; This function might do hidden buffer changes.
8194 ;; Search forward for the end of the "header" of the current
8195 ;; declaration. That's the position where the definition body
8196 ;; starts, or the first variable initializer, or the ending
8197 ;; semicolon. I.e. search forward for the closest following
8198 ;; (syntactically relevant) '{', '=' or ';' token. Point is left
8199 ;; _after_ the first found token, or at point-max if none is found.
8200 ;;
8201 ;; This function might do hidden buffer changes.
8206 ;; In C++ we need to take special care to handle operator
8207 ;; tokens and those pesky template brackets.
8212 ;; Handle operator identifiers, i.e. ignore any
8213 ;; operator token preceded by "operator".
8220 t
8222 nil)))))
8231 ;; Go to the beginning of the current declaration, or the beginning
8232 ;; of the previous one if already at the start of it. Point won't
8233 ;; be moved out of any surrounding paren. Return a cons cell of the
8234 ;; form (MOVE . KNR-POS). MOVE is like the return value from
8235 ;; `c-beginning-of-statement-1'. If point skipped over some K&R
8236 ;; style argument declarations (and they are to be recognized) then
8237 ;; KNR-POS is set to the start of the first such argument
8238 ;; declaration, otherwise KNR-POS is nil. If LIM is non-nil, it's a
8239 ;; position that bounds the backward search.
8240 ;;
8241 ;; NB: Cases where the declaration continues after the block, as in
8242 ;; "struct foo { ... } bar;", are currently recognized as two
8243 ;; declarations, e.g. "struct foo { ... }" and "bar;" in this case.
8244 ;;
8245 ;; This function might do hidden buffer changes.
8251 ;; `c-beginning-of-statement-1' stops at a block start, but we
8252 ;; want to continue if the block doesn't begin a top level
8253 ;; construct, i.e. if it isn't preceded by ';', '}', ':', bob,
8254 ;; or an open paren.
8256 ;; Go back one "statement" each time round the loop until we're just
8257 ;; after a ;, }, or :, or at BOB or the start of a macro or start of
8258 ;; an ObjC method. This will move over a multiple declaration whose
8259 ;; components are comma separated.
8261 ;; Must check with c-opt-method-key in ObjC mode.
8271 ;; Check that we don't move from the first thing in a
8272 ;; macro to its header.
8278 move tentative-move))
8283 ;; Handle K&R argdecls. Back up after the "statement" jumped
8284 ;; over by `c-beginning-of-statement-1', unless it was the
8285 ;; function body, in which case we're sitting on the opening
8286 ;; brace now. Then test if we're in a K&R argdecl region and
8287 ;; that we started at the other side of the first argdecl in
8288 ;; it.
8298 'previous
8300 knr-argdecl-start))
8303 ;; `c-beginning-of-statement-1' counts each brace block as a separate
8304 ;; statement, so the result will be 'previous if we've moved over any.
8305 ;; So change our result back to 'same if necessary.
8306 ;;
8307 ;; If they were brace list initializers we might not have moved over a
8308 ;; declaration boundary though, so change it to 'same if we've moved
8309 ;; past a '=' before '{', but not ';'. (This ought to be integrated
8310 ;; into `c-beginning-of-statement-1', so we avoid this extra pass which
8311 ;; potentially can search over a large amount of text.). Take special
8312 ;; pains not to get mislead by C++'s "operator=", and the like.
8315 c++-template-syntax-table
8321 ; no more, or get to one which isn't an "operator ="
8324 c-overloadable-operators-regexp
8325 c-opt-op-identifier-prefix
8340 ;; Assuming point is at the start of a declaration (as detected by
8341 ;; e.g. `c-beginning-of-decl-1'), go to the end of it. Unlike
8342 ;; `c-beginning-of-decl-1', this function handles the case when a
8343 ;; block is followed by identifiers in e.g. struct declarations in C
8344 ;; or C++. If a proper end was found then t is returned, otherwise
8345 ;; point is moved as far as possible within the current sexp and nil
8346 ;; is returned. This function doesn't handle macros; use
8347 ;; `c-end-of-macro' instead in those cases.
8348 ;;
8349 ;; This function might do hidden buffer changes.
8352 c++-template-syntax-table
8360 ;; Stopped at the ';' in a K&R argdecl section which is
8361 ;; detected using the same criteria as in
8362 ;; `c-beginning-of-decl-1'. Move to the following block
8363 ;; start.
8367 ;; Encountered a block in the declaration. Jump over it.
8378 ;; Check for `c-opt-block-decls-with-vars-key'
8379 ;; before the first paren.
8382 c-opt-block-decls-with-vars-key
8384 lim t t t)
8387 ;; Check that the first following paren is
8388 ;; the block.
8390 lim t t t)
8392 ;; The declaration doesn't have any of the
8393 ;; `c-opt-block-decls-with-vars' keywords in the
8394 ;; beginning, so it ends here at the end of the block.
8402 nil)))
8405 ;; Assuming the point is at an open brace, check if it starts a
8406 ;; block that contains another declaration level, i.e. that isn't a
8407 ;; statement block or a brace list, and if so return non-nil.
8408 ;;
8409 ;; If the check is successful, the return value is the start of the
8410 ;; keyword that tells what kind of construct it is, i.e. typically
8411 ;; what `c-decl-block-key' matched. Also, if GOTO-START is set then
8412 ;; the point will be at the start of the construct, before any
8413 ;; leading specifiers, otherwise it's at the returned position.
8414 ;;
8415 ;; The point is clobbered if the check is unsuccessful.
8416 ;;
8417 ;; CONTAINING-SEXP is the position of the open of the surrounding
8418 ;; paren, or nil if none.
8419 ;;
8420 ;; The optional LIMIT limits the backward search for the start of
8421 ;; the construct. It's assumed to be at a syntactically relevant
8422 ;; position.
8423 ;;
8424 ;; If any template arglists are found in the searched region before
8425 ;; the open brace, they get marked with paren syntax.
8426 ;;
8427 ;; This function might do hidden buffer changes.
8434 ;; Could be at the end of a template arglist.
8445 ;; Note: Can't get bogus hits inside template arglists below since they
8446 ;; have gotten paren syntax above.
8448 ;; If `goto-start' is set we begin by searching for the
8449 ;; first possible position of a leading specifier list.
8450 ;; The `c-decl-block-key' search continues from there since
8451 ;; we know it can't match earlier.
8454 open-brace t t)
8456 t)
8457 t)
8463 ;; Exclude cases where we matched what would ordinarily
8464 ;; be a block declaration keyword, except where it's not
8465 ;; legal because it's part of a "compound keyword" like
8466 ;; "enum class". Of course, if c-after-brace-list-key
8467 ;; is nil, we can skip the test.
8477 ;; Found a keyword that can't be a type?
8480 ;; Can be a type too, in which case it's the return type of a
8481 ;; function (under the assumption that no declaration level
8482 ;; block construct starts with a type).
8485 ;; Jumped over a type, but it could be a declaration keyword
8486 ;; followed by the declared identifier that we've jumped over
8487 ;; instead (e.g. in "class Foo {"). If it indeed is a type
8488 ;; then we should be at the declarator now, so check for a
8489 ;; valid declarator start.
8490 ;;
8491 ;; Note: This doesn't cope with the case when a declared
8492 ;; identifier is followed by e.g. '(' in a language where '('
8493 ;; also might be part of a declarator expression. Currently
8494 ;; there's no such language.
8498 ;; In Pike a list of modifiers may be followed by a brace
8499 ;; to make them apply to many identifiers. Note that the
8500 ;; match data will be empty on return in this case.
8506 ;; Use this variant to avoid yet another special regexp.
8510 t)))
8512 ;; Got a match.
8515 ;; Back up over any preceding specifiers and their clauses
8516 ;; by going forward from `first-specifier-pos', which is the
8517 ;; earliest possible position where the specifier list can
8518 ;; start.
8524 ;; Accept any plain symbol token on the ground that
8525 ;; it's a specifier masked through a macro (just
8526 ;; like `c-forward-decl-or-cast-1' skip forward over
8527 ;; such tokens).
8528 ;;
8529 ;; Could be more restrictive wrt invalid keywords,
8530 ;; but that'd only occur in invalid code so there's
8531 ;; no use spending effort on it.
8537 ;; Can't parse a declaration preamble and is still
8538 ;; before `kwd-start'. That means `first-specifier-pos'
8539 ;; was in some earlier construct. Search again.
8543 ;; Got no preamble before the block declaration keyword.
8549 kwd-start)))
8552 ;; Check if the closest containing paren sexp is a declaration
8553 ;; block, returning a 2 element vector in that case. Aref 0
8554 ;; contains the bufpos at boi of the class key line, and aref 1
8555 ;; contains the bufpos of the open brace. This function is an
8556 ;; obsolete wrapper for `c-looking-at-decl-block'.
8557 ;;
8558 ;; This function might do hidden buffer changes.
8566 nil))
8571 ;; Return the buffer position of the most enclosing decl-block brace (in the
8572 ;; sense of c-looking-at-decl-block) in the PAREN-STATE structure, or nil if
8573 ;; none was found.
8582 open-brace))
8585 ;; Return the position of the L-brace if point is inside a brace list
8586 ;; initialization of an array, etc. This is an approximate function,
8587 ;; designed for speed over accuracy. It will not find every bracelist, but
8588 ;; a non-nil result is reliable. We simply search for "= {" (naturally with
8589 ;; syntactic whitespace allowed). PAREN-STATE is the normal thing that it
8590 ;; is everywhere else.
8599 b-pos)))
8602 ;; We're at the token after what might be a type prefixed with a colon. Try
8603 ;; moving backward over this type and the colon. On success, return t and
8604 ;; leave point before colon; on failure, leave point unchanged. Will clobber
8605 ;; match data.
8622 nil)
8624 t)
8626 t)
8630 t)))
8633 ;; We're at a "{". Move back to the enum-like keyword that starts this
8634 ;; declaration and return t, otherwise don't move and return nil.
8636 up-sexp-pos before-identifier)
8652 t)
8658 t)
8664 ;; return the buffer position of the beginning of the brace list
8665 ;; statement if we're inside a brace list, otherwise return nil.
8666 ;; CONTAINING-SEXP is the buffer pos of the innermost containing
8667 ;; paren. PAREN-STATE is the remainder of the state of enclosing
8668 ;; braces
8669 ;;
8670 ;; N.B.: This algorithm can potentially get confused by cpp macros
8671 ;; placed in inconvenient locations. It's a trade-off we make for
8672 ;; speed.
8673 ;;
8674 ;; This function might do hidden buffer changes.
8676 ;; This will pick up brace list declarations.
8680 ;; this will pick up array/aggregate init lists, even if they are nested.
8683 ;; Pike can have class definitions anywhere, so we must
8684 ;; check for the class key here.
8686 c-decl-block-key))
8687 bufpos braceassignp lim next-containing macro-start)
8689 containing-sexp)
8700 ;; We're in an in-expression block of some kind. Do not
8701 ;; check nesting. We deliberately set the limit to the
8702 ;; containing sexp, so that c-looking-at-inexpr-block
8703 ;; doesn't check for an identifier before it.
8705 ;; see if the open brace is preceded by = or [...] in
8706 ;; this statement, but watch out for operator=
8709 ;; Checks to do only on the first sexp before the brace.
8712 ;; In Java, an initialization brace list may follow
8713 ;; directly after "new Foo[]", so check for a "new"
8714 ;; earlier.
8720 ;; Carry on looking if this is an
8721 ;; identifier (may contain "." in Java)
8722 ;; or another "[]" sexp.
8725 ;; Checks to do on all sexps before the brace, up to the
8726 ;; beginning of the statement.
8734 ;; We've seen a =, but must check earlier tokens so
8735 ;; that it isn't something that should be ignored.
8741 ;; Check for operator =
8744 nil)
8745 ;; Check for `<opchar>= in Pike.
8748 ;; Special case for Pikes
8749 ;; `[]=, since '[' is not in
8750 ;; the punctuation class.
8753 nil)
8755 ;; make sure we're not in a C++ template
8756 ;; argument assignment
8768 ))))
8769 nil)
8776 ;; We've hit the beginning of the aggregate list.
8781 ;; Brace lists can't contain a semicolon, so we're done.
8786 ;; We've a macro whose expansion starts with the '{'.
8787 ;; Heuristically, if we have a ';' in it we've not got a
8788 ;; brace list, otherwise we have.
8795 containing-sexp nil)
8798 ;; Go up one level
8800 lim nil
8801 next-containing nil)))))
8803 bufpos))
8804 ))
8807 ;; If we're looking at the start of a pike-style list, i.e., `({Â })',
8808 ;; `([Â ])', `(<Â >)', etc., a cons of a cons of its starting and ending
8809 ;; positions and its entry in c-special-brace-lists is returned, nil
8810 ;; otherwise. The ending position is nil if the list is still open.
8811 ;; LIM is the limit for forward search. The point may either be at
8812 ;; the `(' or at the following paren character. Tries to check the
8813 ;; matching closer, but assumes it's correct if no balanced paren is
8814 ;; found (i.e. the case `({ ... } ... )' is detected as _not_ being
8815 ;; a special brace list).
8816 ;;
8817 ;; This function might do hidden buffer changes.
8822 inner-beg end type)
8837 nil)))))
8847 ;; Check balancing of the inner paren
8848 ;; below.
8851 t)
8852 ;; If the inner char isn't a paren then
8853 ;; we can't check balancing, so just
8854 ;; check the char before the outer
8855 ;; closing paren.
8870 ;; Return non-nil if between two statements or declarations, assuming
8871 ;; point is not inside a literal or comment.
8872 ;;
8873 ;; Obsolete - `c-at-statement-start-p' or `c-at-expression-start-p'
8874 ;; are recommended instead.
8875 ;;
8876 ;; This function might do hidden buffer changes.
8881 ;; Return non-nil if we're looking at the beginning of a block
8882 ;; inside an expression. The value returned is actually a cons of
8883 ;; either 'inlambda, 'inexpr-statement or 'inexpr-class and the
8884 ;; position of the beginning of the construct.
8885 ;;
8886 ;; LIM limits the backward search. CONTAINING-SEXP is the start
8887 ;; position of the closest containing list. If it's nil, the
8888 ;; containing paren isn't used to decide whether we're inside an
8889 ;; expression or not. If both LIM and CONTAINING-SEXP are used, LIM
8890 ;; needs to be farther back.
8891 ;;
8892 ;; If CHECK-AT-END is non-nil then extra checks at the end of the
8893 ;; brace block might be done. It should only be used when the
8894 ;; construct can be assumed to be complete, i.e. when the original
8895 ;; starting position was further down than that.
8896 ;;
8897 ;; This function might do hidden buffer changes.
8902 ;; Look at the character after point only as a last resort
8903 ;; when we can't disambiguate.
8923 ;; If the class definition is at the start of
8924 ;; a statement, we don't consider it an
8925 ;; in-expression class.
8933 ;; Also, in Pike we treat it as an
8934 ;; in-expression class if it's used in an
8935 ;; object clone expression.
8951 nil)
8959 ;; Accept several square bracket sexps for
8960 ;; Java array initializations.
8968 block-follows
8969 containing-sexp
8978 nil
8981 res))))
8984 ;; Returns non-nil if we're looking at the end of an in-expression
8985 ;; block, otherwise the same as `c-looking-at-inexpr-block'.
8986 ;; PAREN-STATE is the paren state relevant at the current position.
8987 ;;
8988 ;; This function might do hidden buffer changes.
8990 ;; We currently only recognize a block.
8993 containing-sexp)
9002 paren-state)
9003 containing-sexp)))))
9006 ;; Is there a "virtual semicolon" at POS or point?
9007 ;; (See cc-defs.el for full details of "virtual semicolons".)
9008 ;;
9009 ;; This is true when point is at the last non syntactic WS position on the
9010 ;; line, there is a macro call last on the line, and this particular macro's
9011 ;; name is defined by the regexp `c-vs-macro-regexp' as not needing a
9012 ;; semicolon.
9020 c-macro-with-semi-re
9023 ;; Check we've got nothing after this except comments and empty lines
9024 ;; joined by escaped EOLs.
9037 nil)
9045 ;; Check for one of the listed macros being before point.
9049 t))
9057 \f
9058 ;; `c-guess-basic-syntax' and the functions that precedes it below
9059 ;; implements the main decision tree for determining the syntactic
9060 ;; analysis of the current line of code.
9062 ;; Dynamically bound to t when `c-guess-basic-syntax' is called during
9063 ;; auto newline analysis.
9067 ;; BRACEPOS is the position of a brace in a construct like "namespace
9068 ;; Bar {". Return the anchor point in this construct; this is the
9069 ;; earliest symbol on the brace's line which isn't earlier than
9070 ;; "namespace".
9071 ;;
9072 ;; Currently (2007-08-17), "like namespace" means "matches
9073 ;; c-other-block-decl-kwds". It doesn't work with "class" or "struct"
9074 ;; or anything like that.
9084 ;; A simple function to prepend a new syntax element to
9085 ;; `c-syntactic-context'. Using `setq' on it is unsafe since it
9086 ;; should always be dynamically bound but since we read it first
9087 ;; we'll fail properly anyway if this function is misused.
9089 c-syntactic-context)))
9092 ;; Like `c-add-syntax' but appends to the end of the syntax list.
9093 ;; (Normally not necessary.)
9098 syntax-extra-args
9099 stop-at-boi-only
9100 containing-sexp
9101 paren-state)
9102 ;; Add the indicated SYNTAX-SYMBOL to `c-syntactic-context', extending it as
9103 ;; needed with further syntax elements of the types `substatement',
9104 ;; `inexpr-statement', `arglist-cont-nonempty', `statement-block-intro', and
9105 ;; `defun-block-intro'.
9106 ;;
9107 ;; Do the generic processing to anchor the given syntax symbol on
9108 ;; the preceding statement: Skip over any labels and containing
9109 ;; statements on the same line, and then search backward until we
9110 ;; find a statement or block start that begins at boi without a
9111 ;; label or comment.
9112 ;;
9113 ;; Point is assumed to be at the prospective anchor point for the
9114 ;; given SYNTAX-SYMBOL. More syntax entries are added if we need to
9115 ;; skip past open parens and containing statements. Most of the added
9116 ;; syntax elements will get the same anchor point - the exception is
9117 ;; for an anchor in a construct like "namespace"[*] - this is as early
9118 ;; as possible in the construct but on the same line as the {.
9119 ;;
9120 ;; [*] i.e. with a keyword matching c-other-block-decl-kwds.
9121 ;;
9122 ;; SYNTAX-EXTRA-ARGS are a list of the extra arguments for the
9123 ;; syntax symbol. They are appended after the anchor point.
9124 ;;
9125 ;; If STOP-AT-BOI-ONLY is nil, we can stop in the middle of the line
9126 ;; if the current statement starts there.
9127 ;;
9128 ;; Note: It's not a problem if PAREN-STATE "overshoots"
9129 ;; CONTAINING-SEXP, i.e. contains info about parens further down.
9130 ;;
9131 ;; This function might do hidden buffer changes.
9134 ;; This is by far the most common case, so let's give it special
9135 ;; treatment.
9140 ;; Set when we're on a label, so that we don't stop there.
9141 ;; FIXME: To be complete we should check if we're on a label
9142 ;; now at the start.
9143 on-label)
9145 ;; Use point as the anchor point for "namespace", "extern", etc.
9149 syntax-extra-args)
9151 ;; Loop while we have to back out of containing blocks.
9156 ;; Loop while we have to back up statements.
9158 on-label
9161 ;; Skip past any comments that stands between the
9162 ;; statement start and boi.
9170 ;; Skip to the beginning of this statement or backward
9171 ;; another one.
9179 ;; If we didn't move we're at the start of a block and
9180 ;; have to continue outside it.
9189 ;; Special case to avoid deeper and deeper indentation
9190 ;; of "else if" clauses.
9191 )
9196 ;; If stop-at-boi-only is nil, we shouldn't back up
9197 ;; over previous or containing statements to try to
9198 ;; reach boi, so go back to the last position and
9199 ;; exit.
9206 ;; If we've moved into another statement then we
9207 ;; should no longer try to stop in the middle of a
9208 ;; line.
9211 ;; Record this as a substatement if we skipped up one
9212 ;; level.
9215 )))
9217 containing-sexp)
9219 ;; Now we have to go out of this block.
9222 ;; Don't stop in the middle of a special brace list opener
9223 ;; like "({".
9235 ;; Analyze the construct in front of the block we've stepped out
9236 ;; from and add the right syntactic element for it.
9239 step-type)
9242 ;; Stepped out of a parenthesis block, so we're in an
9243 ;; expression now.
9255 ;; Stepped out of an in-expression statement. This
9256 ;; syntactic element won't get an anchor pos.
9259 ;; A parenthesis normally belongs to an arglist.
9267 on-label nil))
9269 ;; Stepped out of a brace block.
9281 containing-sexp)))
9283 'defun-block-intro
9285 nil))
9289 c-other-decl-block-key-in-symbols-alist))
9296 ;; Always done if the open brace was at boi. The
9297 ;; c-beginning-of-statement-1 call above is necessary
9298 ;; anyway, to decide the type of block-intro to add.
9301 ))
9303 ;; Fill in the current point as the anchor for all the symbols
9304 ;; added above.
9313 )))
9316 containing-decl-open
9317 containing-decl-start
9318 containing-decl-kwd
9319 paren-state)
9320 ;; The inclass and class-close syntactic symbols are added in
9321 ;; several places and some work is needed to fix everything.
9322 ;; Therefore it's collected here.
9323 ;;
9324 ;; This function might do hidden buffer changes.
9329 containing-decl-open)
9331 ;; Ought to use `c-add-stmt-syntax' instead of backing up to boi
9332 ;; here, but we have to do like this for compatibility.
9342 char-after-ip
9343 beg-of-same-or-containing-stmt
9344 containing-sexp
9345 paren-state)
9346 ;; This function contains the decision tree reached through both
9347 ;; cases 18 and 10. It's a continued statement or top level
9348 ;; construct of some kind.
9349 ;;
9350 ;; This function might do hidden buffer changes.
9357 ;; (CASE A removed.)
9358 ;; CASE B: open braces for class or brace-lists
9365 ;; CASE B.1: class-open
9372 ;; CASE B.2: brace-list-open
9377 indent-point t t t)))
9378 ;; The most semantically accurate symbol here is
9379 ;; brace-list-open, but we normally report it simply as a
9380 ;; statement-cont. The reason is that one normally adjusts
9381 ;; brace-list-open for brace lists as top-level constructs,
9382 ;; and brace lists inside statements is a completely different
9383 ;; context. C.f. case 5A.3.
9386 ;; Turn off the dwim above when we're
9387 ;; analyzing the nature of the brace
9388 ;; for the auto newline feature.
9389 'brace-list-open
9391 nil nil
9392 containing-sexp paren-state))
9394 ;; CASE B.3: The body of a function declared inside a normal
9395 ;; block. Can occur e.g. in Pike and when using gcc
9396 ;; extensions, but watch out for macros followed by blocks.
9397 ;; C.f. cases E, 16F and 17G.
9403 ;; Turn off recognition of constructs that lacks a
9404 ;; type in this case, since that's more likely to be
9405 ;; a macro followed by a block.
9408 containing-sexp paren-state))
9410 ;; CASE B.4: Continued statement with block open. The most
9411 ;; accurate analysis is perhaps `statement-cont' together with
9412 ;; `block-open' but we play DWIM and use `substatement-open'
9413 ;; instead. The rationale is that this typically is a macro
9414 ;; followed by a block which makes it very similar to a
9415 ;; statement with a substatement block.
9418 containing-sexp paren-state))
9419 ))
9421 ;; CASE C: iostream insertion or extraction operator
9425 ;; If there is no preceding streamop in the statement
9426 ;; then indent this line as a normal statement-cont.
9430 t))))
9432 ;; CASE E: In the "K&R region" of a function declared inside a
9433 ;; normal block. C.f. case B.3.
9435 ;; Check that the next token is a '{'. This works as
9436 ;; long as no language that allows nested function
9437 ;; definitions allows stuff like member init lists, K&R
9438 ;; declarations or throws clauses there.
9439 ;;
9440 ;; Note that we do a forward search for something ahead
9441 ;; of the indentation line here. That's not good since
9442 ;; the user might not have typed it yet. Unfortunately
9443 ;; it's exceedingly tricky to recognize a function
9444 ;; prototype in a code block without resorting to this.
9452 ;; Turn off recognition of constructs that lacks a
9453 ;; type in this case, since that's more likely to be
9454 ;; a macro followed by a block.
9457 containing-sexp paren-state))
9459 ;;CASE F: continued statement and the only preceding items are
9460 ;;annotations.
9468 t)
9475 ;; CASE G: a template list continuation?
9476 ;; Mostly a duplication of case 5D.3 to fix templates-19:
9494 ;; In a nested template arglist.
9500 ;; FIXME: Should use c-add-stmt-syntax, but it's not yet
9501 ;; template aware.
9504 ;; CASE D: continued statement.
9508 containing-sexp paren-state))
9509 )))
9511 ;; The next autoload was added by RMS on 2005/8/9 - don't know why (ACM,
9512 ;; 2005/11/29).
9513 ;;;###autoload
9515 "Return the syntactic context of the current line."
9521 open-paren-in-column-0-is-defun-start
9522 ;; A whole ugly bunch of various temporary variables. Have
9523 ;; to declare them here since it's not possible to declare
9524 ;; a variable with only the scope of a cond test and the
9525 ;; following result clauses, and most of this function is a
9526 ;; single gigantic cond. :P
9527 literal char-before-ip before-ws-ip char-after-ip macro-start
9528 in-macro-expr c-syntactic-context placeholder c-in-literal-cache
9529 step-type tmpsymbol keyword injava-inher special-brace-list tmp-pos
9530 containing-<
9531 ;; The following record some positions for the containing
9532 ;; declaration block if we're directly within one:
9533 ;; `containing-decl-open' is the position of the open
9534 ;; brace. `containing-decl-start' is the start of the
9535 ;; declaration. `containing-decl-kwd' is the keyword
9536 ;; symbol of the keyword that tells what kind of block it
9537 ;; is.
9538 containing-decl-open
9539 containing-decl-start
9540 containing-decl-kwd
9541 ;; The open paren of the closest surrounding sexp or nil if
9542 ;; there is none.
9543 containing-sexp
9544 ;; The position after the closest preceding brace sexp
9545 ;; (nested sexps are ignored), or the position after
9546 ;; `containing-sexp' if there is none, or (point-min) if
9547 ;; `containing-sexp' is nil.
9548 lim
9549 ;; The paren state outside `containing-sexp', or at
9550 ;; `indent-point' if `containing-sexp' is nil.
9552 ;; There's always at most one syntactic element which got
9553 ;; an anchor pos. It's stored in syntactic-relpos.
9554 syntactic-relpos
9557 ;; Check if we're directly inside an enclosing declaration
9558 ;; level block.
9567 containing-sexp)
9568 t)))
9571 containing-sexp nil)
9576 ;; Init some position variables.
9585 ;; Ignore balanced paren. The next entry
9586 ;; can't be another one.
9589 ;; If there is no surrounding open paren then
9590 ;; put the last balanced pair back on paren-state.
9592 containing-sexp nil)))
9596 ;; If we're in a parenthesis list then ',' delimits the
9597 ;; "statements" rather than being an operator (with the
9598 ;; exception of the "for" clause). This difference is
9599 ;; typically only noticeable when statements are used in macro
9600 ;; arglists.
9604 ;; cache char before and after indent point, and move point to
9605 ;; the most likely position to perform the majority of tests
9614 ;; are we in a literal?
9617 ;; now figure out syntactic qualities of the current line
9620 ;; CASE 1: in a string.
9624 ;; CASE 2: in a C or C++ style comment.
9626 ;; This is a kludge for XEmacs where we use
9627 ;; `buffer-syntactic-context', which doesn't correctly
9628 ;; recognize "\*/" to end a block comment.
9629 ;; `parse-partial-sexp' which is used by
9630 ;; `c-literal-limits' will however do that in most
9631 ;; versions, which results in that we get nil from
9632 ;; `c-literal-limits' even when `c-in-literal' claims
9633 ;; we're inside a comment.
9637 ;; CASE 3: in a cpp preprocessor macro continuation.
9647 ;; If at the beginning of the body of a #define
9648 ;; directive then analyze as cpp-define-intro
9649 ;; only. Go on with the syntactic analysis
9650 ;; otherwise. in-macro-expr is set if we're in a
9651 ;; cpp expression, i.e. before the #define body
9652 ;; or anywhere in a non-#define directive.
9659 nil)))))
9663 ;; CASE 11: an else clause?
9667 containing-sexp paren-state))
9669 ;; CASE 12: while closure of a do/while construct?
9677 containing-sexp paren-state))
9679 ;; CASE 13: A catch or finally clause? This case is simpler
9680 ;; than if-else and do-while, because a block is required
9681 ;; after every try, catch and finally.
9689 t)
9693 t)
9696 t))
9701 containing-sexp paren-state))
9703 ;; CASE 18: A substatement we can recognize by keyword.
9713 ;; Ought to cache the result from the
9714 ;; c-beginning-of-statement-1 calls here.
9724 ;; Step up to the containing statement if we
9725 ;; stayed in the same one.
9733 ;; There was no containing statement after all.
9735 placeholder))
9737 ;; Require a parenthesis after these keywords.
9738 ;; Necessary to catch e.g. synchronized in Java,
9739 ;; which can be used both as statement and
9740 ;; modifier.
9746 ;; CASE 18A: Simple substatement.
9752 containing-sexp paren-state))
9758 containing-sexp paren-state))
9761 containing-sexp paren-state))))
9763 ;; CASE 18B: Some other substatement. This is shared
9764 ;; with case 10.
9766 char-after-ip
9767 placeholder
9768 lim
9769 paren-state)))
9771 ;; CASE 14: A case or default label
9777 containing-sexp))
9780 ;; Got a bogus label at the top level. In lack of better
9781 ;; alternatives, anchor it on (point-min).
9784 ;; CASE 15: any other label
9791 containing-decl-open
9792 containing-decl-start
9793 containing-decl-kwd
9794 paren-state))
9795 ;; Append access-label with the same anchor point as
9796 ;; inclass gets.
9802 containing-sexp))
9807 ;; If the surrounding statement is a switch then
9808 ;; let's analyze all labels as switch labels, so
9809 ;; that they get lined up consistently.
9810 'case-label
9816 ;; A label on the top level. Treat it as a class
9817 ;; context. (point-min) is the closest we get to the
9818 ;; class open brace.
9821 ;; CASE 4: In-expression statement. C.f. cases 7B, 16A and
9822 ;; 17E.
9825 containing-sexp
9826 ;; Have to turn on the heuristics after
9827 ;; the point even though it doesn't work
9828 ;; very well. C.f. test case class-16.pike.
9829 t))
9834 ;; It's a statement block or an anonymous class.
9836 ;; It's a Pike lambda. Check whether we are between the
9837 ;; lambda keyword and the argument list or at the defun
9838 ;; opener.
9840 'inline-open
9846 paren-state)
9850 ;; CASE 5: Line is inside a declaration level block or at top level.
9854 ;; CASE 5A: we are looking at a defun, brace list, class,
9855 ;; or inline-inclass method opening brace
9862 ;; CASE 5A.1: Non-class declaration block open.
9877 ;; Special case for extern-lang-open.
9878 'extern-lang-open
9880 nil t containing-sexp paren-state))
9882 ;; CASE 5A.2: we are looking at a class opening brace
9891 ;; CASE 5A.3: brace list open
9916 ))))
9920 ;; We're in Java and have found that the open brace
9921 ;; belongs to a "new Foo[]" initialization list,
9922 ;; which means the brace list is part of an
9923 ;; expression and not a top level definition. We
9924 ;; therefore treat it as any topmost continuation
9925 ;; even though the semantically correct symbol still
9926 ;; is brace-list-open, on the same grounds as in
9927 ;; case B.2.
9933 ;; CASE 5A.4: inline defun open
9939 containing-decl-open
9940 containing-decl-start
9941 containing-decl-kwd
9942 paren-state))
9944 ;; CASE 5A.5: ordinary defun open
9952 ;; Bogus to use bol here, but it's the legacy. (Resolved,
9953 ;; 2007-11-09)
9954 ))))
9956 ;; CASE 5R: Member init list. (Used to be part of CASE 5B.1)
9957 ;; Note there is no limit on the backward search here, since member
9958 ;; init lists can, in practice, be very large.
9964 ;; There is no preceding member init clause.
9965 ;; Indent relative to the beginning of indentation
9966 ;; for the topmost-intro line that contains the
9967 ;; prototype's open paren.
9970 ;; Indent relative to the first member init clause.
9975 ;; CASE 5B: After a function header but before the body (or
9976 ;; the ending semicolon if there's no body).
9983 ;; CASE 5B.1: Member init list.
9985 ;; There is no preceding member init clause.
9986 ;; Indent relative to the beginning of indentation
9987 ;; for the topmost-intro line that contains the
9988 ;; prototype's open paren.
9992 ;; CASE 5B.2: K&R arg decl intro
9999 containing-decl-open
10000 containing-decl-start
10001 containing-decl-kwd
10002 paren-state)))
10004 ;; CASE 5B.4: Nether region after a C++ or Java func
10005 ;; decl, which could include a `throws' declaration.
10009 )))
10011 ;; CASE 5C: inheritance line. could be first inheritance
10012 ;; line, or continuation of a multiple inheritance
10020 ;; watch out for scope operator
10025 )))
10034 ;; for Java
10039 cont done)
10044 done t))
10048 )
10050 injava-inher)
10053 ))
10056 ;; CASE 5C.1: non-hanging colon on an inher intro
10060 ;; don't add inclass symbol since relative point already
10061 ;; contains any class offset
10062 )
10064 ;; CASE 5C.2: hanging colon on an inher intro
10070 containing-decl-open
10071 containing-decl-start
10072 containing-decl-kwd
10073 paren-state)))
10075 ;; CASE 5C.3: in a Java implements/extends
10089 )))
10091 ;; CASE 5C.4: a continued inheritance line
10095 ;; don't add inclass symbol since relative point already
10096 ;; contains any class offset
10097 )))
10099 ;; CASE 5P: AWK pattern or function or continuation
10100 ;; thereof.
10106 'topmost-intro-cont
10108 nil nil
10109 containing-sexp paren-state))
10111 ;; CASE 5D: this could be a top-level initialization, a
10112 ;; member init list continuation, or a template argument
10113 ;; list continuation.
10115 ;; Note: We use the fact that lim is always after any
10116 ;; preceding brace sexp.
10126 t))
10131 t)
10137 nil)
10138 t))
10140 ;; NB: No c-after-special-operator-id stuff in this
10141 ;; clause - we assume only C++ needs it.
10146 ;; CASE 5D.3: perhaps a template list continuation?
10161 ;; In a nested template arglist.
10167 ;; FIXME: Should use c-add-stmt-syntax, but it's not yet
10168 ;; template aware.
10171 ;; CASE 5D.4: perhaps a multiple inheritance line?
10183 t)
10188 ;; CASE 5D.5: Continuation of the "expression part" of a
10189 ;; top level construct. Or, perhaps, an unrecognized construct.
10201 ;; A preceding comma at the top level means that a
10202 ;; new variable declaration starts here. Use
10203 ;; topmost-intro-cont for it, for consistency with
10204 ;; the first variable declaration. C.f. case 5N.
10207 nil nil containing-sexp paren-state))
10208 ))
10210 ;; CASE 5F: Close of a non-class declaration level block.
10214 ;; This is inconsistent: Should use `containing-decl-open'
10215 ;; here if it's at boi, like in case 5J.
10219 ;; Special case for compatibility with the
10220 ;; extern-lang syntactic symbols.
10221 'extern-lang-close
10224 nil t
10226 paren-state))
10228 ;; CASE 5G: we are looking at the brace which closes the
10229 ;; enclosing nested class decl
10234 containing-decl-open
10235 containing-decl-start
10236 containing-decl-kwd
10237 paren-state))
10239 ;; CASE 5H: we could be looking at subsequent knr-argdecls
10246 ;; Do an extra check to avoid tripping up on
10247 ;; statements that occur in invalid contexts
10248 ;; (e.g. in macro bodies where we don't really
10249 ;; know the context of what we're looking at).
10256 ;; CASE 5I: ObjC method definition.
10261 ;; Handle the case when it's the first (non-comment)
10262 ;; thing in the buffer. Can't look for a 'same return
10263 ;; value from cbos1 since ObjC directives currently
10264 ;; aren't recognized fully, so that we get 'same
10265 ;; instead of 'previous if it moved over a preceding
10266 ;; directive.
10270 ;; CASE 5N: At a variable declaration that follows a class
10271 ;; definition or some other block declaration that doesn't
10272 ;; end at the closing '}'. C.f. case 5D.5.
10281 ;; Speed up the backward search a bit.
10286 ;; The '}' is unbalanced.
10287 nil
10292 containing-sexp paren-state))
10294 ;; NOTE: The point is at the end of the previous token here.
10296 ;; CASE 5J: we are at the topmost level, make
10297 ;; sure we skip back past any access specifiers
10299 ;; A macro continuation line is never at top level.
10321 nil)))))
10322 ;; For historic reasons we anchor at bol of the last
10323 ;; line of the previous declaration. That's clearly
10324 ;; highly bogus and useless, and it makes our lives hard
10325 ;; to remain compatible. :P
10336 ;; Special case for compatibility with the
10337 ;; extern-lang syntactic symbols.
10338 'inextern-lang
10341 nil t
10343 paren-state))
10345 containing-decl-open
10346 containing-decl-start
10347 containing-decl-kwd
10348 paren-state)))
10350 macro-start
10355 ;; CASE 5K: we are at an ObjC method definition
10356 ;; continuation line.
10365 ;; CASE 5L: we are at the first argument of a template
10366 ;; arglist that begins on the previous line.
10374 ;; CASE 5Q: we are at a statement within a macro.
10379 ;;CASE 5N: We are at a topmost continuation line and the only
10380 ;;preceding items are annotations.
10387 t)
10393 ;; CASE 5M: we are at a topmost continuation line
10404 ))
10406 ;; (CASE 6 has been removed.)
10408 ;; CASE 7: line is an expression, not a statement. Most
10409 ;; likely we are either in a function prototype or a function
10410 ;; call argument list
10418 ;; CASE 7A: we are looking at the arglist closing paren.
10419 ;; C.f. case 7F.
10431 paren-state))
10433 ;; CASE 7B: Looking at the opening brace of an
10434 ;; in-expression block or brace list. C.f. cases 4, 16A
10435 ;; and 17E.
10439 paren-state))
10443 placeholder
10446 paren-state)
10447 containing-sexp)))
10448 ;; placeholder is nil if it's a block directly in
10449 ;; a function arglist. That makes us skip out of
10450 ;; this case.
10451 )))
10456 paren-state)
10460 ;; CASE 7C: we are looking at the first argument in an empty
10461 ;; argument list. Use arglist-close if we're actually
10462 ;; looking at a close paren or bracket.
10474 paren-state))
10476 ;; CASE 7D: we are inside a conditional test clause. treat
10477 ;; these things as statements
10487 ))
10489 ;; CASE 7E: maybe a continued ObjC method call. This is the
10490 ;; case when we are inside a [] bracketed exp, and what
10491 ;; precede the opening bracket is not an identifier.
10499 )))
10501 ;; CASE 7F: we are looking at an arglist continuation line,
10502 ;; but the preceding argument is on the same line as the
10503 ;; opening paren. This case includes multi-line
10504 ;; mathematical paren groupings, but we could be on a
10505 ;; for-list continuation line. C.f. case 7A.
10522 paren-state))
10524 ;; CASE 7G: we are looking at just a normal arglist
10525 ;; continuation line
10528 ))
10530 ;; CASE 8: func-local multi-inheritance line
10540 ;; CASE 8A: non-hanging colon on an inher intro
10545 ;; CASE 8B: hanging colon on an inher intro
10549 ;; CASE 8C: a continued inheritance line
10553 )))
10555 ;; CASE 9: we are inside a brace-list
10565 ;; CASE 9A: In the middle of a special brace list opener.
10585 ;; CASE 9B: brace-list-close brace
10587 ;; Check special brace list closer.
10594 ;; We were between the special close char and the `)'.
10597 ;; We were before the special close char.
10601 ;; Normal brace list check.
10612 ;; Prepare for the rest of the cases below by going to the
10613 ;; token following the opening brace
10626 ;; CASE 9C: we're looking at the first line in a brace-list
10637 ;; CASE 9D: this is just a later brace-list-entry or
10638 ;; brace-entry-open
10647 ))
10648 ))))
10650 ;; CASE 10: A continued statement or top level construct.
10660 ;; This is shared with case 18.
10662 char-after-ip
10663 placeholder
10664 containing-sexp
10665 paren-state))
10667 ;; CASE 16: block close brace, possibly closing the defun or
10668 ;; the class
10670 ;; From here on we have the next containing sexp in lim.
10675 ;; CASE 16E: Closing a statement block? This catches
10676 ;; cases where it's preceded by a statement keyword,
10677 ;; which works even when used in an "invalid" context,
10678 ;; e.g. a macro argument.
10683 ;; CASE 16A: closing a lambda defun or an in-expression
10684 ;; block? C.f. cases 4, 7B and 17E.
10687 nil))
10689 'inline-close
10699 paren-state)
10703 ;; CASE 16B: does this close an inline or a function in
10704 ;; a non-class declaration level block?
10711 nil))
10721 ;; CASE 16F: Can be a defun-close of a function declared
10722 ;; in a statement block, e.g. in Pike or when using gcc
10723 ;; extensions, but watch out for macros followed by
10724 ;; blocks. Let it through to be handled below.
10725 ;; C.f. cases B.3 and 17G.
10731 ;; Turn off recognition of constructs that
10732 ;; lacks a type in this case, since that's more
10733 ;; likely to be a macro followed by a block.
10740 ;; CASE 16C: If there is an enclosing brace then this is
10741 ;; a block close since defun closes inside declaration
10742 ;; level blocks have been handled above.
10744 ;; If the block is preceded by a case/switch label on
10745 ;; the same line, we anchor at the first preceding label
10746 ;; at boi. The default handling in c-add-stmt-syntax
10747 ;; really fixes it better, but we do like this to keep
10748 ;; the indentation compatible with version 5.28 and
10749 ;; earlier. C.f. case 17H.
10756 ;; c-backward-to-block-anchor not necessary here; those
10757 ;; situations are handled in case 16E above.
10760 ;; CASE 16D: Only top level defun close left.
10766 paren-state))
10767 ))
10769 ;; CASE 19: line is an expression, not a statement, and is directly
10770 ;; contained by a template delimiter. Most likely, we are in a
10771 ;; template arglist within a statement. This case is based on CASE
10772 ;; 7. At some point in the future, we may wish to create more
10773 ;; syntactic symbols such as `template-intro',
10774 ;; `template-cont-nonempty', etc., and distinguish between them as we
10775 ;; do for `arglist-intro' etc. (2009-12-07).
10781 ; '<') before indent-point.
10789 paren-state))
10791 ;; CASE 17: Statement or defun catchall.
10794 ;; Back up statements until we find one that starts at boi.
10797 containing-sexp)))
10801 nil)
10806 ;; CASE 17B: continued statement
10810 containing-sexp paren-state))
10812 ;; CASE 17A: After a case/default label?
10820 'statement-case-open
10822 nil t containing-sexp paren-state))
10824 ;; CASE 17D: any old statement
10831 containing-sexp paren-state)
10835 ;; CASE 17I: Inside a substatement block.
10837 ;; The following tests are all based on containing-sexp.
10839 ;; From here on we have the next containing sexp in lim.
10844 lim paren-state)
10848 ;; CASE 17E: first statement in an in-expression block.
10849 ;; C.f. cases 4, 7B and 16A.
10852 nil))
10854 'defun-block-intro
10863 paren-state)
10869 ;; CASE 17F: first statement in an inline, or first
10870 ;; statement in a top-level defun. we can tell this is it
10871 ;; if there are no enclosing braces that haven't been
10872 ;; narrowed out by a class (i.e. don't use bod here).
10875 paren-state)))
10881 nil))))
10886 ;; CASE 17G: First statement in a function declared inside
10887 ;; a normal block. This can occur in Pike and with
10888 ;; e.g. the gcc extensions, but watch out for macros
10889 ;; followed by blocks. C.f. cases B.3 and 16F.
10895 ;; Turn off recognition of constructs that lacks
10896 ;; a type in this case, since that's more likely
10897 ;; to be a macro followed by a block.
10903 lim paren-state))
10905 ;; CASE 17H: First statement in a block.
10907 ;; If the block is preceded by a case/switch label on the
10908 ;; same line, we anchor at the first preceding label at
10909 ;; boi. The default handling in c-add-stmt-syntax is
10910 ;; really fixes it better, but we do like this to keep the
10911 ;; indentation compatible with version 5.28 and earlier.
10912 ;; C.f. case 16C.
10919 ;; c-backward-to-block-anchor not necessary here; those
10920 ;; situations are handled in case 17I above.
10922 lim paren-state))
10925 ))
10926 )
10928 ;; now we need to look at any modifiers
10932 ;; are we looking at a comment only line?
10937 ;; we might want to give additional offset to friends (in C++).
10942 ;; Set syntactic-relpos.
10948 nil)
10949 t))
10952 ;; Start of or a continuation of a preprocessor directive?
10967 ;; If inside a cpp expression, i.e. anywhere in a
10968 ;; cpp directive except a #define body, we only let
10969 ;; through the syntactic analysis that is internal
10970 ;; in the expression. That means the arglist
10971 ;; elements, if they are anchored inside the cpp
10972 ;; expression.
10981 ;; Inside a #define body and the syntactic analysis is
10982 ;; anchored on the start of the #define. In this case
10983 ;; we add cpp-define-intro to get the extra
10984 ;; indentation of the #define body.
10987 ;; return the syntax
10988 c-syntactic-context)))
10990 \f
10991 ;; Indentation calculation.
10994 ;; offset can be a number, a function, a variable, a list, or one of
10995 ;; the symbols + or -
10996 ;;
10997 ;; This function might do hidden buffer changes.
11016 langelem symbol))
11022 offset symbol)
11023 nil)
11037 Error evaluating offset %S for %s: \
11038 Cannot combine absolute offset %S with relative %S in `%s' method"
11044 Error evaluating offset %S for %s: \
11045 Cannot combine relative offset %S with absolute %S in `%s' method"
11050 res))
11068 Error evaluating offset %S for %s: \
11069 Cannot combine absolute offsets %S and %S in `add' method"
11073 res))
11082 res))))
11089 nil))))
11093 res
11095 offset symbol res)
11096 nil)))
11099 ;; Get offset from LANGELEM which is a list beginning with the
11100 ;; syntactic symbol and followed by any analysis data it provides.
11101 ;; That data may be zero or more elements, but if at least one is
11102 ;; given then the first is the anchor position (or nil). The symbol
11103 ;; is matched against `c-offsets-alist' and the offset calculated
11104 ;; from that is returned.
11105 ;;
11106 ;; This function might do hidden buffer changes.
11116 offset
11120 ))
11123 ;; This is a compatibility wrapper for `c-calc-offset' in case
11124 ;; someone is calling it directly. It takes an old style syntactic
11125 ;; element on the form (SYMBOL . ANCHOR-POS) and converts it to the
11126 ;; new list form.
11127 ;;
11128 ;; This function might do hidden buffer changes.
11135 ;; Calculate the syntactic indentation from a syntactic description
11136 ;; as returned by `c-guess-syntax'.
11137 ;;
11138 ;; Note that topmost-intro always has an anchor position at bol, for
11139 ;; historical reasons. It's often used together with other symbols
11140 ;; that has more sane positions. Since we always use the first
11141 ;; found anchor position, we rely on that these other symbols always
11142 ;; precede topmost-intro in the LANGELEMS list.
11143 ;;
11144 ;; This function might do hidden buffer changes.
11152 ;; Got an absolute column that overrides any indentation
11153 ;; we've collected so far, but not the relative
11154 ;; indentation we might get for the nested structures
11155 ;; further down the langelems list.
11159 ;; Got a relative change of the current calculated
11160 ;; indentation.
11163 ;; Use the anchor position from the first syntactic
11164 ;; element with one.
11174 indent)))
11176 \f
11179 ;;; cc-engine.el ends here