From: Manish Katiyar <mkatiyar@gmail.com>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: WaitForMultipleObjects sources for a C application
Date: Tue, 17 Feb 2009 18:21:13 +0530 [thread overview]
Message-ID: <ea11fea30902170451n73afe5c2x32500db847870bb1@mail.gmail.com> (raw)
In-Reply-To: <F5BA82141F7AA94885B9643C77EEA5F2104324@mail.esntechnologies.co.in>
On Tue, Feb 17, 2009 at 5:48 PM, Srinivas G.
<srinivasg@esntechnologies.co.in> wrote:
> Dear All,
>
> I have downloaded the source code for the WaitForMultipleObjects API to
> use on Linux box from the following link.
> http://home.arcor.de/rdengler/
>
> However, the sources are developed in the C++. I am not able to use
> these sources in my C application due to classes and its definitions.
> When I tried to convert the classes into an equivalent C structures I
> got the following error.
>
> std::set<CWinEventHandle*> m_Subscriber; // Used in
> WaitForMultipleObjects()
>
> Could you please let me know how can I use CPP sources in a C
> application? Is there any equivalent C code for the same
> WaitForMultipleObjects?
Aren't they more or less equivalent to condition variables ?? You can
also have a look at the below link
http://www.ibm.com/developerworks/eserver/library/es-win32linux-sem.html
Thanks -
Manish
>
> Thanks in advance.
>
> With Regards,
> Srinivas G
> --
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-02-17 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 12:18 WaitForMultipleObjects sources for a C application Srinivas G.
2009-02-17 12:51 ` Manish Katiyar [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=ea11fea30902170451n73afe5c2x32500db847870bb1@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=srinivasg@esntechnologies.co.in \
/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 NNTP newsgroup(s).