[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#6991:
From: |
Eli Zaretskii |
Subject: |
bug#6991: |
Date: |
Mon, 11 Sep 2017 17:28:01 +0300 |
> From: Rocky Bernstein <rocky@gnu.org>
> Date: Mon, 11 Sep 2017 06:57:58 -0400
>
> have started looking at decompiling ELISP bytecode using the techniques from
> uncompyle6 .
>
> So far the results are promising. Of course one isn't going to get the exact
> source text back.
>
> For the bytecode for source text
>
> (setq a nil)
> (setq b nil)
>
> when decompiled gives the equivalent:
>
> (setq a (setq b nil))
>
> And macros will be in their expanded form. But I believe nevertheless
> programmers will have a very good idea
> of what was going on when an error was raised.
Sounds interesting and potentially useful. Please keep up the good
work.
Thanks.
- bug#6991:, Rocky Bernstein, 2017/09/11
- bug#6991:,
Eli Zaretskii <=