Subject: bug#6991:

From: Eli Zaretskii <[email-masked]>
Date: Mon, 11 Sep 2017 17:28:01 +0300

> From: Rocky Bernstein <[email-masked]>
> 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.