[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/src/lisp.h,v
From: |
Stefan Monnier |
Subject: |
[Emacs-diffs] Changes to emacs/src/lisp.h,v |
Date: |
Tue, 02 Oct 2007 20:51:03 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Stefan Monnier <monnier> 07/10/02 20:51:03
Index: lisp.h
===================================================================
RCS file: /sources/emacs/emacs/src/lisp.h,v
retrieving revision 1.588
retrieving revision 1.589
diff -u -b -r1.588 -r1.589
--- lisp.h 29 Sep 2007 20:55:04 -0000 1.588
+++ lisp.h 2 Oct 2007 20:51:02 -0000 1.589
@@ -1145,6 +1145,8 @@
/* For markers that point somewhere,
this is used to chain of all the markers in a given buffer. */
+ /* We could remove it and use an array in buffer_text instead.
+ That would also allow to preserve it ordered. */
struct Lisp_Marker *next;
/* This is the char position where the marker points. */
EMACS_INT charpos;
@@ -1242,6 +1244,10 @@
unsigned int found_for_frame : 1;
Lisp_Object realvalue;
/* The buffer and frame for which the loaded binding was found. */
+ /* Having both is only needed if we want to allow variables that are
+ both buffer local and frame local (in which case, we currently give
+ precedence to the buffer-local binding). I don't think such
+ a combination is desirable. --Stef */
Lisp_Object buffer, frame;
/* A cons cell, (LOADED-BINDING . DEFAULT-VALUE).
@@ -1723,7 +1729,6 @@
extern void defvar_lisp_nopro P_ ((char *, Lisp_Object *));
extern void defvar_bool P_ ((char *, int *));
extern void defvar_int P_ ((char *, EMACS_INT *));
-extern void defvar_per_buffer P_ ((char *, Lisp_Object *, Lisp_Object, char
*));
extern void defvar_kboard P_ ((char *, int));
/* Macros we use to define forwarded Lisp variables.
@@ -1734,15 +1739,6 @@
#define DEFVAR_BOOL(lname, vname, doc) defvar_bool (lname, vname)
#define DEFVAR_INT(lname, vname, doc) defvar_int (lname, vname)
-/* TYPE is nil for a general Lisp variable.
- An integer specifies a type; then only LIsp values
- with that type code are allowed (except that nil is allowed too).
- LNAME is the LIsp-level variable name.
- VNAME is the name of the buffer slot.
- DOC is a dummy where you write the doc string as a comment. */
-#define DEFVAR_PER_BUFFER(lname, vname, type, doc) \
- defvar_per_buffer (lname, vname, type, 0)
-
#define DEFVAR_KBOARD(lname, vname, doc) \
defvar_kboard (lname, \
(int)((char *)(¤t_kboard->vname) \
- [Emacs-diffs] Changes to emacs/src/lisp.h,v,
Stefan Monnier <=
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/02
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/02
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/02
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/09
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/10
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Eli Zaretskii, 2007/10/13
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/16
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/16
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Stefan Monnier, 2007/10/23
- [Emacs-diffs] Changes to emacs/src/lisp.h,v, Ken Raeburn, 2007/10/29