public inbox for
 help / color / mirror / Atom feed
From: Grant Edwards <>
Subject: [ECOS] Once again, I need a binary semaphore
Date: Mon, 16 Mar 2015 17:18:00 -0000	[thread overview]
Message-ID: <me737v$ojs$> (raw)

Once again, I find I need a binary semaphore for a C application I'm
porting from another OS.

The eCos kernel has binary semaphores, but there is only a C++ API and
no C API.  I and others have asked why there is no C API for binary
semaphores, and all I've ever really understood of the answer was that
certain developers didn't think binary semaphores were cool enough.

I'm implementing a C API for binary semaphores.  It'c completely
trivial and consits of only a few dozen lines of code.  Any chance
such a patch would be accepted, or are binary semaphores still too
uncool to sit at the same lunch table as mutexes and counting

Grant Edwards               grant.b.edwards        Yow! I smell like a wet
                                  at               reducing clinic on Columbus

Before posting, please read the FAQ:
and search the list archive:

             reply	other threads:[~2015-03-16 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 17:18 Grant Edwards [this message]
2015-03-17  9:21 ` lesc
2015-03-17 14:33   ` [ECOS] " Grant Edwards
2015-03-17 14:47     ` Grant Edwards
2015-03-17 14:57       ` Frank Pagliughi
2015-03-17 15:19         ` Grant Edwards

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='me737v$ojs$' \ \ \

* 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).