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." ----------------------------------------------------------Received on Tue Apr 12 12:11:18 2005
This archive was generated by hypermail 2.1.8 : Tue Apr 12 2005 - 12:11:45 PDT