From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2746dae4f161c04e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-22 07:51:52 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: rod@praxis-cs.co.uk (Rod Chapman) Newsgroups: comp.lang.ada Subject: Re: Understanding Booleans Date: 22 Nov 2001 07:51:51 -0800 Organization: http://groups.google.com/ Message-ID: References: <20011121.053507.496987743.3460@web.de> <3BFBDF14.4B83708B@boeing.com> <5ee5b646.0111212023.17ab963d@posting.google.com> NNTP-Posting-Host: 213.155.153.242 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1006444312 22358 127.0.0.1 (22 Nov 2001 15:51:52 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 22 Nov 2001 15:51:52 GMT Xref: archiver1.google.com comp.lang.ada:16872 Date: 2001-11-22T15:51:52+00:00 List-Id: > A := (b = c) or (e = f); > > some people prefer to write > > if (b = c) or (e = f) then > A := True; > else > A := False; > end if; The latter form suffers slightly from introducing two paths, whereas the former only has one (ignoring the possibility for the moment of the compiler transforming the "or" into an "or else".) This could have a negative effect on coverage analysis and the volume (but not the difficulty) of code proof. - Rod