🚀 go-pugleaf

"Borland Lover" <kdhf@kbdf.com> wrote in message
news:444e4463$1@newsgroups.borland.com...

> GetAdaptersInfo - it does not specify a calling convention
> in the MSDN.

As I told you earlier, *all* Win32 API functions use WINAPI (aka __stdcall),
except for wsprintf() which uses __cdecl instead.  If you look in
iphlpapi.h, where GetAdaptersInfo() is actually declared, you can see that:

    DWORD
    WINAPI // <-- here
    GetAdaptersInfo(
        PIP_ADAPTER_INFO pAdapterInfo, PULONG pOutBufLen
    );

> UuidCreateSequential - it specifies RPC_ENTRY. What do I use in BCB?

You use RPC_ENTRY, which transparently maps to __stdcall.  Always use what
is actually in the declaration.

> I am loading and calling both right now without specifying the calling
> convention - and they seem to be working fine.  Is this a fluke?

Yes.  You must always specify a calling convention, or else the compiler is
free to choose its own.  As you have already seen earlier, the compiler can
chose the wrong convention and mess up the runtime behavior as a result.


Gambit