Re: nlffi cvt vs get

Thanks for the analysis.
>
> and the C structure is opaquely sealed with the C signature
>
> structure C :> C_INT
> (* ... *)
> structure C : C = C_Int
>
> thus the type C.double will be a new type.

You mean type and not value right.  So I think that there is going to  
be problem retrieving fields from structures which can be freed.

Don't I need to make a "true" local ML copy of the value.  The whole  
point of nlffi is not to marshall, so it makes sense that using the  
value in a structure via get, and then free'ing the structure would  
cause problems.  I assume that's why Cvt used to be there.

Brian


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV