From: Byron Rakitzis <byron>
To: rc
Subject: Re: eval vs &
Date: Thu, 9 Apr 1992 19:19:36 -0500 [thread overview]
Message-ID: <92Apr9.191943cdt.45334@archone.tamu.edu> (raw)
re: eval and &. Well, input for eval is rescanned noninteractively,
so interactive features get lost during an eval. This is perhaps
bogomorphic. At the same time, however, you don't want rc to print
prompts while it chugs through an eval.
re: wait(). rc does not trap SIGCLD, so it cannot notify you
asynchronously of a child's death. This may be another bogomorphism,
but so far I've been using Occam's razor, i.e., avoiding complexity
in the design whenever possible.
next reply other threads:[~1992-04-10 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-04-10 0:19 Byron Rakitzis [this message]
1992-04-10 0:35 ` schwartz
-- strict thread matches above, loose matches on Subject: below --
1992-04-10 0:06 Scott Schwartz
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=92Apr9.191943cdt.45334@archone.tamu.edu \
--to=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).