GlobalAlloc_() verses AllocateMemory()?

[Karbon]

In Windows, is there a difference between the winAPI GlobalAlloc_() and the PB proc AllocateMemory()?

I see lots of people using GlobalAlloc_() in their examples but don't see any obvious differences..

Thanks!

[edit]

Ok, so I do see one difference.. Flags aren't supported by AllocateMemory() like : GlobalAlloc_(#GMEM_FIXED | #GMEM_ZEROINIT, #BUFFERSIZE)

... but is that the only difference?

[GPI]

The diffrent is, that you must give AllocateMemory() a nr and globalAlloc gives you a "nr" (ok, it is a adress, but it is also the "handle" for the memory)

When you programm a routine, that is in the window-callback, timer and so on, you can get problems, that a routine can called twice and so you get a already allocate error.

[Karbon]

When you programm a routine, that is in the window-callback, timer and so on, you can get problems, that a routine can called twice and so you get a already allocate error.

Problems when using GlobalAlloc_() or PB's AllocateMemory()?

Thanks for the info!

[tinman]

When you programm a routine, that is in the window-callback, timer and so on, you can get problems, that a routine can called twice and so you get a already allocate error.

Problems when using GlobalAlloc_() or PB's AllocateMemory()?

PB's AllocateMemory() because you must specify a bank number. It's a pain when you are working with (lots of) dynamic memory allocations because not only do you need to keep track of the pointer to the memory (or course, you'd need to do this with GlobalAlloc_() anyway) but you must also keep track of what memory banks you have used.

[Karbon]

Got ya. Thanks!!!

[freak]

GlobalAlloc_() is an old, outdated function, which is only still there for
backward compatibility and for some stuff like clipboard management.

You should use the Heap functions like HeapAlloc_() and so on, because
they are faster than GlobalAlloc_(). PB's AllocateMemory() uses the Heap
stuff if i'm not wrong, so it should be a bit faster than GlobalAlloc_().

Timo