Subject: RE: [sv-cc] Updated extern/exports proposal
From: Warmke, Doug (doug_warmke@mentorg.com)
Date: Wed Mar 12 2003 - 09:49:12 PST
Joao,
Excellent work on this proposal.
My comments follow:
1) I recommend svSetUserData() should be svPutUserData().
This is consistent with vpi's equivalent, and "put"
is more indicative of the real action than "set".
2) The purvue of the user data should be per-function,
rather than per-scope. Otherwise it will be impossible
to mix completely independent external context functions
within the same module scope.
This is a trade-off and may be an opinion-call.
As you have defined it (user data shared by all extern
functions in the scope) it is convenient for implementors
of sets of related external functions. However, if there
are multiple independent external context functions
declared in the same module scope, they couldn't
co-exist. (Similar to having multiple UNIX signal
handlers all on SIGINT, but *no* handler-chaining
mechanism defined so that they can co-exist).
3) I agree that it's not good to overload svHandle.
However, if we are to change the name of this use
(which mirrors vpi handles nicely), we should also
change the term in the original sense Andrzej intended.
[Analogy time: It's like he was using the term "fruit",
and I co-opted it and for use as well. But now I need
to use the term "orange" to distinguish my usage. So I
would propose Andrzej's stuff change to "apple". ]
How about:
svHandle (Andrzej-mode) -> svArrayHandle
svHandle (Doug-mode) -> svContextHandle
4) For svGetScopeByName() and svGetScopeName(), how about we
change the latter to svGetScopeNameByHandle() or
svGetNameByScope()? (my preference is svGetNameByScope())
How are we going to get these changes edited into the LRM?
Will Andrzej or you do it? Or would you guys like me to do it?
I'm fine either way.
Please see my responses to Andrzej's mail as well.
This has been a good burst of interaction the last weeks.
Regards,
Doug
> -----Original Message-----
> From: Joao Geada [mailto:Joao.Geada@synopsys.com]
> Sent: Tuesday, March 11, 2003 7:35 PM
> To: sv-cc
> Subject: [sv-cc] Updated extern/exports proposal
>
>
>
> Attached as an HTML file.
> I believe I have accounted for all the required
> clarifications and corrections.
> There is now a lot more detail about the behavior of pure
> and context functions,
> description of the context manipulation APIs, examples of
> context, descriptions
> of the capabilities and limitations of extern and exported
> functions, listing
> of issues that are deferred with current "workarounds".
> In addition, I have also permitted multiple externs to exist
> in 1 scope IFF
> all the externs define exactly the same type signature and
> all agree exactly
> on the names of formals (as requested by Michael). Note that
> in addition, the
> workaround section suggests a few better ways to address this issue.
>
> Joao
> ==============================================================
> ================
> Joao Geada, PhD Principal Engineer
> Verif Tech Group
> Synopsys, Inc
> TEL: (508) 263-8083
> 344 Simarano Drive, Suite 300,
> FAX: (508) 263-8069
> Marlboro, MA 01752, USA
> ==============================================================
> ================
>
This archive was generated by hypermail 2b28 : Wed Mar 12 2003 - 09:50:00 PST