Hi Chris,
> I would like to discuss the following items (please refer to earlier
> posts for more detail):
>
> * Hierarchical library/package namespace
> * Clarification on additional language interfaces, specifically:
> * In what way is VHPI inadequate for this purpose?
> * Shouldn't we rather improve VHPI than create new interfaces?
>
I agree that when we talk about language interfaces that VHPI
should be considered first. However, I think what VHPI is for
is to specifically get at the simulator internals so as to bolt
on another tool.
What we need defined (by VHPI or other mechanism) is the ability
to call a C, SystemVerilog, ?? program directly from VHDL and
have it execute either sequentially or concurrently - for SystemVerilog
to run sequentially it would have to be something that normally ran
sequentially. That means we would also need to define types and/or
conversions that can be used at the interfaces of these languages.
If we want to play nicely with SystemVerilog, we may need more than
basic types to cross the interface.
Best,
Jim
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Feb 17 07:17:44 2011
This archive was generated by hypermail 2.1.8 : Thu Feb 17 2011 - 07:18:07 PST