From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What is required of an open file to be used in ape/select?
Date: Tue, 9 Apr 2002 19:46:53 +0100 [thread overview]
Message-ID: <20020409185058.9CA6D19A57@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 83 bytes --]
i did use it for that reason under second edition
and it worked as i expected.
[-- Attachment #2: Type: message/rfc822, Size: 1608 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] What is required of an open file to be used in ape/select?
Date: Tue, 9 Apr 2002 10:29:07 -0400
Message-ID: <20020409142546.E3C7919A7A@mail.cse.psu.edu>
> I'm not convinced you want to go down this path. It's
> almost always easier to use libthread and have separate
> procs reading from fds and passing data pointers back to a
> main proc.
I agree. But I'm trying to write some stuff that will port
easily to Unix machines.
Brantley
next reply other threads:[~2002-04-09 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 18:46 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 14:29 bwc
2002-04-09 14:28 Russ Cox
2002-04-09 14:23 Russ Cox
2002-04-09 14:27 ` Boyd Roberts
2002-04-09 14:18 bwc
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=20020409185058.9CA6D19A57@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).