From: aureliom@crt.com
To: pthreads-win32@sourceware.cygnus.com
Subject: _POSIX_THREAD constant
Date: Wed, 20 Oct 1999 07:01:00 -0000 [thread overview]
Message-ID: <F931488C3634D11180D700A02461E24502035B4D@chitmd03.nt.il.nbgfn.com> (raw)
To whom it may concern,
Can someone in a future version wrap the compile-time symbolic constant in
the 'pthread.h' header file as follows:
#ifndef _POSIX_THREADS
#define _POSIX_THREADS
#endif
This constant, as well as a few others, is generally set in the 'unistd.h'
header file at compile time (UNIX). My WinNT/UNIX program uses this
constant to determine if POSIX threads are available at compile time and
uses different code segments depending on this check. On WinNT I set this
variable explicitly in the make/project file (i.e. /D "_POSIX_THREADS")
since there is no 'unistd.h' header file. This in turn leads to a 'warning
C4005: '_POSIX_THREADS' : macro redefinition' message. I understand this is
a very minor issue, but this will eliminate this warning for those of us who
have cross-platform applications that need to determine at compile time if
POSIX threads are available.
Thanks,
Aurelio Medina
Bank of America, Distributed Systems Management
mailto:aureliom@crt.com < mailto:aureliom@crt.com >
reply other threads:[~1999-10-20 7:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=F931488C3634D11180D700A02461E24502035B4D@chitmd03.nt.il.nbgfn.com \
--to=aureliom@crt.com \
--cc=pthreads-win32@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).