Microsoft Managed Code
is out, the word
seem to be repeated over and again.
In a .Net context, "managed code" means code that requires
to provide services such as "garbage collection". There is a certain misconception that Managed code is also "thread-safe" code, the latter is a default but has heavy performance penalties.
for a surprise backdoor out of the
(WinFX) - Managed API for
Applications developed for
will only be able to invoke
, although Avalon,
will all have internal routinees that use unmanaged code. From
will be the "tipping point" for widespread adoption of
Question: Any characteristic of Managed code beside the implications of requiring the use of
Due to automated garbage collection, freeing up resources for unwanted objects may be deferred. It is said there are special considerations required as a result of this "feature".
What are these considerations?
You have to consider situations where a resource held by an object is not automatically freed immediately after the object becomes unwanted (keywords here are "automatically" and "immediately").
I wondered what
is other than a
happens to x86-code. But then realized, that this seems to be a more or less new combination (even if it may be a step back). ??
Gunnar I do not understand your remark. I just make a mental translation of "Managed Code = code that works under an environment with garbage collection and sandboxing added to enhance
." -- dl
View edit of
November 13, 2014
with title or text search