Re: To commit or not to commit?
OK, very well, I'll send you the diffs. If I can, I'll make an rtag, else
I'll
tell you the time I last synched up, so you can get a clean application. (Not
much activity currently, anyway.) Note my last message, that I'd gotten
descriptions written for lrecord-list (which was the last not to have a
description), and fixed the problems marking weakness in hash tables and markers
that shouldn't be marked. (basically, i introduced a fifth field `flags' to the
now-renamed memory descriptions. one flag is XD_FLAG_NO_KKCC, which causes KKCC
to ignore that particular entry. I use that to ignore the next and prev fields
on a marker and, in conjunction with a union, to ignore the data inside of a
weak hash table. Without this addition for markers,
I regularly was getting a stack overflow crash after awhile due to an
ever-increasing list of markers.
ben
----- Original Message -----
From: "Michael Sperber [Mr. Preprocessor]"
<sperber(a)informatik.uni-tuebingen.de>
To: "Ben Wing" <ben(a)666.com>
Cc: "XEmacs beta list" <xemacs-beta(a)xemacs.org>; "XEmacs
Reviews"
<xemacs-review(a)xemacs.org>
Sent: Monday, December 16, 2002 12:19 AM
Subject: Re: To commit or not to commit?
>>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
Ben> I have been waiting a couple of days from Mike Sperber for heads-up on
Ben> committing my new KKCC-change workspace. I am getting on a plane in 36
hours
Ben> and haven't heard from him so i need to know what you
guys think. i can
tag the
Ben> tree and then commit so you guys can restore in an emergency,
or just
leave the
Ben> commit till mid-January and hope that Mike isn't planning
on doing any
work on
Ben> KKCC before then.
How about *I* commit after I've reviewed the patch?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla