Managed code: Difference between revisions

Revision as of 05:43, 13 August 2023

Revision as of 15:18, 17 November 2023

Line 8:

The distinction between managed and unmanaged code is prevalent and only relevant when developing applications that interact with CLR implementations. 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 |access-date=2009-06-29 }}</ref>

==Uses==