[xemacs-hg @ 2005-10-25 08:32:40 by ben] more mc-alloc-related factoring; make it hard to do the wrong thing postgresql/postgresql.c, postgresql/postgresql.h: MC-Alloc refactoring. ldap/eldap.c, ldap/eldap.h: MC-Alloc refactoring. alloc.c, buffer.c, console.c, emacs.c, file-coding.c, lrecord.h, lstream.c, mule-charset.c, print.c, scrollbar-gtk.c, scrollbar-msw.c, scrollbar-x.c, scrollbar.c, symbols.c, symeval.h, unicode.c, window.c, xemacs.def.in.in: rename `struct lcrecord_header' to `struct old_lcrecord_header'; likewise for `old_basic_alloc_lcrecord', `old_free_lcrecord', `old_zero_lcrecord', `old_zero_sized_lcrecord', `old_copy_lcrecord', `old_copy_sized_lcrecord', `old_alloc_lcrecord_type'. Created new LISPOBJ_STORAGE_SIZE() used only on objects created through allocation of Lisp-Object memory instead of basic xmalloc()/xfree(). This is distinguished from malloced_storage_size(), for non-Lisp-Objects. The definition of LISPOBJ_STORAGE_SIZE() can reduce down to malloced_storage_size() when not MC-ALLOC, but with MC-ALLOC it's a different function. The whole point other than cleaning up the use of LISPOBJ_STORAGE_SIZE is to make it harder to accidentally use the old kind (lowercase) of function in new code, since you get a compile error.

/* XPM */
static char *folder[] = {
/* width height num_colors chars_per_pixel */
"    17    17        4            1",
/* colors */
". c #000000",
"a c #a8b038",
"b c #f8f800",
"c s None c None",
/* pixels */
"ccccccccccccccccc",
"ccccccccccccccccc",
"ccccccccccccccccc",
"ccccccccccccccccc",
"cccccccccaaaaaacc",
"ccccccccaaaaaaacc",
"cc......a.a.a.aac",
"c.bbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
".bbbbbbbbbbbbbb.c",
"a..............ac"
};