;;; cc-vars.el --- user customization variables for CC Mode
-;; Copyright (C) 1985,1987,1992-2001 Free Software Foundation, Inc.
+;; Copyright (C) 1985,1987,1992-2003 Free Software Foundation, Inc.
-;; Authors: 2000- Martin Stjernholm
-;; 1998-1999 Barry A. Warsaw and Martin Stjernholm
-;; 1992-1997 Barry A. Warsaw
+;; Authors: 1998- Martin Stjernholm
+;; 1992-1999 Barry A. Warsaw
;; 1987 Dave Detlefs and Stewart Clamen
;; 1985 Richard M. Stallman
;; Maintainer: bug-cc-mode@gnu.org
;; GNU General Public License for more details.
;; You should have received a copy of the GNU General Public License
-;; along with this program; see the file COPYING. If not, write to
+;; along with GNU Emacs; see the file COPYING. If not, write to
;; the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
(stringp byte-compile-dest-file))
(cons (file-name-directory byte-compile-dest-file) load-path)
load-path)))
- (require 'cc-bytecomp)))
+ (load "cc-bytecomp" nil t)))
(cc-require 'cc-defs)
(progn
(require 'custom)
(or (fboundp 'defcustom) (error ""))
- (require 'wid-edit)
+ (require 'widget)
'(progn ; Compile in the require's.
(require 'custom)
- (require 'wid-edit)))
+ (require 'widget)))
(error
(message "Warning: Compiling without Customize support \
since a (good enough) custom library wasn't found")
(cc-bytecomp-defmacro define-widget (name class doc &rest args))
+ (cc-bytecomp-defmacro defgroup (symbol members doc &rest args))
(cc-bytecomp-defmacro defcustom (symbol value doc &rest args)
`(defvar ,symbol ,value ,doc))
+ (cc-bytecomp-defmacro custom-declare-variable (symbol value doc
+ &rest args)
+ `(defvar ,(eval symbol) ,(eval value) ,doc))
nil))))
+(cc-eval-when-compile
+ ;; Need the function form of `backquote', which isn't standardized
+ ;; between Emacsen. It's called `bq-process' in XEmacs, and
+ ;; `backquote-process' in Emacs. `backquote-process' returns a
+ ;; slightly more convoluted form, so let `bq-process' be the norm.
+ (if (fboundp 'backquote-process)
+ (cc-bytecomp-defmacro bq-process (form)
+ `(cdr (backquote-process ,form)))))
+
\f
;;; Helpers
-;; This widget will show up in newer versions of the Custom library
+;; This widget exists in newer versions of the Custom library
(or (get 'other 'widget-type)
(define-widget 'other 'sexp
"Matches everything, but doesn't let the user edit the value.
(match-string 0 value)))
value)))
+(define-widget 'c-integer-or-nil 'sexp
+ "An integer or the value nil."
+ :value nil
+ :tag "Optional integer"
+ :match (lambda (widget value) (or (integerp value) (null value))))
+
+(define-widget 'c-symbol-list 'sexp
+ "A single symbol or a list of symbols."
+ :tag "Symbols separated by spaces"
+ :validate 'widget-field-validate
+ :match
+ (lambda (widget value)
+ (or (symbolp value)
+ (catch 'ok
+ (while (listp value)
+ (unless (symbolp (car value))
+ (throw 'ok nil))
+ (setq value (cdr value)))
+ (null value))))
+ :value-to-internal
+ (lambda (widget value)
+ (cond ((null value)
+ "")
+ ((symbolp value)
+ (symbol-name value))
+ ((consp value)
+ (mapconcat (lambda (symbol)
+ (symbol-name symbol))
+ value
+ " "))
+ (t
+ value)))
+ :value-to-external
+ (lambda (widget value)
+ (if (stringp value)
+ (let (list end)
+ (while (string-match "\\S +" value end)
+ (setq list (cons (intern (match-string 0 value)) list)
+ end (match-end 0)))
+ (if (and list (not (cdr list)))
+ (car list)
+ (nreverse list)))
+ value)))
+
(defvar c-style-variables
- '(c-basic-offset c-comment-only-line-offset c-block-comment-prefix
- c-comment-prefix-regexp c-cleanup-list c-hanging-braces-alist
- c-hanging-colons-alist c-hanging-semi&comma-criteria c-backslash-column
+ '(c-basic-offset c-comment-only-line-offset c-indent-comment-alist
+ c-indent-comments-syntactically-p c-block-comment-prefix
+ c-comment-prefix-regexp c-doc-comment-style c-cleanup-list
+ c-hanging-braces-alist c-hanging-colons-alist
+ c-hanging-semi&comma-criteria c-backslash-column c-backslash-max-column
c-special-indent-hook c-label-minimum-indentation c-offsets-alist)
"List of the style variables.")
+(defvar c-fallback-style nil)
+
+(defsubst c-set-stylevar-fallback (name val)
+ (put name 'c-stylevar-fallback val)
+ (setq c-fallback-style (cons (cons name val) c-fallback-style)))
+
(defmacro defcustom-c-stylevar (name val doc &rest args)
"Defines a style variable."
- `(progn
- (put ',name 'c-stylevar-fallback ,val)
- (defcustom ,name 'set-from-style
- ,(concat doc "
+ `(let ((-value- ,val))
+ (c-set-stylevar-fallback ',name -value-)
+ (custom-declare-variable
+ ',name ''set-from-style
+ ,(concat doc "
This is a style variable. Apart from the valid values described
above, it can be set to the symbol `set-from-style'. In that case, it
takes its value from the style system (see `c-default-style' and
-`c-styles-alist') when a CC Mode buffer is initialized. Otherwise,
+`c-style-alist') when a CC Mode buffer is initialized. Otherwise,
the value set here overrides the style system (there is a variable
`c-old-style-variable-behavior' that changes this, though).")
- ,@(plist-put
- args ':type
- `'(radio
- (const :tag "Use style settings"
- set-from-style)
- ,(let ((type (eval (plist-get args ':type))))
- (unless (consp type)
- (setq type (list type)))
- (unless (c-safe (plist-get (cdr type) ':value))
- (setcdr type (append `(:value ,val)
- (cdr type))))
- (unless (c-safe (plist-get (cdr type) ':tag))
- (setcdr type (append '(:tag "Override style settings")
- (cdr type))))
- type))))))
+ ,@(plist-put
+ args ':type
+ `(` (radio
+ (const :tag "Use style settings"
+ set-from-style)
+ ,(, (let ((type (eval (plist-get args ':type))))
+ (unless (consp type)
+ (setq type (list type)))
+ (unless (c-safe (plist-get (cdr type) ':value))
+ (setcdr type (append '(:value (, -value-))
+ (cdr type))))
+ (unless (c-safe (plist-get (cdr type) ':tag))
+ (setcdr type (append '(:tag "Override style settings")
+ (cdr type))))
+ (bq-process type)))))))))
(defun c-valid-offset (offset)
"Return non-nil iff OFFSET is a valid offset for a syntactic symbol.
See `c-offsets-alist'."
+ ;; This function does not do any hidden buffer changes.
(or (eq offset '+)
(eq offset '-)
(eq offset '++)
(eq offset '*)
(eq offset '/)
(integerp offset)
- (vectorp offset)
(functionp offset)
(and (symbolp offset)
(or (boundp offset)
(fboundp offset)))
+ (and (vectorp offset)
+ (= (length offset) 1)
+ (integerp (elt offset 0)))
(progn
(while (and (consp offset)
(c-valid-offset (car offset)))
:type 'boolean
:group 'c)
+(defcustom c-report-syntactic-errors nil
+ "*If non-nil, certain syntactic errors are reported with a ding
+and a message, for example when an \"else\" is indented for which
+there's no corresponding \"if\".
+
+Note however that CC Mode doesn't make any special effort to check for
+syntactic errors; that's the job of the compiler. The reason it can
+report cases like the one above is that it can't find the correct
+anchoring position to indent the line in that case."
+ :type 'boolean
+ :group 'c)
+
(defcustom-c-stylevar c-basic-offset 4
"*Amount of basic offset used by + and - symbols in `c-offsets-alist'.
Also used as the indentation step when `c-syntactic-indentation' is
Note: indentation of lines containing only comments is also controlled
by the `c-comment-only-line-offset' variable."
:type '(radio
- :extra-offset 8
- :format "%{C Tab Always Indent%}:\n The TAB key:\n%v"
- (const :tag "always indents, never inserts TAB" t)
- (const :tag "indents in left margin, otherwise inserts TAB" nil)
- (other :tag "inserts TAB in literals, otherwise indent" other))
+ (const :tag "TAB key always indents, never inserts TAB" t)
+ (const :tag "TAB key indents in left margin, otherwise inserts TAB" nil)
+ (other :tag "TAB key inserts TAB in literals, otherwise indents" other))
:group 'c)
(defcustom c-insert-tab-function 'insert-tab
(defcustom c-syntactic-indentation t
"*Whether the indentation should be controlled by the syntactic context.
-If t, the indentation functions indents according to the syntactic
+If t, the indentation functions indent according to the syntactic
context, using the style settings specified by `c-offsets-alist'.
If nil, every line is just indented to the same level as the previous
-one, and the \\[c-indent-command] command adjusts the indentation in steps
-specified by `c-basic-offset'. The indentation style have no effect
-in this mode, nor any of the indentation associated variables,
+one, and the \\[c-indent-command] command adjusts the indentation in
+steps specified by `c-basic-offset'. The indentation style has no
+effect in this mode, nor any of the indentation associated variables,
e.g. `c-special-indent-hook'."
:type 'boolean
:group 'c)
+(defcustom c-syntactic-indentation-in-macros t
+ "*Enable syntactic analysis inside macros.
+If this is nil, all lines inside macro definitions are analyzed as
+`cpp-macro-cont'. Otherwise they are analyzed syntactically, just
+like normal code, and `cpp-define-intro' is used to create the
+additional indentation of the bodies of \"#define\" macros.
+
+Having this enabled simplifies editing of large multiline macros, but
+it might complicate editing if CC Mode doesn't recognize the context
+of the macro content. The default context inside the macro is the
+same as the top level, so if it contains \"bare\" statements they
+might be indented wrongly, although there are special cases that
+handle this in most cases. If this problem occurs, it's usually
+countered easily by surrounding the statements by a block \(or even
+better with the \"do { ... } while \(0)\" trick)."
+ :type 'boolean
+ :group 'c)
+
(defcustom-c-stylevar c-comment-only-line-offset 0
"*Extra offset for line which contains only the start of a comment.
Can contain an integer or a cons cell of the form:
:type '(choice (integer :tag "Non-anchored offset" 0)
(cons :tag "Non-anchored & anchored offset"
:value (0 . 0)
- :extra-offset 8
(integer :tag "Non-anchored offset")
(integer :tag "Anchored offset")))
:group 'c)
-(defcustom c-indent-comments-syntactically-p nil
+(defcustom-c-stylevar c-indent-comment-alist
+ '((anchored-comment . (column . 0))
+ (end-block . (space . 1))
+ (cpp-end-block . (space . 2)))
+ "*Specifies how \\[indent-for-comment] calculates the comment start column.
+This is an association list that contains entries of the form:
+
+ (LINE-TYPE . INDENT-SPEC)
+
+LINE-TYPE specifies a type of line as described below, and INDENT-SPEC
+says what \\[indent-for-comment] should do when used on that type of line.
+
+The recognized values for LINE-TYPE are:
+
+ empty-line -- The line is empty.
+ anchored-comment -- The line contains a comment that starts in column 0.
+ end-block -- The line contains a solitary block closing brace.
+ cpp-end-block -- The line contains a preprocessor directive that
+ closes a block, i.e. either \"#endif\" or \"#else\".
+ other -- The line does not match any other entry
+ currently on the list.
+
+An INDENT-SPEC is a cons cell of the form:
+
+ (ACTION . VALUE)
+
+ACTION says how \\[indent-for-comment] should align the comment, and
+VALUE is interpreted depending on ACTION. ACTION can be any of the
+following:
+
+ space -- Put VALUE spaces between the end of the line and the start
+ of the comment.
+ column -- Start the comment at the column VALUE. If the line is
+ longer than that, the comment is preceded by a single
+ space. If VALUE is nil, `comment-column' is used.
+ align -- Align the comment with one on the previous line, if there
+ is any. If the line is too long, the comment is preceded
+ by a single space. If there isn't a comment start on the
+ previous line, the behavior is specified by VALUE, which
+ in turn is interpreted as an INDENT-SPEC.
+
+If a LINE-TYPE is missing, then \\[indent-for-comment] indents the comment
+according to `comment-column'.
+
+Note that a non-nil value on `c-indent-comments-syntactically-p'
+overrides this variable, so empty lines are indentented syntactically
+in that case, i.e. as if \\[c-indent-command] was used instead."
+ :type
+ (let ((space '(cons :tag "space"
+ :format "%v"
+ :value (space . 1)
+ (const :format "space " space)
+ (integer :format "%v")))
+ (column '(cons :tag "column"
+ :format "%v"
+ (const :format "column " column)
+ (c-integer-or-nil :format "%v"))))
+ `(set ,@(mapcar
+ (lambda (elt)
+ `(cons :format "%v"
+ (c-const-symbol :format "%v: "
+ :size 20
+ :value ,elt)
+ (choice
+ :format "%[Choice%] %v"
+ :value (column . nil)
+ ,space
+ ,column
+ (cons :tag "align"
+ :format "%v"
+ (const :format "align " align)
+ (choice
+ :format "%[Choice%] %v"
+ :value (column . nil)
+ ,space
+ ,column)))))
+ '(empty-line anchored-comment end-block cpp-end-block other))))
+ :group 'c)
+
+(defcustom-c-stylevar c-indent-comments-syntactically-p nil
"*Specifies how \\[indent-for-comment] should handle comment-only lines.
When this variable is non-nil, comment-only lines are indented
according to syntactic analysis via `c-offsets-alist'. Otherwise, the
more lines for the first time; otherwise the appropriate prefix is
adapted from the comment. This variable is not used for C++ line
style comments."
- ;; We need to specify a :value to prevent `defcustom-c-stylevar' from
- ;; giving it an invalid value. Perhaps `defcustom-c-stylevar'
- ;; should evaluate the value first?
- ;; Per Abrahamsen <abraham@dina.kvl.dk> 2002-04-06.
- :type '(string :value "* ")
+ :type 'string
:group 'c)
(defcustom-c-stylevar c-comment-prefix-regexp
which is sometimes inserted by CC Mode inside block comments. It
should not match any surrounding whitespace.
-Note that CC Mode modifies other variables from this one at mode
-initialization, so you will need to do \\[c-mode] (or whatever mode
-you're currently using) if you change it in a CC Mode buffer."
+Note that CC Mode uses this variable to set many other variables that
+handle the paragraph filling. That's done at mode initialization or
+when you switch to a style which sets this variable. Thus, if you
+change it in some other way, e.g. interactively in a CC Mode buffer,
+you will need to do \\[c-setup-paragraph-variables] afterwards so that
+the other variables are updated with the new value.
+
+Note also that when CC Mode starts up, all variables are initialized
+before the mode hooks are run. It's therefore necessary to make a
+call to `c-setup-paragraph-variables' explicitly if you change this
+variable in a mode hook."
:type '(radio
(regexp :tag "Regexp for all modes")
(list
(const :format "Other " other) (regexp :format "%v"))))
:group 'c)
+(defcustom-c-stylevar c-doc-comment-style
+ '((java-mode . javadoc)
+ (pike-mode . autodoc))
+ "*Specifies documentation comment style(s) to recognize.
+This is primarily used to fontify doc comments and the markup within
+them, e.g. Javadoc comments.
+
+The value can be any of the following symbols for various known doc
+comment styles:
+
+ javadoc -- Javadoc style for \"/** ... */\" comments (default in Java mode).
+ autodoc -- Pike autodoc style for \"//! ...\" comments (default in Pike mode).
+
+The value may also be a list of doc comment styles, in which case all
+of them are recognized simultaneously (presumably with markup cues
+that don't conflict).
+
+The value may also be an association list to specify different doc
+comment styles for different languages. The symbol for the major mode
+is then looked up in the alist, and the value of that element is
+interpreted as above if found. If it isn't found then the symbol
+`other' is looked up and its value is used instead.
+
+Note that CC Mode uses this variable to set other variables that
+handle fontification etc. That's done at mode initialization or when
+you switch to a style which sets this variable. Thus, if you change
+it in some other way, e.g. interactively in a CC Mode buffer, you will
+need to do \\[java-mode] (or whatever mode you're currently using) to
+reinitialize.
+
+Note also that when CC Mode starts up, the other variables are
+modified before the mode hooks are run. If you change this variable
+in a mode hook, you have to call `c-setup-doc-comment-style'
+afterwards to redo that work."
+ ;; Symbols other than those documented above may be used on this
+ ;; variable. If a variable exists that has that name with
+ ;; "-font-lock-keywords" appended, it's value is prepended to the
+ ;; font lock keywords list. If it's a function then it's called and
+ ;; the result is prepended.
+ :type '(radio
+ (c-symbol-list :tag "Doc style(s) in all modes")
+ (list
+ :tag "Mode-specific doc styles"
+ (set
+ :inline t :format "%v"
+ (cons :format "%v"
+ (const :format "C " c-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "C++ " c++-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "ObjC " objc-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "Java " java-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "IDL " idl-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "Pike " pike-mode)
+ (c-symbol-list :format "%v"))
+ (cons :format "%v"
+ (const :format "Other " other)
+ (c-symbol-list :format "%v")))))
+ :group 'c)
+
(defcustom c-ignore-auto-fill '(string cpp code)
"*List of contexts in which automatic filling never occurs.
If Auto Fill mode is active, it will be temporarily disabled if point
cpp -- inside a preprocessor directive
code -- anywhere else, i.e. in normal code"
:type '(set
- :extra-offset 8
(const :tag "String literals" string)
(const :tag "C style block comments" c)
(const :tag "C++ style line comments" c++)
Clean up occurs when the closing parenthesis
is typed."
:type '(set
- :extra-offset 8
(const :tag "Put \"} else {\" on one line"
brace-else-brace)
(const :tag "Put \"} else if (...) {\" on one line"
(defcustom-c-stylevar c-hanging-braces-alist '((brace-list-open)
(brace-entry-open)
+ (statement-cont)
(substatement-open after)
(block-close . c-snug-do-while)
(extern-lang-open after)
+ (namespace-open after)
+ (module-open after)
+ (composition-open after)
(inexpr-class-open after)
(inexpr-class-close before))
"*Controls the insertion of newlines before and after braces
If the context is not found, the default is to insert a newline both
before and after the brace.
-SYNTACTIC-SYMBOL can be any of: defun-open, defun-close, class-open,
-class-close, inline-open, inline-close, block-open, block-close,
-substatement-open, statement-case-open, extern-lang-open,
-extern-lang-close, brace-list-open, brace-list-close,
-brace-list-intro, brace-entry-open, namespace-open, namespace-close,
-inexpr-class-open, or inexpr-class-close. See `c-offsets-alist' for
-details, except for inexpr-class-open and inexpr-class-close, which
-doesn't have any corresponding symbols there. Those two symbols are
-used for the opening and closing braces, respectively, of anonymous
-inner classes in Java.
+SYNTACTIC-SYMBOL can be statement-cont, brace-list-intro,
+inexpr-class-open, inexpr-class-close, and any of the *-open and
+*-close symbols. See `c-offsets-alist' for details, except for
+inexpr-class-open and inexpr-class-close, which doesn't have any
+corresponding symbols there. Those two symbols are used for the
+opening and closing braces, respectively, of anonymous inner classes
+in Java.
ACTION can be either a function symbol or a list containing any
combination of the symbols `before' or `after'. If the list is empty,
:size 20
:value ,elt)
(choice :format "%[Choice%] %v"
- :value (before after)
+ :value (before after)
(set :menu-tag "Before/after"
:format "Newline %v brace\n"
(const :format "%v, " before)
class-open class-close
inline-open inline-close
block-open block-close
- substatement-open statement-case-open
- extern-lang-open extern-lang-close
+ statement-cont substatement-open statement-case-open
brace-list-open brace-list-close
brace-list-intro brace-entry-open
+ extern-lang-open extern-lang-close
namespace-open namespace-close
+ module-open module-close
+ composition-open composition-close
inexpr-class-open inexpr-class-close)))
:group 'c)
:group 'c)
(defcustom-c-stylevar c-backslash-column 48
- "*Column to insert backslashes when macroizing a region."
+ "*Minimum alignment column for line continuation backslashes.
+This is used by the functions that automatically insert or align the
+line continuation backslashes in multiline macros. If any line in the
+macro exceeds this column then the next tab stop from that line is
+used as alignment column instead."
:type 'integer
:group 'c)
-(defcustom c-special-indent-hook nil
- "*Hook for user defined special indentation adjustments.
-This hook gets called after a line is indented by the mode."
- :type 'hook
+(defcustom-c-stylevar c-backslash-max-column 72
+ "*Maximum alignment column for line continuation backslashes.
+This is used by the functions that automatically insert or align the
+line continuation backslashes in multiline macros. If any line in the
+macro exceeds this column then the backslashes for the other lines
+will be aligned at this column."
+ :type 'integer
+ :group 'c)
+
+(defcustom c-auto-align-backslashes t
+ "*Align automatically inserted line continuation backslashes.
+When line continuation backslashes are inserted automatically for line
+breaks in multiline macros, e.g. by \\[c-context-line-break], they are
+aligned with the other backslashes in the same macro if this flag is
+set. Otherwise the inserted backslashes are preceded by a single
+space."
+ :type 'boolean
:group 'c)
(defcustom c-backspace-function 'backward-delete-char-untabify
:group 'c)
(defcustom c-delete-function 'delete-char
- "*Function called by `c-electric-delete' when deleting forwards."
+ "*Function called by `c-electric-delete-forward' when deleting forwards."
:type 'function
:group 'c)
+(defcustom c-require-final-newline
+ ;; C and C++ mandates that all nonempty files should end with a
+ ;; newline. Objective-C refers to C for all things it doesn't
+ ;; specify, so the same holds there. The other languages does not
+ ;; require it (at least not explicitly in a normative text).
+ '((c-mode . t)
+ (c++-mode . t)
+ (objc-mode . t))
+ "*Controls whether a final newline is ensured when the file is saved.
+The value is an association list that for each language mode specifies
+the value to give to `require-final-newline' at mode initialization;
+see that variable for details about the value. If a language isn't
+present on the association list, CC Mode won't set
+`require-final-newline' in buffers for that language."
+ :type `(set (cons :format "%v"
+ (const :format "C " c-mode)
+ (symbol :format "%v" :value ,require-final-newline))
+ (cons :format "%v"
+ (const :format "C++ " c++-mode)
+ (symbol :format "%v" :value ,require-final-newline))
+ (cons :format "%v"
+ (const :format "ObjC " objc-mode)
+ (symbol :format "%v" :value ,require-final-newline))
+ (cons :format "%v"
+ (const :format "Java " java-mode)
+ (symbol :format "%v" :value ,require-final-newline))
+ (cons :format "%v"
+ (const :format "IDL " idl-mode)
+ (symbol :format "%v" :value ,require-final-newline))
+ (cons :format "%v"
+ (const :format "Pike " pike-mode)
+ (symbol :format "%v" :value ,require-final-newline)))
+ :group 'c)
+
(defcustom c-electric-pound-behavior nil
"*List of behaviors for electric pound insertion.
Only currently supported behavior is `alignleft'."
- :type '(set :extra-offset 8 (const alignleft))
+ :type '(set (const alignleft))
+ :group 'c)
+
+(defcustom c-special-indent-hook nil
+ "*Hook for user defined special indentation adjustments.
+This hook gets called after a line is indented by the mode."
+ :type 'hook
:group 'c)
(defcustom-c-stylevar c-label-minimum-indentation 1
- "*Minimum indentation for lines inside of top-level constructs.
+ "*Minimum indentation for lines inside code blocks.
This variable typically only affects code using the `gnu' style, which
-mandates a minimum of one space in front of every line inside
-top-level constructs. Specifically, the function
-`c-gnu-impose-minimum' on your `c-special-indent-hook' is what
-enforces this."
+mandates a minimum of one space in front of every line inside code
+blocks. Specifically, the function `c-gnu-impose-minimum' on your
+`c-special-indent-hook' is what enforces this."
:type 'integer
:group 'c)
(const :format "Other " other) (string :format "%v"))))
:group 'c)
-(put 'c-offsets-alist 'c-stylevar-fallback
+;; *) At the start of a statement or declaration means in more detail:
+;; At the closest preceding statement/declaration that starts at boi
+;; and doesn't have a label or comment at that position. If there's
+;; no such statement within the same block, then back up to the
+;; surrounding block or statement, add the appropriate
+;; statement-block-intro, defun-block-intro or substatement syntax
+;; symbol and continue searching.
+(c-set-stylevar-fallback 'c-offsets-alist
'((string . c-lineup-dont-change)
;; Relpos: Beg of previous line.
(c . c-lineup-C-comments)
;; Relpos: Beg of the comment.
(defun-open . 0)
- ;; Relpos: Boi at the func decl start when inside classes, bol
- ;; at the func decl start when at top level.
+ ;; Relpos: When inside a class: Boi at the func decl start.
+ ;; When at top level: Bol at the func decl start. When inside
+ ;; a code block (only possible in Pike): At the func decl
+ ;; start(*).
(defun-close . 0)
- ;; Relpos: Boi at the func decl start.
+ ;; Relpos: At the defun block open if it's at boi, otherwise
+ ;; boi at the func decl start.
(defun-block-intro . +)
- ;; Relpos: Boi at the block open.
+ ;; Relpos: At the block open(*).
(class-open . 0)
;; Relpos: Boi at the class decl start.
(class-close . 0)
;; Relpos: None for functions (inclass got the relpos then),
;; boi at the lambda start for lambdas.
(inline-close . 0)
- ;; Relpos: For functions: Boi at the func decl start. For
- ;; lambdas: At the block open if it's at boi, at the boi of the
- ;; lambda start otherwise.
+ ;; Relpos: Inexpr functions: At the lambda block open if it's
+ ;; at boi, else at the statement(*) at boi of the start of the
+ ;; lambda construct. Otherwise: At the inline block open if
+ ;; it's at boi, otherwise boi at the func decl start.
(func-decl-cont . +)
;; Relpos: Boi at the func decl start.
(knr-argdecl-intro . +)
- ;; Relpos: Boi at the current line.
+ ;; Relpos: Boi at the topmost intro line.
(knr-argdecl . 0)
- ;; Relpos: Boi at the argdecl intro line.
+ ;; Relpos: At the beginning of the first K&R argdecl.
(topmost-intro . 0)
;; Relpos: Bol at the last line of previous construct.
- (topmost-intro-cont . 0)
+ (topmost-intro-cont . c-lineup-topmost-intro-cont)
;; Relpos: Boi at the topmost intro line.
(member-init-intro . +)
;; Relpos: Boi at the func decl arglist open.
(member-init-cont . c-lineup-multi-inher)
;; Relpos: Beg of the first member init.
(inher-intro . +)
- ;; Relpos: Java: Boi at the class decl start. Otherwise: Boi
- ;; of current line (a bug?), unless it begins with an inher
- ;; start colon, in which case boi of previous line is used.
+ ;; Relpos: Boi at the class decl start.
(inher-cont . c-lineup-multi-inher)
;; Relpos: Java: At the implements/extends keyword start.
;; Otherwise: At the inher start colon, or boi at the class
;; decl start if the first inherit clause hangs and it's not a
;; func-local inherit clause (when does that occur?).
(block-open . 0)
- ;; Relpos: Inexpr statement: Boi at the preceding
- ;; paren. Otherwise: None.
+ ;; Relpos: Inexpr statement: At the statement(*) at boi of the
+ ;; start of the inexpr construct. Otherwise: None.
(block-close . 0)
- ;; Relpos: At the open brace if it's at boi. Otherwise boi at
- ;; the start of the statement the open brace hangs on, or boi
- ;; at the preceding paren for inexpr statements.
+ ;; Relpos: Inexpr statement: At the inexpr block open if it's
+ ;; at boi, else at the statement(*) at boi of the start of the
+ ;; inexpr construct. Block hanging on a case/default label: At
+ ;; the closest preceding label that starts at boi. Otherwise:
+ ;; At the block open(*).
(brace-list-open . 0)
;; Relpos: Boi at the brace list decl start, but a starting
;; "typedef" token is ignored.
(brace-list-close . 0)
- ;; Relpos: Boi at the brace list open.
+ ;; Relpos: At the brace list decl start(*).
(brace-list-intro . +)
- ;; Relpos: Boi at the brace list open.
+ ;; Relpos: At the brace list decl start(*).
(brace-list-entry . 0)
;; Relpos: At the first non-ws char after the open paren if the
;; first token is on the same line, otherwise boi at that
(brace-entry-open . 0)
;; Relpos: Same as brace-list-entry.
(statement . 0)
- ;; Relpos: After a ';' in the condition clause of a for
+ ;; Relpos: After a `;' in the condition clause of a for
;; statement: At the first token after the starting paren.
- ;; Otherwise: Boi at the start of the closest non-hanging
- ;; previous statement, but after any switch label.
+ ;; Otherwise: At the preceding statement(*).
(statement-cont . +)
;; Relpos: After the first token in the condition clause of a
;; for statement: At the first token after the starting paren.
- ;; On the first line in a continued expression that starts with
- ;; a stream op and there's no stream op on the previous line:
- ;; Boi of previous line. Otherwise: Boi at the beginning of
- ;; the statement, but after any type of label.
+ ;; Otherwise: At the containing statement(*).
(statement-block-intro . +)
- ;; Relpos: At the block start if it's at boi, otherwise boi at
- ;; the start of the statement the open brace hangs on, or boi
- ;; at the preceding paren for inexpr statements.
+ ;; Relpos: In inexpr statement block: At the inexpr block open
+ ;; if it's at boi, else at the statement(*) at boi of the start
+ ;; of the inexpr construct. In a block hanging on a
+ ;; case/default label: At the closest preceding label that
+ ;; starts at boi. Otherwise: At the start of the containing
+ ;; block(*).
(statement-case-intro . +)
- ;; Relpos: At the label keyword (always at boi).
+ ;; Relpos: At the case/default label(*).
(statement-case-open . 0)
- ;; Relpos: At the label keyword (always at boi).
+ ;; Relpos: At the case/default label(*).
(substatement . +)
- ;; Relpos: Boi at the containing statement or else clause.
+ ;; Relpos: At the containing statement(*).
(substatement-open . +)
- ;; Relpos: Boi at the containing statement or else clause.
+ ;; Relpos: At the containing statement(*).
+ (substatement-label . 2)
+ ;; Relpos: At the containing statement(*).
(case-label . 0)
- ;; Relpos: At the switch block start if it's at boi, otherwise
- ;; boi at the start of the switch condition clause.
+ ;; Relpos: At the start of the switch block(*).
(access-label . -)
- ;; Relpos: Eol (a bug?).
+ ;; Relpos: Same as inclass.
(label . 2)
- ;; Relpos: At the start of the containing block if it's at boi,
- ;; otherwise boi at the start of the sexp before the block.
+ ;; Relpos: At the start of the containing block(*).
(do-while-closure . 0)
- ;; Relpos: Boi at the corresponding while keyword.
+ ;; Relpos: At the corresponding while statement(*).
(else-clause . 0)
- ;; Relpos: Boi at the corresponding if keyword.
+ ;; Relpos: At the corresponding if statement(*).
(catch-clause . 0)
- ;; Relpos: Boi at the previous try or catch keyword in the try
- ;; statement.
- (comment-intro . c-lineup-comment)
+ ;; Relpos: At the previous try or catch statement clause(*).
+ (comment-intro . (c-lineup-knr-region-comment c-lineup-comment))
;; Relpos: None.
(arglist-intro . +)
;; Relpos: Boi at the open paren, or at the first non-ws after
;; the open paren of the surrounding sexp, whichever is later.
- (arglist-cont . 0)
+ (arglist-cont . (c-lineup-gcc-asm-reg 0))
;; Relpos: At the first token after the open paren.
- (arglist-cont-nonempty . c-lineup-arglist)
- ;; Relpos: Boi at the open paren, or at the first non-ws after
- ;; the open paren of the surrounding sexp, whichever is later.
+ (arglist-cont-nonempty . (c-lineup-gcc-asm-reg c-lineup-arglist))
+ ;; Relpos: At the containing statement(*).
+ ;; 2nd pos: At the open paren.
(arglist-close . +)
- ;; Relpos: Boi at the open paren, or at the first non-ws after
- ;; the open paren of the surrounding sexp, whichever is later.
+ ;; Relpos: At the containing statement(*).
+ ;; 2nd pos: At the open paren.
(stream-op . c-lineup-streamop)
;; Relpos: Boi at the first stream op in the statement.
(inclass . +)
;; boi at the class decl start.
(cpp-macro . [0])
;; Relpos: None.
- (cpp-macro-cont . c-lineup-dont-change)
+ (cpp-macro-cont . +)
;; Relpos: At the macro start (always at boi).
+ (cpp-define-intro . (c-lineup-cpp-define +))
+ ;; Relpos: None.
(friend . 0)
;; Relpos: None.
(objc-method-intro . [0])
(objc-method-call-cont . c-lineup-ObjC-method-call)
;; Relpos: At the open bracket.
(extern-lang-open . 0)
- ;; Relpos: Boi at the extern keyword.
- (extern-lang-close . 0)
- ;; Relpos: Boi at the corresponding extern keyword.
- (inextern-lang . +)
- ;; Relpos: At the extern block open brace if it's at boi,
- ;; otherwise boi at the extern keyword.
(namespace-open . 0)
- ;; Relpos: Boi at the namespace keyword.
+ (module-open . 0)
+ (composition-open . 0)
+ ;; Relpos: Boi at the extern/namespace/etc keyword.
+ (extern-lang-close . 0)
(namespace-close . 0)
- ;; Relpos: Boi at the corresponding namespace keyword.
+ (module-close . 0)
+ (composition-close . 0)
+ ;; Relpos: Boi at the corresponding extern/namespace/etc keyword.
+ (inextern-lang . +)
(innamespace . +)
- ;; Relpos: At the namespace block open brace if it's at boi,
- ;; otherwise boi at the namespace keyword.
+ (inmodule . +)
+ (incomposition . +)
+ ;; Relpos: At the extern/namespace/etc block open brace if it's
+ ;; at boi, otherwise boi at the keyword.
(template-args-cont . (c-lineup-template-args +))
- ;; Relpos: Boi at the decl start.
+ ;; Relpos: Boi at the decl start. This might be changed; the
+ ;; logical position is clearly the opening '<'.
(inlambda . c-lineup-inexpr-block)
;; Relpos: None.
(lambda-intro-cont . +)
;; Relpos: Boi at the lambda start.
- (inexpr-statement . 0)
+ (inexpr-statement . +)
;; Relpos: None.
(inexpr-class . +)
;; Relpos: None.
`c-offsets-alist' is a style variable. This means that the offsets on
this variable are normally taken from the style system in CC Mode
-\(see `c-default-style' and `c-styles-alist'). However, any offsets
+\(see `c-default-style' and `c-style-alist'). However, any offsets
put explicitly on this list will override the style system when a CC
Mode buffer is initialized \(there is a variable
`c-old-style-variable-behavior' that changes this, though).
statement-case-open -- The first line in a case block starting with brace.
substatement -- The first line after an if/while/for/do/else.
substatement-open -- The brace that opens a substatement block.
- case-label -- A `case' or `default' label.
+ substatement-label -- Labelled line after an if/while/for/do/else.
+ case-label -- A \"case\" or \"default\" label.
access-label -- C++ private/protected/public access label.
label -- Any ordinary label.
- do-while-closure -- The `while' that ends a do/while construct.
- else-clause -- The `else' of an if/else construct.
- catch-clause -- The `catch' or `finally' of a try/catch construct.
+ do-while-closure -- The \"while\" that ends a do/while construct.
+ else-clause -- The \"else\" of an if/else construct.
+ catch-clause -- The \"catch\" or \"finally\" of a try/catch construct.
comment-intro -- A line containing only a comment introduction.
arglist-intro -- The first line in an argument list.
arglist-cont -- Subsequent argument list lines when no
inclass -- The construct is nested inside a class definition.
Used together with e.g. `topmost-intro'.
cpp-macro -- The start of a C preprocessor macro definition.
- cpp-macro-cont -- Subsequent lines in a multi-line C preprocessor
- macro definition.
+ cpp-macro-cont -- Inside a multi-line C preprocessor macro definition.
friend -- A C++ friend declaration.
objc-method-intro -- The first line of an Objective-C method definition.
objc-method-args-cont -- Lines continuing an Objective-C method definition.
objc-method-call-cont -- Lines continuing an Objective-C method call.
- extern-lang-open -- Brace that opens an external language block.
- extern-lang-close -- Brace that closes an external language block.
+ extern-lang-open -- Brace that opens an \"extern\" block.
+ extern-lang-close -- Brace that closes an \"extern\" block.
inextern-lang -- Analogous to the `inclass' syntactic symbol,
- but used inside extern constructs.
- namespace-open -- Brace that opens a C++ namespace block.
- namespace-close -- Brace that closes a C++ namespace block.
- innamespace -- Analogous to the `inextern-lang' syntactic
- symbol, but used inside C++ namespace constructs.
+ but used inside \"extern\" blocks.
+ namespace-open, namespace-close, innamespace
+ -- Similar to the three `extern-lang' symbols, but for
+ C++ \"namespace\" blocks.
+ module-open, module-close, inmodule
+ -- Similar to the three `extern-lang' symbols, but for
+ CORBA IDL \"module\" blocks.
+ composition-open, composition-close, incomposition
+ -- Similar to the three `extern-lang' symbols, but for
+ CORBA CIDL \"composition\" blocks.
template-args-cont -- C++ template argument list continuations.
inlambda -- In the header or body of a lambda function.
lambda-intro-cont -- Continuation of the header of a lambda function.
(get 'c-offsets-alist 'c-stylevar-fallback)))
:group 'c)
+;; The syntactic symbols that can occur inside code blocks. Used by
+;; `c-gnu-impose-minimum'.
+(defconst c-inside-block-syms
+ '(defun-block-intro block-open block-close statement statement-cont
+ statement-block-intro statement-case-intro statement-case-open
+ substatement substatement-open substatement-label case-label label
+ do-while-closure else-clause catch-clause inlambda))
+
(defcustom c-style-variables-are-local-p t
"*Whether style variables should be buffer local by default.
If non-nil, then all indentation style related variables will be made
are made buffer local when this file is loaded, and once buffer
localized, they cannot be made global again.
+This variable must be set appropriately before CC Mode is loaded.
+
The list of variables to buffer localize are:
- c-offsets-alist
c-basic-offset
c-comment-only-line-offset
+ c-indent-comment-alist
+ c-indent-comments-syntactically-p
c-block-comment-prefix
c-comment-prefix-regexp
+ c-doc-comment-style
c-cleanup-list
c-hanging-braces-alist
c-hanging-colons-alist
c-hanging-semi&comma-criteria
c-backslash-column
+ c-backslash-max-column
c-label-minimum-indentation
+ c-offsets-alist
c-special-indent-hook
c-indentation-style"
:type 'boolean
(defcustom c-mode-common-hook nil
"*Hook called by all CC Mode modes for common initializations."
- :type '(hook :format "%{CC Mode Common Hook%}:\n%v")
+ :type 'hook
:group 'c)
(defcustom c-initialization-hook nil
times for core indentation functions (e.g. `c-parse-state'). For
styles that conform to the Emacs recommendation of putting these
braces in column zero, this can degrade performance about as much.
-This variable only has effect in XEmacs.")
+This variable only has effect in XEmacs."
+ :type 'boolean
+ :group 'c)
-(defcustom c-old-style-variable-behavior nil
+(defvar c-old-style-variable-behavior nil
"*Enables the old style variable behavior when non-nil.
Normally the values of the style variables will override the style
settings specified by the variables `c-default-style' and
-`c-styles-alist'. However, in CC Mode 5.25 and earlier, it was the
+`c-style-alist'. However, in CC Mode 5.25 and earlier, it was the
other way around, meaning that changes made to the style variables
from e.g. Customize would not take effect unless special precautions
were taken. That was confusing, especially for novice users.
state. Set this variable only if your configuration has stopped
working due to this change.")
+(define-widget 'c-extra-types-widget 'radio
+ "Internal CC Mode widget for the `*-font-lock-extra-types' variables."
+ :args '((const :tag "none" nil)
+ (repeat :tag "types" regexp)))
+
+(eval-and-compile
+ ;; XEmacs 19 evaluates this at compile time below, while most other
+ ;; versions delays the evaluation until the package is loaded.
+ (defun c-make-font-lock-extra-types-blurb (mode1 mode2 example)
+ (concat "\
+*List of extra types (aside from the type keywords) to recognize in "
+mode1 " mode.
+Each list item should be a regexp matching a single identifier.
+" example "
+
+On decoration level 3 (and higher, where applicable), a method is used
+that finds most types and declarations by syntax alone. This variable
+is still used as a first step, but other types are recognized
+correctly anyway in most cases. Therefore this variable should be
+fairly restrictive and not contain patterns that are uncertain.
+
+Note that this variable is only consulted when the major mode is
+initialized. If you change it later you have to reinitialize CC Mode
+by doing \\[" mode2 "].
+
+Despite the name, this variable is not only used for font locking but
+also elsewhere in CC Mode to tell types from other identifiers.")))
+
+;; Note: Most of the variables below are also defined in font-lock.el
+;; in older versions in Emacs, so depending on the load order we might
+;; not install the values below. There's no kludge to cope with this
+;; (as opposed to the *-font-lock-keywords-* variables) since the old
+;; values work fairly well anyway.
+
+(defcustom c-font-lock-extra-types
+ '("FILE" "\\sw+_t"
+ "bool" "complex" "imaginary" ; Defined in C99.
+ ;; I do not appreciate the following very Emacs-specific luggage
+ ;; in the default value, but otoh it can hardly get in the way for
+ ;; other users, and removing it would cause unnecessary grief for
+ ;; the old timers that are used to it. /mast
+ "Lisp_Object")
+ (c-make-font-lock-extra-types-blurb "C" "c-mode"
+"For example, a value of (\"FILE\" \"\\\\sw+_t\") means the word FILE
+and words ending in _t are treated as type names.")
+ :type 'c-extra-types-widget
+ :group 'c)
+
+(defcustom c++-font-lock-extra-types
+ '("\\sw+_t"
+ "\\([iof]\\|str\\)+stream\\(buf\\)?" "ios"
+ "string" "rope"
+ "list" "slist"
+ "deque" "vector" "bit_vector"
+ "set" "multiset"
+ "map" "multimap"
+ "hash\\(_\\(m\\(ap\\|ulti\\(map\\|set\\)\\)\\|set\\)\\)?"
+ "stack" "queue" "priority_queue"
+ "type_info"
+ "iterator" "const_iterator" "reverse_iterator" "const_reverse_iterator"
+ "reference" "const_reference")
+ (c-make-font-lock-extra-types-blurb "C++" "c++-mode"
+"For example, a value of (\"string\") means the word string is treated
+as a type name.")
+ :type 'c-extra-types-widget
+ :group 'c)
+
+(defcustom objc-font-lock-extra-types
+ (list (concat "[" c-upper "]\\sw*[" c-lower "]\\sw*"))
+ (c-make-font-lock-extra-types-blurb "ObjC" "objc-mode" (concat
+"For example, a value of (\"[" c-upper "]\\\\sw*[" c-lower "]\\\\sw*\") means
+capitalized words are treated as type names (the requirement for a
+lower case char is to avoid recognizing all-caps macro and constant
+names)."))
+ :type 'c-extra-types-widget
+ :group 'c)
+
+(defcustom java-font-lock-extra-types
+ (list (concat "[" c-upper "]\\sw*[" c-lower "]\\sw*"))
+ (c-make-font-lock-extra-types-blurb "Java" "java-mode" (concat
+"For example, a value of (\"[" c-upper "]\\\\sw*[" c-lower "]\\\\sw*\") means
+capitalized words are treated as type names (the requirement for a
+lower case char is to avoid recognizing all-caps constant names)."))
+ :type 'c-extra-types-widget
+ :group 'c)
+
+(defcustom idl-font-lock-extra-types nil
+ (c-make-font-lock-extra-types-blurb "IDL" "idl-mode" "")
+ :type 'c-extra-types-widget
+ :group 'c)
+
+(defcustom pike-font-lock-extra-types
+ (list (concat "[" c-upper "]\\sw*[" c-lower "]\\sw*"))
+ (c-make-font-lock-extra-types-blurb "Pike" "pike-mode" (concat
+"For example, a value of (\"[" c-upper "]\\\\sw*[" c-lower "]\\\\sw*\") means
+capitalized words are treated as type names (the requirement for a
+lower case char is to avoid recognizing all-caps macro and constant
+names)."))
+ :type 'c-extra-types-widget
+ :group 'c)
\f
;; Non-customizable variables, still part of the interface to CC Mode
as designated in the variable `c-file-style'.")
(make-variable-buffer-local 'c-file-offsets)
-(defvar c-syntactic-context nil
- "Variable containing syntactic analysis list during indentation.
-This is always bound dynamically. It should never be set statically
-\(e.g. with `setq').")
+;; It isn't possible to specify a docstring without specifying an
+;; initial value with `defvar', so the following two variables have
+;; only doc comments even though they are part of the API. It's
+;; really good not to have an initial value for variables like these
+;; that always should be dynamically bound, so it's worth the
+;; inconvenience.
+
+(cc-bytecomp-defvar c-syntactic-context)
+(defvar c-syntactic-context)
+;; Variable containing the syntactic analysis list during indentation.
+;; It is a list with one element for each found syntactic symbol. See
+;; `c-syntactic-element' for further info.
+;;
+;; This is always bound dynamically. It should never be set
+;; statically (e.g. with `setq').
+
+(cc-bytecomp-defvar c-syntactic-element)
+(defvar c-syntactic-element)
+;; Variable containing the info regarding the current syntactic
+;; element during calls to the lineup functions. The value is one of
+;; the elements in the list in `c-syntactic-context' and is a list
+;; with the symbol name in the first position, followed by zero or
+;; more elements containing any additional info associated with the
+;; syntactic symbol. There are accessor functions `c-langelem-sym',
+;; `c-langelem-pos', `c-langelem-col', and `c-langelem-2nd-pos' to
+;; access the list.
+;;
+;; Specifically, the element returned by `c-langelem-pos' is the
+;; relpos (a.k.a. anchor position), or nil if there isn't any. See
+;; the comments in the `c-offsets-alist' variable for more detailed
+;; info about the data each syntactic symbol provides.
+;;
+;; This is always bound dynamically. It should never be set
+;; statically (e.g. with `setq').
(defvar c-indentation-style nil
"Name of the currently installed style.
\f
;; Figure out what features this Emacs has
-;;;###autoload
-(defconst c-emacs-features
- (let ((infodock-p (boundp 'infodock-version))
- (comments
- ;; XEmacs 19 and beyond use 8-bit modify-syntax-entry flags.
- ;; Emacs 19 uses a 1-bit flag. We will have to set up our
- ;; syntax tables differently to handle this.
- (let ((table (copy-syntax-table))
- entry)
- (modify-syntax-entry ?a ". 12345678" table)
- (cond
- ;; XEmacs 19, and beyond Emacs 19.34
- ((arrayp table)
- (setq entry (aref table ?a))
- ;; In Emacs, table entries are cons cells
- (if (consp entry) (setq entry (car entry))))
- ;; XEmacs 20
- ((fboundp 'get-char-table) (setq entry (get-char-table ?a table)))
- ;; before and including Emacs 19.34
- ((and (fboundp 'char-table-p)
- (char-table-p table))
- (setq entry (car (char-table-range table [?a]))))
- ;; incompatible
- (t (error "CC Mode is incompatible with this version of Emacs")))
- (if (= (logand (lsh entry -16) 255) 255)
- '8-bit
- '1-bit))))
- (if infodock-p
- (list comments 'infodock)
- (list comments)))
- "A list of features extant in the Emacs you are using.
-There are many flavors of Emacs out there, each with different
-features supporting those needed by CC Mode. Here's the current
-supported list, along with the values for this variable:
- XEmacs 19, 20, 21: (8-bit)
- Emacs 19, 20: (1-bit)
+(cc-bytecomp-defvar open-paren-in-column-0-is-defun-start)
-Infodock (based on XEmacs) has an additional symbol on this list:
-`infodock'.")
+(defconst c-emacs-features
+ (let (list)
+
+ (if (boundp 'infodock-version)
+ ;; I've no idea what this actually is, but it's legacy. /mast
+ (setq list (cons 'infodock list)))
+
+ ;; XEmacs 19 and beyond use 8-bit modify-syntax-entry flags.
+ ;; Emacs 19 uses a 1-bit flag. We will have to set up our
+ ;; syntax tables differently to handle this.
+ (let ((table (copy-syntax-table))
+ entry)
+ (modify-syntax-entry ?a ". 12345678" table)
+ (cond
+ ;; XEmacs 19, and beyond Emacs 19.34
+ ((arrayp table)
+ (setq entry (aref table ?a))
+ ;; In Emacs, table entries are cons cells
+ (if (consp entry) (setq entry (car entry))))
+ ;; XEmacs 20
+ ((fboundp 'get-char-table) (setq entry (get-char-table ?a table)))
+ ;; before and including Emacs 19.34
+ ((and (fboundp 'char-table-p)
+ (char-table-p table))
+ (setq entry (car (char-table-range table [?a]))))
+ ;; incompatible
+ (t (error "CC Mode is incompatible with this version of Emacs")))
+ (setq list (cons (if (= (logand (lsh entry -16) 255) 255)
+ '8-bit
+ '1-bit)
+ list)))
+
+ (let ((buf (generate-new-buffer " test"))
+ parse-sexp-lookup-properties
+ parse-sexp-ignore-comments
+ lookup-syntax-properties)
+ (save-excursion
+ (set-buffer buf)
+ (set-syntax-table (make-syntax-table))
+
+ ;; For some reason we have to set some of these after the
+ ;; buffer has been made current. (Specifically,
+ ;; `parse-sexp-ignore-comments' in Emacs 21.)
+ (setq parse-sexp-lookup-properties t
+ parse-sexp-ignore-comments t
+ lookup-syntax-properties t)
+
+ ;; Find out if the `syntax-table' text property works.
+ (modify-syntax-entry ?< ".")
+ (modify-syntax-entry ?> ".")
+ (insert "<()>")
+ (c-mark-<-as-paren 1)
+ (c-mark->-as-paren 4)
+ (goto-char 1)
+ (c-forward-sexp)
+ (if (= (point) 5)
+ (setq list (cons 'syntax-properties list)))
+
+ ;; Find out if generic comment delimiters work.
+ (c-safe
+ (modify-syntax-entry ?x "!")
+ (if (string-match "\\s!" "x")
+ (setq list (cons 'gen-comment-delim list))))
+
+ ;; Find out if generic string delimiters work.
+ (c-safe
+ (modify-syntax-entry ?x "|")
+ (if (string-match "\\s|" "x")
+ (setq list (cons 'gen-string-delim list))))
+
+ ;; See if `open-paren-in-column-0-is-defun-start' exists and
+ ;; isn't buggy.
+ (when (boundp 'open-paren-in-column-0-is-defun-start)
+ (let ((open-paren-in-column-0-is-defun-start nil)
+ (parse-sexp-ignore-comments t))
+ (set-syntax-table (make-syntax-table))
+ (modify-syntax-entry ?\' "\"")
+ (cond
+ ;; XEmacs. Afaik this is currently an Emacs-only
+ ;; feature, but it's good to be prepared.
+ ((memq '8-bit list)
+ (modify-syntax-entry ?/ ". 1456")
+ (modify-syntax-entry ?* ". 23"))
+ ;; Emacs
+ ((memq '1-bit list)
+ (modify-syntax-entry ?/ ". 124b")
+ (modify-syntax-entry ?* ". 23")))
+ (modify-syntax-entry ?\n "> b")
+ (insert "/* '\n () */")
+ (backward-sexp)
+ (if (bobp)
+ (setq list (cons 'col-0-paren list))))
+ (kill-buffer buf))
+
+ (set-buffer-modified-p nil))
+ (kill-buffer buf))
+
+ ;; See if `parse-partial-sexp' returns the eighth element.
+ (when (c-safe (>= (length (save-excursion (parse-partial-sexp 1 1))) 10))
+ (setq list (cons 'pps-extended-state list)))
+
+ ;; See if POSIX char classes work.
+ (when (string-match "[[:alpha:]]" "a")
+ (setq list (cons 'posix-char-classes list)))
+
+ list)
+ "A list of certain features in the (X)Emacs you are using.
+There are many flavors of Emacs out there, each with different
+features supporting those needed by CC Mode. The following values
+might be present:
+
+'8-bit 8 bit syntax entry flags (XEmacs style).
+'1-bit 1 bit syntax entry flags (Emacs style).
+'syntax-properties It works to override the syntax for specific characters
+ in the buffer with the 'syntax-table property.
+'gen-comment-delim Generic comment delimiters work
+ (i.e. the syntax class `!').
+'gen-string-delim Generic string delimiters work
+ (i.e. the syntax class `|').
+'pps-extended-state `parse-partial-sexp' returns a list with at least 10
+ elements, i.e. it contains the position of the
+ start of the last comment or string.
+'posix-char-classes The regexp engine understands POSIX character classes.
+'col-0-paren It's possible to turn off the ad-hoc rule that a paren
+ in column zero is the start of a defun.
+'infodock This is Infodock (based on XEmacs).
+
+'8-bit and '1-bit are mutually exclusive.")
\f
(cc-provide 'cc-vars)
+;;; arch-tag: d62e9a55-c9fe-409b-b5b6-050b6aa202c9
;;; cc-vars.el ends here