This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: 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.
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, roland dot illig at gmx dot de
- Date: 22 Mar 2003 04:26:02 -0000
- Subject: Re: 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.
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, roland dot illig at gmx dot de, gcc-gnats at gcc dot gnu dot org
Synopsis: new keyword "boolif" that accepts only <stdbool.h>bool values "true" or "false" as arguments; comparison operators that return <stdbool.h>bool values.
State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Sat Mar 22 04:26:01 2003
State-Changed-Why:
As desirable as this might be, I don't see any chance of this
being implemented. The standards provide default conversions
between integers and booleans, which would have to be
abandoned temporarily if inside if-statements. I cannot
imagine that people will want to work on this inside gcc
any time soon, so can't see a value in keeping this report
open.
Sorry
Wolfgang
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10036