Re: CoInitialize/CoUninitialize
* Igor Tandetnik:
"Alf P. Steinbach" <alfps@start.no> wrote in message
news:BfmdnWLhn6dySfXVnZ2dnUVZ_ofinZ2d@posted.comnet
CoInitialize/CoUninitialize are per thread. Calling CoUninitialize in
one thread cannot affect other threads.
You'd think so, wouldn't you? :-)
But reality is a bit different.
In particular, there's much messaging between threads, and just to
make the point, the above is an actual case, not some hypothetical
silly-example.
You seem to be hinting at some dark secret only you know about. Do you
have any evidence to back up the claim? Perhaps a working sample where a
code similar to what you show causes problems?
I totally agree, it should. Ideally. Reality is that it doesn't. Or
didn't. Perhaps Microsoft has now fixed all their libraries (I doubt
it, however).
Again, can you show an example that would demonstrate the bug you
allege?
I don't like being called a liar.
And I'm not about to waste time (which could be hours) creating /more detailed/
example code for the badmouthed one.
Bye, best,
- Alf
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?