| blob | 4f9289c307d684210ea3d397e7058319af3219e6 |
1 ;;; cc-fonts.el --- font lock support for CC Mode
3 ;; Copyright (C) 2002-2013 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 ;; Keywords: c languages
10 ;; Package: cc-mode
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 3 of the License, or
17 ;; (at your option) 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 GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
27 ;;; Commentary:
29 ;; Some comments on the use of faces:
30 ;;
31 ;; o `c-label-face-name' is either `font-lock-constant-face' (in
32 ;; Emacs), or `font-lock-reference-face'.
33 ;;
34 ;; o `c-constant-face-name', `c-reference-face-name' and
35 ;; `c-doc-markup-face-name' are essentially set up like
36 ;; `c-label-face-name'.
37 ;;
38 ;; o `c-preprocessor-face-name' is `font-lock-preprocessor-face' in
39 ;; XEmacs and - in lack of a closer equivalent -
40 ;; `font-lock-builtin-face' or `font-lock-reference-face' in Emacs.
41 ;;
42 ;; o `c-doc-face-name' is `font-lock-doc-string-face' in XEmacs,
43 ;; `font-lock-doc-face' in Emacs 21 and later, or
44 ;; `font-lock-comment-face' in older Emacs (that since source
45 ;; documentation are actually comments in these languages, as opposed
46 ;; to elisp).
47 ;;
48 ;; TBD: We should probably provide real faces for the above uses and
49 ;; instead initialize them from the standard faces.
51 ;;; Code:
53 ;; The faces that already have been put onto the text is tested in
54 ;; various places to direct further fontifications. For this to work,
55 ;; the following assumptions regarding the faces must hold (apart from
56 ;; the dependencies on the font locking order):
57 ;;
58 ;; o `font-lock-comment-face' and the face in `c-doc-face-name' is
59 ;; not used in anything but comments.
60 ;; o If any face (e.g. `c-doc-markup-face-name') but those above is
61 ;; used in comments, it doesn't replace them.
62 ;; o `font-lock-string-face' is not used in anything but string
63 ;; literals (single or double quoted).
64 ;; o `font-lock-keyword-face' and the face in `c-label-face-name' are
65 ;; never overlaid with other faces.
72 load-path)))
80 ;; prevent cc-awk being loaded when it's not needed. There is now a (require
81 ;; 'cc-awk) in (defun awk-mode ..).
83 ;; Avoid repeated loading through the eval-after-load directive in
84 ;; cc-mode.el.
91 ;; Need to declare these local symbols during compilation since
92 ;; they're referenced from lambdas in `byte-compile' calls that are
93 ;; executed at compile time. They don't need to have the proper
94 ;; definitions, though, since the generated functions aren't called
95 ;; during compilation.
103 \f
104 ;; Note that font-lock in XEmacs doesn't expand face names as
105 ;; variables, so we have to use the (eval . FORM) in the font lock
106 ;; matchers wherever we use these alias variables.
110 ;; XEmacs has a font-lock-preprocessor-face.
113 ;; In Emacs font-lock-builtin-face has traditionally been
114 ;; used for preprocessor directives.
123 ;; If it happens to occur in the future. (Well, the more
124 ;; pragmatic reason is to get unique faces for the test
125 ;; suite.)
129 ;; Test both if font-lock-constant-face exists and that it's
130 ;; not an alias for something else. This is important since
131 ;; we compare already set faces in various places.
139 ;; This doesn't exist in some earlier versions of XEmacs 21.
140 'font-lock-constant-face
141 c-label-face-name))
147 ;; This is considered obsolete in Emacs, but it still maps well
148 ;; to this use. (Another reason to do this is to get unique
149 ;; faces for the test suite.)
150 'font-lock-reference-face
151 c-label-face-name)))
153 ;; This should not mapped to a face that also is used to fontify things
154 ;; that aren't comments or string literals.
157 ;; XEmacs.
160 ;; Emacs 21 and later.
167 ;; If it happens to occur in the future. (Well, the more
168 ;; pragmatic reason is to get unique faces for the test
169 ;; suite.)
170 'font-lock-doc-markup-face
171 c-label-face-name))
175 ;; Emacs 22 has a special face for negation chars.
181 ;; Emacs and XEmacs have completely different face manipulation
182 ;; routines. :P
185 ;; Emacs. This only looks at the inverse flag in the current
186 ;; frame. Other display configurations might be different,
187 ;; but it can only show if the same Emacs has frames on
188 ;; e.g. a color and a monochrome display simultaneously.
192 ;; XEmacs. Same pitfall here.
200 "Face for highlighting annotations in Java mode and similar modes."
205 ;; We need the following definitions during compilation since they're
206 ;; used when the `c-lang-defconst' initializers are evaluated. Define
207 ;; them at runtime too for the sake of derived modes.
209 ;; This indicates the "font locking context", and is set just before
210 ;; fontification is done. If non-nil, it says, e.g., point starts
211 ;; from within a #if preprocessor construct.
216 ;; Put a face on a region (overriding any existing face) in the way
217 ;; font-lock would do it. In XEmacs that means putting an
218 ;; additional font-lock property, or else the font-lock package
219 ;; won't recognize it as fontified and might override it
220 ;; incorrectly.
221 ;;
222 ;; This function does a hidden buffer change.
224 ;; Note: This function has no docstring in XEmacs so it might be
225 ;; considered internal.
230 ;; This is the inverse of `c-put-font-lock-face'.
231 ;;
232 ;; This function does a hidden buffer change.
238 ;; Put `font-lock-string-face' on a string. The surrounding
239 ;; quotes are included in Emacs but not in XEmacs. The passed
240 ;; region should include them.
241 ;;
242 ;; This function does a hidden buffer change.
248 ;; Like `let', but additionally activates `c-record-type-identifiers'
249 ;; and `c-record-ref-identifiers', and fontifies the recorded ranges
250 ;; accordingly on exit.
251 ;;
252 ;; This function does hidden buffer changes.
254 c-record-ref-identifiers
261 ;; If the point is within a region fontified as a comment or
262 ;; string literal skip to the end of it or to LIMIT, whichever
263 ;; comes first, and return t. Otherwise return nil. The match
264 ;; data is not clobbered.
265 ;;
266 ;; This function might do hidden buffer changes.
273 t))
276 ;; Returns a byte compiled function suitable for use in place of a
277 ;; regexp string in a `font-lock-keywords' matcher, except that
278 ;; only matches outside comments and string literals count.
279 ;;
280 ;; This function does not do any hidden buffer changes, but the
281 ;; generated functions will. (They are however used in places
282 ;; covered by the font-lock context.)
292 nil)))))
293 res))))
296 ;; Return a lisp form which will fontify every occurrence of REGEXP
297 ;; (a regular expression, NOT a function) between POINT and `limit'
298 ;; with HIGHLIGHTS, a list of highlighters as specified on page
299 ;; "Search-based Fontification" in the elisp manual.
308 ;; e.g. highlight is (1 font-lock-type-face t)
312 "The override flag must currently be t in %s"
313 highlight))
316 "The laxmatch flag may currently not be set in %s"
317 highlight))
323 ;; highlight is an "ANCHORED HIGHLIGHTER" of the form
324 ;; (ANCHORED-MATCHER PRE-FORM POST-FORM SUBEXP-HIGHLIGHTERS...)
327 highlight))
332 highlights))))
335 ;; This function makes a byte compiled function that works much like
336 ;; a matcher element in `font-lock-keywords'. It cuts out a little
337 ;; bit of the overhead compared to a real matcher. The main reason
338 ;; is however to pass the real search limit to the anchored
339 ;; matcher(s), since most (if not all) font-lock implementations
340 ;; arbitrarily limit anchored matchers to the same line, and also
341 ;; to insulate against various other irritating differences between
342 ;; the different (X)Emacs font-lock packages.
343 ;;
344 ;; REGEXP is the matcher, which must be a regexp. Only matches
345 ;; where the beginning is outside any comment or string literal are
346 ;; significant.
347 ;;
348 ;; HIGHLIGHTS is a list of highlight specs, just like in
349 ;; `font-lock-keywords', with these limitations: The face is always
350 ;; overridden (no big disadvantage, since hits in comments etc are
351 ;; filtered anyway), there is no "laxmatch", and an anchored matcher
352 ;; is always a form which must do all the fontification directly.
353 ;; `limit' is a variable bound to the real limit in the context of
354 ;; the anchored matcher forms.
355 ;;
356 ;; This function does not do any hidden buffer changes, but the
357 ;; generated functions will. (They are however used in places
358 ;; covered by the font-lock context.)
360 ;; Note: Replace `byte-compile' with `eval' to debug the generated
361 ;; lambda more easily.
365 ;; `parse-sexp-lookup-properties' (when it exists).
370 ;; (while (re-search-forward ,regexp limit t)
371 ;; (unless (progn
372 ;; (goto-char (match-beginning 0))
373 ;; (c-skip-comments-and-strings limit))
374 ;; (goto-char (match-end 0))
375 ;; ,@(mapcar
376 ;; (lambda (highlight)
377 ;; (if (integerp (car highlight))
378 ;; (progn
379 ;; (unless (eq (nth 2 highlight) t)
380 ;; (error
381 ;; "The override flag must currently be t in %s"
382 ;; highlight))
383 ;; (when (nth 3 highlight)
384 ;; (error
385 ;; "The laxmatch flag may currently not be set in %s"
386 ;; highlight))
387 ;; `(save-match-data
388 ;; (c-put-font-lock-face
389 ;; (match-beginning ,(car highlight))
390 ;; (match-end ,(car highlight))
391 ;; ,(elt highlight 1))))
392 ;; (when (nth 3 highlight)
393 ;; (error "Match highlights currently not supported in %s"
394 ;; highlight))
395 ;; `(progn
396 ;; ,(nth 1 highlight)
397 ;; (save-match-data ,(car highlight))
398 ;; ,(nth 2 highlight))))
399 ;; highlights)))
402 nil)))
405 ;; This function makes a byte compiled function that first moves back
406 ;; to the beginning of the current declaration (if any), then searches
407 ;; forward for matcher elements (as in `font-lock-keywords') and
408 ;; fontifies them.
409 ;;
410 ;; The motivation for moving back to the declaration start is to
411 ;; establish a context for the current text when, e.g., a character
412 ;; is typed on a C++ inheritance continuation line, or a jit-lock
413 ;; chunk starts there.
414 ;;
415 ;; The new function works much like a matcher element in
416 ;; `font-lock-keywords'. It cuts out a little bit of the overhead
417 ;; compared to a real matcher. The main reason is however to pass the
418 ;; real search limit to the anchored matcher(s), since most (if not
419 ;; all) font-lock implementations arbitrarily limit anchored matchers
420 ;; to the same line, and also to insulate against various other
421 ;; irritating differences between the different (X)Emacs font-lock
422 ;; packages.
423 ;;
424 ;; REGEXP is the matcher, which must be a regexp. Only matches
425 ;; where the beginning is outside any comment or string literal are
426 ;; significant.
427 ;;
428 ;; HIGHLIGHTS is a list of highlight specs, just like in
429 ;; `font-lock-keywords', with these limitations: The face is always
430 ;; overridden (no big disadvantage, since hits in comments etc are
431 ;; filtered anyway), there is no "laxmatch", and an anchored matcher
432 ;; is always a form which must do all the fontification directly.
433 ;; `limit' is a variable bound to the real limit in the context of
434 ;; the anchored matcher forms.
435 ;;
436 ;; This function does not do any hidden buffer changes, but the
437 ;; generated functions will. (They are however used in places
438 ;; covered by the font-lock context.)
440 ;; Note: Replace `byte-compile' with `eval' to debug the generated
441 ;; lambda more easily.
445 ;; `parse-sexp-lookup-properties' (when it exists).
455 here)))
457 nil)))
460 ;; This function makes a byte compiled function that works much like
461 ;; a matcher element in `font-lock-keywords', with the following
462 ;; enhancement: the generated function will test for particular "font
463 ;; lock contexts" at the start of the region, i.e. is this point in
464 ;; the middle of some particular construct? if so the generated
465 ;; function will first fontify the tail of the construct, before
466 ;; going into the main loop and fontify full constructs up to limit.
467 ;;
468 ;; The generated function takes one parameter called `limit', and
469 ;; will fontify the region between POINT and LIMIT.
470 ;;
471 ;; NORMAL is a list of the form (REGEXP HIGHLIGHTS .....), and is
472 ;; used to fontify the "regular" bit of the region.
473 ;; STATE-STANZAS is list of elements of the form (STATE LIM REGEXP
474 ;; HIGHLIGHTS), each element coding one possible font lock context.
476 ;; o - REGEXP is a font-lock regular expression (NOT a function),
477 ;; o - HIGHLIGHTS is a list of zero or more highlighters as defined
478 ;; on page "Search-based Fontification" in the elisp manual. As
479 ;; yet (2009-06), they must have OVERRIDE set, and may not have
480 ;; LAXMATCH set.
481 ;;
482 ;; o - STATE is the "font lock context" (e.g. in-cpp-expr) and is
483 ;; not quoted.
484 ;; o - LIM is a lisp form whose evaluation will yield the limit
485 ;; position in the buffer for fontification by this stanza.
486 ;;
487 ;; This function does not do any hidden buffer changes, but the
488 ;; generated functions will. (They are however used in places
489 ;; covered by the font-lock context.)
490 ;;
491 ;; Note: Replace `byte-compile' with `eval' to debug the generated
492 ;; lambda more easily.
496 ;; `parse-sexp-lookup-properties' (when it exists).
509 regexp highlights)))))
510 state-stanzas)
512 nil))))
514 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
515 ; '(progn
518 ;; If there are literal quoted or backquoted highlight specs in
519 ;; the call to `c-make-font-lock-search-function' then let's
520 ;; instrument the forms in them.
525 ;; Convert the ranges recorded on `c-record-type-identifiers' and
526 ;; `c-record-ref-identifiers' to fontification.
527 ;;
528 ;; This function does hidden buffer changes.
538 ;; Note that the reference face is a variable that is
539 ;; dereferenced, since it's an alias in Emacs.
541 c-reference-face-name))))
544 "Font lock matchers for preprocessor directives and purely lexical
545 stuff. Used on level 1 and higher."
547 ;; Note: `c-font-lock-declarations' assumes that no matcher here
548 ;; sets `font-lock-type-face' in languages where
549 ;; `c-recognize-<>-arglists' is set.
558 ;; fontify it as a string.
565 re
569 ;; Fontify filenames in #include <...> as strings.
576 re
580 font-lock-string-face)
582 ;; Use an anchored matcher to put paren syntax
583 ;; on the brackets.
594 ;; (c-clear-char-property beg 'syntax-table)
596 nil)))))))
598 ;; #define.
602 noncontinued-line-end
609 ;; Macro with arguments - a "function".
612 ;; Macro without arguments - a "variable".
619 ;; "Function". Fontify the name and the arguments.
644 ;; "Variable".
650 ;; Fontify cpp function names in preprocessor
651 ;; expressions in #if and #elif.
662 ced-re ; 1 + ncle-depth
663 ;; Match the whole logical line to look
664 ;; for the functions in.
670 c-preprocessor-face-name)))
674 ,cef-re
677 ;; Fontify the directive names.
691 c-negation-char-face-name
693 )))
696 ;; Recognize hashbangs in Pike.
700 ;; Make hard spaces visible through an inverted `font-lock-warning-face'.
708 ))
711 ;; Assuming the point is after the opening character of a string,
712 ;; fontify that char with `font-lock-warning-face' if the string
713 ;; decidedly isn't terminated properly.
714 ;;
715 ;; This function does hidden buffer changes.
720 ;; There's no multiline string start char before the
721 ;; string, so newlines aren't allowed.
723 ;; Multiline strings are allowed anywhere if
724 ;; c-multiline-string-start-char is t.
727 ;; There's no \ before the newline.
729 ;; Escaped newlines aren't supported.
730 t)
734 "Font lock matchers for basic keywords, labels, references and various
735 other easily recognizable things that should be fontified before generic
736 casts and declarations are fontified. Used on level 2 and higher."
738 ;; Note: `c-font-lock-declarations' assumes that no matcher here
739 ;; sets `font-lock-type-face' in languages where
740 ;; `c-recognize-<>-arglists' is set.
743 ;; can't span lines. Later font
744 ;; lock packages have a `font-lock-syntactic-face-function' for
745 ;; this, but it doesn't give the control we want since any
746 ;; fontification done inside the function will be
747 ;; unconditionally overridden.
749 ;; Match a char before the string starter to make
750 ;; `c-skip-comments-and-strings' work correctly.
754 ;; Fontify keyword constants.
758 ;; No symbol is a keyword after "->" in Pike.
765 ;; Fontify all keywords except the primitive types.
767 ;; No symbol is a keyword after "->" in Pike.
774 ;; Fontify leading identifiers in fully qualified names like
775 ;; "foo::bar" in languages that supports such things.
778 ;; Java needs special treatment since "." is used both to
779 ;; qualify names and in normal indexing. Here we look for
780 ;; capital characters at the beginning of an identifier to
781 ;; recognize the class. "*" is also recognized to cover
782 ;; wildcard import declarations. All preceding dot separated
783 ;; identifiers are taken as package names and therefore
784 ;; fontified as references.
786 ;; Search for class identifiers preceded by ".". The
787 ;; anchored matcher takes it from there.
807 c-reference-face-name)
809 nil
813 ;; Must use a function here since we match longer than
814 ;; we want to move before doing a new search. This is
815 ;; not necessary for XEmacs since it restarts the
816 ;; search from the end of the first highlighted
817 ;; submatch (something that causes problems in other
818 ;; places).
830 limit t)
837 c-reference-face-name))
840 ;; Fontify the special declarations in Objective-C.
848 ;; In this case we accept both primitive and known types.
855 ;; The @interface/@implementation/@protocol directives.
860 t)
864 ;; `parse-sexp-lookup-properties' (when it exists).
869 nil)
873 ))
876 ;; This function will be called from font-lock for a region bounded by POINT
877 ;; and LIMIT, as though it were to identify a keyword for
878 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
879 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
880 ;; Fontification".
881 ;;
882 ;; Called before any of the matchers in `c-complex-decl-matchers'.
883 ;;
884 ;; This function does hidden buffer changes.
886 ;;(message "c-font-lock-complex-decl-prepare %s %s" (point) limit)
888 ;; Clear the list of found types if we start from the start of the
889 ;; buffer, to make it easier to get rid of misspelled types and
890 ;; variables that have gotten recognized as types in malformed code.
894 ;; Clear the c-type char properties which mark the region, to recalculate
895 ;; them properly. The most interesting properties are those put on the
896 ;; closest token before the region.
904 c-decl-end
905 c-decl-id-start
906 c-decl-type-start)))
908 pos)
911 ;; Update `c-state-cache' to the beginning of the region. This will
912 ;; make `c-beginning-of-syntax' go faster when it's used later on,
913 ;; and it's near the point most of the time.
916 ;; Check if the fontified region starts inside a declarator list so
917 ;; that `c-font-lock-declarators' should be called at the start.
918 ;; The declared identifiers are font-locked correctly as types, if
919 ;; that is what they are.
934 nil)
937 ;; This function will be called from font-lock for a region bounded by POINT
938 ;; and LIMIT, as though it were to identify a keyword for
939 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
940 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
941 ;; Fontification".
942 ;;
943 ;; Fontify types and references in names containing angle bracket
944 ;; arglists from the point to LIMIT. Note that
945 ;; `c-font-lock-declarations' already has handled many of them.
946 ;;
947 ;; This function might do hidden buffer changes.
950 ;; `parse-sexp-lookup-properties' (when it exists).
955 c-restricted-<>-arglists
956 id-start id-end id-face pos kwd-sym)
968 c-restricted-<>-arglists nil
973 ;; The identifier got the type face so it has already been
974 ;; handled in `c-font-lock-declarations'.
975 nil)
979 ;; There's a special keyword before the "<" that tells
980 ;; that it's an angle bracket arglist.
984 ;; There's a normal identifier before the "<". If we're not in
985 ;; a declaration context then we set `c-restricted-<>-arglists'
986 ;; to avoid recognizing templates in function calls like "foo (a
987 ;; < b, c > d)".
993 t))
997 ;; Check for comment/string both at the identifier and
998 ;; at the "<".
1009 c-reference-face-name)
1015 nil)
1018 ;; Assuming the point is at the start of a declarator in a declaration,
1019 ;; fontify the identifier it declares. (If TYPES is set, it does this via
1020 ;; the macro `c-fontify-types-and-refs'.)
1021 ;;
1022 ;; If LIST is non-nil, also fontify the ids in any following declarators in
1023 ;; a comma separated list (e.g. "foo" and "*bar" in "int foo = 17, *bar;");
1024 ;; additionally, mark the commas with c-type property 'c-decl-id-start or
1025 ;; 'c-decl-type-start (according to TYPES). Stop at LIMIT.
1026 ;;
1027 ;; If TYPES is non-nil, fontify all identifiers as types.
1028 ;;
1029 ;; Nil is always returned. The function leaves point at the delimiter after
1030 ;; the last declarator it processes.
1031 ;;
1032 ;; This function might do hidden buffer changes.
1034 ;;(message "c-font-lock-declarators from %s to %s" (point) limit)
1037 paren-depth
1038 id-face got-init
1039 c-last-identifier-range
1042 ;; The following `while' fontifies a single declarator id each time round.
1043 ;; It loops only when LIST is non-nil.
1045 ;; Inside the following "condition form", we move forward over the
1046 ;; declarator's identifier up as far as any opening bracket (for array
1047 ;; size) or paren (for parameters of function-type) or brace (for
1048 ;; array/struct initialization) or "=" or terminating delimiter
1049 ;; (e.g. "," or ";" or "}").
1051 pos
1054 ;; The following form moves forward over the declarator's
1055 ;; identifier (and what precedes it), returning t. If there
1056 ;; wasn't one, it returns nil, terminating the `while'.
1059 ;; Skip over type decl prefix operators, one for each iteration
1060 ;; of the while. These are, e.g. "*" in "int *foo" or "(" and
1061 ;; "*" in "int (*foo) (void)" (Note similar code in
1062 ;; `c-forward-decl-or-cast-1'.)
1066 ;; If the third submatch matches in C++ then
1067 ;; we're looking at an identifier that's a
1068 ;; prefix only if it specifies a member pointer.
1073 ;; We only check for a trailing "::" and
1074 ;; let the "*" that should follow be
1075 ;; matched in the next round.
1076 t
1077 ;; It turned out to be the real identifier,
1078 ;; so flag that and stop.
1080 nil))
1081 t))
1089 ;; If we haven't passed the identifier already, do it now.
1097 ;; Skip out of the parens surrounding the identifier. If closing
1098 ;; parens are missing, this form returns nil.
1104 ;; Skip over any trailing bit, such as "__attribute__".
1110 ;; Search syntactically to the end of the declarator (";",
1111 ;; ",", a closing paren, eob etc) or to the beginning of an
1112 ;; initializer or function prototype ("=" or "\\s\(").
1113 ;; Note that the open paren will match array specs in
1114 ;; square brackets, and we treat them as initializers too.
1124 'font-lock-function-name-face
1130 ;; Register and fontify the identifier as a type.
1134 ;; Fontify the last symbol in the identifier if it isn't fontified
1135 ;; already. The check is necessary only in certain cases where this
1136 ;; function is used "sloppily", e.g. in `c-simple-decl-matchers'.
1142 id-face)))
1147 ;; Jump past any initializer or function prototype to see if
1148 ;; there's a ',' to continue at.
1151 ;; Skip a parenthesized initializer (C++) or a function
1152 ;; prototype.
1158 ;; Skip an initializer expression. If we're at a '='
1159 ;; then accept a brace list directly after it to cope
1160 ;; with array initializers. Otherwise stop at braces
1161 ;; to avoid going past full function and class blocks.
1166 t)
1167 ;; FIXME: Should look for c-decl-end markers here;
1168 ;; we might go far into the following declarations
1169 ;; in e.g. ObjC mode (see e.g. methods-4.m).
1175 ;; If a ',' is found we set pos to the next declarator and iterate.
1181 nil)
1184 ;; List of faces that might be put at the start of a type when
1185 ;; `c-font-lock-declarations' runs. This needs to be evaluated to
1186 ;; ensure that face name aliases in Emacs are resolved.
1188 font-lock-type-face
1189 c-reference-face-name
1190 font-lock-keyword-face))
1193 ;; Fontify all the declarations, casts and labels from the point to LIMIT.
1194 ;; Assumes that strings and comments have been fontified already.
1195 ;;
1196 ;; This function will be called from font-lock for a region bounded by POINT
1197 ;; and LIMIT, as though it were to identify a keyword for
1198 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1199 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1200 ;; Fontification".
1201 ;;
1202 ;; This function might do hidden buffer changes.
1204 ;;(message "c-font-lock-declarations search from %s to %s" (point) limit)
1208 start-pos
1209 ;; o - 'decl if we're in an arglist containing declarations
1210 ;; (but if `c-recognize-paren-inits' is set it might also be
1211 ;; an initializer arglist);
1212 ;; o - '<> if the arglist is of angle bracket type;
1213 ;; o - 'arglist if it's some other arglist;
1214 ;; o - nil, if not in an arglist at all. This includes the
1215 ;; parenthesized condition which follows "if", "while", etc.
1216 context
1217 ;; The position of the next token after the closing paren of
1218 ;; the last detected cast.
1219 last-cast-end
1220 ;; The result from `c-forward-decl-or-cast-1'.
1221 decl-or-cast
1222 ;; The maximum of the end positions of all the checked type
1223 ;; decl expressions in the successfully identified
1224 ;; declarations. The position might be either before or
1225 ;; after the syntactic whitespace following the last token
1226 ;; in the type decl expression.
1228 ;; Same as `max-type-decl-*', but used when we're before
1229 ;; `token-pos'.
1231 ;; Set according to the context to direct the heuristics for
1232 ;; recognizing C++ templates.
1233 c-restricted-<>-arglists
1234 ;; Turn on recording of identifier ranges in
1235 ;; `c-forward-decl-or-cast-1' and `c-forward-label' for
1236 ;; later fontification.
1238 label-type
1239 c-record-ref-identifiers
1240 ;; Make `c-forward-type' calls mark up template arglists if
1241 ;; it finds any. That's necessary so that we later will
1242 ;; stop inside them to fontify types there.
1244 lbrace ; position of some {.
1245 ;; The font-lock package in Emacs is known to clobber
1246 ;; `parse-sexp-lookup-properties' (when it exists).
1251 ;; Below we fontify a whole declaration even when it crosses the limit,
1252 ;; to avoid gaps when jit/lazy-lock fontifies the file a block at a
1253 ;; time. That is however annoying during editing, e.g. the following is
1254 ;; a common situation while the first line is being written:
1255 ;;
1256 ;; my_variable
1257 ;; some_other_variable = 0;
1258 ;;
1259 ;; font-lock will put the limit at the beginning of the second line
1260 ;; here, and if we go past it we'll fontify "my_variable" as a type and
1261 ;; "some_other_variable" as an identifier, and the latter will not
1262 ;; correct itself until the second line is changed. To avoid that we
1263 ;; narrow to the limit if the region to fontify is a single line.
1268 ;; Narrow after any operator chars following the limit though,
1269 ;; since those characters can be useful in recognizing a
1270 ;; declaration (in particular the '{' that opens a function body
1271 ;; after the header).
1277 limit
1278 c-decl-start-re
1279 c-font-lock-maybe-decl-faces
1284 ;; The result of the form below is true when we don't recognize a
1285 ;; declaration or cast.
1291 ;; Don't do anything more if we're looking at a keyword that
1292 ;; can't start a declaration.
1293 t
1295 ;; Set `context' and `c-restricted-<>-arglists'. Look for
1296 ;; "<" for the sake of C++-style template arglists.
1297 ;; Ignore "(" when it's part of a control flow construct
1298 ;; (e.g. "for (").
1304 ;; A control flow expression
1314 ;; Near BOB.
1318 ;; Got a cached hit in a declaration arglist.
1322 ;; Inside an angle bracket arglist.
1327 ;; Got a cached hit in some other type of arglist.
1334 ;; The point is within the range of a previously
1335 ;; encountered type decl expression, so the arglist
1336 ;; is probably one that contains declarations.
1337 ;; However, if `c-recognize-paren-inits' is set it
1338 ;; might also be an initializer arglist.
1341 ;; The result of this check is cached with a char
1342 ;; property on the match token, so that we can look
1343 ;; it up again when refontifying single lines in a
1344 ;; multiline declaration.
1350 ;; Check we haven't missed a preceding "typedef".
1357 ;; In QT, "more" is an irritating keyword that expands to nothing.
1358 ;; We skip over it to prevent recognition of "more slots: <symbol>"
1359 ;; as a bitfield declaration.
1366 ;; Now analyze the construct.
1368 match-pos context last-cast-end))
1372 ;; Save the position after the previous cast so we can feed
1373 ;; it to `c-forward-decl-or-cast-1' in the next round. That
1374 ;; helps it discover cast chains like "(a) (b) c".
1377 nil)
1380 ;; We've found a declaration.
1382 ;; Set `max-type-decl-end' or `max-type-decl-end-before-token'
1383 ;; under the assumption that we're after the first type decl
1384 ;; expression in the declaration now. That's not really true;
1385 ;; we could also be after a parenthesized initializer
1386 ;; expression in C++, but this is only used as a last resort
1387 ;; to slant ambiguous expression/declarations, and overall
1388 ;; it's worth the risk to occasionally fontify an expression
1389 ;; as a declaration in an initializer expression compared to
1390 ;; getting ambiguous things in normal function prototypes
1391 ;; fontified as expressions.
1398 ;; Back up to the type to fontify the declarator(s).
1403 ;; Should normally not fontify a list of
1404 ;; declarators inside an arglist, but the first
1405 ;; argument in the ';' separated list of a "for"
1406 ;; statement is an exception.
1413 t)))
1415 ;; Fix the `c-decl-id-start' or `c-decl-type-start' property
1416 ;; before the first declarator if it's a list.
1417 ;; `c-font-lock-declarators' handles the rest.
1424 'c-decl-type-start
1430 ;; A declaration has been successfully identified, so do all the
1431 ;; fontification of types and refs that've been recorded.
1433 nil)
1435 ;; Restore point, since at this point in the code it has been
1436 ;; left undefined by c-forward-decl-or-cast-1 above.
1439 ;; If point is inside a bracelist, there's no point checking it
1440 ;; being at a declarator.
1443 ;; Move past this bracelist to prevent an endless loop.
1448 nil)
1450 ;; If point is just after a ")" which is followed by an
1451 ;; identifier which isn't a label, or at the matching "(", we're
1452 ;; at either a macro invocation, a cast, or a
1453 ;; for/while/etc. statement. The cast case is handled above.
1454 ;; None of these cases can contain a declarator.
1466 nil)
1469 ;; An optimization quickly to eliminate scans of long enum
1470 ;; declarations in the next cond arm.
1486 t)
1491 nil)
1494 ;; Are we at a declarator? Try to go back to the declaration
1495 ;; to check this. If we get there, check whether a "typedef"
1496 ;; is there, then fontify the declarators accordingly.
1498 paren-state bod-res encl-pos is-typedef
1500 ; speeds up lisp.h tremendously.
1509 ;; We're now putatively at the declaration.
1511 ;; At top level or inside a "{"?
1520 ;; At a real declaration?
1524 nil)
1525 ;; False alarm. Return t to go on to the next check.
1527 t))
1528 t))))))
1530 ;; It was a false alarm. Check if we're in a label (or other
1531 ;; construct with `:' except bitfield) instead.
1534 ;; Can't use `c-fontify-types-and-refs' here since we
1535 ;; use the label face at times.
1539 c-label-face-name))
1549 c-record-ref-identifiers)))
1551 ;; `c-forward-label' has probably added a `c-decl-end'
1552 ;; marker, so return t to `c-find-decl-spots' to signal
1553 ;; that.
1554 t))))
1556 nil)))
1559 ;; Fontify an enum's identifiers when POINT is within the enum's brace
1560 ;; block.
1561 ;;
1562 ;; This function will be called from font-lock for a region bounded by POINT
1563 ;; and LIMIT, as though it were to identify a keyword for
1564 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1565 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1566 ;; Fontification".
1567 ;;
1568 ;; Note that this function won't attempt to fontify beyond the end of the
1569 ;; current enum block, if any.
1573 )
1575 encl-pos
1589 t)
1598 nil)
1601 ;; Fontify the declarators of (nested) declarations we're in the middle of.
1602 ;; This is mainly for when a jit-lock etc. chunk starts inside the brace
1603 ;; block of a struct/union/class, etc.
1604 ;;
1605 ;; This function will be called from font-lock for a region bounded by POINT
1606 ;; and LIMIT, as though it were to identify a keyword for
1607 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1608 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1609 ;; Fontification".
1612 decl-context in-typedef ps-elt)
1613 ;; Are we in any nested struct/union/class/etc. braces?
1631 "Simple font lock matchers for types and declarations. These are used
1632 on level 2 only and so aren't combined with `c-complex-decl-matchers'."
1640 ;; `parse-sexp-lookup-properties' (when it exists).
1647 nil))
1650 ;; Fontify all type names and the identifiers in the
1651 ;; declarations they might start. Use eval here since
1652 ;; `c-known-type-key' gets its value from
1653 ;; `*-font-lock-extra-types' on mode init.
1655 'c-known-type-key
1663 ;; Fontify types preceded by `c-type-prefix-kwds' and the
1664 ;; identifiers in the declarations they might start.
1677 `(,type-match
1685 ;; Fontify special declarations that lacks a type.
1697 ;; Fontify generic colon labels in languages that support them.
1702 "Complex font lock matchers for types and declarations. Used on level
1703 3 and higher."
1705 ;; Note: This code in this form dumps a number of functions into the
1706 ;; resulting constant, `c-matchers-3'. At run time, font lock will call
1707 ;; each of them as a "FUNCTION" (see Elisp page "Search-based
1708 ;; Fontification"). The font lock region is delimited by POINT and the
1709 ;; single parameter, LIMIT. Each of these functions returns NIL (thus
1710 ;; inhibiting spurious font-lock-keyword-face highlighting and another
1711 ;; call).
1714 c-font-lock-complex-decl-prepare
1717 ;; Fontify method declarations in Objective-C, but first
1718 ;; we have to put the `c-decl-end' `c-type' property on
1719 ;; all the @-style directives that haven't been handled in
1720 ;; `c-basic-matchers-before'.
1723 ;; Exclude "@class" since that directive ends with a
1724 ;; semicolon anyway.
1728 nil)))
1731 c-font-lock-objc-methods))
1733 ;; Fontify all declarations, casts and normal labels.
1734 c-font-lock-declarations
1736 ;; Fontify declarators when POINT is within their declaration.
1737 c-font-lock-enclosing-decls
1739 ;; Fontify angle bracket arglists like templates in C++.
1743 ;; The first two rules here mostly find occurrences that
1744 ;; `c-font-lock-declarations' has found already, but not
1745 ;; declarations containing blocks in the type (see note below).
1746 ;; It's also useful to fontify these everywhere to show e.g. when
1747 ;; a type keyword is accidentally used as an identifier.
1749 ;; Fontify basic types.
1753 ;; No symbol is a keyword after "->" in Pike.
1760 ;; Fontify types preceded by `c-type-prefix-kwds' (e.g. "struct").
1766 ;; The font-lock package in Emacs is known to clobber
1767 ;; `parse-sexp-lookup-properties' (when it exists).
1772 ;; Narrow to avoid going past the limit in
1773 ;; `c-forward-type'.
1780 limit t)
1783 ;; Handle prefix declaration specifiers.
1791 ;; In C++ we additionally check for a "class
1792 ;; X = Y" construct which is used in
1793 ;; templates, to fontify Y as a type.
1798 )))))))))
1800 ;; Fontify symbols after closing braces as declaration
1801 ;; identifiers under the assumption that they are part of
1802 ;; declarations like "class Foo { ... } foo;". It's too
1803 ;; expensive to check this accurately by skipping past the
1804 ;; brace block, so we use the heuristic that it's such a
1805 ;; declaration if the first identifier is on the same line as
1806 ;; the closing brace. `c-font-lock-declarations' will later
1807 ;; override it if it turns out to be an new declaration, but
1808 ;; it will be wrong if it's an expression (see the test
1809 ;; decls-8.cc).
1810 ;; ,@(when (c-lang-const c-opt-block-decls-with-vars-key)
1811 ;; `((,(c-make-font-lock-search-function
1812 ;; (concat "}"
1813 ;; (c-lang-const c-single-line-syntactic-ws)
1814 ;; "\\(" ; 1 + c-single-line-syntactic-ws-depth
1815 ;; (c-lang-const c-type-decl-prefix-key)
1816 ;; "\\|"
1817 ;; (c-lang-const c-symbol-key)
1818 ;; "\\)")
1819 ;; `((c-font-lock-declarators limit t nil) ; That `nil' says use `font-lock-variable-name-face';
1820 ;; ; `t' would mean `font-lock-function-name-face'.
1821 ;; (progn
1822 ;; (c-put-char-property (match-beginning 0) 'c-type
1823 ;; 'c-decl-id-start)
1824 ;; ; 'c-decl-type-start)
1825 ;; (goto-char (match-beginning
1826 ;; ,(1+ (c-lang-const
1827 ;; c-single-line-syntactic-ws-depth)))))
1828 ;; (goto-char (match-end 0)))))))
1830 ;; Fontify the type in C++ "new" expressions.
1832 ;; This pattern is a probably a "(MATCHER . ANCHORED-HIGHLIGHTER)"
1833 ;; (see Elisp page "Search-based Fontification").
1836 ))
1839 ;; Fontify all statement labels from the point to LIMIT. Assumes
1840 ;; that strings and comments have been fontified already. Nil is
1841 ;; always returned.
1842 ;;
1843 ;; Note: This function is only used on decoration level 2; this is
1844 ;; taken care of directly by the gargantuan
1845 ;; `c-font-lock-declarations' on higher levels.
1846 ;;
1847 ;; This function might do hidden buffer changes.
1850 ;; The font-lock package in Emacs is known to clobber
1851 ;; `parse-sexp-lookup-properties' (when it exists).
1870 ;; Check for a char that precedes a statement.
1872 ;; Check for a preceding label. We exploit the font
1873 ;; locking made earlier by this function.
1880 c-label-face-name))
1881 ;; Check for a keyword that precedes a statement.
1885 ;; Got a label.
1889 c-label-face-name)))
1892 nil)
1895 "Font lock matchers for various things that should be fontified after
1896 generic casts and declarations are fontified. Used on level 2 and
1897 higher."
1900 ;; Fontify the remaining identifiers inside an enum list when we start
1901 ;; inside it.
1903 ;; Fontify the identifiers inside enum lists. (The enum type
1904 ;; name is handled by `c-simple-decl-matchers' or
1905 ;; `c-complex-decl-matchers' below.
1911 ;; Disallow various common punctuation chars that can't come
1912 ;; before the '{' of the enum list, to avoid searching too far.
1913 "[^\]\[{}();,/#=]*"
1923 ;; Fontify labels after goto etc.
1926 ;; which makes it a bit complicated: 1) The backquote
1927 ;; stuff is expanded when compiled or loaded, 2) the
1928 ;; eval form is evaluated at font-lock setup (to
1929 ;; substitute c-label-face-name correctly), and 3) the
1930 ;; resulting structure is interpreted during
1931 ;; fontification.)
1943 c-label-face-name nil t))))))
1945 ;; Fontify the clauses after various keywords.
1972 ))
1990 ;; Incorporate the font lock keyword lists according to
1991 ;; `c-doc-comment-style' on the given keyword list and return it.
1992 ;; This is used in the function bindings of the
1993 ;; `*-font-lock-keywords-*' symbols since we have to build the list
1994 ;; when font-lock is initialized.
2003 c-doc-comment-style))
2015 doc-keywords
2017 base-list)))
2019 ;; Kludge: If `c-font-lock-complex-decl-prepare' is on the list we
2020 ;; move it first since the doc comment font lockers might add
2021 ;; `c-type' text properties, so they have to be cleared before that.
2027 list))
2030 ;; This is used to override the value on a `*-font-lock-keywords'
2031 ;; variable only if it's nil or has the same value as one of the
2032 ;; `*-font-lock-keywords-*' variables. Older font-lock packages
2033 ;; define a default value for `*-font-lock-keywords' which we want
2034 ;; to override, but we should otoh avoid clobbering a user setting.
2035 ;; This heuristic for that isn't perfect, but I can't think of any
2036 ;; better. /mast
2043 suffix))))
2046 ;; The overriding is done by unbinding the variable so that the normal
2047 ;; defvar will install its default value later on.
2050 \f
2051 ;;; C.
2056 "Minimal font locking for C mode.
2057 Fontifies only preprocessor directives (in addition to the syntactic
2061 "Fast normal font locking for C mode.
2062 In addition to `c-font-lock-keywords-1', this adds fontification of
2063 keywords, simple types, declarations that are easy to recognize, the
2064 user defined types on `c-font-lock-extra-types', and the doc comment
2068 "Accurate normal font locking for C mode.
2069 Like the variable `c-font-lock-keywords-2' but detects declarations in a more
2070 accurate way that works in most cases for arbitrary types without the
2083 \f
2084 ;;; C++.
2087 ;; FIXME!!! Put in a comment about the context of this function's
2088 ;; invocation. I think it's called as an ANCHORED-MATCHER within an
2089 ;; ANCHORED-HIGHLIGHTER. (2007/2/10).
2090 ;;
2091 ;; Assuming point is after a "new" word, check that it isn't inside
2092 ;; a string or comment, and if so try to fontify the type in the
2093 ;; allocation expression. Nil is always returned.
2094 ;;
2095 ;; As usual, C++ takes the prize in coming up with a hard to parse
2096 ;; syntax. :P
2097 ;;
2098 ;; This function might do hidden buffer changes.
2103 ;; A "new" keyword is followed by one to three expressions, where
2104 ;; the type is the middle one, and the only required part.
2106 ;; Enable recording of identifier ranges in `c-forward-type'
2107 ;; etc for later fontification. Not using
2108 ;; `c-fontify-types-and-refs' here since the ranges should
2109 ;; be fontified selectively only when an allocation
2110 ;; expression is successfully recognized.
2112 c-record-ref-identifiers
2113 ;; The font-lock package in Emacs is known to clobber
2114 ;; `parse-sexp-lookup-properties' (when it exists).
2120 ;; The first placement arglist is always parenthesized, if it
2121 ;; exists.
2129 ;; The second expression is either a type followed by some "*" or
2130 ;; "[...]" or similar, or a parenthesized type followed by a full
2131 ;; identifierless declarator.
2141 ;; No second expression, so the first has to be a
2142 ;; parenthesized type.
2148 ;; Got two parenthesized expressions, so we have to look
2149 ;; closer at them to decide which is the type. No need to
2150 ;; handle `c-record-ref-identifiers' since all references
2151 ;; has already been handled by other fontification rules.
2160 ;; There's something after the would-be type that
2161 ;; can't be there, so this is a placement arglist.
2170 ;; There's something after the would-be type that can't
2171 ;; be there, so this is an initialization expression.
2176 ;; If there's a third initialization expression
2177 ;; then the second one is the type, so demote the
2178 ;; first match.
2181 ;; We fontify the most likely type, with a preference for
2182 ;; the first argument since a placement arglist is more
2183 ;; unusual than an initializer.
2202 ;; If both type matches are 'maybe then we're
2203 ;; too uncertain to promote either of them.
2204 )))))
2206 ;; Fontify the type that now is recorded in
2207 ;; `c-record-type-identifiers', if any.
2209 nil)
2214 "Minimal font locking for C++ mode.
2215 Fontifies only preprocessor directives (in addition to the syntactic
2219 "Fast normal font locking for C++ mode.
2220 In addition to `c++-font-lock-keywords-1', this adds fontification of
2221 keywords, simple types, declarations that are easy to recognize, the
2222 user defined types on `c++-font-lock-extra-types', and the doc comment
2226 "Accurate normal font locking for C++ mode.
2227 Like the variable `c++-font-lock-keywords-2' but detects declarations in a more
2228 accurate way that works in most cases for arbitrary types without the
2241 \f
2242 ;;; Objective-C.
2245 ;; Assuming the point is after the + or - that starts an Objective-C
2246 ;; method declaration, fontify it. This must be done before normal
2247 ;; casts, declarations and labels are fontified since they will get
2248 ;; false matches in these things.
2249 ;;
2250 ;; This function might do hidden buffer changes.
2260 ;; An optional method type.
2268 t))
2270 ;; The name. The first time it's the first part of
2271 ;; the function name, the rest of the time it's an
2272 ;; argument name.
2279 'font-lock-function-name-face
2283 ;; Another optional part of the function name.
2291 ;; There's another argument if a colon follows.
2297 ;; Fontify method declarations in Objective-C. Nil is always
2298 ;; returned.
2299 ;;
2300 ;; This function might do hidden buffer changes.
2303 ;; `parse-sexp-lookup-properties' (when it exists).
2309 limit
2310 "[-+]"
2311 nil
2315 nil)
2320 "Minimal font locking for Objective-C mode.
2321 Fontifies only compiler directives (in addition to the syntactic
2325 "Fast normal font locking for Objective-C mode.
2326 In addition to `objc-font-lock-keywords-1', this adds fontification of
2327 keywords, simple types, declarations that are easy to recognize, the
2328 user defined types on `objc-font-lock-extra-types', and the doc
2332 "Accurate normal font locking for Objective-C mode.
2333 Like the variable `objc-font-lock-keywords-2' but detects declarations in a more
2334 accurate way that works in most cases for arbitrary types without the
2347 ;; Kludge to override the default value that
2348 ;; `objc-font-lock-extra-types' might have gotten from the font-lock
2349 ;; package. The value replaced here isn't relevant now anyway since
2350 ;; those types are builtin and therefore listed directly in
2351 ;; `c-primitive-type-kwds'.
2357 \f
2358 ;;; Java.
2363 "Minimal font locking for Java mode.
2364 Fontifies nothing except the syntactic fontification of strings and
2368 "Fast normal font locking for Java mode.
2369 In addition to `java-font-lock-keywords-1', this adds fontification of
2370 keywords, simple types, declarations that are easy to recognize, the
2371 user defined types on `java-font-lock-extra-types', and the doc
2375 "Accurate normal font locking for Java mode.
2376 Like variable `java-font-lock-keywords-2' but detects declarations in a more
2377 accurate way that works in most cases for arbitrary types without the
2390 \f
2391 ;;; CORBA IDL.
2396 "Minimal font locking for CORBA IDL mode.
2397 Fontifies nothing except the syntactic fontification of strings and
2401 "Fast normal font locking for CORBA IDL mode.
2402 In addition to `idl-font-lock-keywords-1', this adds fontification of
2403 keywords, simple types, declarations that are easy to recognize, the
2404 user defined types on `idl-font-lock-extra-types', and the doc comment
2408 "Accurate normal font locking for CORBA IDL mode.
2409 Like the variable `idl-font-lock-keywords-2' but detects declarations in a more
2410 accurate way that works in most cases for arbitrary types without the
2423 \f
2424 ;;; Pike.
2429 "Minimal font locking for Pike mode.
2430 Fontifies only preprocessor directives (in addition to the syntactic
2434 "Fast normal font locking for Pike mode.
2435 In addition to `pike-font-lock-keywords-1', this adds fontification of
2436 keywords, simple types, declarations that are easy to recognize, the
2437 user defined types on `pike-font-lock-extra-types', and the doc
2441 "Accurate normal font locking for Pike mode.
2442 Like the variable `pike-font-lock-keywords-2' but detects declarations in a more
2443 accurate way that works in most cases for arbitrary types without the
2456 \f
2457 ;;; Doc comments.
2460 ;; Fontify the comments between the point and LIMIT whose start
2461 ;; matches PREFIX with `c-doc-face-name'. Assumes comments have been
2462 ;; fontified with `font-lock-comment-face' already. nil is always
2463 ;; returned.
2464 ;;
2465 ;; After the fontification of a matching comment, fontification
2466 ;; according to KEYWORDS is applied inside it. It's a list like
2467 ;; `font-lock-keywords' except that anchored matches and eval
2468 ;; clauses aren't supported and that some abbreviated forms can't be
2469 ;; used. The buffer is narrowed to the comment while KEYWORDS is
2470 ;; applied; leading comment starters are included but trailing
2471 ;; comment enders for block comment are not.
2472 ;;
2473 ;; Note that faces added through KEYWORDS should never replace the
2474 ;; existing `c-doc-face-name' face since the existence of that face
2475 ;; is used as a flag in other code to skip comments.
2476 ;;
2477 ;; This function might do hidden buffer changes.
2482 ;; Handle the case when the fontified region starts inside a
2483 ;; comment.
2492 comment-beg
2494 ;; Search for the prefix until a match is found at the start
2495 ;; of a comment.
2499 c-literal-faces))
2502 c-literal-faces))))
2507 ;; Collect a sequence of doc style line comments.
2524 ;; Narrow to the doc comment. Among other things, this
2525 ;; helps by making "^" match at the start of the comment.
2526 ;; Do not include a trailing block comment ender, though.
2550 nil)
2554 ;; Used to fontify invalid markup in doc comments after the correct
2555 ;; ones have been fontified: Find the first occurrence of REGEXP
2556 ;; between the point and LIMIT that only is fontified with
2557 ;; `c-doc-face-name'. If a match is found then submatch 0 surrounds
2558 ;; the first char and t is returned, otherwise nil is returned.
2559 ;;
2560 ;; This function might do hidden buffer changes.
2565 c-doc-face-name))
2570 t)))
2572 ;; GtkDoc patterns contributed by Masatake YAMATO <jet@gyve.org>.
2585 ))
2594 gtkdoc-font-lock-doc-comments)
2596 gtkdoc-font-lock-doc-protection)
2597 ))))
2599 ;; Javadoc.
2614 ;; Fontify remaining markup characters as invalid. Note
2615 ;; that the Javadoc spec is hazy about when "@" is
2616 ;; allowed in non-markup use.
2624 javadoc-font-lock-doc-comments)))))
2626 ;; Pike autodoc.
2629 ;; Adorned regexp matching the keywords that introduce declarations
2630 ;; in Pike Autodoc.
2635 ;; Adorned regexp matching the keywords that are followed by a type.
2640 ;; Fontify all line oriented keywords between the point and LIMIT.
2641 ;; Nil is always returned.
2642 ;;
2643 ;; This function might do hidden buffer changes.
2646 c-current-comment-prefix
2657 end)
2661 ;; Put a declaration end mark at the markup keyword and
2662 ;; remove the faces from the rest of the line so that it
2663 ;; gets refontified as a declaration later on by
2664 ;; `c-font-lock-declarations'.
2680 ;; Include the final newline in the removed area. This
2681 ;; has no visual effect but it avoids some tricky special
2682 ;; cases in the testsuite wrt the differences in string
2683 ;; fontification in Emacs vs XEmacs.
2686 ;; Must handle string literals explicitly inside the declaration.
2694 ;; Fontify types after keywords that always are followed
2695 ;; by them.
2703 ;; Mark each whole line as markup, as long as the logical line
2704 ;; continues.
2708 markup-faces)
2716 nil)
2720 ;; In-text markup.
2723 ;; Fontify remaining markup characters as invalid.
2727 ))
2730 ;; Note that we depend on that `c-current-comment-prefix' has got
2731 ;; its proper value here.
2732 ;;
2733 ;; This function might do hidden buffer changes.
2735 ;; The `c-type' text property with `c-decl-end' is used to mark the
2736 ;; end of the `autodoc-decl-keywords' occurrences to fontify the
2737 ;; following declarations.
2742 autodoc-font-lock-doc-comments)))))
2744 \f
2745 ;; 2006-07-10: awk-font-lock-keywords has been moved back to cc-awk.el.
2748 ;;; cc-fonts.el ends here