[sv-bc] task/function actuals for mode "ref"

At the last BC meeting, 2097 was discussed and I observed that
there is language related to ref modes that uses similar
terminology but for which a "wider" interpretation was expected.
I offered to write up a clarification.  I've attached a
first cut clarification below; if there is not objection, I
can enter a Mantis item with the proposal and we can see how/if
this can get into 1800.  At very least I want to make sure that
there is "intent agreement" on this.

Gord
-- 
--------------------------------------------------------------------
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.

Section 13.5.2

CHANGE:

 

The semantics of assignments to variables passed by reference is that changes are seen outside the subroutine immediately (before the subroutine returns). Only variables, not nets, can be passed by reference.  Only variables, not nets, can be passed by reference.

 

TO:

The semantics of assignments to variables passed by reference is that changes are seen outside the subroutine immediately (before the subroutine returns). Only variables, not nets, can be passed by reference.  Only variables, not nets, can be passed by reference.

 

Only the following shall be legal to pass by reference:

·        a variable

·        a member select of a class property or  a member of an unpacked structure

·        a non-slice indexed select of an unpacked array.

Nets and selects into nets shall not be passed by reference.