Now that you know how the 16-bit memory manager handled the global heap, it’s time to see how this got transitioned to the new 32-bit world.<\/p>\n
The This means that the old trick of caching a selector and reallocating the memory out from under it no longer worked. <\/p>\n Moveability semantics were preserved. Memory blocks still had a lock count, even though it didn’t really accomplish anything since Win32 never compacted memory. (Recall that the purpose of the lock count was to prevent memory from moving during a compaction.) <\/p>\n Moveable memory and locking could have been eliminated completely, if it weren’t for the Aside from that, moveable memory gets you nothing aside from overhead. <\/p>\nGlobalAlloc<\/code> function<\/a> continued to emulate all its previous moveability rules, but the return value of GlobalAlloc<\/code> was no longer a selector since Win32 used the processor in “flat mode”. <\/p>\nGlobalFlags<\/code> function<\/a>. This function returns several strange bits of information—now entirely irrelevant—the most troubling of which is the lock count. Consequently, the charade of locking must be maintained just in case there’s some application that actually snoops at the lock count, or a program that expected the GlobalReAlloc<\/code> function<\/a> to fail on a locked block. <\/p>\n