HeapAlloc分配的内存句柄,可以用于剪贴版,或者和OLE函数打交道么?该如何解决
HeapAlloc分配的内存句柄,可以用于剪贴版,或者和OLE函数打交道么?
既然GlobalAlloc=LocalAlloc，而且分配的都是内存句柄，那么HeapAlloc分配的也是内存句柄，都是从进程堆(已经没有了全局堆和局部堆的概念了)上面分配的，那么以前windows编程里面的剪切板和OLE函数要求用GlobalAlloc分配句柄的地方，现在都能用HeapAlloc代替么?
HeapAlloc和GlobalAlloc分配出来的东西，有没有什么实质的不同?
------解决方案--------------------
查一下msdn不就明白啦
------解决方案--------------------
你管那么多干嘛？人家叫你用GlobalAlloc你就用吧。
------解决方案--------------------
试一试就知道行不行，例如用CreateStreamOnHGlobal就必须用GlobalAlloc
The movable-memory flags GHND and GMEM_MOVABLE add unnecessary overhead and require locking to be used safely. They should be avoided unless documentation specifically states that they should be used.
New applications should use the heap functions to allocate and manage memory unless the documentation specifically states that a global function should be used. For example, the global functions are still used with Dynamic Data Exchange (DDE), the clipboard functions, and OLE data objects.
既然GlobalAlloc=LocalAlloc，而且分配的都是内存句柄，那么HeapAlloc分配的也是内存句柄，都是从进程堆(已经没有了全局堆和局部堆的概念了)上面分配的，那么以前windows编程里面的剪切板和OLE函数要求用GlobalAlloc分配句柄的地方，现在都能用HeapAlloc代替么?
HeapAlloc和GlobalAlloc分配出来的东西，有没有什么实质的不同?
------解决方案--------------------
查一下msdn不就明白啦
------解决方案--------------------
你管那么多干嘛？人家叫你用GlobalAlloc你就用吧。
------解决方案--------------------
试一试就知道行不行，例如用CreateStreamOnHGlobal就必须用GlobalAlloc
The movable-memory flags GHND and GMEM_MOVABLE add unnecessary overhead and require locking to be used safely. They should be avoided unless documentation specifically states that they should be used.
New applications should use the heap functions to allocate and manage memory unless the documentation specifically states that a global function should be used. For example, the global functions are still used with Dynamic Data Exchange (DDE), the clipboard functions, and OLE data objects.