I was not aware of the __fastcall 'bias' in Windows 64bit.
After installing Win64 and playing around with VS2005 it is clear that the MS topics on this are misleading when they use the term "fastcall" wrt to 64-bit applications.
I don't yet understand what the win64 compiler does with __stdcall vs __fastcall. I would have thought it reasonable to have __stdcall be the same as __fastcall in win64...
VS2005 C compiler completely (and silently) ignores both __stdcall and __fastcall. There is one calling convention and it is neither of those.
The jlib.h header file to use the j.dll has __stdcall hardwired in. So the j.dll in win64 requires __stdcall calls.
See above. As __stdcall declspec is literally ignored when compiling for 64-bit then the calling conventions should be the standard 64-bit ABI.
We don't currently distribute the jlib.h header file, but this will be added as a standard part of the next beta and at some point a simple lab showing its use from J will also be included.
Will jlib.h still be included in 6.01? When will the Win64 version be brought up to the latest? I am prepared to validate this when it is released. Thanks, Joseph Battelle ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
