From: Steven Sharp (sharp@cadence.com)
Date: Tue Feb 15 2005 - 12:40:00 PST
The following reply was made to PR errata/650; it has been noted by GNATS.
From: Steven Sharp <sharp@cadence.com>
To: etf-bugs@boyd.com, Shalom.Bresticker@freescale.com
Cc:
Subject: Re: errata/650: 9.7.6 does not explicitly say what happens if "wait" condition is x or z
Date: Tue, 15 Feb 2005 15:54:30 -0500 (EST)
> I agree that this was the intent. However, the terms true and false are almost
> certainly used in other contexts where x and z are not included. So it would
> be more precise to say that x is considered false in the context of a
> condition, not an arbitrary expression.
>
> And even there, there are exceptions. Remember issue 237?
For that issue, the text in 15.6 clearly states how x is treated, and
does not use the terms true and false. The correctness of the text is
questionable, but it does not appear to conflict with the definitions
of true and false.
The conditional operator also describes how x is treated. However, it
uses the terms true and false, and defines them differently from the
definition for "if" statements. This could create confusion.
> Further, if someone looks up what is written in 9.6 or 9.7.6, there is no
> reason he should think that 9.4 is relevant.
I agree that the organization is poor. It may work for someone reading
the text from front to back, but not for someone looking something up.
It could be specified better by repeating the definition every place it
is used, or by moving the definition into a separate section and stating
that it apples to all conditions in procedural statements.
Steven Sharp
sharp@cadence.com
This archive was generated by hypermail 2.1.4
: Tue Feb 15 2005 - 12:40:06 PST
and
sponsored by Boyd Technology, Inc.