public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: roland.illig@gmx.de To: gcc-gnats@gcc.gnu.org Subject: c/10036: new keyword "boolif" that accepts only <stdbool.h>bool values "true" or "false" as arguments; comparison operators that return <stdbool.h>bool values. Date: Wed, 12 Mar 2003 10:26:00 -0000 [thread overview] Message-ID: <20030312102121.2724.qmail@sources.redhat.com> (raw) >Number: 10036 >Category: c >Synopsis: new keyword "boolif" that accepts only <stdbool.h>bool values "true" or "false" as arguments; comparison operators that return <stdbool.h>bool values. >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Wed Mar 12 10:26:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: roland.illig@gmx.de >Release: unknown-1.0 >Organization: >Environment: any >Description: #include <stdbool.h> /* let === be an equality operator whose type is (any,any)->bool. */ int main(void) { int a = 12345; int b = -12345; boolif (a - b === 0) { printf("ok\n"); } else { printf("not ok\n"); } boolif (a) { /* this shall lead to a compiler error */ printf("12345 == true\n"); } else { printf("12345 != true\n"); } } The strict-bool type shall have no implicit conversion rules from or to other types. The only way to get a strict-bool is the application of the strict-bool operators. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-12 10:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 10:26 roland.illig [this message] 2003-03-22 4:26 bangerth
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=20030312102121.2724.qmail@sources.redhat.com \ --to=roland.illig@gmx.de \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).