From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] semaphores
Date: Fri, 25 Jan 2002 09:53:33 -0500 [thread overview]
Message-ID: <20020125145334.DD45B19A55@mail.cse.psu.edu> (raw)
> Should that be `typedef struct Semaphore Sema;' in order for s->data to
> work?
probably struct Sema, but yeah.
i haven't actually compiled the code.
like i said, as soon as i wrote it
i discovered i didn't need it.
next reply other threads:[~2002-01-25 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 14:53 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-22 23:05 [9fans] Semaphores Joel Salomon
2006-10-22 23:21 ` Russ Cox
2006-10-22 23:29 ` Steve Simon
2002-01-16 7:48 [9fans] semaphores nigel
[not found] <rsc@plan9.bell-labs.com>
2002-01-16 3:44 ` Russ Cox
2002-01-16 3:54 ` Scott Schwartz
2002-01-16 11:14 ` Boyd Roberts
2002-01-16 15:47 ` Ronald G Minnich
2002-01-25 10:30 ` Ralph Corderoy
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=20020125145334.DD45B19A55@mail.cse.psu.edu \
--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).