Re: ELisp data: new C representation

Martin> As to the goals of the project, I assume it is to reduce memory Martin> footprint for the xemacs process. Unused lisp objects can be paged to Martin> disk and mostly stay there? There's little of that, even though generational GC will probably sometimes have that effect. The main ultimate goal is to have *way* faster GC. Having the GC take up >50% of runtime *especially* in the presence of a slow mutator like XEmacss is just unacceptable. Another aim is to reduce the duration of GC pauses. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla