Re: Unified Event Model and support for multithreaded usage
No, it's not this, and BTW, what kind of events did you expect in
ATL anyway? ATL has nothing to do with .NET - it's all native.
The problem I'm talking about was with dispinterfaces and
mishandining the EXCEPINFO argument to IDispatch::Invoke
which ends up being leaked. E..g we are talking about __raise.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Boris" <boris@gtemail.net> wrote in message
news:op.t1iowchb45fww6@burk.mshome.net...
On Fri, 09 Nov 2007 02:18:35 +0200, Alexander Nickolov
<agnickolov@mvps.org> wrote:
My guess would be that the generated code is thread safe - e.g.
it uses critical sections.
Note that attributed ATL is deprecated in the next release of
VC - VC 9.0 part of VS 2008 due later this month. It contains
Is this for sure? I ask as the only thing I read so far about ATL in
VS2008 was that "ATL Server is no longer under active development by the
Visual C++ team and will not be included in VS2008 or any future version
of Visual Studio"
(http://blogs.msdn.com/vcblog/archive/2007/07/27/support-policy-for-atl-server-library.aspx).
bugs in the generated code (specifically events cause memory
leaks IIRC) in the previous releases of VC.
I think that's only true for native events. At least I only found this bug
report at
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=100355
which mentions native events only?
Boris