Manual - note on calling conventions on Win64
Clarification based on discussion in mailing list https://discourse.julialang.org/t/callback-to-winapi/1381
This seems sort of misleading to me, since Win64 has at least 2 calling conventions officially defined. Also, for compatibility with Win32, it is also convenient to specify the calling convention, even though at the ABI level it doesn't change anything.
Based on [MSDN](https://msdn.microsoft.com/en-us/library/ms235286.aspx?f=255&MSPPError=-2147217396), there is only one calling convention. I was confused when writing a WINAPI ccall with a callback function and i couldn't find `cfunction` where i could specify calling convention. @ihnorton clarified the situation for me that on Win64 I don't have to worry about as Win64 only uses one calling convention.
On the other hand, the ability to call into WINAPI is pretty important (for win32 users without the full power of bash, etc.) and may deserve some notice in manual.
I can delete it from calling convention and move a remark to the callback section, that only C-style callback is available on Win32, but on Win64 you are save to proceed.
I would suggest:
- add `(no-op on 64-bit Windows)` after sentence `Other supported conventions are: stdcall, cdecl, fastcall, and thiscall.`
- add note to `cfunction` description (and help) that `cfunction` only supports platform-default CC.
Agree. I'll update the PR.
I don't think it is necessary to do changes in the help string, only changed the manual.
White space removed. Is there an easy way to check for the trailing whitespaces?