Mercurial > hg > xemacs-beta
view BUGS @ 888:201c016cfc12
[xemacs-hg @ 2002-06-28 14:24:07 by michaels]
2002-06-27 Mike Sperber <mike@xemacs.org>
* data.c (prune_weak_boxes): Rewrite for better readability.
2002-06-23 Martin Köbele <martin@mkoebele.de>
Jens Müller <jmueller@informatik.uni-tuebingen.de>
Mike Sperber <mike@xemacs.org>
* lrecord.h (lrecord_type): add lrecord_type_ephemeron to lrecord_type enumeration.
* lisp.h (XEPHEMERON):
(XEPHEMERON_REF):
(XEPHEMERON_NEXT):
(XEPHEMERON_FINALIZER):
(XSET_EPHEMERON_NEXT):
(XSET_EPHEMERON_VALUE):
(XSET_EPHEMERON_KEY):
(wrap_ephemeron):
(EPHEMERONP):
(CHECK_EPHEMERON):
(CONCHECK_EPHEMERON):
(struct ephemeron): Add representation of ephemerons.
* alloc.c (garbage_collect_1):
(finish_marking_ephemerons):
(prune_ephemerons): Call.
* data.c:
(finish_marking_ephemerons):
(prune_ephemerons):
(mark_ephemeron):
(print_ephemeron):
(ephemeron_equal)
(ephemeron_hash)::
(make_ephemeron):
(Fmake_ephemeron):
(Fephemeronp):
(Fephemeron_ref):
(syms_of_data):
(vars_of_data): Add implementation of ephemerons
author | michaels |
---|---|
date | Fri, 28 Jun 2002 14:24:08 +0000 |
parents | 9f59509498e1 |
children |
line wrap: on
line source
If you think you may have found a bug in XEmacs, please read the Bugs section of the XEmacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the XEmacs manual. (2) With Info. Start XEmacs, do C-h i to enter Info, then m XEmacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the XEmacs distribution.) (3) By hand. Do cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs," Part II of the XEmacs FAQ, available in a manner similar to the above, or via the world wide web, contains extensive information on how to track down and report bugs. http://www.xemacs.org/faq/