[Trac: Originally commented by jf_menard on 2007-09-07 04:33:35]

Someone should commit this patch to SVN.

I'm not sure the PA_API_CC macro format used here is sufficent to cover calling conventions on all platforms. I've seen other calling convention macros that take the return types as parameters. Also need to resolve how this interacts with doxygen.

The question is not so much with whether we need what this patch does -- it's whether this patch does it the best way for all platforms.

Should review other code bases for guidance. (python libs?)

The patch included a number of unrelated doc comment typo corrections. These have now been committed as r1594.

Recent list discussion have identified the following issues and open questions (not sure this is exhaustive yet):
- how to wrap calling conventions? (need to accomodate {{{__declspec(import)}}} and calling convention). Python uses macros like PA_API_FUNC(RETURNTYPE) that can insert code before and after the return type.
- which calling convention to use on Windows? {{{__stdcall}}} is the defacto standard but we will need to explore name mangling issues.
- what amount of packing to use? (4 byte packing is standard for say VB, but we have 8-byte doubles in some structs so perhaps we want to combine manual padding and pragmas to give both 8 byte natural alignment and compatibility with 4 byte packing schemes)

TRAC migration: propagating ticket status from TRAC

file:bFPVPssjOr4zieacwqjQWU

Ticket58.patch (26.8 KB) - added to Trac by jf_menard 4 years ago:
SVN patch for ticket #58