From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Booting on slow CPUs
Date: Fri, 15 Mar 2002 15:07:49 -0500 [thread overview]
Message-ID: <5a41b36e913f59de1dd89b542c8d9a55@plan9.bell-labs.com> (raw)
You need to poperror() on the path where there's no error, thus:
if(waserror()){
/* no poperror on this path ... */
return nil;
}
poperror();
but
if(!waserror()){
/* do some stuff... */
poperror();
}
/* more stuff */
The second is idiomatic for ``do some stuff, stopping early
if you encounter an error; either way, then do more stuff.''
Russ
next reply other threads:[~2002-03-15 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 20:07 Russ Cox [this message]
2002-03-16 18:31 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2002-03-16 18:55 Russ Cox
2002-03-17 7:26 ` Lucio De Re
2002-03-15 18:10 Lucio De Re
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=5a41b36e913f59de1dd89b542c8d9a55@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).