From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
Date: 1999/03/03
Message-ID: <3129458184729552@naggum.no>#1/1
X-Deja-AN: 450751975
References: <joswig-1202992137420001@pbg3.lavielle.com> <p0sz2.5546$fZ4.3483@news2.giganews.com> <87zp69mnql.fsf_-_@2xtreme.ne <m3aey3n9hy.fsf@eho.eaglets.com> <7betab$rci$1@news.u-bordeaux.fr> <3129317074195616@naggum.no> <m390dfk030.fsf@eho.eaglets.com> <3129402613403914@naggum.no> <m34so3jtov.fsf@eho.eaglets.com> <3129441516179845@naggum.no> <nkju2w2es79.fsf@tfeb.org>
mail-copies-to: never
Organization: Naggum Software; +47 8800 8879; http://www.naggum.no
Newsgroups: comp.lang.lisp

* Tim Bradshaw <tfb@tfeb.org>
| That doesn't have to be that bad.  Obviously it depends on the
| application, but shared heaps are fairly doable.  Either using the Emacs
| technique (purecopy + unexec) or just relying on copy-on-first-write VM,
| which I think most Unices can do now.  Whether they'll do that is another
| matter of course.

  first: that isn't how GUILE is intended to be used.  second: I'm talking
  about actual memory consumed by the process for its _own_ data.  data or
  code that cannot be shared.  state information, whatever you want to call
  it.  I haven't see anyone refer to this as anything other than "heap",
  and I find it odd that you think such a heap should be sharable.

#:Erik