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
With the introduction of *JUMP_BACKWARD* opcodes and new exception handling table and opcodes it becomes hard to maintain old code without breaking it or affecting the new code in unexpected ways.
Similar approach has been taken with decompile3 with similar reasoning albeit with lower 3.7 version
The proposition itself consists of:
Remove any code that handles <3.11 cases, for better readability and easier maintainability
Add 3.11 + support
The text was updated successfully, but these errors were encountered:
Just imagine for a moment how much men-hours where spent and invested into this project for yeas...
I guess it makes sense to split somehow the codebase
eg - different branches or maybe even different repos?..
Just imagine for a moment how much men-hours where spent and invested into this project for yeas...
I don't disqualify the previous efforts. I probably should have made it clearer in the body of the post, my suggestion is to fork this repo into a new one where the proposition would apply while maintaining this repo for bugfixes mostly.
With the introduction of
*JUMP_BACKWARD*
opcodes and new exception handling table and opcodes it becomes hard to maintain old code without breaking it or affecting the new code in unexpected ways.Similar approach has been taken with decompile3 with similar reasoning albeit with lower 3.7 version
The proposition itself consists of:
The text was updated successfully, but these errors were encountered: