>>>> "Nix" == Nix
<nix(a)esperi.demon.co.uk> writes:
Nix> On Mon, 21 May 2001, Ovidiu Predescu said:
> This sounds like a really fun project!
Nix> Absolutely. I like cleaning up ugly cruft, and the XEmacs GC
Nix> layer is really rather in need of a good clean, encrufted by
Nix> sheer age.
Well, it would be nice if you could be compatible with Richard
Reingrub's basic outline. Then we could choose among similarly
implemented GCs with different basic strategies, and avoid the
question of "is it the GC or the way it's hooked into XEmacs?"
BTW, I can't think of a good way to see what has been proposed, except
by reading tons of old xemacs-beta posts. Ben's Architecting XEmacs
page (link from
www.xemacs.org) is the most complete (although dated by
now). But you can see some of what's in the process of implementation
by doing "cvs status -v version.sh" (in particular, grep for "gc" or
"GC" to find Richard Reingrub's branch).
I checked fairly recently with our host, and
cvs.xemacs.org has
sufficient bandwidth and disk space to add a more branches like that.
So once you've got things in shape where you're willing to let other
people look at it, talk to martin(a)xemacs.org about getting CVS commit
privileges, create a branch, and let us know about it. :-)
Nix> Myself, I'm still slightly worried about what this will do to
Nix> the weird old architectures XEmacs presumably still builds
Nix> on.
Don't worry; for released XEmacsen your collector will surely go in as
a configure option at first. If they still are in use but can't use
your collector, so be it---the configure option won't work for them.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."