[sv-cc] RE: Configuration compiler directive for DPI-OO open array arguments

This sounds reasonable to me - provided we get a definition of how open arrays are mapped to the DPI-OO intermediate layer as handles.

We should make clear that the directive applies to all subroutines _declared_ in the scope, rather than to those called or invoked within the scope.

Regards,
Jim Vellenga

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Vitaly Yankelevich
Sent: Sunday, 18 Sep 2011 9:50 AM
To: sv-cc@eda.org
Cc: Arturo.Saltz@synopsys.com
Subject: [sv-cc] Configuration compiler directive for DPI-OO open array arguments

I got an AI to suggest a syntax and definition for a special compiler directive for configuration of the open array arguments in the DPI-OO inter-language calls.

We propose to add a new directive that can be provided in a compilation unit or a package scope:

`dpi_oo_open_array [handle | STL]

This compiler directive shall be documented as a new sub-section of section 22 "Compiler directives".

When `dpi_oo_open_array is specified, it affects all the open array arguments in the corresponding scope. I think that such granularity is sufficient to support VIP's of both kinds: legacy Dpi-C-oriented and new DPI-OO-oriented VIP's. It's reasonable to expect that different VIP API's will be encapsulated in different packages or compilation units.

I can send a new version of the DPI-OO proposal, containing the proposed modifications, this week - so that we'll be able to vote at the next meeting.

Regards,
Vitaly

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.