MrJoltCola wrote:
I doubt there is much that could not be mapped to Parrot, but Parrot
does things that would be impossible to map directly back to a CPU.
Currently I am only thinking of just a CPU X to Parrot asm translation,
not the reverse, and this is just an attempt to get to a consolidated
At 12:57 PM 2/25/2005, Steve Coleman wrote:
constructs that could not be logically mapped from other CPU's into
Parrot? Does Parrot assume/use many high level constructs not found in
real processors? Some CPU translations, like from CISC to RISC, are
clearly easier than the reverse, but other t
