From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@9fans.net
Subject: Re: [9fans] lisp
Date: Tue, 8 Jul 2008 22:12:10 +0100 [thread overview]
Message-ID: <5db17b46fc3457c4311a6bc59619ff2d@vitanuova.com> (raw)
In-Reply-To: <20080708190528.919FA5B46@mail.bitblocks.com>
if you make it executable, i think you should also find that the resulting
executable has its contents read into memory on demand (ie, a page fault causes
a read from the executable file), which might suit you.
next prev parent reply other threads:[~2008-07-08 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 18:15 Bakul Shah
2008-07-07 18:45 ` erik quanstrom
2008-07-07 19:20 ` David Leimbach
2008-07-07 19:44 ` Bakul Shah
2008-07-07 19:55 ` Charles Forsyth
2008-07-07 20:15 ` Bakul Shah
2008-07-07 20:21 ` David Leimbach
2008-07-07 20:47 ` Bakul Shah
2008-07-07 20:51 ` David Leimbach
2008-07-08 14:08 ` Dave Eckhardt
2008-07-08 15:07 ` David Leimbach
2008-07-08 19:05 ` Bakul Shah
2008-07-08 21:12 ` C H Forsyth [this message]
2008-07-08 21:42 ` Bakul Shah
2008-07-07 20:43 ` geoff
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=5db17b46fc3457c4311a6bc59619ff2d@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@9fans.net \
/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).