Microsoft KB Archive/45704: Difference between revisions
From BetaArchive Wiki
m (1 revision imported: importing part 1) |
m (Text replacement - "&" to "&") |
||
| Line 27: | Line 27: | ||
Instead, use the following: | Instead, use the following: | ||
<pre class="CODESAMP"> if(GlobalFlags(hMem) & | <pre class="CODESAMP"> if(GlobalFlags(hMem) & GMEM_DISCARDABLE) </pre> | ||
This is necessary because GlobalFlags() returns a one, i.e., 0x0100, rather than 0x0F00 if the object is discardable. It is also possible that the return value could be 0x0800 or 0x0400 or 0x0200. These cases are also taken care of with the bitwise AND. | This is necessary because GlobalFlags() returns a one, i.e., 0x0100, rather than 0x0F00 if the object is discardable. It is also possible that the return value could be 0x0800 or 0x0400 or 0x0200. These cases are also taken care of with the bitwise AND. | ||
Latest revision as of 14:14, 21 July 2020
Using GlobalFlags() to Test for GMEM_DISCARDABLE |
Q45704
The information in this article applies to:
- Microsoft Windows Software Development Kit (SDK) versions 3.0, 3.1
SUMMARY
When testing for GMEM_DISCARDABLE, do not use the following:
if(GlobalFlags(hMem) == GMEM_DISCARDABLE)
Instead, use the following:
if(GlobalFlags(hMem) & GMEM_DISCARDABLE)
This is necessary because GlobalFlags() returns a one, i.e., 0x0100, rather than 0x0F00 if the object is discardable. It is also possible that the return value could be 0x0800 or 0x0400 or 0x0200. These cases are also taken care of with the bitwise AND.
Additional query words: 3.00 3.10
Keywords : kb16bitonly
Issue type :
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK300 kbWinSDK310
Last Reviewed: November 6, 1999 |
