From: Brendan Kehoe <brendan@cs.widener.edu>
To: rc@archone.tamu.edu
Subject: avoiding recursion in functions
Date: Sat, 23 Nov 1991 19:58:16 -0600 [thread overview]
Message-ID: <199111240158.AA02228@lisa.cs.widener.edu> (raw)
I had this defined:
fn rm { rm -i }
which is wrong -- it'll constantly call itself & spiral into
oblivion. How can I avoid the second rm being interpreted as the
function, and instead have it run through the path for it? (I'd like
to avoid putting the explicit path in there.)
--
Brendan Kehoe, Sun Network Manager brendan@cs.widener.edu
Widener University Chester, PA
``The reference section discusses Calc in complete depth.''...complete depth?
-- Calc 2.00 manual
next reply other threads:[~1991-11-24 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-11-24 1:58 Brendan Kehoe [this message]
1991-11-24 2:17 ` Robert Earl
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=199111240158.AA02228@lisa.cs.widener.edu \
--to=brendan@cs.widener.edu \
--cc=rc@archone.tamu.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).