public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Václav Haisman" <V.Haisman@sh.cvut.cz>
To: cygwin@cygwin.com
Subject: Re: wrong macro definition in pthread.h
Date: Tue, 14 Feb 2006 16:09:00 -0000	[thread overview]
Message-ID: <43F2002B.3090405@sh.cvut.cz> (raw)
In-Reply-To: <1139836005.8591.384.camel@rosella.wigram>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]



skaller wrote:
> On Mon, 2006-02-13 at 21:27 +0900, 橋 宏彰 wrote:
>> In cvs head.
>>
>> winsup/cygwin/include/pthread.h
>>
>>   #define pthread_cleanup_push(_fn, _arg) { __pthread_cleanup_handler __cleanup_handler = \
>>                                            { _fn, _arg, NULL }; \
>>                                            _pthread_cleanup_push( &__cleanup_handler );
>>   #define pthread_cleanup_pop(_execute) _pthread_cleanup_pop( _execute ); }
>>
>> incorrect '}' position.
>>
> 
>From my man pthread_cleanup_push:
> 
> Matching  pairs of !pthread_cleanup_push! and !pthread_cleanup_pop!
> must occur in the same function, at the same level of  block  nest‐
> ing.   Actually,  !pthread_cleanup_push!  and !pthread_cleanup_pop!
> are macros, and the expansion of !pthread_cleanup_push!  introduces
> an open brace !{!  with the matching closing brace !}! being intro‐
> duced by the expansion of the matching !pthread_cleanup_pop!.
This is what SUSv3 says too.

> 
> SO if this is a bug .. it is shared by Linux..:)
> 

VH


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 542 bytes --]

      parent reply	other threads:[~2006-02-14 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 13:06 橋 宏彰
2006-02-13 13:47 ` skaller
2006-02-13 14:33   ` HASHI Hiroaki
2006-02-14 16:09   ` Václav Haisman [this message]

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=43F2002B.3090405@sh.cvut.cz \
    --to=v.haisman@sh.cvut.cz \
    --cc=cygwin@cygwin.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).