Managed code: Difference between revisions

Content deleted Content added
m Reverting possible vandalism by 2605:6001:F383:4D00:540D:B393:DEEE:CB45 to version by مصعب. Report False Positive? Thanks, ClueBot NG. (3551744) (Bot)
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
Line 1:
{{RefImprove|date=April 2019}}
'''Managed code''' is computer program code that requires and will execute only under the ''management'' of a [[Common Language Runtime]] [[virtual machine]], typically the [[.NET Framework]], or [[Mono (software)|Mono]]. The term was coined by [[Microsoft]].
 
'''Managed code''' is computer program code that requires and will execute only under the ''management'' of a [[Common Language Runtime]] (CLR) [[virtual machine]], typicallye.g. the[[.NET Core]], [[.NET Framework]], or [[Mono (software)|Mono]]. The term was coined by [[Microsoft]].
Managed code is the compiler output of [[source code]] written in one of over twenty high-level programming languages that are available for use with the Microsoft .NET Framework, including C#, J#, Microsoft Visual Basic .NET, Microsoft JScript and .NET, while unmanaged code refers to programs written in [[C (programming language)|C]], [[C++]], and other languages that target the host CPU and operating system directly. Managed code in the Microsoft .Net Framework is defined according to the [[Common Intermediate Language]] specification.
 
Managed code is the compiler output of [[source code]] written in one of over twenty{{Which|date=April 2019}} high-level programming languages, including [[C Sharp (programming language)|C#]], [[J Sharp|J#]] and [[Visual Basic .NET]].
 
== Terminology ==
The distinction between managed and unmanaged code is prevalent and only relevant when developing applications that interact with the [[.NET Framework]] or other Common Language Runtime (CLR) implementations, like [[Mono (software)|Mono]]. Since many{{Which|date=April 2019}} 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 does not rely on the CLR is termed ''"unmanaged''".
 
A 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]]''. The creator of the C++ programming language and member of the C++ standards committee, [[Bjarne Stroustrup]], 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."<ref name="Stroustrup">{{cite web |author=Stroustrup, Bjarne |title=Bjarne Stroustrup's FAQ: What do you think of C++/CLI? |date=2009-06-29 |url=http://www.stroustrup.com/bs_faq.html#CppCLI |accessdate=2009-06-29 }}</ref>
 
== Uses ==
 
The [[Microsoft's Visual C++]] development environmentcompiler can produce both managed code, running under the .NET CLR, or compiledunmanaged binaries, running directly on the Windows platform with the help of its C++ Runtime Library.<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). Drawbacks include slower startup speed (the managed code must be [[Just-in-time compilation|JIT compiled]] by the VM) and generally increased use of system resources on any machine that is executing the code.
 
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)|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]]. The WLanguage of WINDEV is also a pCode running on a virtual machine.
 
==References==