public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: stephan o'farrill <stephan.ofarrill@gmail.com>
Cc: pthreads-win32@sourceware.org
Subject: Re: const missing?
Date: Tue, 03 Mar 2009 21:46:00 -0000	[thread overview]
Message-ID: <49ADA52D.8090007@homemail.com.au> (raw)
In-Reply-To: <91535b350903030407t54204a7cnb500baaa055d296d@mail.gmail.com>

I've applied Stephan's change to the following routines in CVS 
(currently untested):-

pthread_attr_getschedpolicy()
pthread_attr_getinheritsched()
pthread_mutexattr_gettype()

Thanks Stephan.

stephan o'farrill wrote:
> Hi All,
>
> I just subscribed to the pthreads-win32 mailing list since I am
> developing a pthread C++ class (in a very early stage). To be able to
> support pthreads-win32 I need that the declarations are following the
> posix standard.
> Usually this is does not make a big difference, but for my purpose it
> is important:
> pthreads-win32s declaration of
>
> PTW32_DLLPORT int PTW32_CDECL pthread_mutexattr_gettype
> (pthread_mutexattr_t * attr, int *kind);
>
> should be re-defined as:
>
> PTW32_DLLPORT int PTW32_CDECL pthread_mutexattr_gettype (const
> pthread_mutexattr_t * attr, int *kind);
>
> according to the posix standard:
> int pthread_mutexattr_gettype(const pthread_mutexattr_t *restrict
> attr, int *restrict type);
>
> I changed it successfully in my test copy of pthreads-win32.
> I could apply the change by myself to CVS if write access could be granted.
>
> All the best,
> and thanks for the good work,
> Hagen.
>   

  reply	other threads:[~2009-03-03 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 12:07 stephan o'farrill
2009-03-03 21:46 ` Ross Johnson [this message]
2009-03-05 21:47 ` condvar implementation Michel Pacilli

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=49ADA52D.8090007@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --cc=pthreads-win32@sourceware.org \
    --cc=stephan.ofarrill@gmail.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).