Re: Minutes from John

Hi John,

 > And, in light of the newly reworded
> LRM text relaxing illegality of the utility functions in non-context
> imports I would go on to say that even svGetScope() is generally
> harmless and would not, in and of itself lead to side effects

But could it return an invalid scope?  Or is there always a valid
scope on the SV side whenever the C side is running (assuming we're
after elaboration and before the simulation has ended)?

Is it fair to say that the way to get to the C side is always via
an imported function?  I suppose in pure SV you could get there via
PLI or VPI, but we are not supporting those in SCE-MI 2.

> svSetScope() is probably the only one we really have to be
> careful with.

Yes, that one is the only one that actually changes the current
scope.

> So, now as you see from today's e-mail to Shabtay this is no
> longer the case. Now these functions have "undefined" rather
> than "illegal" effects so hopefully we can provide some more specific
> definition here.

Unfortunately, the turned something that could have been interpreted
as legal and supported into something that is undefined . . .  I
am referring to the svGetUserData() and svPutUserData() methods.

> It is probably the case that we in the ITC should take a stab at making
> a strawman proposal here, then submitting to some of the gurus on
> other committees to review.

Yes, and it shouldn't be that hard to come up with.

Per