[quote="brett":3dfxtpws]by the way we’re using cdecl exports for functions and stdcall for callbacks, so there wont be any mangling of normal functions, and VB needs stdcall for callbacks so we’ll leave them that way.[/quote:3dfxtpws]
Will this hold true for Windows and Linux? It made the Delphi port quite messy having a conditional at the end of each function declaration to declare it as stdcall for Windows and cdecl for Linux.

I see that you are using the int type for passing boolean flags around. I have made a FMOD_BOOL similar to your FMOD_FLOAT. In Delphi this type will be equivalent to LongBool which is a predefined boolean type of four bytes. Perhaps you could use this in your official headers?

typedef int FMOD_BOOL;

Then there will be no confusion as to what that integer parameter really means.

Having taken a close look at the API during the conversion to Delphi, I must commend you on a clean and easy to understand API.

Excellent!

I’m curled up in the foetal position in anticipation. 😀

Just thought I’d add a note to say that I have tried to keep to the same symbol, struct and enum names as closely as possible this time through. No Delphi-izing the names (mixed case, no underscores, ‘T’ prefix for types, etc).

Hopefully that will make support a little easier when everything is named the same.