From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Rocky Bernstein Newsgroups: gmane.emacs.devel Subject: Re: RFC - documenting LAP Date: Tue, 19 Dec 2017 07:56:52 -0500 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114c51d234ea360560b100ec" X-Trace: blaine.gmane.org 1513688140 23803 195.159.176.226 (19 Dec 2017 12:55:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 19 Dec 2017 12:55:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 19 13:55:36 2017 Return-path: Envelope-to: ged-emacs-devel@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 1eRHQg-0005Sy-Ry for ged-emacs-devel@m.gmane.org; Tue, 19 Dec 2017 13:55:30 +0100 Original-Received: from localhost ([::1]:42786 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eRHSd-0008OQ-Vp for ged-emacs-devel@m.gmane.org; Tue, 19 Dec 2017 07:57:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42530) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eRHS2-0008O3-IE for emacs-devel@gnu.org; Tue, 19 Dec 2017 07:56:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eRHS1-0000DP-Fw for emacs-devel@gnu.org; Tue, 19 Dec 2017 07:56:54 -0500 Original-Received: from mail-qk0-x229.google.com ([2607:f8b0:400d:c09::229]:32877) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eRHS1-0000D5-Aq for emacs-devel@gnu.org; Tue, 19 Dec 2017 07:56:53 -0500 Original-Received: by mail-qk0-x229.google.com with SMTP id x7so4933173qkb.0 for ; Tue, 19 Dec 2017 04:56:53 -0800 (PST) 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; bh=7Y6pBFvIUN+F9ZBLxu+UgrzGU6esVV/R6Bbgv/sNwE4=; b=synCWPOjVwURzSgRtfzRI5wO2bQ4EAHOmKVGFQCg96gAp/dhBHge/A8OFQgAa7DLBT wvqx2CFbXiM3/G2owVIi8B9QLZxKxVIZyjItLZB+eOi05u+Ck5xn7YONO74rZeLSNGrS pVE6VzufKQuetOkXZp47XdV1thUGk2t1hUdr/2ZnzrbSCEhurPMamIMvC4kJtzkEhMUs xkT16YZLPcx0xDgWqvUIQEjUVTw+dECvAJsk3n1vSy2IwDa4wZTQEIaN0tIN4tEU9Blq qkfSLedxbt62hxe2duFuxTA2oJT8y4+THgouqbTcuNaVo03rCmMl1tuK49t7NqGR9Z9X DEXw== 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; bh=7Y6pBFvIUN+F9ZBLxu+UgrzGU6esVV/R6Bbgv/sNwE4=; b=t1o5eeLMyr7ahA+9EIPI1Bz/4z3or23Llm+Iqtv/zFOv2Ab0sPSNuziWmUCSqXEz+s CGHHptJ2HUWhWLKnprznQ9H7PSghapmnXFj1S/xrs4ekYuO0U7GHdIPVZWG+CBmKVuAN gnctHLyqsogINEOtXo/WeQwQjOevXAZVLFJn9CjOtR1zx0Q8jHdG6ZulLymkztCqVrWd mSjO0bCns/yB5u5gvgO9xpbTTFF6QWp6iKIW73gHXUEoWFW1f7AFzRiGEahB5IOsLDvv wE5J/yaJ7FvK87DrIwwS2+jV/fsVI2tKroTYSTHJ0kMj7FJUCSe+KX5Nylcn0TSFL6m3 ZWEA== X-Gm-Message-State: AKGB3mJX/rk+fBkr4+fXUI6VXqXev0JHKIV8Kaisgv8HzFxJtQTaqWU+ ASQ/S54MwSr3eaQOq2/RRgOWdEvR/piLL/fyC/xRSw== X-Google-Smtp-Source: ACJfBovh3xgX2jM8XAGnj+Y6rcvk+eHmnEkJND9wyXhpEnXOe8txORd802TNkZWvUk0QUILMWyFqB/yeTXBuKIGGh3I= X-Received: by 10.55.8.136 with SMTP id 130mr4839467qki.146.1513688212495; Tue, 19 Dec 2017 04:56:52 -0800 (PST) Original-Received: by 10.12.197.8 with HTTP; Tue, 19 Dec 2017 04:56:52 -0800 (PST) In-Reply-To: X-Google-Sender-Auth: m7l9dk3TZiYou6urzCnqQ-SDDQo X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400d:c09::229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221245 Archived-At: --001a114c51d234ea360560b100ec Content-Type: text/plain; charset="UTF-8" One of the things the LAP/Elisp Bytecode doc should have are notes as to when certain opcodes were added or removed. Again, I'll cull Changelogs or git history, but if folks who have made changes want to explain what changed when and why, that's certainly more friendly than doing the investigative digging. Thanks. On Mon, Dec 18, 2017 at 9:47 PM, Rocky Bernstein wrote: > The LAP instruction set isn't documented. I will undertake to make a pass > at it. > > At this early stage though, changes to the organization are the easiest to > make; so if you have thoughts, please speak up. > > So we have something concrete to discuss, The first stab at this is at > https://github.com/rocky/elisp-lap > > I can put this on savanna.gnu.org such as under emacs or somewhere else > pending discussion. However at this stage where it is mostly amorphous and > not filled in, I don't think it really matters much. > --001a114c51d234ea360560b100ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
One of the things the LAP/Elisp Bytecode doc should h= ave are notes as to when certain opcodes were added or removed. Again, I= 9;ll cull Changelogs or git history, but if folks who have made changes wan= t to explain what changed when and why, that's certainly more friendly = than doing the investigative digging.

Thanks.

On Mon, Dec 18, 2017 at= 9:47 PM, Rocky Bernstein <rocky@gnu.org> wrote:
The LAP instruction set isn&#= 39;t documented. I will undertake to make a pass at it.

At thi= s early stage though, changes to the organization are the easiest to make; = so if you have thoughts, please speak up.

So = we have something concrete to discuss, The first stab at this is at https://github.co= m/rocky/elisp-lap

I can put this on savanna.gnu.org such as= under emacs or somewhere else pending discussion. However at this stage wh= ere it is mostly amorphous and not filled in, I don't think it really m= atters much.

--001a114c51d234ea360560b100ec--