Managed code: Difference between revisions

Content deleted Content added
Updated article to match today's facts, including .NET Core. For example, the JIT compilation drawback no longer applies to UWP apps. I also deleted some tall claims, like JScript being a managed language
Tags: Mobile edit Mobile web edit
Line 14:
The [[Microsoft Visual C++]] compiler can produce both managed code, running under CLR, or unmanaged binaries, running directly on Windows.<ref name="Gregory">{{cite web |author=Gregory, Kate |title=Managed, Unmanaged, Native: What Kind of Code Is This? |date=2003-04-28 |url=http://www.developer.com/net/cplus/article.php/2197621 |accessdate=2009-04-22 }}</ref>
 
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 machine|p-code]], and the operating system [[Inferno (operating system(OS)|Inferno]] from [[Bell Labs]] using the [[Dis virtual machine]]. [[Java (programming language)|Java]] popularized this approach with its [[Java bytecode|bytecode]] executed by the [[Java virtual machine]].
 
==References==