Content deleted Content added
Corrected out of order acronym. Tag: Reverted |
m Disambiguating links to Object-orientation (link changed to Object-oriented programming) using DisamAssist. |
||
(24 intermediate revisions by 22 users not shown) | |||
Line 3:
{{refimprove|date=November 2017}}
'''Common Intermediate Language''' ('''CIL'''), formerly called '''Microsoft Intermediate Language''' ('''MSIL''') or '''Intermediate Language''' ('''IL'''),<ref>{{cite web |url = https://
CIL was originally known as Microsoft Intermediate Language (MSIL) during the beta releases of the .NET languages. Due to standardization of [[C Sharp (programming language)|C#]] and the CLI, the bytecode is now officially known as CIL.<ref>{{cite web
Line 12:
==General information==
During compilation of [[List of CLI languages|CLI programming languages]], the [[source code]] is translated into CIL code rather than into platform- or processor-specific [[object file|object code]]. CIL is a [[CPU]]- and platform-independent instruction set that can be executed in any environment supporting the Common Language Infrastructure, such as the [[Common Language Runtime|.NET runtime]] on [[Microsoft Windows|Windows]], or the [[cross-platform]] [[Mono (software)|Mono]] runtime. In theory, this eliminates the need to distribute different executable files for different platforms and CPU types. CIL code is verified for safety during runtime, providing better security and reliability than natively compiled executable files.<ref>{{cite book| url = https://books.google.com/books?id=VGT1_UJzjM0C&q=CIL+is+platform-independent&pg=PA15| title = Benefits of CIL| access-date = 2011-02-17| last1 = Troelsen| first1 = Andrew| date = 2009-05-02| publisher = Apress| isbn = 9781590598849}}</ref><ref>{{cite web|url=https://www.visualcplusdotnet.com/visualcplusdotnet1.html|title=Unmanaged, Managed Extensions for C++, Managed and .Net Framework|website=www.visualcplusdotnet.com|access-date=2020-07-07}}</ref>
The execution process looks like this:
Line 54:
===Object-oriented concepts===
CIL is designed to be object-oriented.
Every [[Method (programming)|method]] needs (with some exceptions) to reside in a class. So does this static method:
Line 137:
==Example==
Below is a basic [["Hello, World!" program]]
<syntaxhighlight lang="csharp">
.assembly Hello {}
Line 170:
</syntaxhighlight>
In CIL assembler syntax it looks like this:
<syntaxhighlight lang="cpp">
.method private hidebysig static void Main(string[] args) cil managed
Line 227:
==Pointer instructions - C++/CLI==
A notable difference from Java's bytecode is that CIL comes with {{code|ldind}}, {{code|stind}}, {{code|ldloca}}, and many call instructions which are enough for data/function pointers manipulation needed to compile C/C++ code into CIL.
<syntaxhighlight lang="cpp">
Line 293:
==See also==
*[[LLVM]]
*[[MLIR (software)]]
*[[List of CIL instructions]]
*[[List of CLI languages]]
Line 298 ⟶ 300:
==References==
{{Reflist}}
==Further reading==
* {{cite book|author-last=Bock|author-first=Jason|year=2002|title=CIL Programming: Under the Hood of .NET|publisher=Apress|isbn=978-1590590416}}
==External links==
*[
*[https://www.visualstudio.com/license-terms/ecma-c-common-language-infrastructure-standards/ “ECMA C# and Common Language Infrastructure Standards” on the Visual Studio website]
*[[wikibooks:Computer Programming/Hello world#CIL|Hello world program in CIL]]
Line 309 ⟶ 314:
[[Category:Assembly languages]]
[[Category:Bytecodes]]
[[Category:Common Language Infrastructure]]
|