Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Its been about 16 years now since it was created and I still don’t know why there was a reserved parameter in the CoInitialize method. Does anyone know (or is able to make an intelligent guess about) why this parameter was added and what the anticipated use was?
This is actually not for future use, but for backward compatibility. Read: Why was the ability to specify an allocator during CoInitialize removed from the system? by @Larry Osterman, who actually hangs around here occasionally…
In short: that argument used to allow you to specify a custom allocator. But since that feature has been misused, it was deprecated.