From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc futures
Date: Wed, 15 Dec 1999 11:32:27 -0500 [thread overview]
Message-ID: <199912151632.LAA19961@smtp3.fas.harvard.edu> (raw)
> 23. Dynamically load readline only when rc is about to read from a
> terminal device. This would mean that a single rc binary would be
> lean and fast for scripts, but still do readline for interactive use.
> However, I suspect that the effort involved in making this happen
> portably would be considerable.
What operating system doesn't demand-load the binaries anyway?
If you're not using the readline code, (the large majority of) it won't
be resident in memory.
And furthermore surely your OS is sharing text pages, so as long
as there is one rc binary running on a terminal, you've already got
it loaded and there's no penalty for running more or for running
scripts.
As Byron said, the mind boggles.
Russ
next reply other threads:[~1999-12-19 7:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 16:32 Russ Cox [this message]
2000-01-05 11:59 ` Dynamically loading readline on demand (was Re: rc futures) Tim Goodwin
2000-01-01 0:22 ` Paul Haahr
2000-01-14 16:26 ` Tim Goodwin
2000-01-14 19:18 ` Paul Haahr
2000-01-13 0:19 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2000-01-14 12:20 rc futures Bengt Kleberg
2000-01-14 12:16 Bengt Kleberg
2000-01-12 21:34 Chet Ramey
2000-01-01 2:55 ` Paul Haahr
2000-01-12 14:22 Bengt Kleberg
2000-01-03 15:46 Bengt Kleberg
1999-12-16 16:40 Chet Ramey
1999-12-16 12:43 Smarasderagd
1999-12-19 11:06 ` Steve Kilbane
1999-12-22 0:00 ` Christopher Vance
1999-12-14 9:44 Byron Rakitzis
1999-12-13 12:55 Elliott Hughes
1999-12-10 16:55 Tim Goodwin
1999-12-13 18:54 ` Paul Haahr
2000-01-04 16:43 ` Tim Goodwin
1999-12-31 23:26 ` Paul Haahr
1999-12-15 0:17 ` Chris Siebenmann
2000-01-07 3:45 ` Decklin Foster
2000-01-01 4:20 ` Paul Haahr
2000-01-15 8:58 ` Steve Kilbane
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=199912151632.LAA19961@smtp3.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).