From: Bastian Voigt <bastian@voigt.in-berlin.de>
To: pthreads-win32@sources.redhat.com
Subject: Re: unexpected end of file :-(
Date: Wed, 03 Nov 2004 10:50:00 -0000 [thread overview]
Message-ID: <4188B7F6.6060004@voigt.in-berlin.de> (raw)
In-Reply-To: <41883645.70704@callisto.canberra.edu.au>
Ross Johnson wrote:
> #define pthread_cleanup_push(a,b)
> and no
> #define pthread_cleanup_pop(a)
>
> Is that an omission?
No, it's not :-)
> The way these are defined is as a pair that forms the start and end of
> a block. That is, push with no pop will create an unbalanced { ... },
> and that could be the problem.
Yes, that was the problem. I must admit Iam a pthreads n00b ..Thanks for
your help!
Regards,
Bastian Voigt
prev parent reply other threads:[~2004-11-03 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 9:59 Bastian Voigt
2004-11-03 1:38 ` Ross Johnson
[not found] ` <41883645.70704@callisto.canberra.edu.au>
2004-11-03 10:50 ` Bastian Voigt [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=4188B7F6.6060004@voigt.in-berlin.de \
--to=bastian@voigt.in-berlin.de \
--cc=pthreads-win32@sources.redhat.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).