You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for bringing the Relooper problem class to my attention (and indirectly the Stackifier problem class).
.
I had previously assumed that bytecode was "always" a 100% decompilable substitute for missing source code (100% identical, except temporary names), as is the case with Smalltalk decompiler.
.
What might be the reason for the problems of Relooper and Stackifier that are not present in the Smalltalk system?
The text was updated successfully, but these errors were encountered:
But the main issue is a mismatch between structured code (loops and if/else) and jump/branch to address models. Some languages only support one of them, and some VM formats use the other.
Also many, probably most, bytecodes definitely aren't 100% reversible. That sounds like Python's which is really just a compressed source code. Most bytecodes for VMs are truly compiled for them, and lots of information is lost.
what information can be lost by Inform7 compiled bytecode; I'm sure I can find examples (going the very long way), but your experience could shortcut that for me; thanks
Thank you for bringing the Relooper problem class to my attention (and indirectly the Stackifier problem class).
.
I had previously assumed that bytecode was "always" a 100% decompilable substitute for missing source code (100% identical, except temporary names), as is the case with Smalltalk decompiler.
.
What might be the reason for the problems of Relooper and Stackifier that are not present in the Smalltalk system?
The text was updated successfully, but these errors were encountered: