May 23, 2014
12:14 p.m.
On 23.05.2014 02:36, Torsten Bergmann wrote:
With that info I compared the C/C++ calls to the Pharo/NativeBoost calls more deeply and found out that in C/C++ the following call for an object setting works (by returning 1):
while in Pharo the same call fails (by returning 0):
I tried to use another DLL which required me to change "stackAlignment" on Windows to answer 16 instead of 1; running on Win7 64 Bit. Could your problem be caused by something like that? (Just a shot in the dark). Best regards, Markus