Re: [sv-ec] RE: Clarification of 19.4 modports


Subject: Re: [sv-ec] RE: Clarification of 19.4 modports
From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Mon Mar 01 2004 - 05:36:54 PST


Rob,

I think the answer is as follows:

In SV 3.1a Draft 5, in 19.9, it says,

"When an interface is connected with a modport in either the module header or port connection,
access by port reference is limited to only those objects listed in the modport,
for only those types of objects legal to be listed in modports (nets, variables, tasks, and
functions)."

Shalom

Slater Rob-R53680 wrote:

> I would argue that the current modport behavior is contrary to what one would expect.
>
> When I define a list of signals in a modport, I would expect only those signals
> to be visible in the instantiating module. If I intentionally left a signal out of a modport
> list, I think that would imply that I do not what this particular module to have any
> access to the missing signal.

--
Shalom Bresticker                           Shalom.Bresticker@motorola.com
Design & Reuse Methodology                             Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd.                    Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL                       Cell: +972 50 441478

[x]Motorola General Business Information [ ]Motorola Internal Use Only [ ]Motorola Confidential Proprietary



This archive was generated by hypermail 2b28 : Mon Mar 01 2004 - 05:45:03 PST