GlobalAlloc() conversion from void to char*

Everytime I try to compile this it gives me this error code

" invalid conversion from `void*' to `CHAR*' "

I changed the GlobalAlloc() function to an integer to see if it was trying to return void, but it would give me a "invalid conversion from void* to int" error, so something is wrong with the DWORD FileSize, but I can't figure out what. It's suppose to be the save as... part of the program, but this is the only spot I'm hung up on. It does the same thing for open...

Code:

---

        if(hFile != INVALID_HANDLE_VALUE){
                LPSTR FileSize;
                DWORD BufferSize;
                BufferSize = GetWindowTextLength(hSave);

                if(BufferSize > 0){
                        DWORD Buff;
                        Buff = BufferSize + 1;
                        FileSize = GlobalAlloc(GHND,Buff);  //<--- says that is the error

---

Yes, if you are compiling this as C++, then you need to cast your void* returning functions to the appropriate type.

FileSize = (LPSTR)GlobalAlloc(GHND,Buff);

But why are you using GlobalAlloc() in preference to the standard C++ 'new' operator for allocating memory, which does not need any casting.

Quote:

---

Originally Posted by Salem

But why are you using GlobalAlloc() in preference to the standard C++ 'new' operator for allocating memory, which does not need any casting.

---

Mainly because I'm new to Win32/API/windows programming and do not know a lot of functions yet. I've been surfing around tutorials, books, and msdn to find everything so far. I will look in to other ways of allocating memory, thanks.

If you want to use the Win32 API memory management functions, look into the Heap functions. Microsoft discourages usage of GlobalAlloc() and LocalAlloc() these days.

ok i tried the new and delete operators, way easier, thank you.

Quote:

---

Originally Posted by Salem

But why are you using GlobalAlloc() in preference to the standard C++ 'new' operator for allocating memory, which does not need any casting.

---

GlobalAlloc() is part of the API, and hence will support faster API features ( such as block transfers) if the user upgrades their system/os. whereas the functionality of 'new' is fixed at compile time.

'new' wins on portability
GlobalAlloc() wins on functionality

for applications that only target Win32/Win64 systems, it makes sense to use GlobalAlloc();

As I already said, MSDN says to skip GlobalAlloc() and move to HeapAlloc(). From my understanding I would assume that GlobalAlloc() just calls HeapAlloc() on the default heap object assigned to the process, but for whatever reason, the warning is that GlobalAlloc() is actually slower....

Quote:

---

Note The global functions are slower than other memory management functions and do not provide as many features. Therefore, new applications should use the heap functions. However, the global functions are still used with DDE, the clipboard functions, and OLE data objects.

---

So, make whatever you will of it....