Programming language implementation - Revision history

37.154.166.127: /* Multiple implementations */

2025-05-16T12:53:11Z

Multiple implementations

← Previous revision		Revision as of 12:53, 16 May 2025
Line 29:		Line 29:
	* [[Jython]], an implementation targeting the [[Java virtual machine]]		* [[Jython]], an implementation targeting the [[Java virtual machine]]
	* [[PyPy]], an implementation designed for speed (written in RPython)		* [[PyPy]], an implementation designed for speed (written in RPython)


	==References==		==References==
	{{Reflist}}		{{Reflist}}

Annh07: Reverted 2 edits by CLACM (talk): Spam

2025-02-18T08:42:36Z

Reverted 2 edits by CLACM (talk): Spam

← Previous revision		Revision as of 08:42, 18 February 2025
Line 24:		Line 24:

	==Multiple implementations==		==Multiple implementations==
	Programming languages<ref>{{cite web \|title=What are Programming Languages \|url=https://codelabsacademy.com/en/blog/what-is-a-programming-language?source=wikipedia \|website=Code Labs Academy \|access-date=2025-02-14}}</ref> can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>		Programming languages can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>
	* [[CPython]], the [[reference implementation]] of Python		* [[CPython]], the [[reference implementation]] of Python
	* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])		* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])
	* [[Jython]], an implementation targeting the [[Java virtual machine]]		* [[Jython]], an implementation targeting the [[Java virtual machine]]
	* [[PyPy]], an implementation designed for speed (written in RPython)		* [[PyPy]], an implementation designed for speed (written in RPython)


	==References==		==References==
	{{Reflist}}		{{Reflist}}

CLACM: /* Multiple implementations */

2025-02-18T08:38:38Z

Multiple implementations

← Previous revision		Revision as of 08:38, 18 February 2025
Line 24:		Line 24:

	==Multiple implementations==		==Multiple implementations==
	Programming languages<ref>{{cite web \|title=What are Programming Languages \|url=https://codelabsacademy.com/en/blog/what-is-a-programming-language \|website=Code Labs Academy \|access-date=2025-02-14}}</ref> can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>		Programming languages<ref>{{cite web \|title=What are Programming Languages \|url=https://codelabsacademy.com/en/blog/what-is-a-programming-language?source=wikipedia \|website=Code Labs Academy \|access-date=2025-02-14}}</ref> can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>
	* [[CPython]], the [[reference implementation]] of Python		* [[CPython]], the [[reference implementation]] of Python
	* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])		* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])

CLACM: /* Multiple implementations */ - Explained Programming Languages

2025-02-17T09:20:29Z

Multiple implementations: - Explained Programming Languages

