Another purpose of source-to-source-compiling is translating legacy code to use the next version of the underlying programming language or an API that breaks backward compatibility. It will perform automatic code refactoring which is useful when the programs to refactor are outside the control of the original implementer (for example, converting programs from Python 2 to Python 3, or converting programs from an old API to the new API) or when the size of the program makes it impractical or time consuming to refactor it by hand.
One of the earliest programs of this kind was Digital Research's XLT86 in 1981, a program written by Gary Kildall, which translated .ASM source code for the Intel 8080 processor into .A86 source code for the Intel 8086. Using global data flow analysis on 8080 register usage, the translator would also optimize the output for code size and take care of calling conventions, so that CP/M-80 and MP/M-80 programs could be ported to the CP/M-86 and MP/M-86 platforms automatically. XLT86 itself was written in PL/I-80 and was available for CP/M-80 platforms as well as for DEC VMS (for VAX 11/750 or 11/780).
A similar, but much less sophisticated program was TRANS.COM, written by Tim Paterson in 1980 as part of 86-DOS. It could translate some Z80 assembly source code into .ASM source code for the 8086, but supported only a subset of opcodes, registers and modes, often still requiring significant manual correction and rework afterwards. Also it did not carry out any register and jump optimizations.
Programming language implementationsEdit
|Name||Source language||Target language|
|HipHop for PHP (HPHPc)||PHP||C++|
Porting a codebaseEdit
When developers want to switch to a different language while retaining most of an existing codebase, it might be better to use a transcompiler compared to rewriting the whole software by hand. Depending on the quality of the transcompiler, the code may or may not need manual intervention in order to work properly. This is different from "transcompiled languages" where the specifications demand that the output source code always works without modification. All transpilers used to port a codebase will expect manual adjustment of the output source code if there is a need to achieve maximum code quality in terms of readability and platform convention.
|Tool||Source language||Target language||Comments|
|2to3 script||Python 2||Python 3||Even though 2to3 does its best at automating the translation process, further manual corrections are often needed.|
|c2go||C||Go||Before the 1.5 release, the Go compiler was written in C. An automatic translator was developed to automatically convert the compiler codebase from C into Go. Since Go 1.5, the "compiler and runtime are now implemented in Go and assembler, without C".|
|J2Eif||Java||Eiffel||The resulting Eiffel code has classes and structures similar to the Java program but following Eiffel syntax and conventions.|
|C2Eif||C||Eiffel||The resulting Eiffel code has classes and structures that try to be as clean as possible. The tool is complete and relies on embedding the C and assembly code if it cannot translate it properly.|
|Swiftify||Objective-C||Swift||Swiftify is an online source to source conversion tool from Objective-C into Swift. It assists developers who are migrating all or part of their iOS codebase into Swift. The conversion is aimed primarily at converting the syntax between Objective-C and Swift, and is helped because Apple took efforts to ensure compatibility between Swift and Objective-C runtimes.|
|Runtime Converter||PHP||Java||The Runtime Converter is an automatic tool which converts PHP source code into Java source code. There is a Java runtime library for certain features of the PHP language, as well as the ability to call into the PHP binary itself using JNI for PHP standard library and extension function calls.|
A transcompiler pipeline is what results from recursive transcompiling. By stringing together multiple layers of tech, with a transcompile step between each layer, technology can be repeatedly transformed, effectively creating a distributed language independent specification.
- Post processor
- C to HDL
- DMS Software Reengineering Toolkit – a source-to-source compiler framework using explicit pattern-directed rewrite rules
- Language interoperability
- Binary recompiler
- Code generation (compiler)
- Program transformation
- ROSE compiler framework – a source-to-source compiler framework
- Translation (computing)
- Language binding
- Language-independent specification
- Intermediate language
- Recursive transcompiling
- f2c – a source-to-source compiler from Fortran 77 to C
- "Transpiler". devopedia.org. Retrieved 2019-06-22.
- "Types of compilers". compilers.net. 1997–2005. Retrieved 28 October 2010.
- Fowler, Martin (February 12, 2013). "Transparent Compilation". Retrieved February 13, 2013.
- Lenz, Fitzgerald (11 February 2011). "Source Map Revision 3 Proposal".
- Epic Games; Mozilla. "HTML5 Epic Citadel".
- Digital Research (1981). XLT86 - 8080 to 8086 Assembly Language Translator - User's Guide (PDF). Pacific Grove, CA, USA: Digital Research Inc. Archived (PDF) from the original on 2016-11-18. Retrieved 2016-11-18.
- Seattle Computer Products (1980): 86-DOS - Disk Operating System for the 8086. User's manual, version 0.3 - Preliminary. Seattle Computer Products, Seattle ().
- Paterson, Tim (2013-12-19) . "Microsoft DOS V1.1 and V2.0: Z80 to 8086 Translator version 2.21 /msdos/v11source/TRANS.ASM". Computer History Museum, Microsoft. Retrieved 2014-03-25. (NB. While the publishers claim this would be MS-DOS 1.1 and 2.0, it actually is SCP MS-DOS 1.25 and TeleVideo PC DOS 2.11.)
- "List of languages that compile to JS". Retrieved 2018-03-11.
- "Transpiler". devopedia.org. Retrieved 2019-01-08.
- "C->Go translator". Retrieved 11 January 2018.
- "Go 1.5 Release Notes". Retrieved 11 January 2018.
- Russ Cox. "Go 1.3+ Compiler Overhaul". Retrieved 11 January 2018.
- "Js_of_ocaml". Retrieved 8 October 2014.
- "J2Eif Research Page - Chair of Software Engineering". Se.inf.ethz.ch. doi:10.1007/978-3-642-21952-8_4. Retrieved 2014-07-08.
- "C2Eif Research Page - Chair of Software Engineering". Se.inf.ethz.ch. Retrieved 2014-07-08.
- "Swiftify Objective-C to Swift Converter". Retrieved 2017-11-14.
- "Runtime Converter". Retrieved 2017-11-14.