Re: Unmark pdumped objects
>>>> "Hrv" == Hrvoje Niksic
<hniksic(a)srce.hr> writes:
Hrv> Olivier Galibert <galibert(a)pobox.com> writes:
> Hence it has gone with my killer blow on the purespace code.
Well,
> I don't think I have a "in the dumping" flag handy enymore, but it
> is easy enough to add. Hvroje seems to think that the space
> expansion due to the systematic use of o-c-f may be a problem,
> though. Comments?
Hrv> Only "may". If you can find the size of the dumped code with and
Hrv> without o-c-f dumping and present us the two numbers, it might very
Hrv> well prove that the size increase is irrelevant.
It used to be, when you build XEmacs in debug mode, that it would
print out the sizes of things, including byte-code stuff, when it
dumped. Olivier, you could try building one of those ancient
pre-pdump XEmacsen and see what happens. That sort of information
*is* useful for core C developers such as yourself.
The original bytecode string is discarded (and ``re-constructed'' when
the user calls compiled-function-instructions or disassemble), so
there is effectively NO extra space used, in fact there may be a
slight saving in space when the original compiled function
instructions are (hopefully) garbage collected.
Martin