| blob | 9a1273ddcce09f9fbdac86d8309949ca0c8a419a |
1 ;;; cc-fonts.el --- font lock support for CC Mode
3 ;; Copyright (C) 2002-2015 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 nil)))
373 ;; This function makes a byte compiled function that first moves back
374 ;; to the beginning of the current declaration (if any), then searches
375 ;; forward for matcher elements (as in `font-lock-keywords') and
376 ;; fontifies them.
377 ;;
378 ;; The motivation for moving back to the declaration start is to
379 ;; establish a context for the current text when, e.g., a character
380 ;; is typed on a C++ inheritance continuation line, or a jit-lock
381 ;; chunk starts there.
382 ;;
383 ;; The new function works much like a matcher element in
384 ;; `font-lock-keywords'. It cuts out a little bit of the overhead
385 ;; compared to a real matcher. The main reason is however to pass the
386 ;; real search limit to the anchored matcher(s), since most (if not
387 ;; all) font-lock implementations arbitrarily limit anchored matchers
388 ;; to the same line, and also to insulate against various other
389 ;; irritating differences between the different (X)Emacs font-lock
390 ;; packages.
391 ;;
392 ;; REGEXP is the matcher, which must be a regexp. Only matches
393 ;; where the beginning is outside any comment or string literal are
394 ;; significant.
395 ;;
396 ;; HIGHLIGHTS is a list of highlight specs, just like in
397 ;; `font-lock-keywords', with these limitations: The face is always
398 ;; overridden (no big disadvantage, since hits in comments etc are
399 ;; filtered anyway), there is no "laxmatch", and an anchored matcher
400 ;; is always a form which must do all the fontification directly.
401 ;; `limit' is a variable bound to the real limit in the context of
402 ;; the anchored matcher forms.
403 ;;
404 ;; This function does not do any hidden buffer changes, but the
405 ;; generated functions will. (They are however used in places
406 ;; covered by the font-lock context.)
408 ;; Note: Replace `byte-compile' with `eval' to debug the generated
409 ;; lambda more easily.
413 ;; `parse-sexp-lookup-properties' (when it exists).
423 here)))
425 nil)))
428 ;; This function makes a byte compiled function that works much like
429 ;; a matcher element in `font-lock-keywords', with the following
430 ;; enhancement: the generated function will test for particular "font
431 ;; lock contexts" at the start of the region, i.e. is this point in
432 ;; the middle of some particular construct? if so the generated
433 ;; function will first fontify the tail of the construct, before
434 ;; going into the main loop and fontify full constructs up to limit.
435 ;;
436 ;; The generated function takes one parameter called `limit', and
437 ;; will fontify the region between POINT and LIMIT.
438 ;;
439 ;; NORMAL is a list of the form (REGEXP HIGHLIGHTS .....), and is
440 ;; used to fontify the "regular" bit of the region.
441 ;; STATE-STANZAS is list of elements of the form (STATE LIM REGEXP
442 ;; HIGHLIGHTS), each element coding one possible font lock context.
444 ;; o - REGEXP is a font-lock regular expression (NOT a function),
445 ;; o - HIGHLIGHTS is a list of zero or more highlighters as defined
446 ;; on page "Search-based Fontification" in the elisp manual. As
447 ;; yet (2009-06), they must have OVERRIDE set, and may not have
448 ;; LAXMATCH set.
449 ;;
450 ;; o - STATE is the "font lock context" (e.g. in-cpp-expr) and is
451 ;; not quoted.
452 ;; o - LIM is a lisp form whose evaluation will yield the limit
453 ;; position in the buffer for fontification by this stanza.
454 ;;
455 ;; This function does not do any hidden buffer changes, but the
456 ;; generated functions will. (They are however used in places
457 ;; covered by the font-lock context.)
458 ;;
459 ;; Note: Replace `byte-compile' with `eval' to debug the generated
460 ;; lambda more easily.
464 ;; `parse-sexp-lookup-properties' (when it exists).
477 regexp highlights)))))
478 state-stanzas)
480 nil))))
482 ; (eval-after-load "edebug" ; 2006-07-09: def-edebug-spec is now in subr.el.
483 ; '(progn
486 ;; If there are literal quoted or backquoted highlight specs in
487 ;; the call to `c-make-font-lock-search-function' then let's
488 ;; instrument the forms in them.
493 ;; Convert the ranges recorded on `c-record-type-identifiers' and
494 ;; `c-record-ref-identifiers' to fontification.
495 ;;
496 ;; This function does hidden buffer changes.
506 ;; Note that the reference face is a variable that is
507 ;; dereferenced, since it's an alias in Emacs.
509 c-reference-face-name))))
512 "Font lock matchers for preprocessor directives and purely lexical
513 stuff. Used on level 1 and higher."
515 ;; Note: `c-font-lock-declarations' assumes that no matcher here
516 ;; sets `font-lock-type-face' in languages where
517 ;; `c-recognize-<>-arglists' is set.
526 ;; fontify it as a string.
533 re
537 ;; Fontify filenames in #include <...> as strings.
544 re
548 font-lock-string-face)
550 ;; Use an anchored matcher to put paren syntax
551 ;; on the brackets.
563 nil)))))))
565 ;; #define.
569 noncontinued-line-end
576 ;; Macro with arguments - a "function".
579 ;; Macro without arguments - a "variable".
586 ;; "Function". Fontify the name and the arguments.
611 ;; "Variable".
617 ;; Fontify cpp function names in preprocessor
618 ;; expressions in #if and #elif.
629 ced-re ; 1 + ncle-depth
630 ;; Match the whole logical line to look
631 ;; for the functions in.
637 c-preprocessor-face-name)))
641 ,cef-re
644 ;; Fontify the directive names.
658 c-negation-char-face-name
660 )))
663 ;; Recognize hashbangs in Pike.
667 ;; Make hard spaces visible through an inverted `font-lock-warning-face'.
675 ))
678 ;; Assuming the point is after the opening character of a string,
679 ;; fontify that char with `font-lock-warning-face' if the string
680 ;; decidedly isn't terminated properly.
681 ;;
682 ;; This function does hidden buffer changes.
687 ;; Emacs
689 ;; XEmacs
691 ;; There's no multiline string start char before the
692 ;; string, so newlines aren't allowed.
694 ;; Multiline strings are allowed anywhere if
695 ;; c-multiline-string-start-char is t.
698 ;; There's no \ before the newline.
700 ;; Escaped newlines aren't supported.
701 t)
705 "Font lock matchers for basic keywords, labels, references and various
706 other easily recognizable things that should be fontified before generic
707 casts and declarations are fontified. Used on level 2 and higher."
709 ;; Note: `c-font-lock-declarations' assumes that no matcher here
710 ;; sets `font-lock-type-face' in languages where
711 ;; `c-recognize-<>-arglists' is set.
714 ;; can't span lines. Later font
715 ;; lock packages have a `font-lock-syntactic-face-function' for
716 ;; this, but it doesn't give the control we want since any
717 ;; fontification done inside the function will be
718 ;; unconditionally overridden.
720 ;; Match a char before the string starter to make
721 ;; `c-skip-comments-and-strings' work correctly.
725 ;; Fontify keyword constants.
729 ;; No symbol is a keyword after "->" in Pike.
736 ;; Fontify all keywords except the primitive types.
738 ;; No symbol is a keyword after "->" in Pike.
745 ;; Fontify leading identifiers in fully qualified names like
746 ;; "foo::bar" in languages that supports such things.
749 ;; Java needs special treatment since "." is used both to
750 ;; qualify names and in normal indexing. Here we look for
751 ;; capital characters at the beginning of an identifier to
752 ;; recognize the class. "*" is also recognized to cover
753 ;; wildcard import declarations. All preceding dot separated
754 ;; identifiers are taken as package names and therefore
755 ;; fontified as references.
757 ;; Search for class identifiers preceded by ".". The
758 ;; anchored matcher takes it from there.
778 c-reference-face-name)
780 nil
784 ;; Must use a function here since we match longer than
785 ;; we want to move before doing a new search. This is
786 ;; not necessary for XEmacs since it restarts the
787 ;; search from the end of the first highlighted
788 ;; submatch (something that causes problems in other
789 ;; places).
801 limit t)
808 c-reference-face-name))
811 ;; Fontify the special declarations in Objective-C.
819 ;; In this case we accept both primitive and known types.
826 ;; The @interface/@implementation/@protocol directives.
831 t)
835 ;; `parse-sexp-lookup-properties' (when it exists).
840 nil)
844 ))
847 ;; This function will be called from font-lock for a region bounded by POINT
848 ;; and LIMIT, as though it were to identify a keyword for
849 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
850 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
851 ;; Fontification".
852 ;;
853 ;; Called before any of the matchers in `c-complex-decl-matchers'.
854 ;;
855 ;; This function does hidden buffer changes.
857 ;;(message "c-font-lock-complex-decl-prepare %s %s" (point) limit)
859 ;; Clear the list of found types if we start from the start of the
860 ;; buffer, to make it easier to get rid of misspelled types and
861 ;; variables that have gotten recognized as types in malformed code.
865 ;; Clear the c-type char properties which mark the region, to recalculate
866 ;; them properly. The most interesting properties are those put on the
867 ;; closest token before the region.
875 c-decl-end
876 c-decl-id-start
877 c-decl-type-start)))
879 pos)
882 ;; Update `c-state-cache' to the beginning of the region. This will
883 ;; make `c-beginning-of-syntax' go faster when it's used later on,
884 ;; and it's near the point most of the time.
887 ;; Check if the fontified region starts inside a declarator list so
888 ;; that `c-font-lock-declarators' should be called at the start.
889 ;; The declared identifiers are font-locked correctly as types, if
890 ;; that is what they are.
905 nil)
908 ;; This function will be called from font-lock for a region bounded by POINT
909 ;; and LIMIT, as though it were to identify a keyword for
910 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
911 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
912 ;; Fontification".
913 ;;
914 ;; Fontify types and references in names containing angle bracket
915 ;; arglists from the point to LIMIT. Note that
916 ;; `c-font-lock-declarations' already has handled many of them.
917 ;;
918 ;; This function might do hidden buffer changes.
921 ;; `parse-sexp-lookup-properties' (when it exists).
926 c-restricted-<>-arglists
927 id-start id-end id-face pos kwd-sym)
939 c-restricted-<>-arglists nil
944 ;; The identifier got the type face so it has already been
945 ;; handled in `c-font-lock-declarations'.
946 nil)
950 ;; There's a special keyword before the "<" that tells
951 ;; that it's an angle bracket arglist.
955 ;; There's a normal identifier before the "<". If we're not in
956 ;; a declaration context then we set `c-restricted-<>-arglists'
957 ;; to avoid recognizing templates in function calls like "foo (a
958 ;; < b, c > d)".
964 t))
968 ;; Check for comment/string both at the identifier and
969 ;; at the "<".
980 c-reference-face-name)
986 nil)
989 ;; Assuming the point is at the start of a declarator in a declaration,
990 ;; fontify the identifier it declares. (If TYPES is set, it does this via
991 ;; the macro `c-fontify-types-and-refs'.)
992 ;;
993 ;; If LIST is non-nil, also fontify the ids in any following declarators in
994 ;; a comma separated list (e.g. "foo" and "*bar" in "int foo = 17, *bar;");
995 ;; additionally, mark the commas with c-type property 'c-decl-id-start or
996 ;; 'c-decl-type-start (according to TYPES). Stop at LIMIT.
997 ;;
998 ;; If TYPES is non-nil, fontify all identifiers as types.
999 ;;
1000 ;; Nil is always returned. The function leaves point at the delimiter after
1001 ;; the last declarator it processes.
1002 ;;
1003 ;; This function might do hidden buffer changes.
1005 ;;(message "c-font-lock-declarators from %s to %s" (point) limit)
1008 paren-depth
1009 id-face got-init
1010 c-last-identifier-range
1012 brackets-after-id)
1014 ;; The following `while' fontifies a single declarator id each time round.
1015 ;; It loops only when LIST is non-nil.
1017 ;; Inside the following "condition form", we move forward over the
1018 ;; declarator's identifier up as far as any opening bracket (for array
1019 ;; size) or paren (for parameters of function-type) or brace (for
1020 ;; array/struct initialization) or "=" or terminating delimiter
1021 ;; (e.g. "," or ";" or "}").
1023 pos
1026 ;; The following form moves forward over the declarator's
1027 ;; identifier (and what precedes it), returning t. If there
1028 ;; wasn't one, it returns nil, terminating the `while'.
1031 ;; Skip over type decl prefix operators, one for each iteration
1032 ;; of the while. These are, e.g. "*" in "int *foo" or "(" and
1033 ;; "*" in "int (*foo) (void)" (Note similar code in
1034 ;; `c-forward-decl-or-cast-1'.)
1038 ;; If the third submatch matches in C++ then
1039 ;; we're looking at an identifier that's a
1040 ;; prefix only if it specifies a member pointer.
1045 ;; We only check for a trailing "::" and
1046 ;; let the "*" that should follow be
1047 ;; matched in the next round.
1048 t
1049 ;; It turned out to be the real identifier,
1050 ;; so flag that and stop.
1052 nil))
1053 t))
1061 ;; If we haven't passed the identifier already, do it now.
1069 ;; Skip out of the parens surrounding the identifier. If closing
1070 ;; parens are missing, this form returns nil.
1076 ;; Skip over any trailing bit, such as "__attribute__".
1082 ;; Search syntactically to the end of the declarator (";",
1083 ;; ",", a closing paren, eob etc) or to the beginning of an
1084 ;; initializer or function prototype ("=" or "\\s\(").
1085 ;; Note that square brackets are now not also treated as
1086 ;; initializers, since this broke when there were also
1087 ;; initializing brace lists.
1095 found))
1100 'font-lock-function-name-face
1106 ;; Register and fontify the identifier as a type.
1110 ;; Fontify the last symbol in the identifier if it isn't fontified
1111 ;; already. The check is necessary only in certain cases where this
1112 ;; function is used "sloppily", e.g. in `c-simple-decl-matchers'.
1118 id-face)))
1123 ;; Jump past any initializer or function prototype to see if
1124 ;; there's a ',' to continue at.
1126 ;; Skip a parenthesized initializer (C++) or a function
1127 ;; prototype.
1133 ;; Skip an initializer expression. If we're at a '='
1134 ;; then accept a brace list directly after it to cope
1135 ;; with array initializers. Otherwise stop at braces
1136 ;; to avoid going past full function and class blocks.
1141 t)
1142 ;; FIXME: Should look for c-decl-end markers here;
1143 ;; we might go far into the following declarations
1144 ;; in e.g. ObjC mode (see e.g. methods-4.m).
1150 ;; If a ',' is found we set pos to the next declarator and iterate.
1156 nil)
1159 ;; List of faces that might be put at the start of a type when
1160 ;; `c-font-lock-declarations' runs. This needs to be evaluated to
1161 ;; ensure that face name aliases in Emacs are resolved.
1163 font-lock-type-face
1164 c-reference-face-name
1165 font-lock-keyword-face))
1168 ;; Fontify all the declarations, casts and labels from the point to LIMIT.
1169 ;; Assumes that strings and comments have been fontified already.
1170 ;;
1171 ;; This function will be called from font-lock for a region bounded by POINT
1172 ;; and LIMIT, as though it were to identify a keyword for
1173 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1174 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1175 ;; Fontification".
1176 ;;
1177 ;; This function might do hidden buffer changes.
1179 ;;(message "c-font-lock-declarations search from %s to %s" (point) limit)
1183 start-pos
1184 ;; o - 'decl if we're in an arglist containing declarations
1185 ;; (but if `c-recognize-paren-inits' is set it might also be
1186 ;; an initializer arglist);
1187 ;; o - '<> if the arglist is of angle bracket type;
1188 ;; o - 'arglist if it's some other arglist;
1189 ;; o - nil, if not in an arglist at all. This includes the
1190 ;; parenthesized condition which follows "if", "while", etc.
1191 context
1192 ;; A list of starting positions of possible type declarations, or of
1193 ;; the typedef preceding one, if any.
1194 last-cast-end
1195 ;; The result from `c-forward-decl-or-cast-1'.
1196 decl-or-cast
1197 ;; The maximum of the end positions of all the checked type
1198 ;; decl expressions in the successfully identified
1199 ;; declarations. The position might be either before or
1200 ;; after the syntactic whitespace following the last token
1201 ;; in the type decl expression.
1203 ;; Same as `max-type-decl-*', but used when we're before
1204 ;; `token-pos'.
1206 ;; Set according to the context to direct the heuristics for
1207 ;; recognizing C++ templates.
1208 c-restricted-<>-arglists
1209 ;; Turn on recording of identifier ranges in
1210 ;; `c-forward-decl-or-cast-1' and `c-forward-label' for
1211 ;; later fontification.
1213 label-type
1214 c-record-ref-identifiers
1215 ;; Make `c-forward-type' calls mark up template arglists if
1216 ;; it finds any. That's necessary so that we later will
1217 ;; stop inside them to fontify types there.
1219 lbrace ; position of some {.
1220 ;; The font-lock package in Emacs is known to clobber
1221 ;; `parse-sexp-lookup-properties' (when it exists).
1226 ;; Below we fontify a whole declaration even when it crosses the limit,
1227 ;; to avoid gaps when jit/lazy-lock fontifies the file a block at a
1228 ;; time. That is however annoying during editing, e.g. the following is
1229 ;; a common situation while the first line is being written:
1230 ;;
1231 ;; my_variable
1232 ;; some_other_variable = 0;
1233 ;;
1234 ;; font-lock will put the limit at the beginning of the second line
1235 ;; here, and if we go past it we'll fontify "my_variable" as a type and
1236 ;; "some_other_variable" as an identifier, and the latter will not
1237 ;; correct itself until the second line is changed. To avoid that we
1238 ;; narrow to the limit if the region to fontify is a single line.
1243 ;; Narrow after any operator chars following the limit though,
1244 ;; since those characters can be useful in recognizing a
1245 ;; declaration (in particular the '{' that opens a function body
1246 ;; after the header).
1252 limit
1253 c-decl-start-re
1254 c-font-lock-maybe-decl-faces
1257 ;; Note to maintainers: don't use `limit' inside this lambda form;
1258 ;; c-find-decl-spots sometimes narrows to less than `limit'.
1261 ;; The result of the form below is true when we don't recognize a
1262 ;; declaration or cast.
1268 ;; Don't do anything more if we're looking at a keyword that
1269 ;; can't start a declaration.
1270 t
1272 ;; Set `context' and `c-restricted-<>-arglists'. Look for
1273 ;; "<" for the sake of C++-style template arglists.
1274 ;; Ignore "(" when it's part of a control flow construct
1275 ;; (e.g. "for (").
1281 ;; A control flow expression or a decltype
1292 ;; Near BOB.
1296 ;; Got a cached hit in a declaration arglist.
1300 ;; Inside an angle bracket arglist.
1305 ;; Got a cached hit in some other type of arglist.
1312 ;; The point is within the range of a previously
1313 ;; encountered type decl expression, so the arglist
1314 ;; is probably one that contains declarations.
1315 ;; However, if `c-recognize-paren-inits' is set it
1316 ;; might also be an initializer arglist.
1319 ;; The result of this check is cached with a char
1320 ;; property on the match token, so that we can look
1321 ;; it up again when refontifying single lines in a
1322 ;; multiline declaration.
1328 ;; Check we haven't missed a preceding "typedef".
1335 ;; In QT, "more" is an irritating keyword that expands to nothing.
1336 ;; We skip over it to prevent recognition of "more slots: <symbol>"
1337 ;; as a bitfield declaration.
1344 ;; Now analyze the construct.
1346 match-pos context last-cast-end))
1350 ;; Save the position after the previous cast so we can feed
1351 ;; it to `c-forward-decl-or-cast-1' in the next round. That
1352 ;; helps it discover cast chains like "(a) (b) c".
1355 nil)
1358 ;; We've found a declaration.
1360 ;; Set `max-type-decl-end' or `max-type-decl-end-before-token'
1361 ;; under the assumption that we're after the first type decl
1362 ;; expression in the declaration now. That's not really true;
1363 ;; we could also be after a parenthesized initializer
1364 ;; expression in C++, but this is only used as a last resort
1365 ;; to slant ambiguous expression/declarations, and overall
1366 ;; it's worth the risk to occasionally fontify an expression
1367 ;; as a declaration in an initializer expression compared to
1368 ;; getting ambiguous things in normal function prototypes
1369 ;; fontified as expressions.
1376 ;; Back up to the type to fontify the declarator(s).
1381 ;; Should normally not fontify a list of
1382 ;; declarators inside an arglist, but the first
1383 ;; argument in the ';' separated list of a "for"
1384 ;; statement is an exception.
1391 t)))
1393 ;; Fix the `c-decl-id-start' or `c-decl-type-start' property
1394 ;; before the first declarator if it's a list.
1395 ;; `c-font-lock-declarators' handles the rest.
1402 'c-decl-type-start
1408 ;; A declaration has been successfully identified, so do all the
1409 ;; fontification of types and refs that've been recorded.
1411 nil)
1413 ;; Restore point, since at this point in the code it has been
1414 ;; left undefined by c-forward-decl-or-cast-1 above.
1417 ;; If point is inside a bracelist, there's no point checking it
1418 ;; being at a declarator.
1421 ;; Move past this bracelist to prevent an endless loop.
1426 nil)
1428 ;; If point is just after a ")" which is followed by an
1429 ;; identifier which isn't a label, or at the matching "(", we're
1430 ;; at either a macro invocation, a cast, or a
1431 ;; for/while/etc. statement. The cast case is handled above.
1432 ;; None of these cases can contain a declarator.
1444 nil)
1447 ;; An optimization quickly to eliminate scans of long enum
1448 ;; declarations in the next cond arm.
1456 nil)
1459 ;; Are we at a declarator? Try to go back to the declaration
1460 ;; to check this. If we get there, check whether a "typedef"
1461 ;; is there, then fontify the declarators accordingly.
1463 paren-state bod-res encl-pos is-typedef
1465 ; speeds up lisp.h tremendously.
1468 t ; Can't be at a declarator
1479 ;; We're now putatively at the declaration.
1481 ;; At top level or inside a "{"?
1490 ;; At a real declaration?
1494 nil)
1495 ;; False alarm. Return t to go on to the next check.
1497 t))
1498 t)))))))
1500 ;; It was a false alarm. Check if we're in a label (or other
1501 ;; construct with `:' except bitfield) instead.
1504 ;; Can't use `c-fontify-types-and-refs' here since we
1505 ;; use the label face at times.
1509 c-label-face-name))
1519 c-record-ref-identifiers)))
1521 ;; `c-forward-label' has probably added a `c-decl-end'
1522 ;; marker, so return t to `c-find-decl-spots' to signal
1523 ;; that.
1524 t))))
1526 nil)))
1529 ;; Fontify an enum's identifiers when POINT is within the enum's brace
1530 ;; block.
1531 ;;
1532 ;; This function will be called from font-lock for a region bounded by POINT
1533 ;; and LIMIT, as though it were to identify a keyword for
1534 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1535 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1536 ;; Fontification".
1537 ;;
1538 ;; Note that this function won't attempt to fontify beyond the end of the
1539 ;; current enum block, if any.
1543 encl-pos
1553 nil)
1556 ;; Fontify the declarators of (nested) declarations we're in the middle of.
1557 ;; This is mainly for when a jit-lock etc. chunk starts inside the brace
1558 ;; block of a struct/union/class, etc.
1559 ;;
1560 ;; This function will be called from font-lock for a region bounded by POINT
1561 ;; and LIMIT, as though it were to identify a keyword for
1562 ;; font-lock-keyword-face. It always returns NIL to inhibit this and
1563 ;; prevent a repeat invocation. See elisp/lispref page "Search-based
1564 ;; Fontification".
1567 decl-context in-typedef ps-elt)
1568 ;; Are we in any nested struct/union/class/etc. braces?
1586 "Simple font lock matchers for types and declarations. These are used
1587 on level 2 only and so aren't combined with `c-complex-decl-matchers'."
1595 ;; `parse-sexp-lookup-properties' (when it exists).
1602 nil))
1605 ;; Fontify all type names and the identifiers in the
1606 ;; declarations they might start. Use eval here since
1607 ;; `c-known-type-key' gets its value from
1608 ;; `*-font-lock-extra-types' on mode init.
1610 'c-known-type-key
1618 ;; Fontify types preceded by `c-type-prefix-kwds' and the
1619 ;; identifiers in the declarations they might start.
1632 `(,type-match
1640 ;; Fontify special declarations that lacks a type.
1652 ;; Fontify generic colon labels in languages that support them.
1657 "Complex font lock matchers for types and declarations. Used on level
1658 3 and higher."
1660 ;; Note: This code in this form dumps a number of functions into the
1661 ;; resulting constant, `c-matchers-3'. At run time, font lock will call
1662 ;; each of them as a "FUNCTION" (see Elisp page "Search-based
1663 ;; Fontification"). The font lock region is delimited by POINT and the
1664 ;; single parameter, LIMIT. Each of these functions returns NIL (thus
1665 ;; inhibiting spurious font-lock-keyword-face highlighting and another
1666 ;; call).
1669 c-font-lock-complex-decl-prepare
1672 ;; Fontify method declarations in Objective-C, but first
1673 ;; we have to put the `c-decl-end' `c-type' property on
1674 ;; all the @-style directives that haven't been handled in
1675 ;; `c-basic-matchers-before'.
1678 ;; Exclude "@class" since that directive ends with a
1679 ;; semicolon anyway.
1683 nil)))
1686 c-font-lock-objc-methods))
1688 ;; Fontify all declarations, casts and normal labels.
1689 c-font-lock-declarations
1691 ;; Fontify declarators when POINT is within their declaration.
1692 c-font-lock-enclosing-decls
1694 ;; Fontify angle bracket arglists like templates in C++.
1698 ;; The first two rules here mostly find occurrences that
1699 ;; `c-font-lock-declarations' has found already, but not
1700 ;; declarations containing blocks in the type (see note below).
1701 ;; It's also useful to fontify these everywhere to show e.g. when
1702 ;; a type keyword is accidentally used as an identifier.
1704 ;; Fontify basic types.
1708 ;; No symbol is a keyword after "->" in Pike.
1715 ;; Fontify types preceded by `c-type-prefix-kwds' (e.g. "struct").
1721 ;; The font-lock package in Emacs is known to clobber
1722 ;; `parse-sexp-lookup-properties' (when it exists).
1727 ;; Narrow to avoid going past the limit in
1728 ;; `c-forward-type'.
1735 limit t)
1738 ;; Handle prefix declaration specifiers.
1746 ;; In C++ we additionally check for a "class
1747 ;; X = Y" construct which is used in
1748 ;; templates, to fontify Y as a type.
1753 )))))))))
1755 ;; Fontify symbols after closing braces as declaration
1756 ;; identifiers under the assumption that they are part of
1757 ;; declarations like "class Foo { ... } foo;". It's too
1758 ;; expensive to check this accurately by skipping past the
1759 ;; brace block, so we use the heuristic that it's such a
1760 ;; declaration if the first identifier is on the same line as
1761 ;; the closing brace. `c-font-lock-declarations' will later
1762 ;; override it if it turns out to be an new declaration, but
1763 ;; it will be wrong if it's an expression (see the test
1764 ;; decls-8.cc).
1765 ;; ,@(when (c-lang-const c-opt-block-decls-with-vars-key)
1766 ;; `((,(c-make-font-lock-search-function
1767 ;; (concat "}"
1768 ;; (c-lang-const c-single-line-syntactic-ws)
1769 ;; "\\(" ; 1 + c-single-line-syntactic-ws-depth
1770 ;; (c-lang-const c-type-decl-prefix-key)
1771 ;; "\\|"
1772 ;; (c-lang-const c-symbol-key)
1773 ;; "\\)")
1774 ;; `((c-font-lock-declarators limit t nil) ; That `nil' says use `font-lock-variable-name-face';
1775 ;; ; `t' would mean `font-lock-function-name-face'.
1776 ;; (progn
1777 ;; (c-put-char-property (match-beginning 0) 'c-type
1778 ;; 'c-decl-id-start)
1779 ;; ; 'c-decl-type-start)
1780 ;; (goto-char (match-beginning
1781 ;; ,(1+ (c-lang-const
1782 ;; c-single-line-syntactic-ws-depth)))))
1783 ;; (goto-char (match-end 0)))))))
1785 ;; Fontify the type in C++ "new" expressions.
1787 ;; This pattern is a probably a "(MATCHER . ANCHORED-HIGHLIGHTER)"
1788 ;; (see Elisp page "Search-based Fontification").
1791 ))
1794 ;; Fontify all statement labels from the point to LIMIT. Assumes
1795 ;; that strings and comments have been fontified already. Nil is
1796 ;; always returned.
1797 ;;
1798 ;; Note: This function is only used on decoration level 2; this is
1799 ;; taken care of directly by the gargantuan
1800 ;; `c-font-lock-declarations' on higher levels.
1801 ;;
1802 ;; This function might do hidden buffer changes.
1805 ;; The font-lock package in Emacs is known to clobber
1806 ;; `parse-sexp-lookup-properties' (when it exists).
1825 ;; Check for a char that precedes a statement.
1827 ;; Check for a preceding label. We exploit the font
1828 ;; locking made earlier by this function.
1835 c-label-face-name))
1836 ;; Check for a keyword that precedes a statement.
1840 ;; Got a label.
1844 c-label-face-name)))
1847 nil)
1850 "Font lock matchers for various things that should be fontified after
1851 generic casts and declarations are fontified. Used on level 2 and
1852 higher."
1855 ;; Fontify the remaining identifiers inside an enum list when we start
1856 ;; inside it.
1858 ;; Fontify the identifiers inside enum lists. (The enum type
1859 ;; name is handled by `c-simple-decl-matchers' or
1860 ;; `c-complex-decl-matchers' below.
1866 ;; Disallow various common punctuation chars that can't come
1867 ;; before the '{' of the enum list, to avoid searching too far.
1868 "[^\]\[{}();/#=]*"
1878 ;; Fontify labels after goto etc.
1881 ;; which makes it a bit complicated: 1) The backquote
1882 ;; stuff is expanded when compiled or loaded, 2) the
1883 ;; eval form is evaluated at font-lock setup (to
1884 ;; substitute c-label-face-name correctly), and 3) the
1885 ;; resulting structure is interpreted during
1886 ;; fontification.)
1898 c-label-face-name nil t))))))
1900 ;; Fontify the clauses after various keywords.
1927 ))
1945 ;; Incorporate the font lock keyword lists according to
1946 ;; `c-doc-comment-style' on the given keyword list and return it.
1947 ;; This is used in the function bindings of the
1948 ;; `*-font-lock-keywords-*' symbols since we have to build the list
1949 ;; when font-lock is initialized.
1958 c-doc-comment-style))
1970 doc-keywords
1972 base-list)))
1974 ;; Kludge: If `c-font-lock-complex-decl-prepare' is on the list we
1975 ;; move it first since the doc comment font lockers might add
1976 ;; `c-type' text properties, so they have to be cleared before that.
1982 list))
1985 ;; This is used to override the value on a `*-font-lock-keywords'
1986 ;; variable only if it's nil or has the same value as one of the
1987 ;; `*-font-lock-keywords-*' variables. Older font-lock packages
1988 ;; define a default value for `*-font-lock-keywords' which we want
1989 ;; to override, but we should otoh avoid clobbering a user setting.
1990 ;; This heuristic for that isn't perfect, but I can't think of any
1991 ;; better. /mast
1998 suffix))))
2001 ;; The overriding is done by unbinding the variable so that the normal
2002 ;; defvar will install its default value later on.
2005 \f
2006 ;;; C.
2011 "Minimal font locking for C mode.
2012 Fontifies only preprocessor directives (in addition to the syntactic
2016 "Fast normal font locking for C mode.
2017 In addition to `c-font-lock-keywords-1', this adds fontification of
2018 keywords, simple types, declarations that are easy to recognize, the
2019 user defined types on `c-font-lock-extra-types', and the doc comment
2023 "Accurate normal font locking for C mode.
2024 Like the variable `c-font-lock-keywords-2' but detects declarations in a more
2025 accurate way that works in most cases for arbitrary types without the
2038 \f
2039 ;;; C++.
2042 ;; FIXME!!! Put in a comment about the context of this function's
2043 ;; invocation. I think it's called as an ANCHORED-MATCHER within an
2044 ;; ANCHORED-HIGHLIGHTER. (2007/2/10).
2045 ;;
2046 ;; Assuming point is after a "new" word, check that it isn't inside
2047 ;; a string or comment, and if so try to fontify the type in the
2048 ;; allocation expression. Nil is always returned.
2049 ;;
2050 ;; As usual, C++ takes the prize in coming up with a hard to parse
2051 ;; syntax. :P
2052 ;;
2053 ;; This function might do hidden buffer changes.
2058 ;; A "new" keyword is followed by one to three expressions, where
2059 ;; the type is the middle one, and the only required part.
2061 ;; Enable recording of identifier ranges in `c-forward-type'
2062 ;; etc for later fontification. Not using
2063 ;; `c-fontify-types-and-refs' here since the ranges should
2064 ;; be fontified selectively only when an allocation
2065 ;; expression is successfully recognized.
2067 c-record-ref-identifiers
2068 ;; The font-lock package in Emacs is known to clobber
2069 ;; `parse-sexp-lookup-properties' (when it exists).
2075 ;; The first placement arglist is always parenthesized, if it
2076 ;; exists.
2084 ;; The second expression is either a type followed by some "*" or
2085 ;; "[...]" or similar, or a parenthesized type followed by a full
2086 ;; identifierless declarator.
2096 ;; No second expression, so the first has to be a
2097 ;; parenthesized type.
2103 ;; Got two parenthesized expressions, so we have to look
2104 ;; closer at them to decide which is the type. No need to
2105 ;; handle `c-record-ref-identifiers' since all references
2106 ;; have already been handled by other fontification rules.
2115 ;; There's something after the would-be type that
2116 ;; can't be there, so this is a placement arglist.
2125 ;; There's something after the would-be type that can't
2126 ;; be there, so this is an initialization expression.
2131 ;; If there's a third initialization expression
2132 ;; then the second one is the type, so demote the
2133 ;; first match.
2136 ;; We fontify the most likely type, with a preference for
2137 ;; the first argument since a placement arglist is more
2138 ;; unusual than an initializer.
2141 ;; Presumably 'decltype's will be fontified elsewhere.
2160 ;; If both type matches are 'maybe then we're
2161 ;; too uncertain to promote either of them.
2162 )))))
2164 ;; Fontify the type that now is recorded in
2165 ;; `c-record-type-identifiers', if any.
2167 nil)
2172 "Minimal font locking for C++ mode.
2173 Fontifies only preprocessor directives (in addition to the syntactic
2177 "Fast normal font locking for C++ mode.
2178 In addition to `c++-font-lock-keywords-1', this adds fontification of
2179 keywords, simple types, declarations that are easy to recognize, the
2180 user defined types on `c++-font-lock-extra-types', and the doc comment
2184 "Accurate normal font locking for C++ mode.
2185 Like the variable `c++-font-lock-keywords-2' but detects declarations in a more
2186 accurate way that works in most cases for arbitrary types without the
2199 \f
2200 ;;; Objective-C.
2203 ;; Assuming the point is after the + or - that starts an Objective-C
2204 ;; method declaration, fontify it. This must be done before normal
2205 ;; casts, declarations and labels are fontified since they will get
2206 ;; false matches in these things.
2207 ;;
2208 ;; This function might do hidden buffer changes.
2218 ;; An optional method type.
2226 t))
2228 ;; The name. The first time it's the first part of
2229 ;; the function name, the rest of the time it's an
2230 ;; argument name.
2237 'font-lock-function-name-face
2241 ;; Another optional part of the function name.
2249 ;; There's another argument if a colon follows.
2255 ;; Fontify method declarations in Objective-C. Nil is always
2256 ;; returned.
2257 ;;
2258 ;; This function might do hidden buffer changes.
2261 ;; `parse-sexp-lookup-properties' (when it exists).
2267 limit
2268 "[-+]"
2269 nil
2273 nil)
2278 "Minimal font locking for Objective-C mode.
2279 Fontifies only compiler directives (in addition to the syntactic
2283 "Fast normal font locking for Objective-C mode.
2284 In addition to `objc-font-lock-keywords-1', this adds fontification of
2285 keywords, simple types, declarations that are easy to recognize, the
2286 user defined types on `objc-font-lock-extra-types', and the doc
2290 "Accurate normal font locking for Objective-C mode.
2291 Like the variable `objc-font-lock-keywords-2' but detects declarations in a more
2292 accurate way that works in most cases for arbitrary types without the
2305 ;; Kludge to override the default value that
2306 ;; `objc-font-lock-extra-types' might have gotten from the font-lock
2307 ;; package. The value replaced here isn't relevant now anyway since
2308 ;; those types are builtin and therefore listed directly in
2309 ;; `c-primitive-type-kwds'.
2315 \f
2316 ;;; Java.
2321 "Minimal font locking for Java mode.
2322 Fontifies nothing except the syntactic fontification of strings and
2326 "Fast normal font locking for Java mode.
2327 In addition to `java-font-lock-keywords-1', this adds fontification of
2328 keywords, simple types, declarations that are easy to recognize, the
2329 user defined types on `java-font-lock-extra-types', and the doc
2333 "Accurate normal font locking for Java mode.
2334 Like variable `java-font-lock-keywords-2' but detects declarations in a more
2335 accurate way that works in most cases for arbitrary types without the
2348 \f
2349 ;;; CORBA IDL.
2354 "Minimal font locking for CORBA IDL mode.
2355 Fontifies nothing except the syntactic fontification of strings and
2359 "Fast normal font locking for CORBA IDL mode.
2360 In addition to `idl-font-lock-keywords-1', this adds fontification of
2361 keywords, simple types, declarations that are easy to recognize, the
2362 user defined types on `idl-font-lock-extra-types', and the doc comment
2366 "Accurate normal font locking for CORBA IDL mode.
2367 Like the variable `idl-font-lock-keywords-2' but detects declarations in a more
2368 accurate way that works in most cases for arbitrary types without the
2381 \f
2382 ;;; Pike.
2387 "Minimal font locking for Pike mode.
2388 Fontifies only preprocessor directives (in addition to the syntactic
2392 "Fast normal font locking for Pike mode.
2393 In addition to `pike-font-lock-keywords-1', this adds fontification of
2394 keywords, simple types, declarations that are easy to recognize, the
2395 user defined types on `pike-font-lock-extra-types', and the doc
2399 "Accurate normal font locking for Pike mode.
2400 Like the variable `pike-font-lock-keywords-2' but detects declarations in a more
2401 accurate way that works in most cases for arbitrary types without the
2414 \f
2415 ;;; Doc comments.
2418 ;; Fontify the comments between the point and LIMIT whose start
2419 ;; matches PREFIX with `c-doc-face-name'. Assumes comments have been
2420 ;; fontified with `font-lock-comment-face' already. nil is always
2421 ;; returned.
2422 ;;
2423 ;; After the fontification of a matching comment, fontification
2424 ;; according to KEYWORDS is applied inside it. It's a list like
2425 ;; `font-lock-keywords' except that anchored matches and eval
2426 ;; clauses aren't supported and that some abbreviated forms can't be
2427 ;; used. The buffer is narrowed to the comment while KEYWORDS is
2428 ;; applied; leading comment starters are included but trailing
2429 ;; comment enders for block comment are not.
2430 ;;
2431 ;; Note that faces added through KEYWORDS should never replace the
2432 ;; existing `c-doc-face-name' face since the existence of that face
2433 ;; is used as a flag in other code to skip comments.
2434 ;;
2435 ;; This function might do hidden buffer changes.
2440 ;; Handle the case when the fontified region starts inside a
2441 ;; comment.
2450 comment-beg
2452 ;; Search for the prefix until a match is found at the start
2453 ;; of a comment.
2457 c-literal-faces))
2460 c-literal-faces))))
2465 ;; Collect a sequence of doc style line comments.
2482 ;; Narrow to the doc comment. Among other things, this
2483 ;; helps by making "^" match at the start of the comment.
2484 ;; Do not include a trailing block comment ender, though.
2508 nil)
2512 ;; Used to fontify invalid markup in doc comments after the correct
2513 ;; ones have been fontified: Find the first occurrence of REGEXP
2514 ;; between the point and LIMIT that only is fontified with
2515 ;; `c-doc-face-name'. If a match is found then submatch 0 surrounds
2516 ;; the first char and t is returned, otherwise nil is returned.
2517 ;;
2518 ;; This function might do hidden buffer changes.
2523 c-doc-face-name))
2528 t)))
2530 ;; GtkDoc patterns contributed by Masatake YAMATO <jet@gyve.org>.
2543 ))
2552 gtkdoc-font-lock-doc-comments)
2554 gtkdoc-font-lock-doc-protection)
2555 ))))
2557 ;; Javadoc.
2572 ;; Fontify remaining markup characters as invalid. Note
2573 ;; that the Javadoc spec is hazy about when "@" is
2574 ;; allowed in non-markup use.
2582 javadoc-font-lock-doc-comments)))))
2584 ;; Pike autodoc.
2587 ;; Adorned regexp matching the keywords that introduce declarations
2588 ;; in Pike Autodoc.
2593 ;; Adorned regexp matching the keywords that are followed by a type.
2598 ;; Fontify all line oriented keywords between the point and LIMIT.
2599 ;; Nil is always returned.
2600 ;;
2601 ;; This function might do hidden buffer changes.
2604 c-current-comment-prefix
2615 end)
2619 ;; Put a declaration end mark at the markup keyword and
2620 ;; remove the faces from the rest of the line so that it
2621 ;; gets refontified as a declaration later on by
2622 ;; `c-font-lock-declarations'.
2638 ;; Include the final newline in the removed area. This
2639 ;; has no visual effect but it avoids some tricky special
2640 ;; cases in the testsuite wrt the differences in string
2641 ;; fontification in Emacs vs XEmacs.
2644 ;; Must handle string literals explicitly inside the declaration.
2652 ;; Fontify types after keywords that always are followed
2653 ;; by them.
2661 ;; Mark each whole line as markup, as long as the logical line
2662 ;; continues.
2666 markup-faces)
2674 nil)
2678 ;; In-text markup.
2681 ;; Fontify remaining markup characters as invalid.
2685 ))
2688 ;; Note that we depend on that `c-current-comment-prefix' has got
2689 ;; its proper value here.
2690 ;;
2691 ;; This function might do hidden buffer changes.
2693 ;; The `c-type' text property with `c-decl-end' is used to mark the
2694 ;; end of the `autodoc-decl-keywords' occurrences to fontify the
2695 ;; following declarations.
2700 autodoc-font-lock-doc-comments)))))
2702 \f
2703 ;; 2006-07-10: awk-font-lock-keywords has been moved back to cc-awk.el.
2706 ;;; Local Variables:
2707 ;;; indent-tabs-mode: t
2708 ;;; tab-width: 8
2709 ;;; End:
2710 ;;; cc-fonts.el ends here