vc++ lib of api declarations ??

yo, i want to create a vc++ lib of api declarations for my vb projects,

so if i knew how to convert vb api declarations into c++ it would be helpfull

Public Declare Sub ReleaseCapture Lib "user32" ()

Public Declare Function SetForegroundWindow Lib "user32" (ByVal hwnd As Long) As Long
these in c++????

Code:

---

#include <windows.h>

---

After you insert the code above, the API functions will be available to use, like:

Code:

---

i = GetForeGroundWindow();

---

Just a little bonus - making your own APIs:

Code:

---

extern "C" __declspec(dllexport) int _stdcall Iamanfunction(int a, LPCTSTR str);

---

Code:

---

extern "C"

---

What does that do?

It forces the internal naming convention to follow C rules (like the API - the DLL mechanism in Windows only understands that).

Otherwise, you'd end up with a C++ mangled name (which looks something like @KX_MyFunctionName@12@3fFFxxKJ).

Quote:

---

Originally posted by Microbasic
Just a little bonus - making your own APIs:

Code:

---

extern "C" __declspec(dllexport) int _stdcall Iamanfunction(int a, LPCTSTR str);

---

---

I just noticed. Don't use LPCTSTR - that's only for USING them.

When you define them, if you really have to have ANSI/Unicode compatibility you need to define two functions. If you're using them in a DLL from something like VB then you'd need to have A and W versions, like Windows does.

The C++ method, of course, is to use templates :)

Code:

---

        extern "C" int __stdcall MessageBoxA(HWND hWnd, const char *lpText, const char *lpCaption, UINT uType);
        extern "C" int __stdcall MessageBoxW(HWND hWnd, const wchar_t *lpText, const wchar_t *lpCaption, UINT uType);
        template<class chrtyp> inline int __stdcall MessageBox(HWND hWnd, const chrtyp *lpText, const chrtyp *lpCaption, UINT uType);
        inline int __stdcall MessageBox<char>(HWND hWnd, const char *lpText, const char *lpCaption, UINT uType)
                { return MessageBoxA(hWnd, lpText, lpCaption, uType); }
        inline int __stdcall MessageBox<wchar_t>(HWND hWnd, const wchar_t *lpText, const wchar_t *lpCaption, UINT uType)
                { return MessageBoxW(hWnd, lpText, lpCaption, uType); }

---

:D Bonzer!

Oh hail the great master of C++.

OK, sorry, I usually do not worry about compatibility (most of the software that I make are programs, not DLLs) and therefore, I forgot about compatability.

Code:

---

__int64 Parksie_in_C++;
long MicroBasic_in_C++;

---

parksie: why templates? I'd use overloaded functions because:

PHP Code:

---

template<class chrtyp> inline int __stdcall MessageBox(HWND hWnd, const chrtyp *lpText, const chrtyp *lpCaption, UINT uType);
    inline int __stdcall MessageBox<char>(HWND hWnd, const char *lpText, const char *lpCaption, UINT uType)
        { return MessageBoxA(hWnd, lpText, lpCaption, uType); }
    inline int __stdcall MessageBox<wchar_t>(HWND hWnd, const wchar_t *lpText, const wchar_t *lpCaption, UINT uType)
        { return MessageBoxW(hWnd, lpText, lpCaption, uType); } 


---

What if I then write:

PHP Code:

---

float ar[5] = {1.2, 45.231, 46.6, 2.3e3, 0};
MessageBox(NULL, ar, ar, 0); 


---

Not that I would do such a thing, but it is somewhat disquieting to me...

Oh yeah, and overloads are usually easier to read and ave no disadvantage that I see.

If you do that it just won't compile. Note that I only provided function code for those two specialisations - nothing else.

Accepted.
Nevertheless, why templates? Why not overloaded functions?

This is an easier way to use it, and also lets you force the resolution where necessary by using MessageBox<char>(...).

Basically, using templates means that it fits in with anything else that's parameterised on character type.

ill just use a vb activexdll