From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] _xinc vs ainc
Date: Sat, 7 May 2011 23:00:37 -0700 [thread overview]
Message-ID: <BANLkTikqnHVz=s6yoJi2_J4FueDu4uFC5g@mail.gmail.com> (raw)
In-Reply-To: <f7a852a029ef39ffa039b8ff51293722@brasstown.quanstro.net>
The type signature reveals all: ainc returns a long, and xinc is void.
You really can't test the value of the long * after you call xinc
because somebody else might have done an xinc after your xinc but
before you test the value.
I think, among others, floren and I needed ainc for devtrace years
ago. I am sure that there are even better reasons than that.
ainc is correct as written, as far as I can tell. I don't think the
definition of ainc really requires fairness, since life doesn't either
:-)
ron
next prev parent reply other threads:[~2011-05-08 6:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:05 erik quanstrom
2011-05-07 19:33 ` Bakul Shah
2011-05-07 22:47 ` erik quanstrom
2011-05-07 23:10 ` Bakul Shah
2011-05-08 0:25 ` erik quanstrom
2011-05-08 1:24 ` Bakul Shah
2011-05-08 2:44 ` Venkatesh Srinivas
2011-05-08 6:00 ` ron minnich [this message]
2011-05-08 13:14 ` erik quanstrom
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='BANLkTikqnHVz=s6yoJi2_J4FueDu4uFC5g@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=9fans@9fans.net \
/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).