Re: [sv-cc] 'Does anyone remember what vpiInterfaceTask means?

I vaguely remember this being related to the handling of extern tasks
and functions in an interface (ie tasks and functions that have multiple
implementations depending on the context of where the interface was
created)

João

On Tue, 2005-04-12 at 12:19 -0700, Tapati Basu wrote:
> Hi Jim,
> 
> This was originally added by me. I am trying to recollect what it was. 
> 
> 
> - Thanks,
> Tapati 
> >X-Authentication-Warning: server.eda.org: majordom set sender to 
> owner-sv-cc@eda.org using -f
> >X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
> >Content-class: urn:content-classes:message
> >MIME-Version: 1.0
> >Subject: [sv-cc] 'Does anyone remember what vpiInterfaceTask means?
> >Date: Tue, 12 Apr 2005 15:11:14 -0400
> >Thread-Topic: 'Does anyone remember what vpiInterfaceTask means?
> >Thread-Index: AcU/k2WScD68qBnpT/e4CiFzruQTPQ==
> >From: "Jim Vellenga" <vellenga@cadence.com>
> >To: <sv-cc@eda.org>
> >X-Received: By mailgate2.Cadence.COM as MAA01492 at Tue Apr 12 12:09:01 2005
> >X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on 
> server.eda.org
> >X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on 
> server.eda.org
> >X-Virus-Status: Clean
> >X-Virus-Status: Clean
> >Content-Transfer-Encoding: 8bit
> >X-MIME-Autoconverted: from quoted-printable to 8bit by server.eda.org id 
> j3CJBHSA002112
> >X-pstn-levels: (S:99.90000/99.90000 R:95.9108 P:95.9108 M:97.0232 C:98.7678 )
> >
> >I'm looking at issue 534.  vpiInterfaceTask and vpiInterfaceFunction 
> >might have some meaning other than the occurrence of the task or 
> >function declaration within the scope of an interface or modport.  If 
> >that's all it is, one can simply find the vpiInstance of the task func, 
> >then get the vpiType of the instance, and the properties are not 
> >needed.
> >
> >But as I read the Interfaces chapter -- er, sorry, clause -- I find 
> >that one can declare a task or function prototype in the interface and 
> >then define the actual task(s) or function(s) in one or more modules 
> >(see 20.6).  VPI's "interface tf decl" must represent the prototype 
> >(See 32.5).
> >
> >Could vpiInterfaceTask and vpiInterfaceFunction possibly mean that, 
> >although the real task or function is declared in a module, it 
> >instantiates a prototype declared in an associated interface?
> >
> >Does anyone remember what the intent was?
> >
> >Regards, 
> >Jim
> >
> >--------------------------------------------------------- 
> >James H. Vellenga                            978-262-6381 
> >Engineering Director                   (FAX) 978-262-6636 
> >Cadence Design Systems, Inc.         vellenga@cadence.com 
> >270 Billerica Rd 
> >Chelmsford, MA 01824-4179 
> >"We all work with partial information." 
> >---------------------------------------------------------- 
> >  
> 
> Tapati Basu
> 
>