From -2645927981820329895
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,bf65828a2bbbc32e
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 1993-12-13 16:13:49 PST
Path: gmd.de!xlink.net!howland.reston.ans.net!paladin.american.edu!europa.eng.gtefsd.com!uunet!EU.net!sunic!news.lth.se!dag
From: dag@control.lth.se (Dag Bruck)
Newsgroups: comp.std.c++
Subject: Re: bool run-time performance impact
Date: 13 Dec 1993 18:13:40 GMT
Organization: Department of Automatic Control, Lund, Sweden
Lines: 15
Distribution: world
Message-ID: <2eibck$5ii@nic.lth.se>
References: <trickr.11.000B9FAA@uh2372p03.daytonoh.ncr.com> <9334701.20716@mulga.cs.mu.OZ.AU> <2eh58b$fg6@nic.lth.se> <2eiaqt$s87@urmel.informatik.rwth-aachen.de>
NNTP-Posting-Host: control.lth.se

In <comp.std.c++> dak@hathi.informatik.rwth-aachen.de (David Kastrup) writes:
>>In <comp.std.c++> fjh@munta.cs.mu.OZ.AU (Fergus Henderson) writes:
>>>It would be quite reasonable for compilers to use a non-canonical
>>>representation where anything non-zero is true.  In this case,
>>>conversion from int to bool would be a no-op.
>
>>Not quite; the proposal explicitly says that a bool, when promoted to
>>int, yields the values 0 or 1.
>
>Well, what of it?

Quite right.  I read "bool to int" instead of "int to bool."


					-- Dag


