The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Emacs and undump
Date: Mon, 27 Feb 2017 06:41:56 +0000	[thread overview]
Message-ID: <3FA64C9B-4EBB-4EDA-8BD7-B59DAE6BF650@tfeb.org> (raw)
In-Reply-To: <141DC1F7-C4AA-4EF4-8CBE-E99845326D7B@kdbarto.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

> On 26 Feb 2017, at 19:16, David <david at kdbarto.org> wrote:
> 
> I remember that GNU Emacs launched the first time and then dumped itself out as a core file. Each subsequent launch would then ‘undump’ itself back into memory. All this because launching emacs the first time required compiling all that lisp code.

It still works like that.  Indeed that's the conventional way that Lisp systems tend to work for delivering applications: you compile and load your code into a running image and then dump that image in a form where it can be reloaded quickly.  The dumped image is either directly executable or is loaded by some small bootstrap loader which might also provide some low-level support (but might not: all that can be in the dumped image).  What you call these dumped images depends on your culture: they might be 'worlds', 'bands' or 'sysouts' among other things.

(There are often also compiled files which are generally called fasl files, though in emacs they are elc files.)


  parent reply	other threads:[~2017-02-27  6:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.334.1488132096.3779.tuhs@minnie.tuhs.org>
2017-02-26 19:16 ` David
2017-02-26 19:28   ` Mantas Mikulėnas
2017-02-27  6:41   ` Tim Bradshaw [this message]
2017-02-27  7:19     ` Lars Brinkhoff
2017-02-27  7:26       ` Warner Losh
2017-02-27  8:12         ` Nick Downing
2017-02-27 14:33           ` Derek Fawcus
2017-02-27 14:50             ` Nick Downing
2017-02-27 15:43               ` Derek Fawcus
2017-02-27 16:43             ` Joerg Schilling
     [not found]               ` <CAH1jEzZjvOhHnbvsWcw8gbx9d_W47DbBidYd_tteCr5dC6H2ng@mail.gmail.com>
2017-02-28  0:02                 ` Nick Downing
2017-02-27 12:59       ` tfb
2017-02-27 10:35   ` Joerg Schilling
2017-02-27 15:13     ` Tony Finch
     [not found] <mailman.342.1488180370.3779.tuhs@minnie.tuhs.org>
2017-02-27 10:24 ` Johnny Billquist
2017-02-27 10:30   ` Lars Brinkhoff
2017-02-27 10:47     ` Johnny Billquist
2017-02-27 14:04       ` Arthur Krewat
2017-02-28 11:55         ` Ronald Natalie
     [not found] <mailman.346.1488208394.3779.tuhs@minnie.tuhs.org>
2017-02-27 20:09 ` Johnny Billquist
2017-02-27 20:26   ` Lars Brinkhoff
2017-02-27 21:06     ` Johnny Billquist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FA64C9B-4EBB-4EDA-8BD7-B59DAE6BF650@tfeb.org \
    --to=tfb@tfeb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).