[sv-ec] RE: mantis 2900

From: Rich, Dave <Dave_Rich@mentor.com>
Date: Mon Jul 18 2011 - 09:36:40 PDT

New proposal uploaded that clarifies "first time executing"

Dave Rich
Verification Technologist
Mentor Graphics Corporation
New Office Number:   510-354-7439
 

-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Bresticker, Shalom
Sent: Saturday, July 02, 2011 11:44 PM
To: sv-ec@eda.org
Subject: [sv-ec] RE: mantis 2900

For the first issue, how about Steven's "the first time it is reached during execution"?

Shalom

> (3) Mantis 2900 ___Yes _X_No
> http://www.eda.org/svdb/view.php?id=2900
> Title: Associative array should consider the context of an lvalue to
> create an entry]
> [proposal: 2900_assoc_lvalue2.pdf]
>
> I am fine with the intent of this proposal, but I think the wording is
> unclear.
>
> In particular, in the phrase "the first time it appears as the
> target", the term "appear" does not seem like a good choice. The idea
> is that this occurs the first time the context where it appears is
> executed. But "appears" doesn't indicate execution. In a sense, the
> entry "appears as the target of an assignment" as soon as the user writes the code.
>
> The term "appears" is reasonable when talking about syntax being seen.
> If the user or a parser is reading the source code sequentially from
> the start, the entry "first appears" at the point where it is first
> seen in such a scan. But execution isn't a sequential scan and it
> executes code rather than "seeing" it.
>
> I understand that part of this is deliberate. The point is that the
> element is allocated when the construct is reached during execution,
> even if the part where it is used as an lvalue isn't executed until
> slightly later. So describing it in terms of execution isn't right
> either. It is based on "appearing", but appearing in something that has started executing.
>
> My apologies for not noting this earlier, but it became more obvious
> to me when I actually read the text of the proposal.
>
> Also, "context of an assignment" doesn't seem to include use as a ref
> argument. The description as an lvalue in the Mantis item was more
> correct, though the term may not be defined in the LRM.

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Jul 18 09:37:44 2011

This archive was generated by hypermail 2.1.8 : Mon Jul 18 2011 - 09:37:49 PDT