How does the CAD program pass data to a DLL, via a file, via a  
database, via a pipe, via some complex multi-megabyte data structure  
specific to
the Cad vendor for which you hopefully have documentation for.  Once  
you have those magic bits, where do they live, do you make a copy, do
you work with FFI or Alien and poke the bits directly that live in the  
CAD memory space?

Do you copy in to a Smalltalk ByteArray instance and mess with, then  
what do you return to the caller? a number, more data structures, true/ 
false.

If you have an example CAD to foreign  DLL calling sequence we can  
suggest some solutions.


On 15-Feb-09, at 3:18 PM, askoh wrote:

>
> Your words
> "Well since you are building a custom VM based dll you can use the
> primitive interface to get at memory within the dll"
> puzzles me. If I use Alien FFI, do I still need to change the VM?  
> Aren't all
> the changes only in plugin.dll?
>
> Thanks,
> Aik-Siong Koh
>
> -- 
> View this message in context: http://www.nabble.com/Will-Newspeak-be-callable-by-external-programs--tp21896396p22029084.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>

--
= 
= 
= 
========================================================================
John M. McIntosh <johnmci at smalltalkconsulting.com>
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
= 
= 
= 
========================================================================