← Previous revision		Revision as of 09:20, 17 February 2025
Line 24:		Line 24:

	==Multiple implementations==		==Multiple implementations==
	Programming languages can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>		Programming languages<ref>{{cite web \|title=What are Programming Languages \|url=https://codelabsacademy.com/en/blog/what-is-a-programming-language \|website=Code Labs Academy \|access-date=2025-02-14}}</ref> can have multiple implementations. Different implementations can be written in different languages and can use different methods to compile or interpret code. For example, implementations of [[Python (programming language)\|Python]] include:{{thinsp}}<ref name="AltPython">{{cite web \|title=Alternative Python Implementations \|url=https://www.python.org/download/alternatives/ \|website=Python.org \|access-date=23 March 2020}}</ref>
	* [[CPython]], the [[reference implementation]] of Python		* [[CPython]], the [[reference implementation]] of Python
	* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])		* [[IronPython]], an implementation targeting the [[.NET Framework]] (written in [[C Sharp (programming language)\|C#]])
	* [[Jython]], an implementation targeting the [[Java virtual machine]]		* [[Jython]], an implementation targeting the [[Java virtual machine]]
	* [[PyPy]], an implementation designed for speed (written in RPython)		* [[PyPy]], an implementation designed for speed (written in RPython)


	==References==		==References==
	{{Reflist}}		{{Reflist}}

KMaster888: subjective ce 2/2

2024-12-16T17:58:37Z

subjective ce 2/2

← Previous revision		Revision as of 17:58, 16 December 2024
Line 17:		Line 17:
	==Compiler==		==Compiler==
	{{Main\|Compiler}}		{{Main\|Compiler}}
	A [[compiler]] translates programs written in one language into another language. Most compilers are organized into three stages: a [[Compiler#Front end\|front end]], an [[Compiler#Middle end\|optimizer]], and a [[Compiler#Back end\|back end]]. The front end is responsible for understanding the program. It makes sure ~~the~~ program is valid and transforms it into an [[intermediate representation]], a data structure used by the compiler to represent the program. The optimizer improves the intermediate representation to increase the speed or reduce the size of the [[executable]] which is ultimately produced by the compiler. The back end converts the optimized intermediate representation into the output language of the compiler.<ref name="EngineeringCompiler">{{cite book \|last1=Cooper \|first1=Keith \|last2=Torczon \|first2=Linda \|title=Engineering a Compiler \|url=https://archive.org/details/engineeringcompi00coop_143 \|url-access=limited \|date=7 February 2011 \|publisher=Morgan Kaufmann \|isbn=9780120884780 \|pages=[https://archive.org/details/engineeringcompi00coop_143/page/n238 6]-9 \|edition=2nd}}</ref>		A [[compiler]] translates programs written in one language into another language. Most compilers are organized into three stages: a [[Compiler#Front end\|front end]], an [[Compiler#Middle end\|optimizer]], and a [[Compiler#Back end\|back end]]. The front end is responsible for understanding the program. It makes sure a program is valid and transforms it into an [[intermediate representation]], a data structure used by the compiler to represent the program. The optimizer improves the intermediate representation to increase the speed or reduce the size of the [[executable]] which is ultimately produced by the compiler. The back end converts the optimized intermediate representation into the output language of the compiler.<ref name="EngineeringCompiler">{{cite book \|last1=Cooper \|first1=Keith \|last2=Torczon \|first2=Linda \|title=Engineering a Compiler \|url=https://archive.org/details/engineeringcompi00coop_143 \|url-access=limited \|date=7 February 2011 \|publisher=Morgan Kaufmann \|isbn=9780120884780 \|pages=[https://archive.org/details/engineeringcompi00coop_143/page/n238 6]-9 \|edition=2nd}}</ref>

	If a compiler of a given [[high level language]] produces another high level language, it is called a [[Source-to-source compiler\|transpiler]]. Transpilers can be used to extend existing languages or to simplify compiler development by exploiting [[Software portability\|portable]] and well-optimized implementations of other languages (such as [[C (programming language)\|C]]).<ref name="LanguageGreg" />		If a compiler of a given [[high level language]] produces another high level language, it is called a [[Source-to-source compiler\|transpiler]]. Transpilers can be used to extend existing languages or to simplify compiler development by exploiting [[Software portability\|portable]] and well-optimized implementations of other languages (such as [[C (programming language)\|C]]).<ref name="LanguageGreg" />

KMaster888: subjective ce

2024-12-16T17:57:58Z

subjective ce

← Previous revision		Revision as of 17:57, 16 December 2024
Line 17:		Line 17:
	==Compiler==		==Compiler==
	{{Main\|Compiler}}		{{Main\|Compiler}}
	A [[compiler]] translates ~~a program~~ written in one language into another language. Most compilers are organized into three stages: a [[Compiler#Front end\|front end]], an [[Compiler#Middle end\|optimizer]], and a [[Compiler#Back end\|back end]]. The front end is responsible for understanding the program. It makes sure the program is valid and transforms it into an [[intermediate representation]], a data structure used by the compiler to represent the program. The optimizer improves the intermediate representation to increase the speed or reduce the size of the [[executable]] which is ultimately produced by the compiler. The back end converts the optimized intermediate representation into the output language of the compiler.<ref name="EngineeringCompiler">{{cite book \|last1=Cooper \|first1=Keith \|last2=Torczon \|first2=Linda \|title=Engineering a Compiler \|url=https://archive.org/details/engineeringcompi00coop_143 \|url-access=limited \|date=7 February 2011 \|publisher=Morgan Kaufmann \|isbn=9780120884780 \|pages=[https://archive.org/details/engineeringcompi00coop_143/page/n238 6]-9 \|edition=2nd}}</ref>		A [[compiler]] translates programs written in one language into another language. Most compilers are organized into three stages: a [[Compiler#Front end\|front end]], an [[Compiler#Middle end\|optimizer]], and a [[Compiler#Back end\|back end]]. The front end is responsible for understanding the program. It makes sure the program is valid and transforms it into an [[intermediate representation]], a data structure used by the compiler to represent the program. The optimizer improves the intermediate representation to increase the speed or reduce the size of the [[executable]] which is ultimately produced by the compiler. The back end converts the optimized intermediate representation into the output language of the compiler.<ref name="EngineeringCompiler">{{cite book \|last1=Cooper \|first1=Keith \|last2=Torczon \|first2=Linda \|title=Engineering a Compiler \|url=https://archive.org/details/engineeringcompi00coop_143 \|url-access=limited \|date=7 February 2011 \|publisher=Morgan Kaufmann \|isbn=9780120884780 \|pages=[https://archive.org/details/engineeringcompi00coop_143/page/n238 6]-9 \|edition=2nd}}</ref>

	If a compiler of a given [[high level language]] produces another high level language, it is called a [[Source-to-source compiler\|transpiler]]. Transpilers can be used to extend existing languages or to simplify compiler development by exploiting [[Software portability\|portable]] and well-optimized implementations of other languages (such as [[C (programming language)\|C]]).<ref name="LanguageGreg" />		If a compiler of a given [[high level language]] produces another high level language, it is called a [[Source-to-source compiler\|transpiler]]. Transpilers can be used to extend existing languages or to simplify compiler development by exploiting [[Software portability\|portable]] and well-optimized implementations of other languages (such as [[C (programming language)\|C]]).<ref name="LanguageGreg" />

ShelfSkewed: Undid revision 1236778776 by 2409:4052:6DB8:5BD5:0:0:A4C8:2214 (talk)

2024-10-06T13:46:07Z

Undid revision 1236778776 by 2409:4052:6DB8:5BD5:0:0:A4C8:2214 (talk)

← Previous revision		Revision as of 13:46, 6 October 2024
Line 12:		Line 12:
	A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.		A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.

	===[[Just]]-in-time compiler===		===Just-in-time compiler===
	Some virtual machines include a [[just-in-time compilation\|just-in-time (JIT) compiler]] to improve the efficiency of bytecode execution. While the bytecode is being executed by the virtual machine, if the JIT compiler determines that a portion of the bytecode will be used repeatedly, it compiles that particular portion to machine code. The JIT compiler then stores the machine code in [[Random-access memory\|memory]] so that it can be used by the virtual machine. JIT compilers try to strike a balance between longer compilation time and faster execution time.<ref name="LanguageGreg" />		Some virtual machines include a [[just-in-time compilation\|just-in-time (JIT) compiler]] to improve the efficiency of bytecode execution. While the bytecode is being executed by the virtual machine, if the JIT compiler determines that a portion of the bytecode will be used repeatedly, it compiles that particular portion to machine code. The JIT compiler then stores the machine code in [[Random-access memory\|memory]] so that it can be used by the virtual machine. JIT compilers try to strike a balance between longer compilation time and faster execution time.<ref name="LanguageGreg" />

2409:4052:6DB8:5BD5:0:0:A4C8:2214 at 13:32, 26 July 2024

2024-07-26T13:32:41Z

← Previous revision		Revision as of 13:32, 26 July 2024
Line 12:		Line 12:
	A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.		A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.

	===Just-in-time compiler===		===[[Just]]-in-time compiler===
	Some virtual machines include a [[just-in-time compilation\|just-in-time (JIT) compiler]] to improve the efficiency of bytecode execution. While the bytecode is being executed by the virtual machine, if the JIT compiler determines that a portion of the bytecode will be used repeatedly, it compiles that particular portion to machine code. The JIT compiler then stores the machine code in [[Random-access memory\|memory]] so that it can be used by the virtual machine. JIT compilers try to strike a balance between longer compilation time and faster execution time.<ref name="LanguageGreg" />		Some virtual machines include a [[just-in-time compilation\|just-in-time (JIT) compiler]] to improve the efficiency of bytecode execution. While the bytecode is being executed by the virtual machine, if the JIT compiler determines that a portion of the bytecode will be used repeatedly, it compiles that particular portion to machine code. The JIT compiler then stores the machine code in [[Random-access memory\|memory]] so that it can be used by the virtual machine. JIT compilers try to strike a balance between longer compilation time and faster execution time.<ref name="LanguageGreg" />

Ula993: remove comma

2024-04-04T11:28:18Z

remove comma

← Previous revision		Revision as of 11:28, 4 April 2024
Line 3:		Line 3:
	In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=February 6, 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020 \|url-status=live \|archive-url=https://web.archive.org/web/20201107224313/http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|archive-date= Nov 7, 2020 }}</ref>		In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=February 6, 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020 \|url-status=live \|archive-url=https://web.archive.org/web/20201107224313/http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|archive-date= Nov 7, 2020 }}</ref>
	*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020 \|url-status=live \|archive-url= https://web.archive.org/web/20190308033517/http://www.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|archive-date= Mar 8, 2019 }}</ref>		*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020 \|url-status=live \|archive-url= https://web.archive.org/web/20190308033517/http://www.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|archive-date= Mar 8, 2019 }}</ref>
	*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware, or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />		*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />

	==Interpreter==		==Interpreter==

HeyElliott: Category:CS1 maint: location missing publisher, added archives, ce

2023-12-30T04:49:08Z

Category:CS1 maint: location missing publisher, added archives, ce

← Previous revision		Revision as of 04:49, 30 December 2023
Line 1:		Line 1:
	{{short description\|System for executing computer programs}}		{{short description\|System for executing computer programs}}

	In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=9 ~~May~~ 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020}}</ref>		In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=February 6, 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020 \|url-status=live \|archive-url=https://web.archive.org/web/20201107224313/http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|archive-date= Nov 7, 2020 }}</ref>
	*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020}}</ref>		*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020 \|url-status=live \|archive-url= https://web.archive.org/web/20190308033517/http://www.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|archive-date= Mar 8, 2019 }}</ref>
	*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware, or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />		*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware, or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />

	==Interpreter==		==Interpreter==
	{{Main\|Interpreter (computing)}}		{{Main\|Interpreter (computing)}}
	An [[interpreter (computing)\|interpreter]] is composed of two parts: a [[parser]] and an [[evaluator]]. After a program is read as input by an interpreter, it is processed by the parser. The parser breaks the program into [[Syntax (programming languages)\|language components]] to form a [[parse tree]]. The evaluator then uses the parse tree to execute the program.<ref name="IntroToComputing">{{cite book \|last1=Evans \|first1=David \|title=Introduction to Computing \|date=19 August 2011 \|~~location~~=University of Virginia \|page=211 \|url=https://computingbook.org/FullText.pdf#page=221 \|access-date=22 March 2020}}</ref>		An [[interpreter (computing)\|interpreter]] is composed of two parts: a [[parser]] and an [[evaluator]]. After a program is read as input by an interpreter, it is processed by the parser. The parser breaks the program into [[Syntax (programming languages)\|language components]] to form a [[parse tree]]. The evaluator then uses the parse tree to execute the program.<ref name="IntroToComputing">{{cite book \|last1=Evans \|first1=David \|title=Introduction to Computing \|date=19 August 2011 \|publisher=University of Virginia \|page=211 \|url=https://computingbook.org/FullText.pdf#page=221 \|access-date=22 March 2020}}</ref>

	===Virtual machine===		===Virtual machine===
	A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.		A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.

	===Just-in-time compiler===		===Just-in-time compiler===

← Previous revision		Revision as of 04:49, 30 December 2023
Line 1:		Line 1:
	{{short description\|System for executing computer programs}}		{{short description\|System for executing computer programs}}

	In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=9 ~~May~~ 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020}}</ref>		In [[computer programming]], a '''programming language implementation''' is a system for executing [[computer programs]]. There are two general approaches to programming language implementation:<ref name="RantaBook">{{cite book \|last1=Ranta \|first1=Aarne \|title=Implementing Programming Languages \|date=February 6, 2012 \|publisher=College Publications \|isbn=9781848900646 \|pages=16–18 \|url=http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|access-date=22 March 2020 \|url-status=live \|archive-url=https://web.archive.org/web/20201107224313/http://www.cse.chalmers.se/edu/year/2012/course/DAT150/lectures/plt-book.pdf#page=16 \|archive-date= Nov 7, 2020 }}</ref>
	*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020}}</ref>		*''[[Interpreter (computing)\|Interpretation]]:'' The program is read as input by an interpreter, which performs the actions written in the program.<ref name="LanguageGreg">{{cite web \|last1=Baker \|first1=Greg \|title=Language Implementations \|url=https://www2.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|website=Computing Science - Simon Fraser University \|access-date=22 March 2020 \|url-status=live \|archive-url= https://web.archive.org/web/20190308033517/http://www.cs.sfu.ca/~ggbaker/prog-langs/content/lang-implement.html \|archive-date= Mar 8, 2019 }}</ref>
	*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware, or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />		*''[[Compiler\|Compilation]]:'' The program is read by a compiler, which translates it into some other language, such as [[bytecode]] or [[machine code]]. The translated code may either be directly [[Execution (computing)\|executed]] by hardware, or serve as input to another interpreter or another compiler.<ref name="LanguageGreg" />

	==Interpreter==		==Interpreter==
	{{Main\|Interpreter (computing)}}		{{Main\|Interpreter (computing)}}
	An [[interpreter (computing)\|interpreter]] is composed of two parts: a [[parser]] and an [[evaluator]]. After a program is read as input by an interpreter, it is processed by the parser. The parser breaks the program into [[Syntax (programming languages)\|language components]] to form a [[parse tree]]. The evaluator then uses the parse tree to execute the program.<ref name="IntroToComputing">{{cite book \|last1=Evans \|first1=David \|title=Introduction to Computing \|date=19 August 2011 \|~~location~~=University of Virginia \|page=211 \|url=https://computingbook.org/FullText.pdf#page=221 \|access-date=22 March 2020}}</ref>		An [[interpreter (computing)\|interpreter]] is composed of two parts: a [[parser]] and an [[evaluator]]. After a program is read as input by an interpreter, it is processed by the parser. The parser breaks the program into [[Syntax (programming languages)\|language components]] to form a [[parse tree]]. The evaluator then uses the parse tree to execute the program.<ref name="IntroToComputing">{{cite book \|last1=Evans \|first1=David \|title=Introduction to Computing \|date=19 August 2011 \|publisher=University of Virginia \|page=211 \|url=https://computingbook.org/FullText.pdf#page=221 \|access-date=22 March 2020}}</ref>

	===Virtual machine===		===Virtual machine===
	A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.		A [[virtual machine]] is a special type of interpreter that interprets bytecode.<ref name="LanguageGreg" /> Bytecode is a [[Cross-platform software\|portable]] low-level code similar to machine code, though it is generally executed on a virtual machine instead of a physical machine.<ref name="MakeUseOfVM">{{cite web \|last1=Sridhar \|first1=Jay \|title=Why the Java Virtual Machine Helps Your Code Run Better \|url=https://www.makeuseof.com/tag/why-java-virtual-machine-code-run-better/ \|date=Aug 29, 2017 \|website=MakeUseOf \|access-date=22 March 2020}}</ref> To improve their efficiencies, many programming languages such as [[Java (programming language)\|Java]],<ref name="MakeUseOfVM" /> [[Python (programming language)\|Python]],<ref name="PythonBytecode">{{cite web \|last1=Bennett \|first1=James \|title=An introduction to Python bytecode \|url=https://opensource.com/article/18/4/introduction-python-bytecode \|date=April 23, 2018 \|website=Opensource.com \|access-date=22 March 2020}}</ref> and [[C Sharp (programming language)\|C#]]<ref name="CLR">{{cite web \|last1=Ali \|first1=Mirza Farrukh \|title=Common Language Runtime(CLR) DotNet \|url=https://medium.com/@mirzafarrukh13/common-language-runtime-dotnet-83e0218edcae \|date=Oct 12, 2017 \|website=Medium \|access-date=22 March 2020}}</ref> are compiled to bytecode before being interpreted.

	===Just-in-time compiler===		===Just-in-time compiler===