From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Rc shell FAQ
Date: Tue, 4 Mar 2003 18:06:14 +0000 [thread overview]
Message-ID: <f4c3c39b0445a6025c50ad8e38895a10@vitanuova.com> (raw)
> I don't think you're missing anything. It's rc that's missing something.
> I don't know why, but it doesn't have a return statement and it should.
it is at least possible to fake it with:
fn x {
status=blah
}
lack of "break" is sometimes more annoying to work around.
next reply other threads:[~2003-03-04 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 18:06 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-01 23:46 A.S. Kukhar
2003-03-03 19:25 ` andrey mirtchovski
2003-03-04 17:52 ` rob pike, esq.
2003-03-04 18:02 ` andrey mirtchovski
2003-03-05 3:42 ` A.S. Kukhar
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=f4c3c39b0445a6025c50ad8e38895a10@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.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).