Hi Arnab,
In your summary of DPI-OO issues you wrote:
"Need to understand the motivation for how enums are represented in DPI-C. Mapping them directly to C++ enums is convenient as the symbolic names can be used in the foreign language instead of just values but 4 state enums are not supported. A compromise would be to map enum of base type int to C++ enums and represent all other types of enums
as values of the base type. IMO this should be extended in DPI-C and not DPI-OO if possible."
I didn't take part in the DPI-C discussions - hence I cannot provide any comments concerning the motivation there. Your comment concerning the 4-state base types is very valid. IMO we need to update the proposal, based on your comment, so that it will specify that the enumerated types which base type is 2-state shall be mapped to enumerations in the C++ intermediate layer. The enumerated types which base type is 4-state shall be mapped in the same way as in DPI-C.
We think that changing DPI-C is beyond our scope, however we would like to comment that DPI-C doesn't export user-defined types at all.
Regards,
Vitaly
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Aug 24 09:39:27 2011
This archive was generated by hypermail 2.1.8 : Wed Aug 24 2011 - 09:39:37 PDT