Re: PDUMP vs. UNION_TYPE + C++
Martin Buchholz <martin(a)xemacs.org> writes:
dump file `belongs' to that particular binary. One obvious way
would
be to have some unique identifier in each temacs that would get
written to the temacs.dmp file as well.
And possibly (at least at make install time), actually name the file
temacs.dpm.UNIQUEID so the user can have his personal dump files
around for multiple XEmacsen.
We have two conflicting things here..
- We want to keep the search logic in lisp[1], and thus the dump file
tied to the executable [ELF/COFF session]
- We want to make it possible for users/site to do their down dump
(for instance with the package autoloads preloaded, so XEmacs can
startup quickly). This would suggest NOT tying the dump file to
lisp.
This begs the question: Is it possible to restart the undump.., i.e.
- XEmacs starts up
- "loads" a tiny dump file from ELF section (presumably it possible to have
this already mapped by the loader).
- This tiny dump file contains the startup lisp code that looks for
the XEmacs.dump.ID file
- Then the undumping starts again with the real XEmacs.dump.ID file
?
Jan
Footnotes:
[1] Although moving it to C would make it possible to do more tricks to
optimize it.