[sv-cc] RE: [sv-champions] Email vote - Ending December 13th

Hi,

There is one item I want to clarify.

> Minor editorial: in the changes to 37.15 on page 3, the paragraphs
> beginning "A ref obj may be obtained ..." should be labeled as detail
> "2)".
>
> CB> This edit shows a *replacement* for detail #1, which should remain
> as such. I.e., there is no new detail coming before it, so this should
> remain #1.

[SB] The text of the proposal says,

"REPLACE

1) A ref obj represents a declared object or sub-element of that object that is a reference to an actual
instantiated object. A ref obj exists for ports with ref direction, for an interface port, a modport port, or for
formal task function ref arguments. The specific cases for a ref obj are:
- A variable, named event, named event array that is the lowconn of a ref port
- Any subelement expression of the above
- A local declaration of an interface or modport passed through a port or any net, variable, named event,
named event array of those
- A virtual interface declaration in a class definition
- A ref formal argument of a task or function, or sub-element expression of it

A ref obj may be obtained when walking port connections (lowConn, highConn), when traversing an
expression that is a use of such ref obj, when accessing the virtual interface of a class, or when accessing
the io decl of an instance or task or function.

WITH

1) A ref obj represents a declared object or sub-element of that object that is a reference to an actual
instantiated object. A ref obj exists for ports with ref direction, for an interface port, a modport port, or for
formal task function ref arguments. The specific cases for a ref obj are:
- A variable, named event, named event array that is the lowconn of a ref port
- Any subelement expression of the above
- A local declaration of an interface or modport passed through a port or any net, variable, named event,
named event array of those
- A virtual interface declaration in a class definition
- A ref formal argument of a task or function, or sub-element expression of it

A ref obj may be obtained when walking port connections (lowConn, highConn), when traversing an
expression that is a use of such ref obj, when accessing the virtual interface of a class, or when accessing
the io decl of an instance or task or function."

(The crossouts in the WITH portion don't show up in this quotation, but they are not relevant to the point.)

The 2009 LRM says,

"1) A ref obj represents a declared object or sub-element of that object that is a reference to an actual instantiated
object. A ref obj exists for ports with ref direction, for an interface port, a modport port, or for formal task function
ref arguments. The specific cases for a ref obj are:
- A variable, named event, named event array that is the lowconn of a ref port
- Any subelement expression of the above
- A local declaration of an interface or modport passed through a port or any net, variable, named event, named
event array of those
- A virtual interface declaration in a class definition
- A ref formal argument of a task or function, or sub-element expression of it

2) A ref obj may be obtained when walking port connections (lowConn, highConn), when traversing an expression
that is a use of such ref obj, when accessing the virtual interface of a class, or when accessing the io decl of an
instance or task or function."

As you can see, the last paragraph is Detail 2, whereas in the proposal, it appears as a continuation of Detail 1.

I hope my point is clear now.

Thanks,
Shalom
---------------------------------------------------------------------
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.