From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: culliton@srg.af.mil (Tom Culliton x2278)
Cc: haahr@mv.us.adobe.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: Speed of rc
Date: Thu, 8 Apr 1993 20:38:11 -0400 [thread overview]
Message-ID: <93Apr8.203942edt.2538@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 08 Apr 1993 18:31:31 EDT." <9304081831.aa24256@ceres.srg.af.mil>
Just some random thoughts...
Tom writes:
| I actually spent a fair amount of time once trying to figure out a
| stunt to run co-processes under rc so I can fire up sh (for test), and
| something else to do math, exactly once and then have functions that
| talk to them. In the end I decided it either couldn't be done or
| wasn't worth the effort.
Yet another defect in Unix, where IPC is so limited that even simple
and obvious things are so painful that no one does them. Similarly, if
dynamic loading were fundamental and pervasive one could envision
taking any a.out file, mapping it once, and then calling its entry
points. For example, make the system (OS, language runtime, etc)
understand /bin/sh/glob. Then the normal execve means calling
/bin/sh/main.
The problem with being spartan is that you end up being stoic.
next prev parent reply other threads:[~1993-04-09 0:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-08 22:31 Tom Culliton x2278
1993-04-09 0:38 ` Scott Schwartz [this message]
1993-04-09 15:23 ` John Mackin
1993-04-13 19:26 ` Chris Siebenmann
1993-04-13 21:13 ` John Mackin
1993-04-09 16:32 ` Dave Mason
1993-04-09 16:39 ` John Mackin
1993-04-09 19:22 ` Dave Mason
1993-04-09 21:12 ` Chris Siebenmann
-- strict thread matches above, loose matches on Subject: below --
1993-04-15 20:26 speed " Tom Culliton x2278
1993-04-13 20:26 Byron Rakitzis
1993-04-13 21:23 ` John Mackin
1993-04-13 23:42 ` mycroft
1993-04-12 5:51 Speed " Paul Haahr
1993-04-09 15:58 Tom Culliton x2278
1993-04-08 23:09 Paul Haahr
1993-04-08 20:14 Byron Rakitzis
1993-04-08 15:45 Paul Haahr
1993-04-07 19:50 Tom Culliton x2278
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=93Apr8.203942edt.2538@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=culliton@srg.af.mil \
--cc=haahr@mv.us.adobe.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).