Replies: 1 comment
-
|
I though about the same many years ago. But didnt moved forward because of lack of time to priorize this. Maybe those plugins should be loaded from core? Or maybe we must have a separate module named r_deco to provide all those primitives? Imho “deco” looks better than the long name one inconvient i find here is that we lose the ability to run multiple decompilers in one line without changing config vars. Not sure how well that will play if we run them in paralel either. So maybe pdc will require subcommands to hold them or maybe we need another root command handler for them or just keep the current approach for some time for backward compat. Pdc can run a different decompiler with cmd.pdc env var |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Now, decompilers are implemented as core plugins, each with it's own commands. What about defining a decompiler plugin API and unify decompilation commands.
Something like:
Define API
Group settings under decompiler.*
Unify commands
Port currently supported decompilers
Add new decompilers
Beta Was this translation helpful? Give feedback.
All reactions