On Aug 24, 2012, at 1:11 PM, David Jeske dav...@gmail.com wrote:
(1) Why would a call to an instance method not hold this alive for the
entire duration of the call?
`this` isn't special, it's just an implicit variable passed into the method. If
the variable isn't used within the method call,
On Fri, Aug 24, 2012 at 10:50 AM, Jonathan Pryor jonpr...@vt.edu wrote:
It seems this could happen in more cases than just PInvoke. This seems
to allow a finalizer to run before an object is done being used anytime
the object instance is not stored. (i.e. inside a statement of the form
new
-list@lists.ximian.com
Subject: Re: [Mono-dev] Why does .NET object lifetime not extend into an
instance method call?
On Fri, Aug 24, 2012 at 10:50 AM, Jonathan Pryor
jonpr...@vt.edumailto:jonpr...@vt.edu wrote:
It seems this could happen in more cases than just PInvoke. This seems to
allow
] Why does .NET object lifetime not extend into
an instance method call?
** **
On Fri, Aug 24, 2012 at 10:50 AM, Jonathan Pryor jonpr...@vt.edu wrote:*
***
It seems this could happen in more cases than just PInvoke. This seems
to allow a finalizer to run before an object is done being
On Fri, Aug 24, 2012 at 8:31 PM, Jonathan Pryor jonpr...@vt.edu wrote:
I'm sorry for my naivety. Why does allowing unused function arguments to
be collected before a function returns have such important effects on
memory usage?
Java. :-)
The context is the JVM, and large methods. Many JVM
On Aug 24, 2012, at 4:26 PM, David Jeske dav...@gmail.com wrote:
Thanks very mych for the detailed reply. It seems to me there is a race that
has nothing to do with native code.
Native code just makes it easier to reason about, but as you mention it is
quite applicable to managed code. My
