mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
Cc: musl@lists.openwall.com, Michael Clark <michaeljclark@mac.com>
Subject: Re: stdbool.h does not define _Bool when included by C++ code
Date: Mon, 31 Jul 2017 11:46:23 +0200	[thread overview]
Message-ID: <20170731114623.0a449442@inria.fr> (raw)
In-Reply-To: <20170731091828.GA15263@port70.net>

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

Hello,

On Mon, 31 Jul 2017 11:18:28 +0200 Szabolcs Nagy <nsz@port70.net> wrote:

> iow, this is either a minor gcc bug or a big fat c++ defect
> depending on how you look at it, the libc cannot fix this
> properly, just emulate the broken nonsense in gcc stdbool.h
> that nobody should rely on.

Basically stdbool.h is already a header to accomodate C++ usage of
bool, false and true to C. I makes not much sense to include this
in C++ code.

I think that applications that want to be shure that their code
compiles for both should use "bool" and should do

#ifndef __cplusplus
# include <stdbool.h>
#endif

We can put more comfort into this by lifting this #ifndef/#endif stuff
to the contents of the file, if people really want this. But code that
relies on this would not be guaranteed to be portable.

Using "bool" by means of the header is the intended usage, these
attrocities such as _Bool, _Noreturn etc are only there for backwards
compatibility. Hopefully at least some of them will be phased out in
the future.

I think we should not encourage the usage of these keywords in
application code unless this is needed for backwards compatibility,
nor should we try to impose their possible usage into other languages.

Jens

-- 
:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-07-31  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 10:21 Michael Clark
2017-07-28 13:01 ` Rich Felker
2017-07-31  9:18 ` Szabolcs Nagy
2017-07-31  9:46   ` Jens Gustedt [this message]
2017-07-31 21:06     ` Michael Clark
2017-08-01  1:31       ` Rich Felker
2017-08-01  7:24         ` Jens Gustedt

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=20170731114623.0a449442@inria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=michaeljclark@mac.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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