"Richard M. Stallman" <[EMAIL PROTECTED]> writes: > > So, if there's a non-pure object that is only pointed to by pure > > objects, which may happen if the assumption for the pure storage is > > violated, then the object is reachable but get collected. > > Now I'm sure this is the real cause of "Wrong type argument: commandp" > error that is found in some Carbon Emacs distributions that preloads > international/encoded-kb.elc. > > Suppose that the pure structures here were not modified. > (That is, suppose we deleted the code that modifies them, > and put in the correct contents when those data structures > are first created.) Would we still have the problem of > pure pointing to impure which gets GC'd? >
Can't we just gc the pure space too? At least with the mark-stack functionality, that would be fairly trivial. BTW, wouldn't it be about time to drop the old GCPRO stuff -- IMHO it is just too time-consuming to maintain (and it is practically impossible to find those bugs). What platforms cannot use mark-stack? Are they really worth supporting? [after all, emacs 21.4 _is_ still available on those platforms, so users on those systems are not completely lost]. -- Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
