On 8 November 2012 23:25, Jimmie Houchin <[email protected]> wrote: > > On a second look at the API's documentation, the DLL is C++ not C. I don't > know, but that might have been evident by the requirement of implementing > interfaces. > well, with C++ it is a bit worse than C: because C++ compilers use name mangling for the function names. Means that, if you will look for exported function 'abc()', you will probably find it under different name, like abc@nby_xrt
apart from that, once you figure the exact correct name, you can go and call that function. Things is a bit different if the exported function is a member of class. So, what i can say.. you can try and see if it rolls (or rocks).. and if it not, then the best option would be to implement own wrapper library (but this time in C). And then use that library from pharo. > I thought I would provide that information, just in case in has a big > bearing NB/Pharo's ability and on my learning curve. > > Jimmie > -- Best regards, Igor Stasenko.
