Subject: builtins, changes et al
Date: Mon, 20 Sep 1993 05:42:19 -0400 [thread overview]
Message-ID: <9309200942.AA16182@dahlie.techfak.uni-bielefeld.de> (raw)
Why not discuss changes and/or additions to rc until blue-in-the-face?
I for myself am very grateful for the reponses I received in return to
my last proposal 'cause if I had already implemented it, I'd have to
rework the code now. I don't think this forum should evolve into some
kind of beta test group.
And about reusability, libsh.a (librc.a in this case): As someone else
already stated, there is no easy way to ensure that your shell scripts
uses the same version of some not builtin feature, making it difficult
to pass them on to others. The multics approach stems from a time where
networking was a thing of the future. Who can assure that
email@example.com won't receive the necessary library module
lightyears after my script?
Now back to the real world, I don't like the idea of a builtin read
with sh semantics too much. I'd prefer a more general solution,
some kind of printf - scanf pair which is _not_ builtin. It's already
part of the GNU shellutils.
next reply other threads:[~1993-09-20 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-20 9:42 malte [this message]
1993-09-20 13:20 Alan Watson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).