| blob | f857264e0ff705b8d0979ed267291601ea77e898 |
1 ;;; cc-engine.el --- core syntax guessing engine for CC mode
3 ;; Copyright (C) 1985,1987,1992-2000 Free Software Foundation, Inc.
5 ;; Authors: 2000- Martin Stjernholm
6 ;; 1998-1999 Barry A. Warsaw and Martin Stjernholm
7 ;; 1992-1997 Barry A. Warsaw
8 ;; 1987 Dave Detlefs and Stewart Clamen
9 ;; 1985 Richard M. Stallman
10 ;; Maintainer: bug-cc-mode@gnu.org
11 ;; Created: 22-Apr-1997 (split from cc-mode.el)
12 ;; Version: See cc-mode.el
13 ;; Keywords: c languages oop
15 ;; This file is part of GNU Emacs.
17 ;; GNU Emacs is free software; you can redistribute it and/or modify
18 ;; it under the terms of the GNU General Public License as published by
19 ;; the Free Software Foundation; either version 2, or (at your option)
20 ;; any later version.
22 ;; GNU Emacs is distributed in the hope that it will be useful,
23 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
24 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
25 ;; GNU General Public License for more details.
27 ;; You should have received a copy of the GNU General Public License
28 ;; along with GNU Emacs; see the file COPYING. If not, write to the
29 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
30 ;; Boston, MA 02111-1307, USA.
37 load-path)
38 load-path)))
42 \f
43 ;; KLUDGE ALERT: c-maybe-labelp is used to pass information between
44 ;; c-crosses-statement-barrier-p and c-beginning-of-statement-1. A
45 ;; better way should be implemented, but this will at least shut up
46 ;; the byte compiler.
49 ;; WARNING WARNING WARNING
50 ;;
51 ;; Be *exceptionally* careful about modifications to this function!
52 ;; Much of CC Mode depends on this Doing The Right Thing. If you
53 ;; break it you will be sorry. If you think you know how this works,
54 ;; you probably don't. No human on Earth does! :-)
55 ;;
56 ;; WARNING WARNING WARNING
59 ;; move to the start of the current statement, or the previous
60 ;; statement if already at the beginning of one.
63 donep c-in-literal-cache saved
65 ;; first check for bare semicolon
70 t))
73 )
77 ;; stop at beginning of buffer
79 ;; go backwards one balanced expression, but be careful of
80 ;; unbalanced paren being reached
86 ;; skip over any unary operators, or other special
87 ;; characters appearing at front of identifier
97 ;; see if we're in a literal. if not, then this bufpos may be
98 ;; a candidate for stopping
100 ;; CASE 0: did we hit the error condition above?
102 ;; CASE 1: are we in a literal?
105 ;; CASE 2: some other kind of literal?
107 ;; CASE 3: are we looking at a conditional keyword?
122 c-conditional-key
124 ))))
125 ;; did we find a conditional?
128 foundp)))
129 ;; are we in the middle of an else-if clause?
138 ;; are we sitting at an else clause, that we are not a
139 ;; substatement of?
143 ;; a finally or a series of catches?
149 ;; are we sitting at the while of a do-while?
154 donep substmt-p))
155 ;; CASE 4: are we looking at a label? (But we handle
156 ;; switch labels later.)
161 ;; Not inside a Pike type declaration?
164 ;; CASE 5: is this the first time we're checking?
169 ;; CASE 6: have we crossed a statement barrier?
171 ;; Move over in-expression blocks before checking the
172 ;; barrier
179 ;; CASE 7: ignore labels
182 ;; with switch labels, we have to go back further
183 ;; to try to pick up the case or default
184 ;; keyword. Potential bogosity alert: we assume
185 ;; `case' or `default' is first thing on line
190 t
192 nil)))))
193 ;; CASE 8: ObjC or Java method def
197 ;; CASE 9: Normal token. At bob, we can end up at ws or a
198 ;; comment, and last-begin shouldn't be updated then.
201 ))))
203 ;; We always want to skip over the non-whitespace modifier
204 ;; characters that can start a statement.
233 )))
235 \f
237 ;; Does buffer positions FROM to TO cross a C statement boundary?
240 crossedp)
258 crossedp))
260 \f
261 ;; Skipping of "syntactic whitespace", defined as lexical whitespace,
262 ;; C and C++ style comments, and preprocessor directives. Search no
263 ;; farther back or forward than optional LIM. If LIM is omitted,
264 ;; `beginning-of-defun' is used for backward skipping, point-max is
265 ;; used for forward skipping.
268 ;; Forward skip of syntactic whitespace for Emacs 19.
274 ;; skip preprocessor directives
280 )
284 ;; Backward skip over syntactic whitespace for Emacs 19.
293 \f
294 ;; Moving by tokens, where a token is defined as all symbols and
295 ;; identifiers which aren't syntactic whitespace (note that "->" is
296 ;; considered to be two tokens). Point is always either left at the
297 ;; beginning of a token or not moved at all. COUNT specifies the
298 ;; number of tokens to move; a negative COUNT moves in the opposite
299 ;; direction. A COUNT of 0 moves to the next token beginning only if
300 ;; not already at one. If BALANCED is true, move over balanced
301 ;; parens, otherwise move into them. Also, if BALANCED is true, never
302 ;; move out of an enclosing paren. LIM sets the limit for the
303 ;; movement and defaults to the point limit. Returns the number of
304 ;; tokens left to move (positive or negative). If BALANCED is true, a
305 ;; move over a balanced paren counts as one. Note that if COUNT is 0
306 ;; and no appropriate token beginning is found, 1 will be returned.
307 ;; Thus, a return value of 0 guarantees that point is at the requested
308 ;; position and a return value less (without signs) than COUNT
309 ;; guarantees that point is at the beginning of some token.
322 ;; Skip whitespace. Count this as a move if we did in fact
323 ;; move and aren't out of bounds.
331 ;; If count is zero we should jump if in the middle of a
332 ;; token or if there is whitespace between point and the
333 ;; following token beginning.
335 ;; Avoid having the limit tests inside the loop.
353 count)))
362 last)
369 ;; If count is zero we should jump if in the middle of a
370 ;; token or if there is whitespace between point and the
371 ;; following token beginning.
373 ;; Avoid having the limit tests inside the loop.
389 count)))
391 \f
392 ;; Return `c' if in a C-style comment, `c++' if in a C++ style
393 ;; comment, `string' if in a string literal, `pound' if on a
394 ;; preprocessor line, or nil if not in a comment at all. Optional LIM
395 ;; is used as the backward limit of the search. If omitted, or nil,
396 ;; `beginning-of-defun' is used."
399 ;; Determine if point is in a C++ literal. we cache the last point
400 ;; calculated if the cache is enabled
402 c-in-literal-cache
413 ;; cache this result if the cache is enabled
416 rtn)))
418 ;; XEmacs has a built-in function that should make this much quicker.
419 ;; I don't think we even need the cache, which makes our lives more
420 ;; complicated anyway. In this case, lim is ignored.
433 ;; Returns a cons of the beginning and end positions of the comment
434 ;; or string surrounding point (including both delimiters), or nil
435 ;; if point isn't in one. If LIM is non-nil, it's used as the
436 ;; "safe" position to start parsing from. If NEAR is non-nil, then
437 ;; the limits of any literal next to point is returned. "Next to"
438 ;; means there's only [ \t] between point and the literal. The
439 ;; search for such a literal is done first in forward direction. If
440 ;; NOT-IN-DELIMITER is non-nil, the case when point is inside a
441 ;; starting delimiter won't be recognized. This only has effect for
442 ;; comments, which have starting delimiters with more than one
443 ;; character.
449 ;; String. Search backward for the start.
456 ;; Line comment. Search from bol for the comment starter.
468 ;; Block comment. Search backward for the comment starter.
477 ;; We're standing in a comment starter.
482 ;; Search forward for a literal.
491 ;; Search backward.
499 ;; Block comment. Due to the nature of line
500 ;; comments, they will always be covered by the
501 ;; normal case above.
504 ;; If LIM is bogus, beg will be bogus.
507 ))))
510 ;; Like c-literal-limits, but for emacsen whose `parse-partial-sexp'
511 ;; returns the pos of the comment start.
527 ;; We're standing in a comment starter.
532 ;; Search forward for a literal.
541 ;; Search backward.
549 ;; Block comment. Due to the nature of line
550 ;; comments, they will always be covered by the
551 ;; normal case above.
554 ;; If LIM is bogus, beg will be bogus.
557 ))))
563 ;; If the argument is a cons of two buffer positions (such as
564 ;; returned by c-literal-limits), and that range contains a C++
565 ;; style line comment, then an extended range is returned that
566 ;; contains all adjacent line comments (i.e. all comments that
567 ;; starts in the same column with no empty lines or non-whitespace
568 ;; characters between them). Otherwise the argument is returned.
588 range)
592 ;; Convenience function that given the result of c-literal-limits,
593 ;; returns nil or the type of literal that the range surrounds.
594 ;; It's much faster than using c-in-literal and is intended to be
595 ;; used when you need both the type of a literal and its limits.
602 range))
605 \f
606 ;; utilities for moving and querying around syntactic elements
610 ;; Finds and records all open parens between some important point
611 ;; earlier in the file and point.
612 ;;
613 ;; if there's a state cache, return it
618 ;; go back 2 bods, but ignore any bogus positions
619 ;; returned by beginning-of-defun (i.e. open paren
620 ;; in column zero)
626 ;; The following catches an obscure special
627 ;; case where the brace is preceded by an
628 ;; open paren. That can only legally occur
629 ;; with blocks inside expressions and in
630 ;; Pike special brace lists. Even so, this
631 ;; test is still bogus then, but hopefully
632 ;; good enough. (We don't want to use
633 ;; up-list here since it might be slow.)
642 ;;(skip-chars-forward " \t}")
645 placeholder state sexp-end)
646 ;; cache last bod position
657 ;; we want to record both the start and end
658 ;; of this sexp, but we only want to record
659 ;; the last-most of any of them before here
665 state))))
667 ;; we're contained in this sexp so put pos on
668 ;; front of list
670 ;; something bad happened. check to see if we
671 ;; crossed an unbalanced close brace. if so, we
672 ;; didn't really find the right `important bufpos'
673 ;; so lets back up and try again
677 ;;(char-after (1- placeholder))
684 ;; bogus, but what can we do here?
688 pos last-bod)
693 nil))
694 state)))
697 ;; whack off any state information that appears on STATE which lies
698 ;; after the bounds of BUFPOS.
704 ;; just check the car, because in a balanced brace
705 ;; expression, it must be impossible for the corresponding
706 ;; close brace to be before point, but the open brace to be
707 ;; after.
709 nil ; whack it off
710 ;; its possible that the open brace is before bufpos, but
711 ;; the close brace is after. In that case, convert this
712 ;; to a non-cons element.
715 ;; we know that both the open and close braces are
716 ;; before bufpos, so we also know that everything else
717 ;; on state is before bufpos, so we can glom up the
718 ;; whole thing and exit.
720 state nil)))
722 nil ; whack it off
723 ;; it's before bufpos, so everything else should too
725 state nil))))
726 newstate))
729 ;; Using BUFPOS buffer position, and WHICH (must be 'open or
730 ;; 'close), hack the c-parse-state STATE and return the results.
737 state))
740 ;; 'close brace
746 ;; TBD: is this test relevant???
748 state ;on error, don't change
749 ;; watch out for balanced expr already on cdr of list
753 ))))
756 ;; Adjust all points in state that lie in the region FROM..TO by
757 ;; SHIFT amount.
770 e))
771 state))
773 \f
775 ;; Go to the first non-whitespace after the colon that starts a
776 ;; multiple inheritance introduction. Optional LIM is the farthest
777 ;; back we should search.
793 ))
799 ;; Return nil if we aren't in a method definition, otherwise the
800 ;; position of the initial [+-].
806 ))
809 "Return a determination as to whether point is at the `top-level'.
810 Being at the top-level means that point is either outside any
811 enclosing block (such function definition), or inside a class
812 definition, but outside any method blocks.
814 If point is not at the top-level (e.g. it is inside a method
815 definition), then nil is returned. Otherwise, if point is at a
816 top-level not enclosed within a class definition, t is returned.
817 Otherwise, a 2-vector is returned where the zeroth element is the
818 buffer position of the start of the class declaration, and the first
819 element is the buffer position of the enclosing class's opening
820 brace."
826 ;; Return t if we are between a function's argument list closing
827 ;; paren and its opening brace. Note that the list close brace
828 ;; could be followed by a "const" specifier or a member init hanging
829 ;; colon. Optional CONTAINING is position of containing s-exp open
830 ;; brace. If not supplied, point is used as search start.
835 ;; could be looking at const specifier
840 ;; otherwise, we could be looking at a hanging member init
841 ;; colon
844 ;; this will catch member inits with multiple
845 ;; line arglists
857 nil
859 )
861 ;; check if we are looking at a method def
868 ;; or a class category
872 )))))
873 )))
875 ;; defuns to look backwards for things
877 ;; Move to the start of the last "unbalanced" do expression.
878 ;; Optional LIM is the farthest back to search. If none is found,
879 ;; nil is returned and point is left unchanged, otherwise t is returned.
884 foundp)
886 ;; we protect this call because trying to execute this when the
887 ;; while is not associated with a do will throw an error
892 ;; break infloop for illegal C code
908 foundp))
911 ;; Move to the start of the last "unbalanced" if and return t. If
912 ;; none is found, and we are looking at an if clause, nil is
913 ;; returned. If none is found and we are looking at an else clause,
914 ;; an error is thrown.
919 lim)
937 ;; check for else if... skip over
941 nil
947 ))
948 t)))
951 ;; skip forward over conditional at point, including any predicate
952 ;; statements in parentheses. No error checking is performed.
954 ;; else if()
956 ;; do, else, try, finally
958 ;; for, if, while, switch, catch, synchronized, foreach
962 ;; Go back to the closest preceding statement start.
965 c-switch-label-key))
966 stmtbeg)
974 ;; Skip a label.
976 t)
978 ;; Skip a conditional statement.
986 ;; Goes to the beginning of a member init list (i.e. just after the
987 ;; ':') if inside one. Returns t in that case, nil otherwise.
996 ;; this will catch member inits with multiple
997 ;; line arglists
1003 ;; Skip backwards over a fully::qualified::name.
1011 ;; now continue checking
1017 ;; skip forward over case/default bodies, with optional maximal
1018 ;; limit. if no next case body is found, nil is returned and point
1019 ;; is not moved
1022 donep foundp bufpos
1025 ;; search until we've passed the limit, or we've found our match
1029 ;; see if we can find a case statement, not in a literal
1034 ;; if we crossed into a balanced sexp, we know the case is
1035 ;; not part of our switch statement, so just bound over the
1036 ;; sexp and keep looking.
1043 foundp t))))
1046 foundp))
1049 ;; search for the containing class, returning a 2 element vector if
1050 ;; found. aref 0 contains the bufpos of the boi of the class key
1051 ;; line, and aref 1 contains the bufpos of the open brace.
1053 ;; no brace-state means we cannot be inside a class
1054 nil
1056 search-start search-end)
1058 ;; a cons cell in the first element means that there is some
1059 ;; balanced sexp before the current bufpos. this we can
1060 ;; ignore. the nth 1 and nth 2 elements define for us the
1061 ;; search boundaries
1064 ;; if the car was not a cons cell then nth 0 and nth 1 define
1065 ;; for us the search boundaries
1068 ;; search-end cannot be a cons cell
1071 ;; if search-end is nil, or if the search-end character isn't an
1072 ;; open brace, we are definitely not in a class
1076 nil
1077 ;; now, we need to look more closely at search-start. if
1078 ;; search-start is nil, then our start boundary is really
1079 ;; point-min.
1082 ;; if search-start is a cons cell, then we can start
1083 ;; searching from the end of the balanced sexp just ahead of
1084 ;; us
1087 ;; now we can do a quick regexp search from search-start to
1088 ;; search-end and see if we can find a class key. watch for
1089 ;; class like strings in literals
1094 foundp class match-end)
1097 c-inexpr-class-key)))
1106 nil ; its in a comment or string, ignore
1111 ;; check for embedded keywords
1117 ;; make sure we're really looking at the start of a
1118 ;; class definition, and not a forward decl, return
1119 ;; arg, template arg list, or an ObjC or Java method.
1124 ;; Check if this is an anonymous inner class.
1130 ;; We're done. Just trap this case in the cond.
1131 nil
1132 ;; False alarm; all conditions aren't satisfied.
1134 ;; Its impossible to define a regexp for this, and
1135 ;; nearly so to do it programmatically.
1136 ;;
1137 ;; ; picks up forward decls
1138 ;; = picks up init lists
1139 ;; ) picks up return types
1140 ;; > picks up templates, but remember that we can
1141 ;; inherit from templates!
1143 ;; try to see if we found the `class' keyword
1144 ;; inside a template arg list
1155 )))
1156 foundp))
1157 )))))
1160 ;; return the buffer position of the beginning of the brace list
1161 ;; statement if we're inside a brace list, otherwise return nil.
1162 ;; CONTAINING-SEXP is the buffer pos of the innermost containing
1163 ;; paren. BRACE-STATE is the remainder of the state of enclosing braces
1164 ;;
1165 ;; N.B.: This algorithm can potentially get confused by cpp macros
1166 ;; places in inconvenient locations. Its a trade-off we make for
1167 ;; speed.
1169 ;; this will pick up enum lists
1182 ;; this will pick up array/aggregate init lists, even if they are nested.
1185 ;; Pike can have class definitions anywhere, so we must
1186 ;; check for the class key here.
1189 bufpos lim braceassignp)
1191 containing-sexp)
1197 ;; We're in an in-expression block of some kind. Do
1198 ;; not check nesting.
1200 ;; see if the open brace is preceded by = or [...] in
1201 ;; this statement, but watch out for operator=
1207 ;; Checks to do only on the first sexp before the brace.
1210 ;; In Java, an initialization brace list may follow
1211 ;; directly after "new Foo[]", so check for a "new"
1212 ;; earlier.
1218 ;; Carry on looking if this is an
1219 ;; identifier (may contain "." in Java)
1220 ;; or another "[]" sexp.
1223 ;; Checks to do on all sexps before the brace, up to the
1224 ;; beginning of the statement.
1232 ;; We've seen a =, but must check earlier tokens so
1233 ;; that it isn't something that should be ignored.
1239 ;; Check for operator =
1241 ;; Check for `<opchar>= (Pike)
1244 ;; make sure we're not in a C++ template
1245 ;; argument assignment
1256 )))
1257 nil)
1264 ;; Brace lists can't contain a semicolon, so we're done.
1266 ;; lets see if we're nested. find the most nested
1267 ;; containing brace
1270 ;; we've hit the beginning of the aggregate list
1274 ))
1275 bufpos))
1276 ))
1279 ;; If we're looking at the start of a pike-style list, ie `({Â })',
1280 ;; `([Â ])', `(<Â >)' etc, a cons of a cons of its starting and ending
1281 ;; positions and its entry in c-special-brace-lists is returned, nil
1282 ;; otherwise. The ending position is nil if the list is still open.
1283 ;; LIM is the limit for forward search. The point may either be at
1284 ;; the `(' or at the following paren character. Tries to check the
1285 ;; matching closer, but assumes it's correct if no balanced paren is
1286 ;; found (i.e. the case `({ ... } ... )' is detected as _not_ being
1287 ;; a special brace list).
1292 end type)
1305 nil)))))
1314 ;; Kludges needed to handle inner
1315 ;; chars both with and without
1316 ;; paren syntax.
1329 ;; Returns nil if inside a statement or declaration.
1340 ;; Returns non-nil if we're looking at the beginning of a block
1341 ;; inside an expression. The value returned is actually a cons of
1342 ;; either 'inlambda, 'inexpr-statement or 'inexpr-class and the
1343 ;; position of the beginning of the construct. LIM limits the
1344 ;; backward search.
1348 ;; Look at the character after point only as a last resort when
1349 ;; we can't disambiguate.
1363 c-inexpr-class-key
1371 ?w))
1382 res)))))
1385 ;; Returns non-nil if we're looking at the end of an in-expression
1386 ;; block, otherwise the same as `c-looking-at-inexpr-block'.
1397 \f
1399 ;; return the bufpos of the most enclosing brace that hasn't been
1400 ;; narrowed out by any enclosing class, or nil if none was found
1410 enclosingp))
1413 ;; return the bufpos of the least (highest) enclosing brace that
1414 ;; hasn't been narrowed out by any enclosing class, or nil if none
1415 ;; was found.
1419 ;; return the closest known safe position higher up than point
1429 safepos))
1432 ;; narrow the buffer so that the enclosing class is hidden
1441 ;; if point is now left of the class opening brace, we're
1442 ;; hosed, so try a different tact
1448 ;; end point is the end of the current line
1452 ;; return the class vector
1453 inclass-p))
1455 \f
1456 ;; This function implements the main decision tree for determining the
1457 ;; syntactic analysis of the current line of code. Yes, it's huge and
1458 ;; bloated!
1468 literal containing-sexp char-before-ip char-after-ip lim
1469 syntax placeholder c-in-literal-cache inswitch-p
1470 tmpsymbol keyword injava-inher special-brace-list
1471 ;; narrow out any enclosing class or extern "C" block
1473 inenclosing-p)
1474 ;; check for meta top-level enclosing constructs, possible
1475 ;; extern language definitions, possibly (in C++) namespace
1476 ;; definitions.
1490 )))))
1491 ;; get the buffer position of the most nested opening brace,
1492 ;; if there is one, and it hasn't been narrowed out
1502 ;; if cdr == point, then containing sexp is the brace
1503 ;; that opens the sexp we close
1506 ;; otherwise, ignore this element
1508 ;; ignore the bufpos if its been narrowed out by the
1509 ;; containing class or does not contain the indent point
1514 ;; set the limit on the farthest back we need to search
1518 nil)
1521 ;; cache char before and after indent point, and move point to
1522 ;; the most likely position to perform the majority of tests
1531 ;; are we in a literal?
1534 ;; now figure out syntactic qualities of the current line
1536 ;; CASE 1: in a string.
1539 ;; CASE 2: in a C or C++ style comment.
1542 ;; CASE 3: in a cpp preprocessor macro continuation.
1549 ;; CASE 4: In-expression statement.
1556 ;; It's a statement block or an anonymous class.
1558 ;; It's a Pike lambda. Check whether we are between the
1559 ;; lambda keyword and the argument list or at the defun
1560 ;; opener.
1562 'inline-open
1567 ;; CASE 5: Line is at top level.
1570 ;; CASE 5A: we are looking at a defun, brace list, class,
1571 ;; or inline-inclass method opening brace
1577 ;; CASE 5A.1: extern language or namespace construct
1593 ))
1596 ;; CASE 5A.2: we are looking at a class opening brace
1600 ;; TBD: watch out! there could be a bogus
1601 ;; c-state-cache in place when we get here. we have
1602 ;; to go through much chicanery to ignore the cache.
1603 ;; But of course, there may not be! BLECH! BOGUS!
1612 )))
1615 ))
1617 ;; CASE 5A.3: brace list open
1620 ;; c-b-o-s could have left us at point-min
1640 ))))
1642 ;; CASE 5A.4: inline defun open
1646 ;; CASE 5A.5: ordinary defun open
1652 )))
1653 ;; CASE 5B: first K&R arg decl or member init
1656 ;; CASE 5B.1: a member init
1659 ;; this line should be indented relative to the beginning
1660 ;; of indentation for the topmost-intro line that contains
1661 ;; the prototype's open paren
1662 ;; TBD: is the following redundant?
1666 ;; TBD: is the preceding redundant?
1680 ;; we don't need to add any class offset since this
1681 ;; should be relative to the ctor's indentation
1682 )
1683 ;; CASE 5B.2: K&R arg decl intro
1687 ;; CASE 5B.3: Inside a member init list.
1691 ;; CASE 5B.4: Nether region after a C++ or Java func
1692 ;; decl, which could include a `throws' declaration.
1696 )))
1697 ;; CASE 5C: inheritance line. could be first inheritance
1698 ;; line, or continuation of a multiple inheritance
1706 ;; watch out for scope operator
1711 )))
1720 ;; for Java
1725 cont done)
1730 done t))
1734 )
1736 injava-inher)
1739 ))
1741 ;; CASE 5C.1: non-hanging colon on an inher intro
1745 ;; don't add inclass symbol since relative point already
1746 ;; contains any class offset
1747 )
1748 ;; CASE 5C.2: hanging colon on an inher intro
1752 ;; CASE 5C.3: in a Java implements/extends
1766 )))
1767 ;; CASE 5C.4: a continued inheritance line
1771 ;; don't add inclass symbol since relative point already
1772 ;; contains any class offset
1773 )))
1774 ;; CASE 5D: this could be a top-level compound statement, a
1775 ;; member init list continuation, or a template argument
1776 ;; list continuation.
1778 c++-template-syntax-table
1787 ;; CASE 5D.1: hanging member init colon, but watch out
1788 ;; for bogus matches on access specifiers inside classes.
1805 )))
1809 ;; we do not need to add class offset since relative
1810 ;; point is the member init above us
1811 )
1812 ;; CASE 5D.2: non-hanging member init colon
1818 ;; CASE 5D.3: perhaps a multiple inheritance line?
1825 ;; CASE 5D.4: perhaps a template list continuation?
1829 ;; not sure if this is the right test, but it should
1830 ;; be fast and mostly accurate.
1834 ;; we can probably indent it just like an arglist-cont
1838 ;; CASE 5D.5: perhaps a top-level statement-cont
1841 ;; skip over any access-specifiers
1845 ;; skip over comments, whitespace
1848 ))
1849 ;; CASE 5E: we are looking at a access specifier
1851 c-access-key
1855 ;; CASE 5F: extern-lang-close or namespace-close?
1859 'extern-lang-close
1862 ;; CASE 5G: we are looking at the brace which closes the
1863 ;; enclosing nested class decl
1872 ))))
1874 ;; CASE 5H: we could be looking at subsequent knr-argdecls
1876 ;; here we essentially use the hack that is used in
1877 ;; Emacs' c-mode.el to limit how far back we should
1878 ;; look. The assumption is made that argdecls are
1879 ;; indented at least one space and that function
1880 ;; headers are not indented.
1899 ;; or a class category
1903 )))))
1904 ))
1910 ;; CASE 5I: ObjC method definition.
1914 ;; CASE 5J: we are at the topmost level, make sure we skip
1915 ;; back past any access specifiers
1919 c-access-key
1928 ;; real beginning-of-line could be narrowed out due to
1929 ;; enclosure in a class block
1944 ))
1945 ))
1946 ;; CASE 5K: we are at an ObjC or Java method definition
1947 ;; continuation line.
1954 ;; CASE 5L: we are at the first argument of a template
1955 ;; arglist that begins on the previous line.
1960 ;; CASE 5M: we are at a topmost continuation line
1966 ;; (CASE 6 has been removed.)
1967 ;; CASE 7: line is an expression, not a statement. Most
1968 ;; likely we are either in a function prototype or a function
1969 ;; call argument list
1977 ;; CASE 7A: we are looking at the arglist closing paren
1979 ;; Don't check this in Pike since it allows a
1980 ;; comma after the last arg.
1991 ;; CASE 7B: Looking at the opening brace of an
1992 ;; in-expression block or brace list.
2004 ;; CASE 7C: we are looking at the first argument in an empty
2005 ;; argument list. Use arglist-close if we're actually
2006 ;; looking at a close paren or bracket.
2016 ;; CASE 7D: we are inside a conditional test clause. treat
2017 ;; these things as statements
2028 ))
2029 ;; CASE 7E: maybe a continued method call. This is the case
2030 ;; when we are inside a [] bracketed exp, and what precede
2031 ;; the opening bracket is not an identifier.
2039 )))
2040 ;; CASE 7F: we are looking at an arglist continuation line,
2041 ;; but the preceding argument is on the same line as the
2042 ;; opening paren. This case includes multi-line
2043 ;; mathematical paren groupings, but we could be on a
2044 ;; for-list continuation line
2061 ;; CASE 7G: we are looking at just a normal arglist
2062 ;; continuation line
2067 ))
2068 ;; CASE 8: func-local multi-inheritance line
2077 ;; CASE 8A: non-hanging colon on an inher intro
2081 ;; CASE 8B: hanging colon on an inher intro
2084 ;; CASE 8C: a continued inheritance line
2088 )))
2089 ;; CASE 9: we are inside a brace-list
2097 ;; CASE 9A: In the middle of a special brace list opener.
2111 ;; CASE 9B: brace-list-close brace
2113 ;; Check special brace list closer.
2120 ;; We were between the special close char and the `)'.
2123 ;; We were before the special close char.
2127 ;; Normal brace list check.
2131 t))
2135 ;; Prepare for the rest of the cases below by going to the
2136 ;; token following the opening brace
2148 ;; CASE 9C: we're looking at the first line in a brace-list
2153 ;; CASE 9D: this is just a later brace-list-entry or
2154 ;; brace-entry-open
2165 ;; CASE 10: A continued statement
2189 nil))))
2191 ;; CASE 10A: substatement
2198 ;; CASE 10B: open braces for class or brace-lists
2204 ;; CASE 10B.1: class-open
2211 ))
2213 ;; CASE 10B.2: brace-list-open
2224 ;; The most semantically accurate symbol here is
2225 ;; brace-list-open, but we report it simply as a
2226 ;; statement-cont. The reason is that one normally
2227 ;; adjusts brace-list-open for brace lists as
2228 ;; top-level constructs, and brace lists inside
2229 ;; statements is a completely different context.
2233 ;; CASE 10B.3: The body of a function declared inside a
2234 ;; normal block. This can only occur in Pike.
2241 ;; CASE 10B.4: catch-all for unknown construct.
2243 ;; Can and should I add an extensibility hook here?
2244 ;; Something like c-recognize-hook so support for
2245 ;; unknown constructs could be added. It's probably a
2246 ;; losing proposition, so I dunno.
2250 ))
2251 ;; CASE 10C: iostream insertion or extraction operator
2258 ;; if we ended up at indent-point, then the first
2259 ;; streamop is on a separate line. Indent the line like
2260 ;; a statement-cont instead
2265 ;; CASE 10D: continued statement. find the accurate
2266 ;; beginning of statement or substatement
2269 ;; KLUDGE ALERT! c-beginning-of-statement-1 can leave
2270 ;; us before the lim we're passing in. It should be
2271 ;; fixed, but I'm worried about side-effects at this
2272 ;; late date. Fix for v5.
2277 )))
2278 ;; CASE 11: an else clause?
2282 ;; CASE 12: Statement. But what kind? Lets see if its a
2283 ;; while closure of a do/while construct
2292 ))
2295 ;; CASE 13: A catch or finally clause? This case is simpler
2296 ;; than if-else and do-while, because a block is required
2297 ;; after every try, catch and finally.
2308 t)
2312 ;; CASE 14: A case or default label
2315 ;; check for hanging braces
2319 ;; CASE 15: any other label
2322 ;; check for hanging braces
2326 ;; CASE 16: block close brace, possibly closing the defun or
2327 ;; the class
2336 ;; CASE 16A: closing a lambda defun or an in-expression
2337 ;; block?
2342 'inline-close
2351 ;; CASE 16B: does this close an inline or a function in
2352 ;; an extern block or namespace?
2360 ;; CASE 16C: if there an enclosing brace that hasn't
2361 ;; been narrowed out by a class, then this is a
2362 ;; block-close
2366 ;; In Pike it can be a defun-close of a
2367 ;; function declared in a statement block. Let
2368 ;; it through to be handled below.
2374 ;; CASE 16D: find out whether we're closing a top-level
2375 ;; class or a defun
2383 )))
2384 ;; CASE 17: statement catchall
2386 ;; we know its a statement, but we need to find out if it is
2387 ;; the first statement in a block
2391 ;; now skip forward past any case/default clauses we might find.
2396 ;; we want to ignore non-case labels when skipping forward
2401 ;; CASE 17A: we are inside a case/default clause inside a
2402 ;; switch statement. find out if we are at the statement
2403 ;; just after the case/default label.
2418 ;; CASE 17B: continued statement
2423 ;; CASE 17C: a question/colon construct? But make sure
2424 ;; what came before was not a label, and what comes after
2425 ;; is not a globally scoped function call!
2436 ;; watch out for scope operator
2441 ;; CASE 17D: any old statement
2444 relpos done)
2447 ;; It is possible we're on the brace that opens a nested
2448 ;; function.
2470 ;; CASE 17E: first statement in an in-expression block
2478 'defun-block-intro
2487 ;; CASE 17F: first statement in an inline, or first
2488 ;; statement in a top-level defun. we can tell this is it
2489 ;; if there are no enclosing braces that haven't been
2490 ;; narrowed out by a class (i.e. don't use bod here!)
2498 ;; if not at boi, then defun-opening braces are hung on
2499 ;; right side, so we need a different relpos
2505 ;; looking at a Java throws clause following a
2506 ;; method's parameter list
2508 ))
2510 ;; CASE 17G: First statement in a function declared inside
2511 ;; a normal block. This can only occur in Pike.
2520 ;; CASE 17H: first statement in a block
2529 ))
2530 )
2531 ;; now we need to look at any modifiers
2535 ;; are we looking at a comment only line?
2538 ;; we might want to give additional offset to friends (in C++).
2542 ;; Start of a preprocessor directive?
2549 ;; return the syntax
2550 syntax))))
2552 \f
2555 nil
2557 c-parsing-error)
2559 c-parsing-error)
2565 nil
2571 ;; If initial point was within line's indentation, position after
2572 ;; the indentation. Else stay at same point in text.
2577 ;; Indent the current line as C/C++/ObjC code, if
2578 ;; c-syntactic-indentation is non-nil. Optional SYNTAX is the
2579 ;; syntactic information for the current line. Returns the amount
2580 ;; of indentation change (in columns).
2595 t
2598 nil))))
2601 shift-amt))
2604 "Show syntactic information for current line.
2605 With universal argument, inserts the analysis as a comment on that line."
2613 ))
2617 "Inserts a comment with the syntactic analysis on every line in the region."
2627 \f
2629 ;;; cc-engine.el ends here