| blob | 8a0ba6d19207d377e8970733d008498b31974fcc |
1 ;;; cc-fonts.el --- font lock support for CC Mode
3 ;; Copyright (C) 2002, 03 Free Software Foundation, Inc.
5 ;; Authors: 2003- Alan Mackenzie
6 ;; 2002- Martin Stjernholm
7 ;; Maintainer: bug-cc-mode@gnu.org
8 ;; Created: 07-Jan-2002
9 ;; Version: See cc-mode.el
10 ;; Keywords: c languages oop
12 ;; This file is part of GNU Emacs.
14 ;; GNU Emacs is free software; you can redistribute it and/or modify
15 ;; it under the terms of the GNU General Public License as published by
16 ;; the Free Software Foundation; either version 2, or (at your option)
17 ;; any later version.
19 ;; GNU Emacs is distributed in the hope that it will be useful,
20 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
21 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
22 ;; GNU General Public License for more details.
24 ;; You should have received a copy of the GNU General Public License
25 ;; along with this program; see the file COPYING. If not, write to
26 ;; the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
27 ;; Boston, MA 02111-1307, USA.
29 ;;; Commentary:
31 ;; Some comments on the use of faces:
32 ;;
33 ;; o `c-label-face-name' is either `font-lock-constant-face' (in Emacs
34 ;; 20 and later), or `font-lock-reference-face'.
35 ;;
36 ;; o `c-constant-face-name', `c-reference-face-name' and
37 ;; `c-doc-markup-face-name' are essentially set up like
38 ;; `c-label-face-name'.
39 ;;
40 ;; o `c-preprocessor-face-name' is `font-lock-preprocessor-face' in
41 ;; XEmacs and - in lack of a closer equivalent -
42 ;; `font-lock-builtin-face' or `font-lock-reference-face' in Emacs.
43 ;;
44 ;; o `c-doc-face-name' is `font-lock-doc-string-face' in XEmacs,
45 ;; `font-lock-doc-face' in Emacs 21 and later, or
46 ;; `font-lock-comment-face' in older Emacs (that since source
47 ;; documentation are actually comments in these languages, as opposed
48 ;; to elisp).
49 ;;
50 ;; o `c-invalid-face-name' is `font-lock-warning-face' in Emacs. In
51 ;; older XEmacs there's no corresponding standard face, so there
52 ;; it's mapped to a special `c-invalid-face'.
53 ;;
54 ;; TBD: We should probably provide real faces for the above uses and
55 ;; instead initialize them from the standard faces.
57 ;;; Code:
59 ;; The faces that already have been put onto the text is tested in
60 ;; various places to direct further fontifications. For this to work,
61 ;; the following assumptions regarding the faces must hold (apart from
62 ;; the dependencies on the font locking order):
63 ;;
64 ;; o `font-lock-comment-face' and the face in `c-doc-face-name' is
65 ;; not used in anything but comments.
66 ;; o If any face (e.g. `c-doc-markup-face-name') but those above is
67 ;; used in comments, it doesn't replace them.
68 ;; o `font-lock-string-face' is not used in anything but string
69 ;; literals (single or double quoted).
70 ;; o `font-lock-keyword-face' and the face in `c-label-face-name' are
71 ;; never overlaid with other faces.
78 load-path)))
86 ;; prevent cc-awk being loaded when it's not needed. There is now a (require
87 ;; 'cc-awk) in (defun awk-mode ..).
89 ;; Avoid repeated loading through the eval-after-load directive in
90 ;; cc-mode.el.
97 ;; Need to declare these local symbols during compilation since
98 ;; they're referenced from lambdas in `byte-compile' calls that are
99 ;; executed at compile time. They don't need to have the proper
100 ;; definitions, though, since the generated functions aren't called
101 ;; during compilation.
110 ;; Emacs 19 doesn't have `defface'. This "replacement" leaves a lot
111 ;; to be wished for but at least it avoids any errors.
117 \f
118 ;; Note that font-lock in XEmacs doesn't expand face names as
119 ;; variables, so we have to use the (eval . FORM) in the font lock
120 ;; matchers wherever we use these alias variables.
124 ;; XEmacs has a font-lock-preprocessor-face.
127 ;; In Emacs 20 and later font-lock-builtin-face has
128 ;; traditionally been used for preprocessor directives.
137 ;; If it happens to occur in the future. (Well, the more
138 ;; pragmatic reason is to get unique faces for the test
139 ;; suite.)
143 ;; Test both if font-lock-constant-face exists and that it's
144 ;; not an alias for something else. This is important since
145 ;; we compare already set faces in various places.
153 ;; This doesn't exist in XEmacs <= 20 and some earlier versions
154 ;; of XEmacs 21.
155 'font-lock-constant-face
156 c-label-face-name))
161 ;; This is considered obsolete in Emacs 20 and later, but it
162 ;; still maps well to this use. (Another reason to do this is
163 ;; to get unique faces for the test suite.)
164 'font-lock-reference-face
165 c-label-face-name))
167 ;; This should not mapped to a face that also is used to fontify things
168 ;; that aren't comments or string literals.
171 ;; XEmacs.
174 ;; Emacs 21 and later.
181 ;; If it happens to occur in the future. (Well, the more
182 ;; pragmatic reason is to get unique faces for the test
183 ;; suite.)
184 'font-lock-doc-markup-face
185 c-label-face-name))
189 ;; Emacs >= 20 and XEmacs >= 21 has a font-lock-warning-face.
190 'font-lock-warning-face
191 ;; Otherwise we provide a face.
200 "Face used to highlight invalid syntax."
203 ;; To make hard spaces visible an inverted version of
204 ;; `c-invalid-face-name' is used. Since font-lock in Emacs expands
205 ;; all face names in `font-lock-keywords' as variables we need to have
206 ;; a variable for it that resolves to its own name.
213 ;; Emacs and XEmacs have completely different face manipulation
214 ;; routines. :P
215 ;;
216 ;; This function does not do any hidden buffer changes
219 ;; Emacs 20 and later. This only looks at the inverse flag
220 ;; in the current frame. Other display configurations might
221 ;; be different, but it can only show if the same Emacs has
222 ;; frames on e.g. a color and a monochrome display
223 ;; simultaneously.
227 ;; XEmacs. Same pitfall here.
231 ;; Emacs 19 has no inverse flag at all. Just inverse the
232 ;; face and hope it wasn't inversed already.
236 ;; We need the following functions during compilation since they're
237 ;; called when the `c-lang-defconst' initializers are evaluated.
238 ;; Define them at runtime too for the sake of derived modes.
241 ;; Put a face on a region (overriding any existing face) in the way
242 ;; font-lock would do it. In XEmacs that means putting an
243 ;; additional font-lock property, or else the font-lock package
244 ;; won't recognize it as fontified and might override it
245 ;; incorrectly.
247 ;; Note: This function has no docstring in XEmacs so it might be
248 ;; considered internal.
253 ;; This is the inverse of `c-put-font-lock-face'.
259 ;; Put `font-lock-string-face' on a string. The surrounding
260 ;; quotes are included in Emacs but not in XEmacs. The passed
261 ;; region should include them.
267 ;; Like `let', but additionally activates `c-record-type-identifiers'
268 ;; and `c-record-ref-identifiers', and fontifies the recorded ranges
269 ;; accordingly on exit.
271 c-record-ref-identifiers
279 ;; If the point is within a region fontified as a comment or
280 ;; string literal skip to the end of it or to LIMIT, whichever
281 ;; comes first, and return t. Otherwise return nil. The match
282 ;; data is not clobbered.
289 t))
292 ;; This function makes a byte compiled function that works much like
293 ;; a matcher element in `font-lock-keywords'. It cuts out a little
294 ;; bit of the overhead compared to a real matcher. The main reason
295 ;; is however to pass the real search limit to the anchored
296 ;; matcher(s), since most (if not all) font-lock implementations
297 ;; arbitrarily limits anchored matchers to the same line, and also
298 ;; to insulate against various other irritating differences between
299 ;; the different (X)Emacs font-lock packages.
300 ;;
301 ;; REGEXP is the matcher, which must be a regexp. Only matches
302 ;; where the beginning is outside any comment or string literal are
303 ;; significant.
304 ;;
305 ;; HIGHLIGHTS is a list of highlight specs, just like in
306 ;; `font-lock-keywords', with these limitations: The face is always
307 ;; overridden (no big disadvantage, since hits in comments etc are
308 ;; filtered anyway), there is no "laxmatch", and an anchored matcher
309 ;; is always a form which must do all the fontification directly.
310 ;; `limit' is a variable bound to the real limit in the context of
311 ;; the anchored matcher forms.
312 ;;
313 ;; This function does not do any hidden buffer changes, but the
314 ;; generated functions will. They are however used in places
315 ;; covered by the font-lock context.
317 ;; Note: Replace `byte-compile' with `eval' to debug the generated
318 ;; lambda easier.
322 ;; The font-lock package in Emacs is known to clobber
323 ;; `parse-sexp-lookup-properties' (when it exists).
339 "The override flag must currently be set in %s"
340 highlight))
343 "The laxmatch flag may currently not be set in %s"
344 highlight))
352 highlight))
357 highlights))))
358 nil))))
361 ;; Converts the ranges recorded on `c-record-type-identifiers' and
362 ;; `c-record-ref-identifiers' to fontification.
372 ;; Note that the reference face is a variable that is
373 ;; dereferenced, since it's an alias in Emacs.
375 c-reference-face-name))))
378 "Font lock matchers for preprocessor directives and purely lexical
379 stuff. Used on level 1 and higher."
381 ;; Note: `c-font-lock-declarations' assumes that no matcher here
382 ;; sets `font-lock-type-face' in languages where
383 ;; `c-recognize-<>-arglists' is set.
390 ;; fontify it as a string.
396 ;; Fontify filenames in #include <...> as strings.
403 font-lock-string-face)
405 ;; Use an anchored matcher to put paren syntax on the brackets.
417 nil))))
419 ;; #define.
422 noncontinued-line-end
428 ;; Macro with arguments - a "function".
431 ;; Macro without arguments - a "variable".
436 ;; "Function". Fontify the name and the arguments.
460 ;; "Variable".
466 ;; Fontify cpp function names in preprocessor
467 ;; expressions in #if and #elif.
473 ;; Match the whole logical line to look
474 ;; for the functions in.
481 nil)
487 c-preprocessor-face-name)))
490 ;; Fontify the directive names.
498 )))
504 ;; Make hard spaces visible through an inverted `c-invalid-face-name'.
512 ))
515 ;; Assuming the point is after the opening character of a string,
516 ;; fontify that char with `c-invalid-face-name' if the string
517 ;; decidedly isn't terminated properly. Assumes the string already
518 ;; is syntactically fontified.
522 ;; We're at eol inside a string. The first check above is
523 ;; necessary in XEmacs since it doesn't fontify the string
524 ;; delimiters themselves. Thus an empty string won't have
525 ;; the string face anywhere.
527 ;; There's no \ before the newline.
529 ;; Quoted newlines aren't supported.
530 t)
532 ;; There's no # before the string, so newlines
533 ;; aren't allowed.
535 t)
539 "Font lock matchers for basic keywords, labels, references and various
540 other easily recognizable things that should be fontified before generic
541 casts and declarations are fontified. Used on level 2 and higher."
543 ;; Note: `c-font-lock-declarations' assumes that no matcher here
544 ;; sets `font-lock-type-face' in languages where
545 ;; `c-recognize-<>-arglists' is set.
548 ;; can't span lines. Later font
549 ;; lock packages have a `font-lock-syntactic-face-function' for
550 ;; this, but it doesn't give the control we want since any
551 ;; fontification done inside the function will be
552 ;; unconditionally overridden.
554 ;; Match a char before the string starter to make
555 ;; `c-skip-comments-and-strings' work correctly.
559 ;; Fontify keyword constants.
563 ;; No symbol is a keyword after "->" in Pike.
570 ;; Fontify all keywords except the primitive types.
572 ;; No symbol is a keyword after "->" in Pike.
579 ;; Fontify leading identifiers in fully qualified names like
580 ;; "foo::bar" in languages that supports such things.
583 ;; Must use a function here since we match longer
584 ;; than we want to move before doing a new search.
585 ;; This is not necessary for XEmacs >= 20 since it
586 ;; restarts the search from the end of the first
587 ;; highlighted submatch (something that causes
588 ;; problems in other places).
600 limit t)
607 c-reference-face-name))
610 ;; Fontify the special declarations in Objective-C.
618 ;; In this case we accept both primitive and known types.
625 ;; The @interface/@implementation/@protocol directives.
629 t)
634 ;; `parse-sexp-lookup-properties' (when it exists).
641 nil))))))
642 ))
645 ;; Called before any of the matchers in `c-complex-decl-matchers'.
646 ;; Nil is always returned.
648 ;;(message "c-font-lock-complex-decl-prepare %s %s" (point) limit)
650 ;; Clear the list of found types if we start from the start of the
651 ;; buffer, to make it easier to get rid of misspelled types and
652 ;; variables that has gotten recognized as types in malformed code.
656 ;; Clear the c-type char properties in the region to recalculate
657 ;; them properly. This is necessary e.g. to handle constructs that
658 ;; might been required as declarations temporarily during editing.
659 ;; The interesting properties are anyway those put on the closest
660 ;; token before the region.
663 ;; Update `c-state-cache' to the beginning of the region. This will
664 ;; make `c-beginning-of-syntax' go faster when it's used later on,
665 ;; and it's near the point most of the time.
668 ;; Check if the fontified region starts inside a declarator list so
669 ;; that `c-font-lock-declarators' should be called at the start.
678 nil)
681 ;; Fontify types and references in names containing angle bracket
682 ;; arglists from the point to LIMIT. This will also fontify cases
683 ;; like normal function calls on the form "foo (a < b, c > d)", but
684 ;; `c-font-lock-declarations' will undo that later. Nil is always
685 ;; returned.
688 ;; `parse-sexp-lookup-properties' (when it exists).
692 id-start id-end pos kwd-sym)
710 ;; Check for comment/string both at the identifier and
711 ;; at the "<".
716 t)
722 c-reference-face-name)
728 nil)
731 ;; Assuming the point is at the start of a declarator in a
732 ;; declaration, fontify it. If LIST is non-nil, fontify also all
733 ;; following declarators in a comma separated list (e.g. "foo" and
734 ;; "bar" in "int foo = 17, bar;"). Stop at LIMIT. If TYPES is
735 ;; non-nil, fontify all identifiers as types. Nil is always
736 ;; returned.
738 ;;(message "c-font-lock-declarators from %s to %s" (point) limit)
741 paren-depth
742 id-face got-init
743 c-last-identifier-range
747 pos
752 ;; Skip over type decl prefix operators. (Note similar
753 ;; code in `c-font-lock-declarations'.)
757 ;; If the second submatch matches in C++ then
758 ;; we're looking at an identifier that's a
759 ;; prefix only if it specifies a member pointer.
764 ;; We only check for a trailing "::" and
765 ;; let the "*" that should follow be
766 ;; matched in the next round.
767 t
768 ;; It turned out to be the real identifier,
769 ;; so flag that and stop.
771 nil))
772 t))
780 ;; If we didn't pass the identifier above already, do it now.
788 ;; Skip out of the parens surrounding the identifier.
794 ;; Search syntactically to the end of the declarator (";",
795 ;; ",", ")", ">" (for <> arglists), eob etc) or to the
796 ;; beginning of an initializer or function prototype ("="
797 ;; or "\\s\(").
803 'font-lock-function-name-face
808 ;; Register and fontify the identifer as a type.
812 ;; Fontify the last symbol in the identifier if it isn't fontified
813 ;; already. The check is necessary only in certain cases where this
814 ;; function is used "sloppily", e.g. in `c-simple-decl-matchers'.
820 id-face)))
825 ;; Jump past any initializer or function prototype to see if
826 ;; there's a ',' to continue at.
829 ;; Skip a parenthesized initializer (C++) or a function
830 ;; prototype.
836 ;; Skip an initializer expression.
842 ;; If a ',' is found we set pos to the next declarator and iterate.
848 nil)
851 ;; List of faces that might be put at the start of a type when
852 ;; `c-font-lock-declarations' runs. This needs to be evaluated to
853 ;; ensure that face name aliases in Emacs are resolved.
855 font-lock-type-face
856 c-reference-face-name
857 font-lock-keyword-face))
859 ;; Macro used inside `c-font-lock-declarations'. It ought to be a
860 ;; defsubst or perhaps even a defun, but it contains lots of free
861 ;; variables that refer to things inside `c-font-lock-declarations'.
863 ;; `c-font-lock-declarations' can consume an arbitrary length list
864 ;; of types when parsing a declaration, which means that it
865 ;; sometimes consumes the identifier in the declaration as a type.
866 ;; This is used to "backtrack" and make the last type be treated
867 ;; as an identifier instead.
870 ;; These identifiers are bound only in the inner let.
872 identifier-start type-start
873 identifier-end type-end))
875 t
876 prev-at-type))
878 type-end prev-type-end)
880 type-end start-pos))
882 ;; These identifiers are bound only in the inner let.
884 got-parens nil
885 got-identifier t
886 got-suffix t
887 got-suffix-after-parens t
891 ;; Fontify all the declarations and casts from the point to LIMIT.
892 ;; Assumes that strings and comments have been fontified already.
893 ;; Nil is always returned.
894 ;;
895 ;; This function can make hidden buffer changes, but the font-lock
896 ;; context covers that.
898 ;;(message "c-font-lock-declarations search from %s to %s" (point) limit)
902 c-disallow-comma-in-<>-arglists
903 ;; Nonzero if the `c-decl-prefix-re' match is in an arglist context,
904 ;; as opposed to a statement-level context. The major difference is
905 ;; that "," works as declaration delimiter in an arglist context,
906 ;; whereas it only separates declarators in the same declaration in
907 ;; a statement context. If it's nonzero then the value is the
908 ;; matched char, e.g. ?\( or ?,.
909 arglist-match
910 ;; 'decl if we're in an arglist containing declarations (but if
911 ;; `c-recognize-paren-inits' is set it might also be an initializer
912 ;; arglist), '<> if the arglist is of angle bracket type, 'other if
913 ;; it's some other arglist, or nil if not in an arglist at all.
914 arglist-type
915 ;; Set to the result of `c-forward-type'.
916 at-type
917 ;; These record the start and end of the type or possible type found
918 ;; by `c-forward-type'. `type-start' is at the start of the first
919 ;; type token, and `type-end' is at the start of the first token
920 ;; after the type (and after any specifiers).
921 type-start type-end
922 ;; These store `at-type', `type-start' and `type-end' of the
923 ;; identifier before the one in those variables. The previous
924 ;; identifier might turn out to be the real type in a declaration if
925 ;; the last one has to be the declarator in it. If `prev-at-type'
926 ;; is nil then the other variables have undefined values.
927 prev-at-type prev-type-start prev-type-end
928 ;; Whether we've found a declaration or a cast. We might know this
929 ;; before we've found the type in it.
930 at-decl-or-cast
931 ;; Set when we need to back up to parse this as a declaration but
932 ;; not as a cast.
933 backup-if-not-cast
934 ;; Set if we've found a "typedef" specifier. The identifiers in the
935 ;; declaration are then fontified as types.
936 at-typedef
937 ;; Set if we've found a specifier that can start a declaration where
938 ;; there's no type.
939 maybe-typeless
940 ;; The position of the next token after the closing paren of the
941 ;; last fontified cast.
942 last-cast-end
943 ;; The same for the currently investigated cast.
944 cast-end
945 ;; The maximum of the end positions of all the checked type decl
946 ;; expressions in the successfully identified declarations. The
947 ;; position might be either before or after the syntactic whitespace
948 ;; following the last token in the type decl expression.
950 ;; Same as `max-type-decl-*', but used when we're before
951 ;; `token-pos'.
953 ;; Allow recording of identifier ranges in `c-forward-type' etc for
954 ;; later fontification. Not using `c-fontify-types-and-refs' here
955 ;; since the ranges should be fontified selectively only when a
956 ;; declaration or cast has been successfully recognized.
957 c-record-type-identifiers
958 c-record-ref-identifiers
959 ;; The font-lock package in Emacs is known to clobber
960 ;; `parse-sexp-lookup-properties' (when it exists).
965 ;; Below we fontify a whole declaration even when it crosses the limit,
966 ;; to avoid gaps when lazy-lock fontifies the file a screenful at a
967 ;; time. That is however annoying during editing, e.g. the following is
968 ;; a common situation while the first line is being written:
969 ;;
970 ;; my_variable
971 ;; some_other_variable = 0;
972 ;;
973 ;; font-lock will put the limit at the beginning of the second line
974 ;; here, and if we go past it we'll fontify "my_variable" as a type and
975 ;; "some_other_variable" as an identifier, and the latter will not
976 ;; correct itself until the second line is changed. To avoid that we
977 ;; narrow to the limit if the region to fontify is a single line.
982 ;; Narrow after any operator chars following the limit though, since
983 ;; those characters can be useful in recognizing a declaration (in
984 ;; particular the '{' that opens a function body after the header).
990 limit
991 c-identifier-start
992 c-font-lock-maybe-decl-faces
996 ;; Don't do anything more if we're looking at a keyword
997 ;; that can't start a declaration.
1003 ;; Set `arglist-match' and `arglist-type'. Look for "<" for the
1004 ;; sake of C++-style template arglists.
1008 ;; Find out the type of the arglist.
1013 ;; Got a cached hit in a declaration arglist.
1017 ;; Inside an angle bracket arglist.
1020 ;; Got a cached hit in some other type of arglist.
1025 ;; The point is within the range of a previously
1026 ;; encountered type decl expression, so the arglist
1027 ;; is probably one that contains declarations.
1028 ;; However, if `c-recognize-paren-inits' is set it
1029 ;; might also be an initializer arglist.
1031 ;; The result of this check is cached with a char
1032 ;; property on the match token, so that we can look
1033 ;; it up again when refontifying single lines in a
1034 ;; multiline declaration.
1041 arglist-type nil))
1044 at-decl-or-cast nil
1045 backup-if-not-cast nil
1046 at-typedef nil
1047 maybe-typeless nil
1048 c-record-type-identifiers t
1049 c-record-ref-identifiers nil
1050 ;; `start-pos' is used below to point to the start of the
1051 ;; first type, i.e. after any leading specifiers. It might
1052 ;; also point at the beginning of the preceding syntactic
1053 ;; whitespace.
1055 ;; If we're in a normal arglist context we don't want to
1056 ;; recognize commas in nested angle bracket arglists since
1057 ;; those commas could be part of our own arglist.
1058 c-disallow-comma-in-<>-arglists
1064 ;; We're standing at the start of a normal arglist so remove any
1065 ;; angle bracket arglists containing commas that's been
1066 ;; recognized inside it by the preceding slightly opportunistic
1067 ;; scan in `c-font-lock-<>-arglists'.
1078 ;; Check for a type, but be prepared to skip over leading
1079 ;; specifiers like "static". Unknown symbols are treated as
1080 ;; possible types, but they could also be specifiers disguised
1081 ;; through macros like __INLINE__, so we recognize both types and
1082 ;; known specifiers after them too.
1085 ;; Don't look for a type if we already found a
1086 ;; positive one; we only loop for the
1087 ;; `c-specifier-key' check then.
1091 ;; Found a known or possible type or a prefix of a known
1092 ;; type.
1095 ;; Got two identifiers with nothing but whitespace
1096 ;; between them. That can only happen in
1097 ;; declarations.
1101 ;; If the previous identifier is a found type we
1102 ;; record it as a real one; it might be some sort of
1103 ;; alias for a prefix like "unsigned".
1110 prev-type-start type-start
1111 prev-type-end type-end
1112 at-type res
1113 type-start start
1116 ;; If the type isn't known we continue so that we'll
1117 ;; jump over all specifiers and type identifiers. The
1118 ;; reason to do this for a known type prefix is to make
1119 ;; things like "unsigned INT16" work.
1123 ;; Found a known specifier keyword. The specifier
1124 ;; keywords are restrictive, so we check for them
1125 ;; anywhere inside or around the type(s). We thereby
1126 ;; avoid having special cases for specifiers like MSVC
1127 ;; '__declspec' which can come after the type.
1138 ;; Move type-end forward if we've passed a type,
1139 ;; otherwise move start-pos forward.
1144 res)))
1148 ;; A prefix type is itself a primitive type when it's not
1149 ;; followed by another type.
1153 ;; Got no type but set things up to continue anyway to handle the
1154 ;; various cases when a declaration doesn't start with a type.
1159 ;; If it's C++ then check if the last "type" ends on the form
1160 ;; "foo::foo" or "foo::~foo", i.e. if it's the name of a
1161 ;; (con|de)structor.
1172 ;; Cheating in the handling of syntactic ws below.
1179 name))
1180 ;; It is a (con|de)structor name. In that case the
1181 ;; declaration is typeless so zap out any preceding
1182 ;; identifier(s) that we might have taken as types.
1185 prev-at-type nil
1186 type-end type-start))))))
1188 ;; Check for and step over a type decl expression after the thing
1189 ;; that is or might be a type. This can't be skipped since we need
1190 ;; the correct end position of the declarator for
1191 ;; `max-type-decl-end-*'.
1193 ;; True if there's a non-open-paren match of
1194 ;; `c-type-decl-prefix-key'.
1195 got-prefix
1196 ;; True if the declarator is surrounded by a parenthesis pair.
1197 got-parens
1198 ;; True if there is an identifier in the declarator.
1199 got-identifier
1200 ;; True if there's a non-close-paren match of
1201 ;; `c-type-decl-suffix-key'.
1202 got-suffix
1203 ;; True if there's a prefix or suffix match outside the
1204 ;; outermost paren pair that surrounds the declarator.
1205 got-prefix-before-parens
1206 got-suffix-after-parens
1207 ;; True if we've parsed the type decl to a token that
1208 ;; is known to end declarations in this context.
1209 at-decl-end
1210 ;; The earlier values of `at-type', `type-start' and
1211 ;; `type-end' if we've shifted the type backwards.
1212 identifier-type identifier-start identifier-end)
1215 ;; Skip over type decl prefix operators. (Note similar code in
1216 ;; `c-font-lock-declarators'.)
1220 ;; If the second submatch matches in C++ then
1221 ;; we're looking at an identifier that's a prefix
1222 ;; only if it specifies a member pointer.
1225 ;; We only check for a trailing "::" and
1226 ;; let the "*" that should follow be
1227 ;; matched in the next round.
1229 ;; It turned out to be the real identifier,
1230 ;; so stop.
1231 nil))
1232 t))
1244 ;; Skip over an identifier.
1249 ;; Skip over type decl suffix operators.
1255 t)
1259 t)
1263 ;; No suffix matched. We might have matched the
1264 ;; identifier as a type and the open paren of a function
1265 ;; arglist as a type decl prefix. In that case we
1266 ;; should "backtrack": Reinterpret the last type as the
1267 ;; identifier, move out of the arglist and continue
1268 ;; searching for suffix operators.
1269 ;;
1270 ;; Do this even if there's no preceding type, to cope
1271 ;; with old style function declarations in K&R C,
1272 ;; (con|de)structors in C++ and `c-typeless-decl-kwds'
1273 ;; style declarations. That isn't applicable in an
1274 ;; arglist context, though.
1279 maybe-typeless
1286 t))
1292 at-type
1294 ;; Have found no identifier but `c-typeless-decl-kwds' has
1295 ;; matched so we know we're inside a declaration. The
1296 ;; preceding type must be the identifier instead.
1300 at-decl-or-cast
1304 ;; Encountered something inside parens that isn't matched by
1305 ;; the `c-type-decl-*' regexps, so it's not a type decl
1306 ;; expression. Try to skip out to the same paren depth to
1307 ;; not confuse the cast check below.
1316 ;; Now we've collected info about various characteristics of
1317 ;; the construct we're looking at. Below follows a decision
1318 ;; tree based on that. It's ordered to check more certain
1319 ;; signs before less certain ones.
1326 ;; Got another identifier directly after the type, so
1327 ;; it's a declaration.
1334 ;; Got a declaration of the form "foo bar (gnu);"
1335 ;; where we've recognized "bar" as the type and "gnu"
1336 ;; as the declarator. In this case it's however more
1337 ;; likely that "bar" is the declarator and "gnu" a
1338 ;; function argument or initializer (if
1339 ;; `c-recognize-paren-inits' is set), since the parens
1340 ;; around "gnu" would be superfluous if it's a
1341 ;; declarator. Shift the type one step backward.
1344 ;; Found no identifier.
1351 ;; Got two types after each other, so if this isn't a
1352 ;; cast then the latter probably is the identifier and
1353 ;; we should back up to the previous type.
1358 ;; If the type is known we know that there can't be any
1359 ;; identifier somewhere else, and it's only in
1360 ;; declarations in e.g. function prototypes and in casts
1361 ;; that the identifier may be left out.
1365 ;; Only got a single identifier (parsed as a type so
1366 ;; far).
1368 ;; Check that the identifier isn't at the start of
1369 ;; an expression.
1370 at-decl-end
1373 ;; Inside an arglist that contains declarations.
1374 ;; If K&R style declarations and parenthesis
1375 ;; style initializers aren't allowed then the
1376 ;; single identifier must be a type, else we
1377 ;; require that it's known or found (primitive
1378 ;; types are handled above).
1383 ;; Inside a template arglist. Accept known and
1384 ;; found types; other identifiers could just as
1385 ;; well be constants in C++.
1391 got-parens
1396 prev-at-type
1397 maybe-typeless
1401 c-after-suffixed-type-maybe-decl-key))))))
1402 ;; Got an empty paren pair and a preceding type that
1403 ;; probably really is the identifier. Shift the type
1404 ;; backwards to make the last one the identifier. This
1405 ;; is analogous to the "backtracking" done inside the
1406 ;; `c-type-decl-suffix-key' loop above.
1407 ;;
1408 ;; Exception: In addition to the conditions in that
1409 ;; "backtracking" code, do not shift backward if we're
1410 ;; not looking at either `c-after-suffixed-type-decl-key'
1411 ;; or "[;,]". Since there's no preceding type, the
1412 ;; shift would mean that the declaration is typeless.
1413 ;; But if the regexp doesn't match then we will simply
1414 ;; fall through in the tests below and not recognize it
1415 ;; at all, so it's better to try it as an abstract
1416 ;; declarator instead.
1419 ;; Still no identifier.
1422 ;; Require `got-prefix' together with either
1423 ;; `got-parens' or `got-suffix' to recognize it as an
1424 ;; abstract declarator: `got-parens' only is probably an
1425 ;; empty function call. `got-suffix' only can build an
1426 ;; ordinary expression together with the preceding
1427 ;; identifier which we've taken as a type. We could
1428 ;; actually accept on `got-prefix' only, but that can
1429 ;; easily occur temporarily while writing an expression
1430 ;; so we avoid that case anyway. We could do a better
1431 ;; job if we knew the point when the fontification was
1432 ;; invoked.
1436 ;; By now we've located the type in the declaration that we
1437 ;; know we're in.
1447 ;; Shift the type backward in the case that
1448 ;; there's a single identifier inside parens.
1449 ;; That can only occur in K&R style function
1450 ;; declarations so it's more likely that it
1451 ;; really is a function call. Therefore we
1452 ;; only do this after
1453 ;; `c-after-suffixed-type-decl-key' has
1454 ;; matched.
1456 got-suffix-after-parens))
1457 ;; A declaration according to
1458 ;; `c-after-suffixed-type-decl-key'.
1463 ;; It's a declaration if a known type precedes it and it
1464 ;; can't be a function call.
1467 ;; If we get here we can't tell if this is a type decl or a
1468 ;; normal expression by looking at it alone. (That's under
1469 ;; the assumption that normal expressions always can look like
1470 ;; type decl expressions, which isn't really true but the
1471 ;; cases where it doesn't hold are so uncommon (e.g. some
1472 ;; placements of "const" in C++) it's not worth the effort to
1473 ;; look for them.)
1476 ;; If this is a declaration it should end here or its
1477 ;; initializer(*) should start here, so check for allowed
1478 ;; separation tokens. Note that this rule doesn't work
1479 ;; e.g. with a K&R arglist after a function header.
1480 ;;
1481 ;; *) Don't check for C++ style initializers using parens
1482 ;; since those already have been matched as suffixes.
1485 ;; Below are tests that only should be applied when we're
1486 ;; certain to not have parsed halfway through an expression.
1489 ;; The expression starts with a known type so treat it as a
1490 ;; declaration.
1494 ;; In C++ we check if the identifier is a known
1495 ;; type, since (con|de)structors use the class name
1496 ;; as identifier. We've always shifted over the
1497 ;; identifier as a type and then backed up again in
1498 ;; this case.
1499 identifier-type
1502 ;; `at-type' probably won't be 'found for
1503 ;; destructors since the "~" is then part
1504 ;; of the type name being checked against
1505 ;; the list of known types, so do a check
1506 ;; without that operator.
1508 identifier-end))))
1514 at-type
1518 ;; Got something like "foo * bar;". Since we're not
1519 ;; inside an arglist it would be a meaningless
1520 ;; expression because the result isn't used. We
1521 ;; therefore choose to recognize it as a declaration.
1522 ;; Do not allow a suffix since it could then be a
1523 ;; function call.
1530 ;; Got something like "a (*b) (c);" or "a (b) = c;".
1531 ;; It could be an odd expression or it could be a
1532 ;; declaration. Treat it as a declaration if "a" has
1533 ;; been used as a type somewhere else (if it's a known
1534 ;; type we won't get here).
1542 ;; Got a type followed by an abstract declarator. If
1543 ;; `got-prefix' is set it's something like "a *" without
1544 ;; anything after it. If `got-parens' or `got-suffix' is
1545 ;; set it's "a()", "a[]", "a()[]", or similar, which we
1546 ;; accept only if the context rules out expressions.
1549 ;; If we had a complete symbol table here (which rules out
1550 ;; `c-found-types') we should return t due to the
1551 ;; disambiguation rule (in at least C++) that anything that
1552 ;; can be parsed as a declaration is a declaration. Now we're
1553 ;; being more defensive and prefer to highlight things like
1554 ;; "foo (bar);" as a declaration only if we're inside an
1555 ;; arglist that contains declarations.
1558 ;; Point is now after the type decl expression.
1561 ;; Check for a cast.
1564 c-cast-parens
1566 ;; Should be the first type/identifier in a cast paren.
1569 ;; The closing paren should follow.
1574 ;; There should be a primary expression after it.
1583 ;; Check if the expression begins with a prefix
1584 ;; keyword.
1587 ;; Expression begins with an ambiguous operator.
1588 ;; Treat it as a cast if it's a type decl or if
1589 ;; we've recognized the type somewhere else.
1592 ;; Unless it's a keyword, it's the beginning of a
1593 ;; primary expression.
1595 ;; If `c-primary-expr-regexp' matched a nonsymbol
1596 ;; token, check that it matched a whole one so that we
1597 ;; don't e.g. confuse the operator '-' with '->'. It's
1598 ;; ok if it matches further, though, since it e.g. can
1599 ;; match the float '.5' while the operator regexp only
1600 ;; matches '.'.
1604 ;; There should either be a cast before it or something that
1605 ;; isn't an identifier or close paren.
1613 ;; It's a symbol. Accept it only if it's one of
1614 ;; the keywords that can precede an expression
1615 ;; (without surrounding parens).
1618 ;; Check that it isn't a close paren (block close
1619 ;; is ok, though).
1621 ;; Check that it isn't a nonsymbol identifier.
1624 ;; Handle the cast.
1632 ;; We're at a declaration. Highlight the type and the following
1633 ;; declarators.
1639 ;; Make sure to propagate the `c-decl-arg-start' property to
1640 ;; the next argument if it's set in this one, to cope with
1641 ;; interactive refontification.
1644 ;; Set `max-type-decl-end' or `max-type-decl-end-before-token'
1645 ;; under the assumption that we're after the first type decl
1646 ;; expression in the declaration now. That's not really true; we
1647 ;; could also be after a parenthesized initializer expression in
1648 ;; C++, but this is only used as a last resort to slant ambiguous
1649 ;; expression/declarations, and overall it's worth the risk to
1650 ;; occasionally fontify an expression as a declaration in an
1651 ;; initializer expression compared to getting ambiguous things in
1652 ;; normal function prototypes fontified as expressions.
1668 ;; Should normally not fontify a list of declarators
1669 ;; inside an arglist, but the first argument in the
1670 ;; ';' separated list of a "for" statement is an
1671 ;; exception.
1678 t)))
1680 ;; Fix the `c-decl-id-start' or `c-decl-type-start' property
1681 ;; before the first declarator if it's a list.
1682 ;; `c-font-lock-declarators' handles the rest.
1689 'c-decl-type-start
1695 ;; False alarm. Skip the fontification done below.
1698 ;; A cast or declaration has been successfully identified, so do
1699 ;; all the fontification of types and refs that's been recorded by
1700 ;; the calls to `c-forward-type' and `c-forward-name' above.
1702 nil)))
1704 nil)))
1707 "Simple font lock matchers for types and declarations. These are used
1708 on level 2 only and so aren't combined with `c-complex-decl-matchers'."
1716 ;; `parse-sexp-lookup-properties' (when it exists).
1723 nil))
1726 ;; Fontify all type names and the identifiers in the
1727 ;; declarations they might start. Use eval here since
1728 ;; `c-known-type-key' gets its value from
1729 ;; `*-font-lock-extra-types' on mode init.
1731 'c-known-type-key
1739 ;; Fontify types preceded by `c-type-prefix-kwds' and the
1740 ;; identifiers in the declarations they might start.
1756 ;; Fontify special declarations that lacks a type.
1767 ))
1770 "Complex font lock matchers for types and declarations. Used on level
1771 3 and higher."
1774 c-font-lock-complex-decl-prepare
1776 ;; Fontify angle bracket arglists like templates in C++.
1781 ;; Fontify method declarations in Objective-C, but first
1782 ;; we have to put the `c-decl-end' `c-type' property on
1783 ;; all the @-style directives that haven't been handled in
1784 ;; `c-basic-matchers-before'.
1787 ;; Exclude "@class" since that directive ends with a
1788 ;; semicolon anyway.
1792 nil)))
1796 c-font-lock-objc-methods)
1804 ;; Fontify all declarations and casts.
1805 c-font-lock-declarations
1807 ;; The first two rules here mostly find occurences that
1808 ;; `c-font-lock-declarations' has found already, but not
1809 ;; declarations containing blocks in the type (see note below).
1810 ;; It's also useful to fontify these everywhere to show e.g. when
1811 ;; a type keyword is accidentally used as an identifier.
1813 ;; Fontify basic types.
1817 ;; No symbol is a keyword after "->" in Pike.
1824 ;; Fontify types preceded by `c-type-prefix-kwds'.
1830 ;; The font-lock package in Emacs is known to clobber
1831 ;; `parse-sexp-lookup-properties' (when it exists).
1836 ;; Narrow to avoid going past the limit in
1837 ;; `c-forward-type'.
1844 limit t)
1847 ;; Handle prefix declaration specifiers.
1853 ;; In C++ we additionally check for a "class
1854 ;; X = Y" construct which is used in
1855 ;; templates, to fontify Y as a type.
1860 )))))))))
1862 ;; Fontify symbols after closing braces as declaration
1863 ;; identifiers under the assumption that they are part of
1864 ;; declarations like "class Foo { ... } foo;". It's too
1865 ;; expensive to check this accurately by skipping past the
1866 ;; brace block, so we use the heuristic that it's such a
1867 ;; declaration if the first identifier is on the same line as
1868 ;; the closing brace. `c-font-lock-declarations' will later
1869 ;; override it if it turns out to be an new declaration, but
1870 ;; it will be wrong if it's an expression (see the test
1871 ;; decls-8.cc).
1887 c-single-line-syntactic-ws-depth)))))
1890 ;; Fontify the type in C++ "new" expressions.
1894 ))
1897 ;; Fontify all the declarations from the point to LIMIT. Assumes
1898 ;; that strings and comments have been fontified already. Nil is
1899 ;; always returned.
1900 ;;
1901 ;; This function can make hidden buffer changes, but the font-lock
1902 ;; context covers that.
1905 ;; The font-lock package in Emacs is known to clobber
1906 ;; `parse-sexp-lookup-properties' (when it exists).
1925 ;; Check for a char that precedes a statement.
1927 ;; Check for a preceding label. We exploit the font
1928 ;; locking made earlier by this function.
1935 c-label-face-name))
1936 ;; Check for a keyword that precedes a statement.
1940 ;; Got a label.
1944 c-label-face-name)))
1947 nil)
1950 "Font lock matchers for various things that should be fontified after
1951 generic casts and declarations are fontified. Used on level 2 and
1952 higher."
1955 ;; name is handled by `c-simple-decl-matchers' or
1956 ;; `c-complex-decl-matchers' below.
1963 ;; Disallow various common punctuation chars that can't come
1964 ;; before the '{' of the enum list, to avoid searching too far.
1965 "[^\]\[{}();,/#=]*"
1975 ;; Fontify labels in languages that supports them.
1979 ;; (Got three different interpretation levels here,
1980 ;; which makes it a bit complicated: 1) The backquote
1981 ;; stuff is expanded when compiled or loaded, 2) the
1982 ;; eval form is evaluated at font-lock setup (to
1983 ;; substitute c-label-face-name correctly), and 3) the
1984 ;; resulting structure is interpreted during
1985 ;; fontification.)
1997 c-label-face-name nil t))))
1999 ;; Fontify normal labels.
2000 c-font-lock-labels))
2002 ;; Fontify the clauses after various keywords.
2018 ))
2036 ;; Incorporate the font lock keyword lists according to
2037 ;; `c-doc-comment-style' on the given keyword list and return it.
2038 ;; This is used in the function bindings of the
2039 ;; `*-font-lock-keywords-*' symbols since we have to build the list
2040 ;; when font-lock is initialized.
2049 c-doc-comment-style))
2061 doc-keywords
2063 base-list)))
2065 ;; Kludge: If `c-font-lock-complex-decl-prepare' is on the list we
2066 ;; move it first since the doc comment font lockers might add
2067 ;; `c-type' text properties so they have to be cleared before that.
2073 list))
2076 ;; This is used to override the value on a `*-font-lock-keywords'
2077 ;; variable only if it's nil or has the same value as one of the
2078 ;; `*-font-lock-keywords-*' variables. Older font-lock packages
2079 ;; define a default value for `*-font-lock-keywords' which we want
2080 ;; to override, but we should otoh avoid clobbering a user setting.
2081 ;; This heuristic for that isn't perfect, but I can't think of any
2082 ;; better. /mast
2083 ;;
2084 ;; This function does not do any hidden buffer changes.
2091 suffix))))
2094 ;; The overriding is done by unbinding the variable so that the normal
2095 ;; defvar will install its default value later on.
2098 \f
2099 ;;; C.
2104 "Minimal font locking for C mode.
2105 Fontifies only preprocessor directives (in addition to the syntactic
2109 "Fast normal font locking for C mode.
2110 In addition to `c-font-lock-keywords-1', this adds fontification of
2111 keywords, simple types, declarations that are easy to recognize, the
2112 user defined types on `c-font-lock-extra-types', and the doc comment
2116 "Accurate normal font locking for C mode.
2117 Like `c-font-lock-keywords-2' but detects declarations in a more
2118 accurate way that works in most cases for arbitrary types without the
2131 \f
2132 ;;; C++.
2135 ;; Assuming point is after a "new" word, check that it isn't inside
2136 ;; a string or comment, and if so try to fontify the type in the
2137 ;; allocation expression. Nil is always returned.
2138 ;;
2139 ;; As usual, C++ takes the prize in coming up with a hard to parse
2140 ;; syntax. :P
2145 ;; A "new" keyword is followed by one to three expressions, where
2146 ;; the type is the middle one, and the only required part.
2148 ;; Enable recording of identifier ranges in `c-forward-type'
2149 ;; etc for later fontification. Not using
2150 ;; `c-fontify-types-and-refs' here since the ranges should
2151 ;; be fontified selectively only when an allocation
2152 ;; expression is successfully recognized.
2154 c-record-ref-identifiers
2155 ;; The font-lock package in Emacs is known to clobber
2156 ;; `parse-sexp-lookup-properties' (when it exists).
2162 ;; The first placement arglist is always parenthesized, if it
2163 ;; exists.
2171 ;; The second expression is either a type followed by some "*" or
2172 ;; "[...]" or similar, or a parenthesized type followed by a full
2173 ;; identifierless declarator.
2183 ;; No second expression, so the first has to be a
2184 ;; parenthesized type.
2190 ;; Got two parenthesized expressions, so we have to look
2191 ;; closer at them to decide which is the type. No need to
2192 ;; handle `c-record-ref-identifiers' since all references
2193 ;; has already been handled by other fontification rules.
2202 ;; There's something after the would-be type that
2203 ;; can't be there, so this is a placement arglist.
2212 ;; There's something after the would-be type that can't
2213 ;; be there, so this is an initialization expression.
2218 ;; If there's a third initialization expression
2219 ;; then the second one is the type, so demote the
2220 ;; first match.
2223 ;; We fontify the most likely type, with a preference for
2224 ;; the first argument since a placement arglist is more
2225 ;; unusual than an initializer.
2244 ;; If both type matches are 'maybe then we're
2245 ;; too uncertain to promote either of them.
2246 )))))
2248 ;; Fontify the type that now is recorded in
2249 ;; `c-record-type-identifiers', if any.
2251 nil)
2256 "Minimal font locking for C++ mode.
2257 Fontifies only preprocessor directives (in addition to the syntactic
2261 "Fast normal font locking for C++ mode.
2262 In addition to `c++-font-lock-keywords-1', this adds fontification of
2263 keywords, simple types, declarations that are easy to recognize, the
2264 user defined types on `c++-font-lock-extra-types', and the doc comment
2268 "Accurate normal font locking for C++ mode.
2269 Like `c++-font-lock-keywords-2' but detects declarations in a more
2270 accurate way that works in most cases for arbitrary types without the
2283 \f
2284 ;;; Objective-C.
2287 ;; Assuming the point is after an "@interface", "@implementation",
2288 ;; "@protocol" declaration, fontify all the types in the directive.
2289 ;; Return t if the directive was fully recognized. Point will then
2290 ;; be at the end of it.
2295 ;; Turn off recognition of angle bracket arglists while parsing
2296 ;; types here since the protocol reference list might then be
2297 ;; considered part of the preceding name or superclass-name.
2301 ;; Handle the name of the class itself.
2305 ;; Look for ": superclass-name" or "( category-name )".
2316 ;; Look for a protocol reference list.
2321 t)
2323 t))))
2326 ;; Assuming the point is after the + or - that starts an Objective-C
2327 ;; method declaration, fontify it. This must be done before normal
2328 ;; casts, declarations and labels are fontified since they will get
2329 ;; false matches in these things.
2339 ;; An optional method type.
2347 t))
2349 ;; The name. The first time it's the first part of
2350 ;; the function name, the rest of the time it's an
2351 ;; argument name.
2358 'font-lock-function-name-face
2362 ;; Another optional part of the function name.
2370 ;; There's another argument if a colon follows.
2376 ;; Fontify method declarations in Objective-C. Nil is always
2377 ;; returned.
2380 ;; `parse-sexp-lookup-properties' (when it exists).
2386 limit
2387 "[-+]"
2388 nil
2392 nil)
2397 "Minimal font locking for Objective-C mode.
2398 Fontifies only compiler directives (in addition to the syntactic
2402 "Fast normal font locking for Objective-C mode.
2403 In addition to `objc-font-lock-keywords-1', this adds fontification of
2404 keywords, simple types, declarations that are easy to recognize, the
2405 user defined types on `objc-font-lock-extra-types', and the doc
2409 "Accurate normal font locking for Objective-C mode.
2410 Like `objc-font-lock-keywords-2' but detects declarations in a more
2411 accurate way that works in most cases for arbitrary types without the
2424 ;; Kludge to override the default value that
2425 ;; `objc-font-lock-extra-types' might have gotten from the font-lock
2426 ;; package. The value replaced here isn't relevant now anyway since
2427 ;; those types are builtin and therefore listed directly in
2428 ;; `c-primitive-type-kwds'.
2434 \f
2435 ;;; Java.
2440 "Minimal font locking for Java mode.
2441 Fontifies nothing except the syntactic fontification of strings and
2445 "Fast normal font locking for Java mode.
2446 In addition to `java-font-lock-keywords-1', this adds fontification of
2447 keywords, simple types, declarations that are easy to recognize, the
2448 user defined types on `java-font-lock-extra-types', and the doc
2452 "Accurate normal font locking for Java mode.
2453 Like `java-font-lock-keywords-2' but detects declarations in a more
2454 accurate way that works in most cases for arbitrary types without the
2467 \f
2468 ;;; CORBA IDL.
2473 "Minimal font locking for CORBA IDL mode.
2474 Fontifies nothing except the syntactic fontification of strings and
2478 "Fast normal font locking for CORBA IDL mode.
2479 In addition to `idl-font-lock-keywords-1', this adds fontification of
2480 keywords, simple types, declarations that are easy to recognize, the
2481 user defined types on `idl-font-lock-extra-types', and the doc comment
2485 "Accurate normal font locking for CORBA IDL mode.
2486 Like `idl-font-lock-keywords-2' but detects declarations in a more
2487 accurate way that works in most cases for arbitrary types without the
2500 \f
2501 ;;; Pike.
2506 "Minimal font locking for Pike mode.
2507 Fontifies only preprocessor directives (in addition to the syntactic
2511 "Fast normal font locking for Pike mode.
2512 In addition to `pike-font-lock-keywords-1', this adds fontification of
2513 keywords, simple types, declarations that are easy to recognize, the
2514 user defined types on `pike-font-lock-extra-types', and the doc
2518 "Accurate normal font locking for Pike mode.
2519 Like `pike-font-lock-keywords-2' but detects declarations in a more
2520 accurate way that works in most cases for arbitrary types without the
2533 \f
2534 ;;; Doc comments.
2537 ;; Fontify the comments between the point and LIMIT whose start
2538 ;; matches PREFIX with `c-doc-face-name'. Assumes comments have been
2539 ;; fontified with `font-lock-comment-face' already. nil is always
2540 ;; returned.
2541 ;;
2542 ;; After the fontification of a matching comment, fontification
2543 ;; according to KEYWORDS is applied inside it. It's a list like
2544 ;; `font-lock-keywords' except that anchored matches and eval
2545 ;; clauses aren't supported and that some abbreviated forms can't be
2546 ;; used. The buffer is narrowed to the comment while KEYWORDS is
2547 ;; applied; leading comment starters are included but trailing
2548 ;; comment enders for block comment are not.
2549 ;;
2550 ;; Note that faces added through KEYWORDS should never replace the
2551 ;; existing `c-doc-face-name' face since the existence of that face
2552 ;; is used as a flag in other code to skip comments.
2557 ;; Handle the case when the fontified region starts inside a
2558 ;; comment.
2567 comment-beg
2569 ;; Search for the prefix until a match is found at the start
2570 ;; of a comment.
2574 c-literal-faces))
2577 c-literal-faces))))
2582 ;; Collect a sequence of doc style line comments.
2599 ;; Narrow to the doc comment. Among other things, this
2600 ;; helps by making "^" match at the start of the comment.
2601 ;; Do not include a trailing block comment ender, though.
2625 nil)
2629 ;; Used to fontify invalid markup in doc comments after the correct
2630 ;; ones have been fontified: Find the first occurence of REGEXP
2631 ;; between the point and LIMIT that only is fontified with
2632 ;; `c-doc-face-name'. If a match is found then submatch 0 surrounds
2633 ;; the first char and t is returned, otherwise nil is returned.
2638 c-doc-face-name))
2643 t)))
2662 ;; Fontify remaining markup characters as invalid. Note
2663 ;; that the Javadoc spec is hazy about when "@" is allowed
2664 ;; in non-markup use.
2668 ))))))
2671 ;; Adorned regexp matching the keywords that introduce declarations
2672 ;; in Pike Autodoc.
2677 ;; Adorned regexp matching the keywords that are followed by a type.
2682 ;; Fontify all line oriented keywords between the point and LIMIT.
2683 ;; Nil is always returned.
2686 c-current-comment-prefix
2697 end)
2701 ;; Put a declaration end mark at the markup keyword and
2702 ;; remove the faces from the rest of the line so that it
2703 ;; gets refontified as a declaration later on by
2704 ;; `c-font-lock-declarations'.
2720 ;; Include the final newline in the removed area. This
2721 ;; has no visual effect but it avoids some tricky special
2722 ;; cases in the testsuite wrt the differences in string
2723 ;; fontification in Emacs vs XEmacs.
2726 ;; Must handle string literals explicitly inside the declaration.
2734 ;; Fontify types after keywords that always are followed
2735 ;; by them.
2743 ;; Mark each whole line as markup, as long as the logical line
2744 ;; continues.
2748 markup-faces)
2756 nil)
2759 ;; Note that we depend on that `c-current-comment-prefix' has got
2760 ;; its proper value here.
2762 ;; The `c-type' text property with `c-decl-end' is used to mark the
2763 ;; end of the `autodoc-decl-keywords' occurrences to fontify the
2764 ;; following declarations.
2772 ;; In-text markup.
2775 ;; Fontify remaining markup characters as invalid.
2779 ))))))
2781 \f
2782 ;; AWK.
2784 ;; Awk regexps written with help from Peter Galbraith
2785 ;; <galbraith@mixing.qc.dfo.ca>.
2786 ;; Take GNU Emacs's 'words out of the following regexp-opts. They dont work
2787 ;; in Xemacs 21.4.4. acm 2002/9/19.
2792 ;; Function names.
2795 ;;
2796 ;; Variable names.
2806 ;; Special file names. (acm, 2002/7/22)
2807 ;; The following regexp was created by first evaluating this in GNU Emacs 21.1:
2808 ;; (c-regexp-opt '("/dev/stdin" "/dev/stdout" "/dev/stderr" "/dev/fd/n" "/dev/pid"
2809 ;; "/dev/ppid" "/dev/pgrpid" "/dev/user") 'words)
2810 ;; , removing the "?:" from each "\\(?:" (for backward compatibility with older Emacsen)
2811 ;; , replacing the "n" in "dev/fd/n" with "[0-9]+"
2812 ;; , removing the unwanted \\< at the beginning, and finally filling out the
2813 ;; regexp so that a " must come before, and either a " or heuristic stuff after.
2814 ;; The surrounding quotes are fontified along with the filename, since, semantically,
2815 ;; they are an indivisible unit.
2821 ;; Do the same (almost) with
2822 ;; (c-regexp-opt '("/inet/tcp/lport/rhost/rport" "/inet/udp/lport/rhost/rport"
2823 ;; "/inet/raw/lport/rhost/rport") 'words)
2824 ;; This cannot be combined with the above pattern, because the match number
2825 ;; for the (optional) closing \" would then exceed 9.
2831 ;; Keywords.
2839 ;; Builtins.
2854 ;; gawk debugging keywords. (acm, 2002/7/21)
2855 ;; (Removed, 2003/6/6. These functions are now fontified as built-ins)
2856 ;; (list (concat "\\<" (c-regexp-opt '("adump" "stopme") t) "\\>")
2857 ;; 0 'font-lock-warning-face)
2859 ;; User defined functions with an apparent spurious space before the
2860 ;; opening parenthesis. acm, 2002/5/30.
2865 ;; Space after \ in what looks like an escaped newline. 2002/5/31
2868 ;; Unbalanced string (") or regexp (/) delimiters. 2002/02/16.
2870 ;; gawk 3.1 localizable strings ( _"translate me!"). 2002/5/21
2873 ))
2876 \f
2879 ;;; cc-fonts.el ends here