Mercurial > emacs

changeset 69874:e9739d967d09

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
(PSEUDOVECSIZE): Fix last change.
author Eli Zaretskii <eliz@gnu.org>
date Sat, 08 Apr 2006 16:37:11 +0000
parents 2d844bbbccd4
children 385bc608c677
files src/lisp.h
diffstat 1 files changed, 8 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/src/lisp.h	Sat Apr 08 15:07:35 2006 +0000
+++ b/src/lisp.h	Sat Apr 08 16:37:11 2006 +0000
@@ -713,6 +713,13 @@
   ((int)((char*)&((type*)0)->field - (char*)0))
 #endif
 
+struct Lisp_Vector
+  {
+    EMACS_INT size;
+    struct Lisp_Vector *next;
+    Lisp_Object contents[1];
+  };
+
 /* If a struct is made to look like a vector, this macro returns the length
    of the shortest vector that would hold that struct.  */
 #define VECSIZE(type) ((sizeof (type) - (sizeof (struct Lisp_Vector)  \
@@ -724,16 +731,9 @@
    at the end and we need to compute the number of Lisp_Object fields (the
    ones that the GC needs to trace).  */
 #define PSEUDOVECSIZE(type, nonlispfield) \
-  ((offsetof(type, nonlispfield) - offsetof(struct Lisp_Vector, contents[0])) \
+  ((OFFSETOF(type, nonlispfield) - OFFSETOF(struct Lisp_Vector, contents[0])) \
    / sizeof (Lisp_Object))
 
-struct Lisp_Vector
-  {
-    EMACS_INT size;
-    struct Lisp_Vector *next;
-    Lisp_Object contents[1];
-  };
-
 /* A char table is a kind of vectorlike, with contents are like a
    vector but with a few other slots.  For some purposes, it makes
    sense to handle a chartable with type struct Lisp_Vector.  An