Vitaliy,
I have been messing around shell32/tests some day ago, and stuck upon a MSDN, which states that SHGetMalloc() is obsolete. It says we must should stick with CoTaskMemFree() and CoTaskMemAlloc() instead.
Would you take a thought on this?
By a looks of it wine using same IMalloc interface for both. Native, including XP and server 2003 still export SHGetMalloc.
In other words I don't see a problem using SHGetMalloc on wine and all of native versions.
Vitaliy
Tuesday, June 28, 2005, 11:34:20 PM, you wrote:
Vitaliy,
I have been messing around shell32/tests some day ago, and stuck upon a MSDN, which states that SHGetMalloc() is obsolete. It says we must should stick with CoTaskMemFree() and CoTaskMemAlloc() instead.
Would you take a thought on this?
* On Wed, 29 Jun 2005, Vitaliy Margolen wrote:
By a looks of it wine using same IMalloc interface for both. Native, including XP and server 2003 still export SHGetMalloc.
In other words I don't see a problem using SHGetMalloc on wine and all of native versions.
Not a problem, just a message from MSDN [1]:
| SHGetMalloc Function | Not currently supported. | | Remarks | This function should no longer be used. Use the CoTaskMemFree and | CoTaskMemAlloc functions in its place.
Plus CoTaskMemFree() lets us get rid of one global variable. :-P No, this isn't a persuading act. This might be more of my question: --Why MS decided to write about stopping to support this function?
[1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla...
Wednesday, June 29, 2005, 7:47:38 AM, you wrote:
- On Wed, 29 Jun 2005, Vitaliy Margolen wrote:
By a looks of it wine using same IMalloc interface for both. Native, including XP and server 2003 still export SHGetMalloc.
In other words I don't see a problem using SHGetMalloc on wine and all of native versions.
Not a problem, just a message from MSDN [1]:
| SHGetMalloc Function | Not currently supported. | | Remarks | This function should no longer be used. Use the CoTaskMemFree and | CoTaskMemAlloc functions in its place.
Plus CoTaskMemFree() lets us get rid of one global variable. :-P No, this isn't a persuading act. This might be more of my question: --Why MS decided to write about stopping to support this function?
That's what they do - screwing people up.
[1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla...
Yeh, I read that. There is no way they can delete SHGetMalloc without braking huge number of programs. BTW on Win CE it's still what they suggest.
And the last note: this patch made it in :P
Vitaliy
-
Saulius Krasuckas -
Vitaliy Margolen