锘??xml version="1.0" encoding="utf-8" standalone="yes"?>久久超碰97人人做人人爱,热综合一本伊人久久精品,一级做a爰片久久毛片看看http://m.shnenglu.com/Panda/category/11684.htmlzh-cnTue, 08 Sep 2009 15:43:28 GMTTue, 08 Sep 2009 15:43:28 GMT60HeapAlloc GlobalAlloc new絳夊唴瀛樺垎閰嶇殑鍖哄埆http://m.shnenglu.com/Panda/archive/2009/09/06/95435.htmlChinaPandaChinaPandaSun, 06 Sep 2009 13:50:00 GMThttp://m.shnenglu.com/Panda/archive/2009/09/06/95435.htmlhttp://m.shnenglu.com/Panda/comments/95435.htmlhttp://m.shnenglu.com/Panda/archive/2009/09/06/95435.html#Feedback0http://m.shnenglu.com/Panda/comments/commentRss/95435.htmlhttp://m.shnenglu.com/Panda/services/trackbacks/95435.html

GlobalAlloc鏄爣鍑嗗唴瀛樼鐞嗗嚱鏁幫紝鏍囧噯鍐呭瓨綆$悊鍑芥暟閮芥槸鎿嶄綔榪涚▼鐨勯粯璁ゅ爢錛屾墍浠ヨ繖涓嚱鏁版槸浠庤繘紼嬬殑榛樿鍫嗕腑鍒嗛厤鍐呭瓨絀洪棿錛屽垎閰嶇殑絀洪棿鍙互鏄彲縐誨姩鐨勪篃鍙互鏄笉鍙Щ鍔ㄧ殑銆傚彲縐誨姩鐨勫唴瀛樻槸鎸嘩indows鍦ㄩ渶瑕佺殑鏃跺欏彲浠ュ皢榪欎釜鍐呭瓨縐誨姩鍒板彟澶栦竴涓湴鍧.

 

鍏充簬GlobalAlloc and LocalAlloc,from MSDN  
   
  The global and local functions supported for porting from 16-bit code, or maintaining source code compatibility with 16-bit Windows. The global and local 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 and the clipboard functions.  
   
  Windows memory management does not provide a separate local heap and global heap, as 16-bit Windows does. As a result, there is no difference between the memory objects allocated by the GlobalAlloc and LocalAlloc functions. In addition, the change from a 16-bit segmented memory model to a 32-bit virtual memory model has made some of the related global and local functions and their options unnecessary or meaningless. For example, there are no longer near and far pointers, because both local and global allocations return 32-bit virtual addresses.
 
  Memory objects allocated by GlobalAlloc and LocalAlloc are in private, committed pages with read/write access that cannot be accessed by other processes. Memory allocated by using GlobalAlloc with GMEM_DDESHARE is not actually shared globally as it is in 16-bit Windows. This value has no effect and is available only for compatibility. Applications requiring shared memory for other purposes must use file-mapping objects. Multiple processes can map a view of the same file-mapping object to provide named shared memory. For more information, see File Mapping.

HeapAllock鏄爢綆$悊鍑芥暟錛屽爢綆$悊鍑芥暟鍙互鎿嶄綔闈為粯璁ゅ爢錛堝綋鐒朵篃鍙互鎿嶄綔榛樿鍫嗭級錛屽垱寤轟竴涓爢鏄敤HeapCreate錛岃繖涓嚱鏁拌繑鍥炰竴涓爢鍙? 鏌勶紝鐒跺悗鍙互鐢ㄥ湪HeapAllock鍑芥暟涓紝鍗充粠榪斿洖鐨勮繖涓爢涓敵璇峰唴瀛樼┖闂達紝HeapAllock鐢寵鐨勫唴瀛樺彧鑳芥槸涓嶅彲浠ョЩ鍔ㄧ殑.

鑰宯ew鍒欐槸c++鐨勬爣鍑嗗嚱鏁幫紝鍦╓indows鐨刅C++緙栬瘧鍣ㄤ腑錛宯ew鍦ㄧ敵璇峰唴瀛樻椂鏈緇堣皟鐢ㄧ殑鏄疓labalAlloc錛屼笉榪噉ew榪樺彲浠ヨ皟鐢ㄧ被鐨勬瀯閫犲嚱鏁?

Windows鐨勫唴瀛樼鐞嗛櫎浜嗘爣鍑嗗唴瀛樼鐞嗗嚱鏁板拰鍫嗙鐞嗗嚱鏁頒箣澶栵紝榪樻湁鏇村姞搴曞眰鐨勮櫄鎷熷唴瀛樼鐞嗗嚱鏁幫紝VirtualAlloc灝辨槸涓涓櫄鎷熷唴瀛樼鐞嗗嚱鏁?

 

Personal Comprehension

GlobalAlloc鍒嗛厤鐨勫唴瀛?榪樺彲浠ヨ皟鐢℅lobalLock閿佸畾璇ュ唴瀛樺潡(璇ュ嚱鏁板彲浠ヨ澶氭璋冪敤),鍦ㄦ垜浠病鏈夎皟鐢℅lobalUnlock涔? 鍓?璇ュ唴瀛樺潡浼氫竴鐩翠繚鎸佹湁鏁?鍗充嬌璋冪敤浜咷lobalFree鍑芥暟,浣嗗鏋滆鍐呭瓨鐨勯攣璁℃暟涓嶄負0,璇ュ唴瀛樺潡涔熶笉浼氳閲婃斁鎺?渚濈劧淇濇寔鏈夋晥)!鑰屽鏋滃彧璋冪敤 涓嬈elete,鍒欎嬌鐢╪ew鎵鍒嗛厤鐨勫唴瀛樺氨浼氳閲婃斁鎺?



]]>
久久一区二区三区99| 麻豆精品久久久一区二区| 国产精品99久久久精品无码 | 久久久久久精品免费免费自慰| 欧美成人免费观看久久| 国产亚洲精久久久久久无码| 99久久精品免费| 久久综合狠狠综合久久综合88| 久久久久久久尹人综合网亚洲| 亚洲精品NV久久久久久久久久 | 久久久精品国产亚洲成人满18免费网站 | 青青草国产97免久久费观看| 久久午夜免费视频| 大伊人青草狠狠久久| 久久久久久毛片免费看| 亚洲精品tv久久久久久久久| 久久国产乱子伦精品免费午夜| 一本一本久久A久久综合精品| 超级碰久久免费公开视频| 亚洲综合伊人久久大杳蕉| 精品水蜜桃久久久久久久| 波多野结衣中文字幕久久| 少妇久久久久久被弄到高潮| 91精品国产91热久久久久福利| 亚洲伊人久久精品影院| 久久亚洲国产精品五月天婷| 国产高潮久久免费观看| 久久综合欧美成人| 99久久久国产精品免费无卡顿| 久久人与动人物a级毛片| 亚洲国产成人精品久久久国产成人一区二区三区综| 久久精品九九亚洲精品| 欧美大香线蕉线伊人久久| 亚洲va国产va天堂va久久| 99久久夜色精品国产网站| 伊人色综合久久天天人手人婷| 亚洲精品乱码久久久久久不卡| 久久久国产视频| 香蕉久久久久久狠狠色| 久久久国产亚洲精品| 久久人妻少妇嫩草AV蜜桃|