3 ms·
My take is that a "compiler" always compiles down (i.e. throws away information that cannot be recovered from the result), while a transpiler may actually be lo
by derefr 9y ago
My take is that a "compiler" always compiles down (i.e. throws away information that cannot be recovered from the result), while a transpiler may actually be lossless—you could potentially write another transpiler to go in the other direction, and the two together would form a bijective function.
On the other hand, sometimes "transpiration" involves both throwing away information, and then either heuristically recovering information (i.e. compiling to assembler, followed by decompiling to the target language) or inventing information (i.e. compiling to object code and then wrapping that object code in a VM written in the target language.) You wouldn't call a program that involved either of these a "compiler"; it would most certainly be a "transpiler" only.
- sigjuice 9y agoCitation(s) needed for "compiler" always compiles down.