🚀 go-pugleaf

a > However, if I decided to replace...
a > 
a >   if (GlobalUnlock(hMem) != (HANDLE) NULL)
a >      GlobalFree(hMem);
a > 
a > simply with a call to GlobalFree, as in...
a > 
a >   GlobalFree(hMem);
a > 
a > then the memory object gets freed anyway without using the 'if'
a > condition and a call to GloabalUnlock. Although this works, I'd
a > like to understand why exactly why the article choses to call
a > GlobalUnlock before the the GlobalFree function. 
Not quite sure, but in a app of mine I got the problem, that GlobalUnlock on 
Windows 3.0 returned FALSE, but while running on Win 3.1 TRUE was returned. 
Ignoring the return value had no consequences, all worked fine.
a > Before I leave you to ponder, I'd like to also state my own
a > reasoning behind why the article's method doesn't work. If I am
a > correct, please tell me so (this will also save you some time and
a > writing).
a > 
Greetings Martin