On 16.07.13 17:15, Marcus Denker wrote:
No. A decompiler has to be very specific for the code generated by the compiler. I thought so.
For Pharo3, we even opted to not support decompilation at all⦠(IR -> AST). We will instead save a higher-level representation that has much more information (e.g. names of variables). For deployment, people can strip the names, giving them the same "obfuscation" the decompiler provides now. Sounds reasonable - so if I generate IR (-> BC) from non-Smalltalk sources ... is there any recommended way to make the non-Smalltalk-source visible in browsers? Up to now I would simply generate IR/BC directly which would mean that a class would have a method but w/o the source.
Or do I miss a crucial piece here? Udo