A few minor suggestions below.
First, the second sentence of 7.4.6 is now:
The result of reading from an unpacked array of any kind with
an invalid index shall return the value specified in Table 7-1.
This has managed to become a very awkward sentence (not due
to your changes Jonathan). Can we just have:
Reading from an unpacked array of any kind with
an invalid index shall return the value specified in Table 7-1.
At least we should get rid of "the result ... shall return..."
structure of the sentence.
I think that we now need to be more careful in 7.8.6. It
has:
If an invalid index (i.e., 4-state expression....
But the proposal now very clearly says that "invalid index"
is *either* out-of-bound or containing x/z. 7.8.6 suggests
by the parenthetical comment that "invalid" is just the
x/z case. The parenthetical comment in 7.10.1 is fine as
it covers both cases now.
Finally, in 11.5.1 and 11.5.2, shouldn't we change:
If the bit-select is out of bounds ....
to something like:
If the bit-select index is invalid (out of bounds ...)
That would keep the use of "invalid" with the parenthetical
rephrasing consistent.
Gord.
On 9/13/2011 9:47 AM, Jonathan Bromley wrote:
> hi BC, EC,
>
> I have finally found time to pick up the tweaking of Mantis 1067,
> which has been outstanding for a long while. There's a new proposal
> ("1067-proposal-v2.pdf") which I hope deals with the many issues
> raised by Shalom's analysis. I don't know if there is sufficient time
> or bandwidth to consider it for the current PAR. I think it would be
> good to get these LRM details cleared up for what is a rather
> fundamental part of the language, even though everyone seems basically
> to be agreed about the intent.
>
> There was some uncertainty about whether this was a BC or EC issue,
> hence the mail to both committees.
>
> Regards
> Jonathan Bromley
>
-- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Sep 13 19:14:13 2011
This archive was generated by hypermail 2.1.8 : Tue Sep 13 2011 - 19:14:21 PDT