Editing Parrot virtual machine (section)

==Internals==
There are three forms of program code for Parrot:
*  ''[[Bytecode]]''<ref>{{Cite web |url=http://www.parrotcode.org/docs/parrotbyte.html |title=The Parrot Bytecode (PBC) Format - parrotcode |access-date=2009-07-15 |archive-date=2008-12-24 |archive-url=https://web.archive.org/web/20081224061126/http://www.parrotcode.org/docs/parrotbyte.html |url-status=dead }}</ref> is binary and is natively interpreted by Parrot. Bytecode is usually stored in files with the [[filename extension]] ".pbc".
* ''[[Parrot assembly language]]'' (PASM) is the low level language that [[Compiler|compile]]s down to bytecode. PASM code is usually stored in files with the filename extension ".pasm".
* ''[[Parrot intermediate representation]]'' (PIR<ref>[http://docs.parrot.org/parrot/latest/html/docs/book/ch03_pir.pod.html] {{webarchive|url=https://web.archive.org/web/20090720034439/http://docs.parrot.org/parrot/latest/html/docs/book/ch03_pir.pod.html|date=July 20, 2009}}</ref>) is a slightly higher level language than PASM and also compiles down to bytecode. It is the primary target of language implementations. PIR transparently manages Parrot's inter-routine calling conventions, provides improved syntax, register allocation, and more. PIR code is usually stored in files with the filename extension ".pir".