| blob | c5bbfaf86dd05909e5505bce3aa425f077bf8ad7 |
1 ;;; cc-fonts.el --- font lock support for CC Mode
3 ;; Copyright (C) 2002, 03 Free Software Foundation, Inc.
5 ;; Authors: 2003- Alan Mackenzie
6 ;; 2002- Martin Stjernholm
7 ;; Maintainer: bug-cc-mode@gnu.org
8 ;; Created: 07-Jan-2002
9 ;; Version: See cc-mode.el
10 ;; Keywords: c languages oop
12 ;; This file is part of GNU Emacs.
14 ;; GNU Emacs is free software; you can redistribute it and/or modify
15 ;; it under the terms of the GNU General Public License as published by
16 ;; the Free Software Foundation; either version 2, or (at your option)
17 ;; any later version.
19 ;; GNU Emacs is distributed in the hope that it will be useful,
20 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
21 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
22 ;; GNU General Public License for more details.
24 ;; You should have received a copy of the GNU General Public License
25 ;; along with this program; see the file COPYING. If not, write to
26 ;; the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
27 ;; Boston, MA 02111-1307, USA.
29 ;;; Commentary:
31 ;; Some comments on the use of faces:
32 ;;
33 ;; o `c-label-face-name' is either `font-lock-constant-face' (in Emacs
34 ;; 20 and later), or `font-lock-reference-face'.
35 ;;
36 ;; o `c-constant-face-name', `c-reference-face-name' and
37 ;; `c-doc-markup-face-name' are essentially set up like
38 ;; `c-label-face-name'.
39 ;;
40 ;; o `c-preprocessor-face-name' is `font-lock-preprocessor-face' in
41 ;; XEmacs and - in lack of a closer equivalent -
42 ;; `font-lock-builtin-face' or `font-lock-reference-face' in Emacs.
43 ;;
44 ;; o `c-doc-face-name' is `font-lock-doc-string-face' in XEmacs,
45 ;; `font-lock-doc-face' in Emacs 21 and later, or
46 ;; `font-lock-comment-face' in older Emacs (that since source
47 ;; documentation are actually comments in these languages, as opposed
48 ;; to elisp).
49 ;;
50 ;; o `c-invalid-face-name' is `font-lock-warning-face' in Emacs. In
51 ;; older XEmacs there's no corresponding standard face, so there
52 ;; it's mapped to a special `c-invalid-face'.
53 ;;
54 ;; TBD: We should probably provide real faces for the above uses and
55 ;; instead initialize them from the standard faces.
57 ;;; Code:
59 ;; The faces that already have been put onto the text is tested in
60 ;; various places to direct further fontifications. For this to work,
61 ;; the following assumptions regarding the faces must hold (apart from
62 ;; the dependencies on the font locking order):
63 ;;
64 ;; o `font-lock-comment-face' and the face in `c-doc-face-name' is
65 ;; not used in anything but comments.
66 ;; o If any face (e.g. `c-doc-markup-face-name') but those above is
67 ;; used in comments, it doesn't replace them.
68 ;; o `font-lock-string-face' is not used in anything but string
69 ;; literals (single or double quoted).
70 ;; o `font-lock-keyword-face' and the face in `c-label-face-name' are
71 ;; never overlaid with other faces.
78 load-path)))
86 ;; prevent cc-awk being loaded when it's not needed. There is now a (require
87 ;; 'cc-awk) in (defun awk-mode ..).
89 ;; Avoid repeated loading through the eval-after-load directive in
90 ;; cc-mode.el.
97 ;; Need to declare these local symbols during compilation since
98 ;; they're referenced from lambdas in `byte-compile' calls that are
99 ;; executed at compile time. They don't need to have the proper
100 ;; definitions, though, since the generated functions aren't called
101 ;; during compilation.
110 ;; Emacs 19 doesn't have `defface'. This "replacement" leaves a lot
111 ;; to be wished for but at least it avoids any errors.
117 \f
118 ;; Note that font-lock in XEmacs doesn't expand face names as
119 ;; variables, so we have to use the (eval . FORM) in the font lock
120 ;; matchers wherever we use these alias variables.
124 ;; XEmacs has a font-lock-preprocessor-face.
127 ;; In Emacs 20 and later font-lock-builtin-face has
128 ;; traditionally been used for preprocessor directives.
137 ;; If it happens to occur in the future. (Well, the more
138 ;; pragmatic reason is to get unique faces for the test
139 ;; suite.)
143 ;; Test both if font-lock-constant-face exists and that it's
144 ;; not an alias for something else. This is important since
145 ;; we compare already set faces in various places.
153 ;; This doesn't exist in XEmacs <= 20 and some earlier versions
154 ;; of XEmacs 21.
155 'font-lock-constant-face
156 c-label-face-name))
161 ;; This is considered obsolete in Emacs 20 and later, but it
162 ;; still maps well to this use. (Another reason to do this is
163 ;; to get unique faces for the test suite.)
164 'font-lock-reference-face
165 c-label-face-name))
167 ;; This should not mapped to a face that also is used to fontify things
168 ;; that aren't comments or string literals.
171 ;; XEmacs.
174 ;; Emacs 21 and later.
181 ;; If it happens to occur in the future. (Well, the more
182 ;; pragmatic reason is to get unique faces for the test
183 ;; suite.)
184 'font-lock-doc-markup-face
185 c-label-face-name))
189 ;; Emacs >= 20 and XEmacs >= 21 has a font-lock-warning-face.
190 'font-lock-warning-face
191 ;; Otherwise we provide a face.
200 "Face used to highlight invalid syntax."
203 ;; To make hard spaces visible an inverted version of
204 ;; `c-invalid-face-name' is used. Since font-lock in Emacs expands
205 ;; all face names in `font-lock-keywords' as variables we need to have
206 ;; a variable for it that resolves to its own name.
213 ;; Emacs and XEmacs have completely different face manipulation
214 ;; routines. :P
215 ;;
216 ;; This function does not do any hidden buffer changes
219 ;; Emacs 20 and later. This only looks at the inverse flag
220 ;; in the current frame. Other display configurations might
221 ;; be different, but it can only show if the same Emacs has
222 ;; frames on e.g. a color and a monochrome display
223 ;; simultaneously.
227 ;; XEmacs. Same pitfall here.
231 ;; Emacs 19 has no inverse flag at all. Just inverse the
232 ;; face and hope it wasn't inversed already.
236 ;; We need the following functions during compilation since they're
237 ;; called when the `c-lang-defconst' initializers are evaluated.
238 ;; Define them at runtime too for the sake of derived modes.
241 ;; Put a face on a region (overriding any existing face) in the way
242 ;; font-lock would do it. In XEmacs that means putting an
243 ;; additional font-lock property, or else the font-lock package
244 ;; won't recognize it as fontified and might override it
245 ;; incorrectly.
247 ;; Note: This function has no docstring in XEmacs so it might be
248 ;; considered internal.
253 ;; This is the inverse of `c-put-font-lock-face'.
259 ;; Put `font-lock-string-face' on a string. The surrounding
260 ;; quotes are included in Emacs but not in XEmacs. The passed
261 ;; region should include them.
267 ;; Like `let', but additionally activates `c-record-type-identifiers'
268 ;; and `c-record-ref-identifiers', and fontifies the recorded ranges
269 ;; accordingly on exit.
271 c-record-ref-identifiers
279 ;; If the point is within a region fontified as a comment or
280 ;; string literal skip to the end of it or to LIMIT, whichever
281 ;; comes first, and return t. Otherwise return nil. The match
282 ;; data is not clobbered.
289 t))
292 ;; This function makes a byte compiled function that works much like
293 ;; a matcher element in `font-lock-keywords'. It cuts out a little
294 ;; bit of the overhead compared to a real matcher. The main reason
295 ;; is however to pass the real search limit to the anchored
296 ;; matcher(s), since most (if not all) font-lock implementations
297 ;; arbitrarily limits anchored matchers to the same line, and also
298 ;; to insulate against various other irritating differences between
299 ;; the different (X)Emacs font-lock packages.
300 ;;
301 ;; REGEXP is the matcher, which must be a regexp. Only matches
302 ;; where the beginning is outside any comment or string literal are
303 ;; significant.
304 ;;
305 ;; HIGHLIGHTS is a list of highlight specs, just like in
306 ;; `font-lock-keywords', with these limitations: The face is always
307 ;; overridden (no big disadvantage, since hits in comments etc are
308 ;; filtered anyway), there is no "laxmatch", and an anchored matcher
309 ;; is always a form which must do all the fontification directly.
310 ;; `limit' is a variable bound to the real limit in the context of
311 ;; the anchored matcher forms.
312 ;;
313 ;; This function does not do any hidden buffer changes, but the
314 ;; generated functions will. They are however used in places
315 ;; covered by the font-lock context.
317 ;; Note: Replace `byte-compile' with `eval' to debug the generated
318 ;; lambda easier.
322 ;; The font-lock package in Emacs is known to clobber
323 ;; `parse-sexp-lookup-properties' (when it exists).
339 "The override flag must currently be set in %s"
340 highlight))
343 "The laxmatch flag may currently not be set in %s"
344 highlight))
352 highlight))
357 highlights))))
358 nil))))
361 ;; Converts the ranges recorded on `c-record-type-identifiers' and
362 ;; `c-record-ref-identifiers' to fontification.
372 ;; Note that the reference face is a variable that is
373 ;; dereferenced, since it's an alias in Emacs.
375 c-reference-face-name))))
378 "Font lock matchers for preprocessor directives and purely lexical
379 stuff. Used on level 1 and higher."
381 ;; Note: `c-font-lock-declarations' assumes that no matcher here
382 ;; sets `font-lock-type-face' in languages where
383 ;; `c-recognize-<>-arglists' is set.
390 ;; fontify it as a string.
396 ;; Fontify filenames in #include <...> as strings.
403 font-lock-string-face)
405 ;; Use an anchored matcher to put paren syntax on the brackets.
417 nil))))
419 ;; #define.
422 noncontinued-line-end
428 ;; Macro with arguments - a "function".
431 ;; Macro without arguments - a "variable".
436 ;; "Function". Fontify the name and the arguments.
460 ;; "Variable".
466 ;; Fontify cpp function names in preprocessor
467 ;; expressions in #if and #elif.
473 ;; Match the whole logical line to look
474 ;; for the functions in.
481 nil)
487 c-preprocessor-face-name)))
490 ;; Fontify the directive names.
498 )))
504 ;; Make hard spaces visible through an inverted `c-invalid-face-name'.
512 ))
515 ;; Assuming the point is after the opening character of a string,
516 ;; fontify that char with `c-invalid-face-name' if the string
517 ;; decidedly isn't terminated properly.
522 ;; There's no \ before the newline.
524 ;; Quoted newlines aren't supported.
525 t)
527 ;; There's no # before the string, so newlines
528 ;; aren't allowed.
530 t)
534 "Font lock matchers for basic keywords, labels, references and various
535 other easily recognizable things that should be fontified before generic
536 casts and declarations are fontified. Used on level 2 and higher."
538 ;; Note: `c-font-lock-declarations' assumes that no matcher here
539 ;; sets `font-lock-type-face' in languages where
540 ;; `c-recognize-<>-arglists' is set.
543 ;; can't span lines. Later font
544 ;; lock packages have a `font-lock-syntactic-face-function' for
545 ;; this, but it doesn't give the control we want since any
546 ;; fontification done inside the function will be
547 ;; unconditionally overridden.
549 ;; Match a char before the string starter to make
550 ;; `c-skip-comments-and-strings' work correctly.
554 ;; Fontify keyword constants.
558 ;; No symbol is a keyword after "->" in Pike.
565 ;; Fontify all keywords except the primitive types.
567 ;; No symbol is a keyword after "->" in Pike.
574 ;; Fontify leading identifiers in fully qualified names like
575 ;; "foo::bar" in languages that supports such things.
578 ;; Java needs special treatment since "." is used both to
579 ;; qualify names and in normal indexing. Here we look for
580 ;; capital characters at the beginning of an identifier to
581 ;; recognize the class. "*" is also recognized to cover
582 ;; wildcard import declarations. All preceding dot separated
583 ;; identifiers are taken as package names and therefore
584 ;; fontified as references.
586 ;; Search for class identifiers preceded by ".". The
587 ;; anchored matcher takes it from there.
607 nil
611 ;; Must use a function here since we match longer than we
612 ;; want to move before doing a new search. This is not
613 ;; necessary for XEmacs >= 20 since it restarts the search
614 ;; from the end of the first highlighted submatch (something
615 ;; that causes problems in other places).
627 limit t)
634 c-reference-face-name))
637 ;; Fontify the special declarations in Objective-C.
645 ;; In this case we accept both primitive and known types.
652 ;; The @interface/@implementation/@protocol directives.
656 t)
661 ;; `parse-sexp-lookup-properties' (when it exists).
668 nil))))))
669 ))
672 ;; Called before any of the matchers in `c-complex-decl-matchers'.
673 ;; Nil is always returned.
675 ;;(message "c-font-lock-complex-decl-prepare %s %s" (point) limit)
677 ;; Clear the list of found types if we start from the start of the
678 ;; buffer, to make it easier to get rid of misspelled types and
679 ;; variables that has gotten recognized as types in malformed code.
683 ;; Clear the c-type char properties in the region to recalculate
684 ;; them properly. This is necessary e.g. to handle constructs that
685 ;; might been required as declarations temporarily during editing.
686 ;; The interesting properties are anyway those put on the closest
687 ;; token before the region.
690 ;; Update `c-state-cache' to the beginning of the region. This will
691 ;; make `c-beginning-of-syntax' go faster when it's used later on,
692 ;; and it's near the point most of the time.
695 ;; Check if the fontified region starts inside a declarator list so
696 ;; that `c-font-lock-declarators' should be called at the start.
705 nil)
708 ;; Fontify types and references in names containing angle bracket
709 ;; arglists from the point to LIMIT. This will also fontify cases
710 ;; like normal function calls on the form "foo (a < b, c > d)", but
711 ;; `c-font-lock-declarations' will undo that later. Nil is always
712 ;; returned.
715 ;; `parse-sexp-lookup-properties' (when it exists).
719 id-start id-end pos kwd-sym)
737 ;; Check for comment/string both at the identifier and
738 ;; at the "<".
743 t)
749 c-reference-face-name)
755 nil)
758 ;; Assuming the point is at the start of a declarator in a
759 ;; declaration, fontify it. If LIST is non-nil, fontify also all
760 ;; following declarators in a comma separated list (e.g. "foo" and
761 ;; "bar" in "int foo = 17, bar;"). Stop at LIMIT. If TYPES is
762 ;; non-nil, fontify all identifiers as types. Nil is always
763 ;; returned.
765 ;;(message "c-font-lock-declarators from %s to %s" (point) limit)
768 paren-depth
769 id-face got-init
770 c-last-identifier-range
774 pos
779 ;; Skip over type decl prefix operators. (Note similar
780 ;; code in `c-font-lock-declarations'.)
784 ;; If the second submatch matches in C++ then
785 ;; we're looking at an identifier that's a
786 ;; prefix only if it specifies a member pointer.
791 ;; We only check for a trailing "::" and
792 ;; let the "*" that should follow be
793 ;; matched in the next round.
794 t
795 ;; It turned out to be the real identifier,
796 ;; so flag that and stop.
798 nil))
799 t))
807 ;; If we didn't pass the identifier above already, do it now.
815 ;; Skip out of the parens surrounding the identifier.
821 ;; Search syntactically to the end of the declarator (";",
822 ;; ",", a closen paren, eob etc) or to the beginning of an
823 ;; initializer or function prototype ("=" or "\\s\(").
824 ;; Note that the open paren will match array specs in
825 ;; square brackets, and we treat them as initializers too.
831 'font-lock-function-name-face
837 ;; Register and fontify the identifer as a type.
841 ;; Fontify the last symbol in the identifier if it isn't fontified
842 ;; already. The check is necessary only in certain cases where this
843 ;; function is used "sloppily", e.g. in `c-simple-decl-matchers'.
849 id-face)))
854 ;; Jump past any initializer or function prototype to see if
855 ;; there's a ',' to continue at.
858 ;; Skip a parenthesized initializer (C++) or a function
859 ;; prototype.
865 ;; Skip an initializer expression. If we're at a '='
866 ;; then accept a brace list directly after it to cope
867 ;; with array initializers. Otherwise stop at braces
868 ;; to avoid going past full function and class blocks.
873 t)
879 ;; If a ',' is found we set pos to the next declarator and iterate.
885 nil)
888 ;; List of faces that might be put at the start of a type when
889 ;; `c-font-lock-declarations' runs. This needs to be evaluated to
890 ;; ensure that face name aliases in Emacs are resolved.
892 font-lock-type-face
893 c-reference-face-name
894 font-lock-keyword-face))
896 ;; Macro used inside `c-font-lock-declarations'. It ought to be a
897 ;; defsubst or perhaps even a defun, but it contains lots of free
898 ;; variables that refer to things inside `c-font-lock-declarations'.
900 ;; `c-font-lock-declarations' can consume an arbitrary length list
901 ;; of types when parsing a declaration, which means that it
902 ;; sometimes consumes the identifier in the declaration as a type.
903 ;; This is used to "backtrack" and make the last type be treated
904 ;; as an identifier instead.
907 ;; These identifiers are bound only in the inner let.
909 identifier-start type-start
910 identifier-end type-end))
912 t
913 prev-at-type))
915 type-end prev-type-end)
917 type-end start-pos))
919 ;; These identifiers are bound only in the inner let.
921 got-parens nil
922 got-identifier t
923 got-suffix t
924 got-suffix-after-parens t
928 ;; Fontify all the declarations and casts from the point to LIMIT.
929 ;; Assumes that strings and comments have been fontified already.
930 ;; Nil is always returned.
931 ;;
932 ;; This function can make hidden buffer changes, but the font-lock
933 ;; context covers that.
935 ;;(message "c-font-lock-declarations search from %s to %s" (point) limit)
939 c-restricted-<>-arglists
940 ;; Nonzero if the `c-decl-prefix-re' match is in an arglist context,
941 ;; as opposed to a statement-level context. The major difference is
942 ;; that "," works as declaration delimiter in an arglist context,
943 ;; whereas it only separates declarators in the same declaration in
944 ;; a statement context. If it's nonzero then the value is the
945 ;; matched char, e.g. ?\( or ?,.
946 arglist-match
947 ;; 'decl if we're in an arglist containing declarations (but if
948 ;; `c-recognize-paren-inits' is set it might also be an initializer
949 ;; arglist), '<> if the arglist is of angle bracket type, 'other if
950 ;; it's some other arglist, or nil if not in an arglist at all.
951 arglist-type
952 ;; Set to the result of `c-forward-type'.
953 at-type
954 ;; These record the start and end of the type or possible type found
955 ;; by `c-forward-type'. `type-start' is at the start of the first
956 ;; type token, and `type-end' is at the start of the first token
957 ;; after the type (and after any specifiers).
958 type-start type-end
959 ;; These store `at-type', `type-start' and `type-end' of the
960 ;; identifier before the one in those variables. The previous
961 ;; identifier might turn out to be the real type in a declaration if
962 ;; the last one has to be the declarator in it. If `prev-at-type'
963 ;; is nil then the other variables have undefined values.
964 prev-at-type prev-type-start prev-type-end
965 ;; Whether we've found a declaration or a cast. We might know this
966 ;; before we've found the type in it.
967 at-decl-or-cast
968 ;; Set when we need to back up to parse this as a declaration but
969 ;; not as a cast.
970 backup-if-not-cast
971 ;; Set if we've found a "typedef" specifier. The identifiers in the
972 ;; declaration are then fontified as types.
973 at-typedef
974 ;; Set if we've found a specifier that can start a declaration where
975 ;; there's no type.
976 maybe-typeless
977 ;; The position of the next token after the closing paren of the
978 ;; last fontified cast.
979 last-cast-end
980 ;; The same for the currently investigated cast.
981 cast-end
982 ;; The maximum of the end positions of all the checked type decl
983 ;; expressions in the successfully identified declarations. The
984 ;; position might be either before or after the syntactic whitespace
985 ;; following the last token in the type decl expression.
987 ;; Same as `max-type-decl-*', but used when we're before
988 ;; `token-pos'.
990 ;; Allow recording of identifier ranges in `c-forward-type' etc for
991 ;; later fontification. Not using `c-fontify-types-and-refs' here
992 ;; since the ranges should be fontified selectively only when a
993 ;; declaration or cast has been successfully recognized.
994 c-record-type-identifiers
995 c-record-ref-identifiers
996 ;; The font-lock package in Emacs is known to clobber
997 ;; `parse-sexp-lookup-properties' (when it exists).
1002 ;; Below we fontify a whole declaration even when it crosses the limit,
1003 ;; to avoid gaps when lazy-lock fontifies the file a screenful at a
1004 ;; time. That is however annoying during editing, e.g. the following is
1005 ;; a common situation while the first line is being written:
1006 ;;
1007 ;; my_variable
1008 ;; some_other_variable = 0;
1009 ;;
1010 ;; font-lock will put the limit at the beginning of the second line
1011 ;; here, and if we go past it we'll fontify "my_variable" as a type and
1012 ;; "some_other_variable" as an identifier, and the latter will not
1013 ;; correct itself until the second line is changed. To avoid that we
1014 ;; narrow to the limit if the region to fontify is a single line.
1019 ;; Narrow after any operator chars following the limit though, since
1020 ;; those characters can be useful in recognizing a declaration (in
1021 ;; particular the '{' that opens a function body after the header).
1027 limit
1028 c-identifier-start
1029 c-font-lock-maybe-decl-faces
1033 ;; Don't do anything more if we're looking at a keyword
1034 ;; that can't start a declaration.
1040 ;; Set `arglist-match' and `arglist-type'. Look for "<" for the
1041 ;; sake of C++-style template arglists.
1045 ;; Find out the type of the arglist.
1050 ;; Got a cached hit in a declaration arglist.
1054 ;; Inside an angle bracket arglist.
1057 ;; Got a cached hit in some other type of arglist.
1062 ;; The point is within the range of a previously
1063 ;; encountered type decl expression, so the arglist
1064 ;; is probably one that contains declarations.
1065 ;; However, if `c-recognize-paren-inits' is set it
1066 ;; might also be an initializer arglist.
1068 ;; The result of this check is cached with a char
1069 ;; property on the match token, so that we can look
1070 ;; it up again when refontifying single lines in a
1071 ;; multiline declaration.
1078 arglist-type nil))
1081 at-decl-or-cast nil
1082 backup-if-not-cast nil
1083 at-typedef nil
1084 maybe-typeless nil
1085 c-record-type-identifiers t
1086 c-record-ref-identifiers nil
1087 ;; `start-pos' is used below to point to the start of the
1088 ;; first type, i.e. after any leading specifiers. It might
1089 ;; also point at the beginning of the preceding syntactic
1090 ;; whitespace.
1092 ;; If we're in a normal arglist context we don't want to
1093 ;; recognize commas in nested angle bracket arglists since
1094 ;; those commas could be part of our own arglist.
1095 c-restricted-<>-arglists
1101 ;; We're standing at the start of a normal arglist so remove any
1102 ;; angle bracket arglists containing commas that's been
1103 ;; recognized inside it by the preceding slightly opportunistic
1104 ;; scan in `c-font-lock-<>-arglists'.
1115 ;; Check for a type, but be prepared to skip over leading
1116 ;; specifiers like "static". Unknown symbols are treated as
1117 ;; possible types, but they could also be specifiers disguised
1118 ;; through macros like __INLINE__, so we recognize both types and
1119 ;; known specifiers after them too.
1122 ;; Don't look for a type if we already found a
1123 ;; positive one; we only loop for the
1124 ;; `c-specifier-key' check then.
1128 ;; Found a known or possible type or a prefix of a known
1129 ;; type.
1132 ;; Got two identifiers with nothing but whitespace
1133 ;; between them. That can only happen in
1134 ;; declarations.
1138 ;; If the previous identifier is a found type we
1139 ;; record it as a real one; it might be some sort of
1140 ;; alias for a prefix like "unsigned".
1147 prev-type-start type-start
1148 prev-type-end type-end
1149 at-type res
1150 type-start start
1153 ;; If the type isn't known we continue so that we'll
1154 ;; jump over all specifiers and type identifiers. The
1155 ;; reason to do this for a known type prefix is to make
1156 ;; things like "unsigned INT16" work.
1160 ;; Found a known specifier keyword. The specifier
1161 ;; keywords are restrictive, so we check for them
1162 ;; anywhere inside or around the type(s). We thereby
1163 ;; avoid having special cases for specifiers like MSVC
1164 ;; '__declspec' which can come after the type.
1175 ;; Move type-end forward if we've passed a type,
1176 ;; otherwise move start-pos forward.
1181 res)))
1185 ;; A prefix type is itself a primitive type when it's not
1186 ;; followed by another type.
1190 ;; Got no type but set things up to continue anyway to handle the
1191 ;; various cases when a declaration doesn't start with a type.
1196 ;; If it's C++ then check if the last "type" ends on the form
1197 ;; "foo::foo" or "foo::~foo", i.e. if it's the name of a
1198 ;; (con|de)structor.
1209 ;; Cheating in the handling of syntactic ws below.
1216 name))
1217 ;; It is a (con|de)structor name. In that case the
1218 ;; declaration is typeless so zap out any preceding
1219 ;; identifier(s) that we might have taken as types.
1222 prev-at-type nil
1223 type-end type-start))))))
1225 ;; Check for and step over a type decl expression after the thing
1226 ;; that is or might be a type. This can't be skipped since we need
1227 ;; the correct end position of the declarator for
1228 ;; `max-type-decl-end-*'.
1230 ;; True if there's a non-open-paren match of
1231 ;; `c-type-decl-prefix-key'.
1232 got-prefix
1233 ;; True if the declarator is surrounded by a parenthesis pair.
1234 got-parens
1235 ;; True if there is an identifier in the declarator.
1236 got-identifier
1237 ;; True if there's a non-close-paren match of
1238 ;; `c-type-decl-suffix-key'.
1239 got-suffix
1240 ;; True if there's a prefix or suffix match outside the
1241 ;; outermost paren pair that surrounds the declarator.
1242 got-prefix-before-parens
1243 got-suffix-after-parens
1244 ;; True if we've parsed the type decl to a token that
1245 ;; is known to end declarations in this context.
1246 at-decl-end
1247 ;; The earlier values of `at-type', `type-start' and
1248 ;; `type-end' if we've shifted the type backwards.
1249 identifier-type identifier-start identifier-end)
1252 ;; Skip over type decl prefix operators. (Note similar code in
1253 ;; `c-font-lock-declarators'.)
1257 ;; If the second submatch matches in C++ then
1258 ;; we're looking at an identifier that's a prefix
1259 ;; only if it specifies a member pointer.
1262 ;; We only check for a trailing "::" and
1263 ;; let the "*" that should follow be
1264 ;; matched in the next round.
1266 ;; It turned out to be the real identifier,
1267 ;; so stop.
1268 nil))
1269 t))
1281 ;; Skip over an identifier.
1286 ;; Skip over type decl suffix operators.
1292 t)
1296 t)
1300 ;; No suffix matched. We might have matched the
1301 ;; identifier as a type and the open paren of a function
1302 ;; arglist as a type decl prefix. In that case we
1303 ;; should "backtrack": Reinterpret the last type as the
1304 ;; identifier, move out of the arglist and continue
1305 ;; searching for suffix operators.
1306 ;;
1307 ;; Do this even if there's no preceding type, to cope
1308 ;; with old style function declarations in K&R C,
1309 ;; (con|de)structors in C++ and `c-typeless-decl-kwds'
1310 ;; style declarations. That isn't applicable in an
1311 ;; arglist context, though.
1316 maybe-typeless
1323 t))
1329 at-type
1331 ;; Have found no identifier but `c-typeless-decl-kwds' has
1332 ;; matched so we know we're inside a declaration. The
1333 ;; preceding type must be the identifier instead.
1337 at-decl-or-cast
1341 ;; Encountered something inside parens that isn't matched by
1342 ;; the `c-type-decl-*' regexps, so it's not a type decl
1343 ;; expression. Try to skip out to the same paren depth to
1344 ;; not confuse the cast check below.
1353 ;; Now we've collected info about various characteristics of
1354 ;; the construct we're looking at. Below follows a decision
1355 ;; tree based on that. It's ordered to check more certain
1356 ;; signs before less certain ones.
1363 ;; Got another identifier directly after the type, so
1364 ;; it's a declaration.
1371 ;; Got a declaration of the form "foo bar (gnu);"
1372 ;; where we've recognized "bar" as the type and "gnu"
1373 ;; as the declarator. In this case it's however more
1374 ;; likely that "bar" is the declarator and "gnu" a
1375 ;; function argument or initializer (if
1376 ;; `c-recognize-paren-inits' is set), since the parens
1377 ;; around "gnu" would be superfluous if it's a
1378 ;; declarator. Shift the type one step backward.
1381 ;; Found no identifier.
1388 ;; Got two types after each other, so if this isn't a
1389 ;; cast then the latter probably is the identifier and
1390 ;; we should back up to the previous type.
1395 ;; If the type is known we know that there can't be any
1396 ;; identifier somewhere else, and it's only in
1397 ;; declarations in e.g. function prototypes and in casts
1398 ;; that the identifier may be left out.
1402 ;; Only got a single identifier (parsed as a type so
1403 ;; far).
1405 ;; Check that the identifier isn't at the start of
1406 ;; an expression.
1407 at-decl-end
1410 ;; Inside an arglist that contains declarations.
1411 ;; If K&R style declarations and parenthesis
1412 ;; style initializers aren't allowed then the
1413 ;; single identifier must be a type, else we
1414 ;; require that it's known or found (primitive
1415 ;; types are handled above).
1420 ;; Inside a template arglist. Accept known and
1421 ;; found types; other identifiers could just as
1422 ;; well be constants in C++.
1428 got-parens
1433 prev-at-type
1434 maybe-typeless
1438 c-after-suffixed-type-maybe-decl-key))))))
1439 ;; Got an empty paren pair and a preceding type that
1440 ;; probably really is the identifier. Shift the type
1441 ;; backwards to make the last one the identifier. This
1442 ;; is analogous to the "backtracking" done inside the
1443 ;; `c-type-decl-suffix-key' loop above.
1444 ;;
1445 ;; Exception: In addition to the conditions in that
1446 ;; "backtracking" code, do not shift backward if we're
1447 ;; not looking at either `c-after-suffixed-type-decl-key'
1448 ;; or "[;,]". Since there's no preceding type, the
1449 ;; shift would mean that the declaration is typeless.
1450 ;; But if the regexp doesn't match then we will simply
1451 ;; fall through in the tests below and not recognize it
1452 ;; at all, so it's better to try it as an abstract
1453 ;; declarator instead.
1456 ;; Still no identifier.
1459 ;; Require `got-prefix' together with either
1460 ;; `got-parens' or `got-suffix' to recognize it as an
1461 ;; abstract declarator: `got-parens' only is probably an
1462 ;; empty function call. `got-suffix' only can build an
1463 ;; ordinary expression together with the preceding
1464 ;; identifier which we've taken as a type. We could
1465 ;; actually accept on `got-prefix' only, but that can
1466 ;; easily occur temporarily while writing an expression
1467 ;; so we avoid that case anyway. We could do a better
1468 ;; job if we knew the point when the fontification was
1469 ;; invoked.
1473 ;; By now we've located the type in the declaration that we
1474 ;; know we're in.
1484 ;; Shift the type backward in the case that
1485 ;; there's a single identifier inside parens.
1486 ;; That can only occur in K&R style function
1487 ;; declarations so it's more likely that it
1488 ;; really is a function call. Therefore we
1489 ;; only do this after
1490 ;; `c-after-suffixed-type-decl-key' has
1491 ;; matched.
1493 got-suffix-after-parens))
1494 ;; A declaration according to
1495 ;; `c-after-suffixed-type-decl-key'.
1500 ;; It's a declaration if a known type precedes it and it
1501 ;; can't be a function call.
1504 ;; If we get here we can't tell if this is a type decl or a
1505 ;; normal expression by looking at it alone. (That's under
1506 ;; the assumption that normal expressions always can look like
1507 ;; type decl expressions, which isn't really true but the
1508 ;; cases where it doesn't hold are so uncommon (e.g. some
1509 ;; placements of "const" in C++) it's not worth the effort to
1510 ;; look for them.)
1513 ;; If this is a declaration it should end here or its
1514 ;; initializer(*) should start here, so check for allowed
1515 ;; separation tokens. Note that this rule doesn't work
1516 ;; e.g. with a K&R arglist after a function header.
1517 ;;
1518 ;; *) Don't check for C++ style initializers using parens
1519 ;; since those already have been matched as suffixes.
1522 ;; Below are tests that only should be applied when we're
1523 ;; certain to not have parsed halfway through an expression.
1526 ;; The expression starts with a known type so treat it as a
1527 ;; declaration.
1531 ;; In C++ we check if the identifier is a known
1532 ;; type, since (con|de)structors use the class name
1533 ;; as identifier. We've always shifted over the
1534 ;; identifier as a type and then backed up again in
1535 ;; this case.
1536 identifier-type
1539 ;; `at-type' probably won't be 'found for
1540 ;; destructors since the "~" is then part
1541 ;; of the type name being checked against
1542 ;; the list of known types, so do a check
1543 ;; without that operator.
1548 c-identifier-syntax-table
1551 identifier-end)))))
1557 at-type
1561 ;; Got something like "foo * bar;". Since we're not
1562 ;; inside an arglist it would be a meaningless
1563 ;; expression because the result isn't used. We
1564 ;; therefore choose to recognize it as a declaration.
1565 ;; Do not allow a suffix since it could then be a
1566 ;; function call.
1573 ;; Got something like "a (*b) (c);" or "a (b) = c;".
1574 ;; It could be an odd expression or it could be a
1575 ;; declaration. Treat it as a declaration if "a" has
1576 ;; been used as a type somewhere else (if it's a known
1577 ;; type we won't get here).
1585 ;; Got a type followed by an abstract declarator. If
1586 ;; `got-prefix' is set it's something like "a *" without
1587 ;; anything after it. If `got-parens' or `got-suffix' is
1588 ;; set it's "a()", "a[]", "a()[]", or similar, which we
1589 ;; accept only if the context rules out expressions.
1592 ;; If we had a complete symbol table here (which rules out
1593 ;; `c-found-types') we should return t due to the
1594 ;; disambiguation rule (in at least C++) that anything that
1595 ;; can be parsed as a declaration is a declaration. Now we're
1596 ;; being more defensive and prefer to highlight things like
1597 ;; "foo (bar);" as a declaration only if we're inside an
1598 ;; arglist that contains declarations.
1601 ;; Point is now after the type decl expression.
1604 ;; Check for a cast.
1607 c-cast-parens
1609 ;; Should be the first type/identifier in a cast paren.
1612 ;; The closing paren should follow.
1617 ;; There should be a primary expression after it.
1626 ;; Check if the expression begins with a prefix
1627 ;; keyword.
1630 ;; Expression begins with an ambiguous operator.
1631 ;; Treat it as a cast if it's a type decl or if
1632 ;; we've recognized the type somewhere else.
1635 ;; Unless it's a keyword, it's the beginning of a
1636 ;; primary expression.
1638 ;; If `c-primary-expr-regexp' matched a nonsymbol
1639 ;; token, check that it matched a whole one so that we
1640 ;; don't e.g. confuse the operator '-' with '->'. It's
1641 ;; ok if it matches further, though, since it e.g. can
1642 ;; match the float '.5' while the operator regexp only
1643 ;; matches '.'.
1647 ;; There should either be a cast before it or something that
1648 ;; isn't an identifier or close paren.
1656 ;; It's a symbol. Accept it only if it's one of
1657 ;; the keywords that can precede an expression
1658 ;; (without surrounding parens).
1661 ;; Check that it isn't a close paren (block close
1662 ;; is ok, though).
1664 ;; Check that it isn't a nonsymbol identifier.
1667 ;; Handle the cast.
1675 ;; We're at a declaration. Highlight the type and the following
1676 ;; declarators.
1682 ;; Make sure to propagate the `c-decl-arg-start' property to
1683 ;; the next argument if it's set in this one, to cope with
1684 ;; interactive refontification.
1687 ;; Set `max-type-decl-end' or `max-type-decl-end-before-token'
1688 ;; under the assumption that we're after the first type decl
1689 ;; expression in the declaration now. That's not really true; we
1690 ;; could also be after a parenthesized initializer expression in
1691 ;; C++, but this is only used as a last resort to slant ambiguous
1692 ;; expression/declarations, and overall it's worth the risk to
1693 ;; occasionally fontify an expression as a declaration in an
1694 ;; initializer expression compared to getting ambiguous things in
1695 ;; normal function prototypes fontified as expressions.
1711 ;; Should normally not fontify a list of declarators
1712 ;; inside an arglist, but the first argument in the
1713 ;; ';' separated list of a "for" statement is an
1714 ;; exception.
1721 t)))
1723 ;; Fix the `c-decl-id-start' or `c-decl-type-start' property
1724 ;; before the first declarator if it's a list.
1725 ;; `c-font-lock-declarators' handles the rest.
1732 'c-decl-type-start
1738 ;; False alarm. Skip the fontification done below.
1741 ;; A cast or declaration has been successfully identified, so do
1742 ;; all the fontification of types and refs that's been recorded by
1743 ;; the calls to `c-forward-type' and `c-forward-name' above.
1745 nil)))
1747 nil)))
1750 "Simple font lock matchers for types and declarations. These are used
1751 on level 2 only and so aren't combined with `c-complex-decl-matchers'."
1759 ;; `parse-sexp-lookup-properties' (when it exists).
1766 nil))
1769 ;; Fontify all type names and the identifiers in the
1770 ;; declarations they might start. Use eval here since
1771 ;; `c-known-type-key' gets its value from
1772 ;; `*-font-lock-extra-types' on mode init.
1774 'c-known-type-key
1782 ;; Fontify types preceded by `c-type-prefix-kwds' and the
1783 ;; identifiers in the declarations they might start.
1799 ;; Fontify special declarations that lacks a type.
1810 ))
1813 "Complex font lock matchers for types and declarations. Used on level
1814 3 and higher."
1817 c-font-lock-complex-decl-prepare
1819 ;; Fontify angle bracket arglists like templates in C++.
1824 ;; Fontify method declarations in Objective-C, but first
1825 ;; we have to put the `c-decl-end' `c-type' property on
1826 ;; all the @-style directives that haven't been handled in
1827 ;; `c-basic-matchers-before'.
1830 ;; Exclude "@class" since that directive ends with a
1831 ;; semicolon anyway.
1835 nil)))
1839 c-font-lock-objc-methods)
1847 ;; Fontify all declarations and casts.
1848 c-font-lock-declarations
1850 ;; The first two rules here mostly find occurences that
1851 ;; `c-font-lock-declarations' has found already, but not
1852 ;; declarations containing blocks in the type (see note below).
1853 ;; It's also useful to fontify these everywhere to show e.g. when
1854 ;; a type keyword is accidentally used as an identifier.
1856 ;; Fontify basic types.
1860 ;; No symbol is a keyword after "->" in Pike.
1867 ;; Fontify types preceded by `c-type-prefix-kwds'.
1873 ;; The font-lock package in Emacs is known to clobber
1874 ;; `parse-sexp-lookup-properties' (when it exists).
1879 ;; Narrow to avoid going past the limit in
1880 ;; `c-forward-type'.
1887 limit t)
1890 ;; Handle prefix declaration specifiers.
1896 ;; In C++ we additionally check for a "class
1897 ;; X = Y" construct which is used in
1898 ;; templates, to fontify Y as a type.
1903 )))))))))
1905 ;; Fontify symbols after closing braces as declaration
1906 ;; identifiers under the assumption that they are part of
1907 ;; declarations like "class Foo { ... } foo;". It's too
1908 ;; expensive to check this accurately by skipping past the
1909 ;; brace block, so we use the heuristic that it's such a
1910 ;; declaration if the first identifier is on the same line as
1911 ;; the closing brace. `c-font-lock-declarations' will later
1912 ;; override it if it turns out to be an new declaration, but
1913 ;; it will be wrong if it's an expression (see the test
1914 ;; decls-8.cc).
1930 c-single-line-syntactic-ws-depth)))))
1933 ;; Fontify the type in C++ "new" expressions.
1937 ))
1940 ;; Fontify all the declarations from the point to LIMIT. Assumes
1941 ;; that strings and comments have been fontified already. Nil is
1942 ;; always returned.
1943 ;;
1944 ;; This function can make hidden buffer changes, but the font-lock
1945 ;; context covers that.
1948 ;; The font-lock package in Emacs is known to clobber
1949 ;; `parse-sexp-lookup-properties' (when it exists).
1968 ;; Check for a char that precedes a statement.
1970 ;; Check for a preceding label. We exploit the font
1971 ;; locking made earlier by this function.
1978 c-label-face-name))
1979 ;; Check for a keyword that precedes a statement.
1983 ;; Got a label.
1987 c-label-face-name)))
1990 nil)
1993 "Font lock matchers for various things that should be fontified after
1994 generic casts and declarations are fontified. Used on level 2 and
1995 higher."
1998 ;; name is handled by `c-simple-decl-matchers' or
1999 ;; `c-complex-decl-matchers' below.
2006 ;; Disallow various common punctuation chars that can't come
2007 ;; before the '{' of the enum list, to avoid searching too far.
2008 "[^\]\[{}();,/#=]*"
2018 ;; Fontify labels in languages that supports them.
2022 ;; (Got three different interpretation levels here,
2023 ;; which makes it a bit complicated: 1) The backquote
2024 ;; stuff is expanded when compiled or loaded, 2) the
2025 ;; eval form is evaluated at font-lock setup (to
2026 ;; substitute c-label-face-name correctly), and 3) the
2027 ;; resulting structure is interpreted during
2028 ;; fontification.)
2040 c-label-face-name nil t))))
2042 ;; Fontify normal labels.
2043 c-font-lock-labels))
2045 ;; Fontify the clauses after various keywords.
2061 ))
2079 ;; Incorporate the font lock keyword lists according to
2080 ;; `c-doc-comment-style' on the given keyword list and return it.
2081 ;; This is used in the function bindings of the
2082 ;; `*-font-lock-keywords-*' symbols since we have to build the list
2083 ;; when font-lock is initialized.
2092 c-doc-comment-style))
2104 doc-keywords
2106 base-list)))
2108 ;; Kludge: If `c-font-lock-complex-decl-prepare' is on the list we
2109 ;; move it first since the doc comment font lockers might add
2110 ;; `c-type' text properties, so they have to be cleared before that.
2116 list))
2119 ;; This is used to override the value on a `*-font-lock-keywords'
2120 ;; variable only if it's nil or has the same value as one of the
2121 ;; `*-font-lock-keywords-*' variables. Older font-lock packages
2122 ;; define a default value for `*-font-lock-keywords' which we want
2123 ;; to override, but we should otoh avoid clobbering a user setting.
2124 ;; This heuristic for that isn't perfect, but I can't think of any
2125 ;; better. /mast
2126 ;;
2127 ;; This function does not do any hidden buffer changes.
2134 suffix))))
2137 ;; The overriding is done by unbinding the variable so that the normal
2138 ;; defvar will install its default value later on.
2141 \f
2142 ;;; C.
2147 "Minimal font locking for C mode.
2148 Fontifies only preprocessor directives (in addition to the syntactic
2152 "Fast normal font locking for C mode.
2153 In addition to `c-font-lock-keywords-1', this adds fontification of
2154 keywords, simple types, declarations that are easy to recognize, the
2155 user defined types on `c-font-lock-extra-types', and the doc comment
2159 "Accurate normal font locking for C mode.
2160 Like `c-font-lock-keywords-2' but detects declarations in a more
2161 accurate way that works in most cases for arbitrary types without the
2174 \f
2175 ;;; C++.
2178 ;; Assuming point is after a "new" word, check that it isn't inside
2179 ;; a string or comment, and if so try to fontify the type in the
2180 ;; allocation expression. Nil is always returned.
2181 ;;
2182 ;; As usual, C++ takes the prize in coming up with a hard to parse
2183 ;; syntax. :P
2188 ;; A "new" keyword is followed by one to three expressions, where
2189 ;; the type is the middle one, and the only required part.
2191 ;; Enable recording of identifier ranges in `c-forward-type'
2192 ;; etc for later fontification. Not using
2193 ;; `c-fontify-types-and-refs' here since the ranges should
2194 ;; be fontified selectively only when an allocation
2195 ;; expression is successfully recognized.
2197 c-record-ref-identifiers
2198 ;; The font-lock package in Emacs is known to clobber
2199 ;; `parse-sexp-lookup-properties' (when it exists).
2205 ;; The first placement arglist is always parenthesized, if it
2206 ;; exists.
2214 ;; The second expression is either a type followed by some "*" or
2215 ;; "[...]" or similar, or a parenthesized type followed by a full
2216 ;; identifierless declarator.
2226 ;; No second expression, so the first has to be a
2227 ;; parenthesized type.
2233 ;; Got two parenthesized expressions, so we have to look
2234 ;; closer at them to decide which is the type. No need to
2235 ;; handle `c-record-ref-identifiers' since all references
2236 ;; has already been handled by other fontification rules.
2245 ;; There's something after the would-be type that
2246 ;; can't be there, so this is a placement arglist.
2255 ;; There's something after the would-be type that can't
2256 ;; be there, so this is an initialization expression.
2261 ;; If there's a third initialization expression
2262 ;; then the second one is the type, so demote the
2263 ;; first match.
2266 ;; We fontify the most likely type, with a preference for
2267 ;; the first argument since a placement arglist is more
2268 ;; unusual than an initializer.
2287 ;; If both type matches are 'maybe then we're
2288 ;; too uncertain to promote either of them.
2289 )))))
2291 ;; Fontify the type that now is recorded in
2292 ;; `c-record-type-identifiers', if any.
2294 nil)
2299 "Minimal font locking for C++ mode.
2300 Fontifies only preprocessor directives (in addition to the syntactic
2304 "Fast normal font locking for C++ mode.
2305 In addition to `c++-font-lock-keywords-1', this adds fontification of
2306 keywords, simple types, declarations that are easy to recognize, the
2307 user defined types on `c++-font-lock-extra-types', and the doc comment
2311 "Accurate normal font locking for C++ mode.
2312 Like `c++-font-lock-keywords-2' but detects declarations in a more
2313 accurate way that works in most cases for arbitrary types without the
2326 \f
2327 ;;; Objective-C.
2330 ;; Assuming the point is after an "@interface", "@implementation",
2331 ;; "@protocol" declaration, fontify all the types in the directive.
2332 ;; Return t if the directive was fully recognized. Point will then
2333 ;; be at the end of it.
2338 ;; Turn off recognition of angle bracket arglists while parsing
2339 ;; types here since the protocol reference list might then be
2340 ;; considered part of the preceding name or superclass-name.
2344 ;; Handle the name of the class itself.
2348 ;; Look for ": superclass-name" or "( category-name )".
2359 ;; Look for a protocol reference list.
2364 t)
2366 t))))
2369 ;; Assuming the point is after the + or - that starts an Objective-C
2370 ;; method declaration, fontify it. This must be done before normal
2371 ;; casts, declarations and labels are fontified since they will get
2372 ;; false matches in these things.
2382 ;; An optional method type.
2390 t))
2392 ;; The name. The first time it's the first part of
2393 ;; the function name, the rest of the time it's an
2394 ;; argument name.
2401 'font-lock-function-name-face
2405 ;; Another optional part of the function name.
2413 ;; There's another argument if a colon follows.
2419 ;; Fontify method declarations in Objective-C. Nil is always
2420 ;; returned.
2423 ;; `parse-sexp-lookup-properties' (when it exists).
2429 limit
2430 "[-+]"
2431 nil
2435 nil)
2440 "Minimal font locking for Objective-C mode.
2441 Fontifies only compiler directives (in addition to the syntactic
2445 "Fast normal font locking for Objective-C mode.
2446 In addition to `objc-font-lock-keywords-1', this adds fontification of
2447 keywords, simple types, declarations that are easy to recognize, the
2448 user defined types on `objc-font-lock-extra-types', and the doc
2452 "Accurate normal font locking for Objective-C mode.
2453 Like `objc-font-lock-keywords-2' but detects declarations in a more
2454 accurate way that works in most cases for arbitrary types without the
2467 ;; Kludge to override the default value that
2468 ;; `objc-font-lock-extra-types' might have gotten from the font-lock
2469 ;; package. The value replaced here isn't relevant now anyway since
2470 ;; those types are builtin and therefore listed directly in
2471 ;; `c-primitive-type-kwds'.
2477 \f
2478 ;;; Java.
2483 "Minimal font locking for Java mode.
2484 Fontifies nothing except the syntactic fontification of strings and
2488 "Fast normal font locking for Java mode.
2489 In addition to `java-font-lock-keywords-1', this adds fontification of
2490 keywords, simple types, declarations that are easy to recognize, the
2491 user defined types on `java-font-lock-extra-types', and the doc
2495 "Accurate normal font locking for Java mode.
2496 Like `java-font-lock-keywords-2' but detects declarations in a more
2497 accurate way that works in most cases for arbitrary types without the
2510 \f
2511 ;;; CORBA IDL.
2516 "Minimal font locking for CORBA IDL mode.
2517 Fontifies nothing except the syntactic fontification of strings and
2521 "Fast normal font locking for CORBA IDL mode.
2522 In addition to `idl-font-lock-keywords-1', this adds fontification of
2523 keywords, simple types, declarations that are easy to recognize, the
2524 user defined types on `idl-font-lock-extra-types', and the doc comment
2528 "Accurate normal font locking for CORBA IDL mode.
2529 Like `idl-font-lock-keywords-2' but detects declarations in a more
2530 accurate way that works in most cases for arbitrary types without the
2543 \f
2544 ;;; Pike.
2549 "Minimal font locking for Pike mode.
2550 Fontifies only preprocessor directives (in addition to the syntactic
2554 "Fast normal font locking for Pike mode.
2555 In addition to `pike-font-lock-keywords-1', this adds fontification of
2556 keywords, simple types, declarations that are easy to recognize, the
2557 user defined types on `pike-font-lock-extra-types', and the doc
2561 "Accurate normal font locking for Pike mode.
2562 Like `pike-font-lock-keywords-2' but detects declarations in a more
2563 accurate way that works in most cases for arbitrary types without the
2576 \f
2577 ;;; Doc comments.
2580 ;; Fontify the comments between the point and LIMIT whose start
2581 ;; matches PREFIX with `c-doc-face-name'. Assumes comments have been
2582 ;; fontified with `font-lock-comment-face' already. nil is always
2583 ;; returned.
2584 ;;
2585 ;; After the fontification of a matching comment, fontification
2586 ;; according to KEYWORDS is applied inside it. It's a list like
2587 ;; `font-lock-keywords' except that anchored matches and eval
2588 ;; clauses aren't supported and that some abbreviated forms can't be
2589 ;; used. The buffer is narrowed to the comment while KEYWORDS is
2590 ;; applied; leading comment starters are included but trailing
2591 ;; comment enders for block comment are not.
2592 ;;
2593 ;; Note that faces added through KEYWORDS should never replace the
2594 ;; existing `c-doc-face-name' face since the existence of that face
2595 ;; is used as a flag in other code to skip comments.
2600 ;; Handle the case when the fontified region starts inside a
2601 ;; comment.
2610 comment-beg
2612 ;; Search for the prefix until a match is found at the start
2613 ;; of a comment.
2617 c-literal-faces))
2620 c-literal-faces))))
2625 ;; Collect a sequence of doc style line comments.
2642 ;; Narrow to the doc comment. Among other things, this
2643 ;; helps by making "^" match at the start of the comment.
2644 ;; Do not include a trailing block comment ender, though.
2668 nil)
2672 ;; Used to fontify invalid markup in doc comments after the correct
2673 ;; ones have been fontified: Find the first occurence of REGEXP
2674 ;; between the point and LIMIT that only is fontified with
2675 ;; `c-doc-face-name'. If a match is found then submatch 0 surrounds
2676 ;; the first char and t is returned, otherwise nil is returned.
2681 c-doc-face-name))
2686 t)))
2701 ;; Fontify remaining markup characters as invalid. Note
2702 ;; that the Javadoc spec is hazy about when "@" is
2703 ;; allowed in non-markup use.
2711 javadoc-font-lock-doc-comments)))))
2714 ;; Adorned regexp matching the keywords that introduce declarations
2715 ;; in Pike Autodoc.
2720 ;; Adorned regexp matching the keywords that are followed by a type.
2725 ;; Fontify all line oriented keywords between the point and LIMIT.
2726 ;; Nil is always returned.
2729 c-current-comment-prefix
2740 end)
2744 ;; Put a declaration end mark at the markup keyword and
2745 ;; remove the faces from the rest of the line so that it
2746 ;; gets refontified as a declaration later on by
2747 ;; `c-font-lock-declarations'.
2763 ;; Include the final newline in the removed area. This
2764 ;; has no visual effect but it avoids some tricky special
2765 ;; cases in the testsuite wrt the differences in string
2766 ;; fontification in Emacs vs XEmacs.
2769 ;; Must handle string literals explicitly inside the declaration.
2777 ;; Fontify types after keywords that always are followed
2778 ;; by them.
2786 ;; Mark each whole line as markup, as long as the logical line
2787 ;; continues.
2791 markup-faces)
2799 nil)
2803 ;; In-text markup.
2806 ;; Fontify remaining markup characters as invalid.
2810 ))
2813 ;; Note that we depend on that `c-current-comment-prefix' has got
2814 ;; its proper value here.
2816 ;; The `c-type' text property with `c-decl-end' is used to mark the
2817 ;; end of the `autodoc-decl-keywords' occurrences to fontify the
2818 ;; following declarations.
2823 autodoc-font-lock-doc-comments)))))
2825 \f
2826 ;; AWK.
2828 ;; Awk regexps written with help from Peter Galbraith
2829 ;; <galbraith@mixing.qc.dfo.ca>.
2830 ;; Take GNU Emacs's 'words out of the following regexp-opts. They dont work
2831 ;; in Xemacs 21.4.4. acm 2002/9/19.
2836 ;; Function names.
2839 ;;
2840 ;; Variable names.
2850 ;; Special file names. (acm, 2002/7/22)
2851 ;; The following regexp was created by first evaluating this in GNU Emacs 21.1:
2852 ;; (c-regexp-opt '("/dev/stdin" "/dev/stdout" "/dev/stderr" "/dev/fd/n" "/dev/pid"
2853 ;; "/dev/ppid" "/dev/pgrpid" "/dev/user") 'words)
2854 ;; , removing the "?:" from each "\\(?:" (for backward compatibility with older Emacsen)
2855 ;; , replacing the "n" in "dev/fd/n" with "[0-9]+"
2856 ;; , removing the unwanted \\< at the beginning, and finally filling out the
2857 ;; regexp so that a " must come before, and either a " or heuristic stuff after.
2858 ;; The surrounding quotes are fontified along with the filename, since, semantically,
2859 ;; they are an indivisible unit.
2865 ;; Do the same (almost) with
2866 ;; (c-regexp-opt '("/inet/tcp/lport/rhost/rport" "/inet/udp/lport/rhost/rport"
2867 ;; "/inet/raw/lport/rhost/rport") 'words)
2868 ;; This cannot be combined with the above pattern, because the match number
2869 ;; for the (optional) closing \" would then exceed 9.
2875 ;; Keywords.
2883 ;; Builtins.
2898 ;; gawk debugging keywords. (acm, 2002/7/21)
2899 ;; (Removed, 2003/6/6. These functions are now fontified as built-ins)
2900 ;; (list (concat "\\<" (c-regexp-opt '("adump" "stopme") t) "\\>")
2901 ;; 0 'font-lock-warning-face)
2903 ;; User defined functions with an apparent spurious space before the
2904 ;; opening parenthesis. acm, 2002/5/30.
2909 ;; Space after \ in what looks like an escaped newline. 2002/5/31
2912 ;; Unbalanced string (") or regexp (/) delimiters. 2002/02/16.
2914 ;; gawk 3.1 localizable strings ( _"translate me!"). 2002/5/21
2917 ))
2920 \f
2923 ;;; arch-tag: 2f65f405-735f-4da5-8d4b-b957844c5203
2924 ;;; cc-fonts.el ends here