public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Alexey Sushkov" <sushkov@dins.ru>
To: <pthreads-win32@sourceware.cygnus.com>
Subject: Posix
Date: Fri, 01 Jun 2001 05:43:00 -0000	[thread overview]
Message-ID: <003601c0eaa0$f60789d0$34bd77d4@alex2000> (raw)

Hello,

I am porting some app from Linux to Win32. The app uses functions:
pthread_mutex_init(&myId, NULL) pthread_attr_init(&myAttributes) and so on.
Before calling functions it does not allocate memory for myId and
myAttributes variables. As I understand this in correct behavior in Linux
environment because memory is allocated inside the functions but wrong in
Win32 because it is necessary allocate memory before calling the functions.
Am I right? If yes then my question is: why in Win32 you have not emulated
Linux's behavior?

Thanks,
Alexey Sushkov.

             reply	other threads:[~2001-06-01  5:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01  5:43 Alexey Sushkov [this message]
2001-06-01  7:03 Posix Bossom, John
     [not found] <3B17C9EF.F52BB5AB@hawksoft.com>
2001-06-04  1:26 ` Posix Alexey Sushkov

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='003601c0eaa0$f60789d0$34bd77d4@alex2000' \
    --to=sushkov@dins.ru \
    --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).