Mercurial > hg > xemacs-beta
view etc/recycle2.xpm @ 3024:b7f26b2f78bd
[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.
| author | ben |
|---|---|
| date | Tue, 25 Oct 2005 08:32:50 +0000 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * recycle2_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "32 32 4 1 26 23", /* colors */ " s none m none c none", ". s iconColor1 m black c black", "X c #7F7FFFFF0000", "o c #45458B8B0000", /* pixels */ " ", " ............ ", " .XXXXXXXX.oooXX. ", " XXXXXXXX.ooXXXXX. ", " .XXXXXXXX.ooXXXXXX .. ", " .XXXXXXX..XXXXXXXX .o. ", " .XXXXXXXX .XXXXXXXXX. ", " XXXXXXXX. XXXXXXXX. ", " .XXXXXXXX. XXXXXXXX ", " .XXXXX. .XXXXXX. ", " ..XXX ..XXXXXXX ", " ......... .. .XX ", " .XXXXXXX. .XXXX. ", " .XXXXXX. ..XXXXXX. ", " .XXXXXXX. XXXXXXXXX ", " .XXXXXXX. .XXXXXXXX ", " .XXXXXXXXX. .XXXXXXX.", " .XXXXXXX..X. XXXXXXX.", " .XXXXXXX. .. . XXXXXXX.", " .XXXXX. .X .XXXXXX ", " XXXXX .X .XXXX. ", " .XXX........ XX......... ", " .X.ooXXXXXX .XXXXXXXXXo ", " .X.oXoXXXXX .XXXXXXXXXXo ", " XooXXXXXXX XXXXXXXXXXo. ", " .ooXXXXXXX XXXXXXXXXX. ", " ooXXXXXXX .XXXXXXXXo ", " .XXXXXXX .XXXXXo. ", " ....... XX.... ", " .X ", " .X ", " . "};