From: ISHWAR RATTAN <rattan@cps.cmich.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9port: threadid() etc.
Date: Tue, 17 Oct 2006 20:39:16 -0400 [thread overview]
Message-ID: <Pine.GSO.4.61.0610172036190.22686@cps-kurali.cps.cmich.edu> (raw)
In-Reply-To: <ee9e417a0610171437p1389877bvdb56db4ac175e78c@mail.gmail.com>
On Tue, 17 Oct 2006, Russ Cox wrote:
> If you are talking about the port to Unix:
> Threadid exists. Threadpid does not,
For threadid(), the compiler 9c complainsabout implicit
declaration of threadid(), so, I checked in the header file
there is no prototype for threadid() and linker can't find it.
I did include <thread.h>..
-ishwar
> because it does not make sense
> (multiple procs might share the same pid,
> so using the pid to identify a proc is a
> road to disaster).
>
> Russ
>
next prev parent reply other threads:[~2006-10-18 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 21:25 ISHWAR RATTAN
2006-10-17 21:37 ` Russ Cox
2006-10-18 0:39 ` ISHWAR RATTAN [this message]
2006-10-18 15:31 ` Russ Cox
2006-10-19 5:33 ` ISHWAR RATTAN
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=Pine.GSO.4.61.0610172036190.22686@cps-kurali.cps.cmich.edu \
--to=rattan@cps.cmich.edu \
--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).