For algorithms executing in a "managed code" environment (such as the .NET Framework platform), there are many issues that impinge on performance. These are links to three of them in the Microsoft .Net environment.
Read more about this topic: Algorithmic Efficiency
Other articles related to "managed code, code":
... A managed code API ships as part of the.NET Framework 3.0 ... functionality to SAPI 5 but is more suitable to be used by managed code applications ... The existing SAPI 5 API can also be used from managed code to a limited extent by creating COM Interop code (helper code designed to assist in accessing COM interfaces and classes) ...
Managed code is a term coined by Microsoft to identify computer program source code that requires and will only execute under the management of a Common Language Runtime virtual machine (resulting in bytecode).
This disambiguation is prevalent and only relevant when developing applications that interact with the .NET Framework or other Common Language Runtime (CLR) implementations, like Mono. Since many older programming languages have been ported to the CLR, the differentiation is needed to identify managed code, especially in a mixed setup. In this context, code that doesn't rely on the CLR is termed unmanaged.
Microsoft's Visual C++ development environment can produce both managed code, running under the .NET CLR, or compiled binaries, running directly on the Windows platform with the help of its C++ Runtime Library.
Benefits of using managed code include programmer convenience (by increasing the level of abstraction, creating smaller models) and enhanced security guarantees, depending on the platform (including the VM implementation). There are many historical examples of code running on virtual machines, such as the language UCSD Pascal using p-code, and the operating system Inferno from Bell Labs using the Dis virtual machine. Java popularized this approach with its bytecode executed by the Java virtual machine.
Another source of confusion was created when Microsoft started connecting the .NET Framework with C++, and the choice of how to name the Managed Extensions for C++. It was first named Managed C++ and then renamed to C++/CLI. Bjarne Stroustrup, creator of the C++ programming language and member of the C++ standards committee even commented on this issue, "On the difficult and controversial question of what the CLI binding/extensions to C++ is to be called, I prefer C++/CLI as a shorthand for "The CLI extensions to ISO C++". Keeping C++ as part of the name reminds people what is the base language and will help keep C++ a proper subset of C++ with the C++/CLI extensions."
... The SQLCLR allows managed code to be hosted by, and run in, the Microsoft SQL Server environment ... allow users for example to create the following types of managed code objects in SQL Server in.NET languages such as C# or VB.NET ... deployment, and registration of CLI assemblies, which are physically stored in managed code dynamic load libraries (DLLs) ...
... Application domains are a purely managed code concept ... Any included native/unmanaged code (e.g ...
... Microsoft UI Automation (UIA) is a managed code API replacing Microsoft Active Accessibility to drive user interfaces..NET Framework 3.0 also includes a managed code speech API which has similar functionality to SAPI 5 but is suitable to be used by managed code applications ...
Famous quotes containing the words code and/or managed:
“...I had grown up in a world that was dominated by immature age. Not by vigorous immaturity, but by immaturity that was old and tired and prudent, that loved ritual and rubric, and was utterly wanting in curiosity about the new and the strange. Its era has passed away, and the world it made has crumbled around us. Its finest creation, a code of manners, has been ridiculed and discarded.”
—Ellen Glasgow (18731945)
“The corporate grip on opinion in the United States is one of the wonders of the Western World. No First World country has ever managed to eliminate so entirely from its media all objectivitymuch less dissent.”
—Gore Vidal (b. 1925)