From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Rocky Bernstein Newsgroups: gmane.emacs.bugs Subject: bug#6991: Date: Tue, 12 Sep 2017 21:13:03 -0400 Message-ID: References: <8739tm9vzl.fsf@jidanni.org> <83bmmhtimm.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113d3f569a87d9055907dc3c" X-Trace: blaine.gmane.org 1505265266 21899 195.159.176.226 (13 Sep 2017 01:14:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Sep 2017 01:14:26 +0000 (UTC) Cc: 6991@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Sep 13 03:14:18 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drwFj-0004nq-TZ for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Sep 2017 03:14:08 +0200 Original-Received: from localhost ([::1]:39455 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drwFp-0003Pc-KF for geb-bug-gnu-emacs@m.gmane.org; Tue, 12 Sep 2017 21:14:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drwFj-0003O3-6B for bug-gnu-emacs@gnu.org; Tue, 12 Sep 2017 21:14:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drwFf-00017W-28 for bug-gnu-emacs@gnu.org; Tue, 12 Sep 2017 21:14:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:56231) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1drwFe-00017G-Uq for bug-gnu-emacs@gnu.org; Tue, 12 Sep 2017 21:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1drwFe-0000Zd-IU for bug-gnu-emacs@gnu.org; Tue, 12 Sep 2017 21:14:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Rocky Bernstein Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Sep 2017 01:14:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 6991 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed notabug Original-Received: via spool by 6991-submit@debbugs.gnu.org id=B6991.15052651922129 (code B ref 6991); Wed, 13 Sep 2017 01:14:02 +0000 Original-Received: (at 6991) by debbugs.gnu.org; 13 Sep 2017 01:13:12 +0000 Original-Received: from localhost ([127.0.0.1]:36679 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drwEq-0000YH-EK for submit@debbugs.gnu.org; Tue, 12 Sep 2017 21:13:12 -0400 Original-Received: from mail-oi0-f51.google.com ([209.85.218.51]:34927) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drwEo-0000Y2-94 for 6991@debbugs.gnu.org; Tue, 12 Sep 2017 21:13:10 -0400 Original-Received: by mail-oi0-f51.google.com with SMTP id z73so34621314oia.2 for <6991@debbugs.gnu.org>; Tue, 12 Sep 2017 18:13:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nEEXM5AftajI+sN3bZ+4XK0Cn0pImv+hCd3PGo8NU9I=; b=LERnKOl/5vXQK+xGCMvX2omQy2bba6guafJWukRPJ5lMHrUsfUfWmw9CfHpeZUPba3 1KDBMsxafZKj+KiESkOOKh9wmh+xbBbNdA490BwrngRAac+nBOc+hHELgnBWGqbRNO7J ZKDaqHUC1cyn0T86XPYG6Cja9VK8H4/DWMwuoJUb+nLyCtSxYnQVM/oopqJLHkf+ABOk 1hZZEZyAZ+zEj7YHt49dUQ6TEh6ztsF7orV/t21rfUG8bBkm4Xy0jFPCF26o5q+CNMCw NWuUj/MtIWnBp9vQUWalhfE1CMpTpTSgsS7RuxK2dJlI/YyrooV7s7MTZHBCr1mScKQV E+1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nEEXM5AftajI+sN3bZ+4XK0Cn0pImv+hCd3PGo8NU9I=; b=YjqDD7Jl32i2lOoorPOSavevJUnZWovsdDine7uhIL+u1XsS5DxHLjXERsxKHazvK+ zITj7Z22ZnRoZjCMPXQkD0I9vokAspG0VhZ67/kMR1qxbDap/suWbqr8mwO6djZ38OU9 uaU96oTyEtIkk1nxU8u9Si4DgWKG2G6zTXP0jP+BzlcQEor92Usy9xrg/Ri61n4JxGei RquJZH2hNlWPOlY+Vi4YZiY5ErdRWf9eDpl94W1soFCm+UQM/hNf61z+8SHh+pDuvgix G7Q4x85+kKUsTlY4NPA81HyNfHGv9h+vxl5tCpatB1faTE1EMics6Hgm01SghCnJCCeJ fq3A== X-Gm-Message-State: AHPjjUhy5m6yWszhupjo5JjePNFgJrZYzGNlsNrehaxeqMSLDZ1nCC73 b6+qZMqE+mYTC02YPNESFrIcWOOCS8m1Et4jsm3M/cFk X-Google-Smtp-Source: AOwi7QDNoha3VXL1Gf1ch6oivoltVaP3DL+CXu9MG88EFOFFMHyPM1gG/AISeqROVoxLnI4fg6AjxONDkD0gbCTNFqU= X-Received: by 10.202.180.84 with SMTP id d81mr17994728oif.15.1505265184308; Tue, 12 Sep 2017 18:13:04 -0700 (PDT) Original-Received: by 10.157.24.109 with HTTP; Tue, 12 Sep 2017 18:13:03 -0700 (PDT) In-Reply-To: <83bmmhtimm.fsf@gnu.org> X-Google-Sender-Auth: eQUkSAMQ-7xCjShkAYzhkNxzUAM X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:136853 Archived-At: --001a113d3f569a87d9055907dc3c Content-Type: text/plain; charset="UTF-8" Thanks for the kind words. Right now I see no obstacles to getting this done. Just lots of work, and not enough hands. I'm going to try to get the local Emacs group interested in helping out. And if not in this, then contributing to documenting bytecode in of itself is something that would be of value. What I have right now is at https://github.com/rocky/elisp-decompile . Alas, for expediency it is right now written in Python. On Mon, Sep 11, 2017 at 10:28 AM, Eli Zaretskii wrote: > > From: Rocky Bernstein > > 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. > --001a113d3f569a87d9055907dc3c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the kind words. Right now I see no obstacles to= getting this done. Just lots of work, and not enough hands. I'm going = to try to get the local Emacs group interested in helping out. And if not i= n this, then contributing to documenting bytecode in of itself is something= that would be of value.

What I have =C2=A0right no= w is at=C2=A0https://g= ithub.com/rocky/elisp-decompile . Alas, for expediency it is right now = written in Python.=C2=A0

On Mon, Sep 11, 2017 at 10:28 AM, Eli Zaretskii <eliz@= gnu.org> wrote:
> From: = Rocky Bernstein <rocky@gnu.org><= br> > Date: Mon, 11 Sep 2017 06:57:58 -0400
>
> have started looking at decompiling ELISP bytecode using the technique= s 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.=C2=A0 Please keep up the good work.

Thanks.

--001a113d3f569a87d9055907dc3c--