From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Peter Milliken Newsgroups: gmane.emacs.bugs Subject: bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1? Date: Wed, 21 Nov 2018 12:52:57 +1100 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000004e95d057b230349" X-Trace: blaine.gmane.org 1542765131 27557 195.159.176.226 (21 Nov 2018 01:52:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 21 Nov 2018 01:52:11 +0000 (UTC) Cc: 33441@debbugs.gnu.org, eggert@cs.ucla.edu To: npostavs@gmail.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 21 02:52:07 2018 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 1gPHgT-00071v-6J for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Nov 2018 02:52:05 +0100 Original-Received: from localhost ([::1]:36798 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPHiZ-0001xX-NT for geb-bug-gnu-emacs@m.gmane.org; Tue, 20 Nov 2018 20:54:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPHiP-0001xG-W9 for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 20:54:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPHiL-0007ug-WE for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 20:54:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:33355) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gPHiL-0007uJ-Ra for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 20:54:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gPHiL-0007XU-OW for bug-gnu-emacs@gnu.org; Tue, 20 Nov 2018 20:54:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Peter Milliken Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 21 Nov 2018 01:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33441 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33441-submit@debbugs.gnu.org id=B33441.154276519628922 (code B ref 33441); Wed, 21 Nov 2018 01:54:01 +0000 Original-Received: (at 33441) by debbugs.gnu.org; 21 Nov 2018 01:53:16 +0000 Original-Received: from localhost ([127.0.0.1]:37613 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gPHhc-0007WQ-CX for submit@debbugs.gnu.org; Tue, 20 Nov 2018 20:53:16 -0500 Original-Received: from mail-io1-f52.google.com ([209.85.166.52]:35481) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gPHha-0007WC-46 for 33441@debbugs.gnu.org; Tue, 20 Nov 2018 20:53:14 -0500 Original-Received: by mail-io1-f52.google.com with SMTP id u19so2930750ioc.2 for <33441@debbugs.gnu.org>; Tue, 20 Nov 2018 17:53:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I95HKKRP504sZe/qZftz9n/3vTLKGpYuWrxg0OBzFco=; b=vU+Y+WatB+Dubf8FRv8LSfjDXk2RgfqX7rofB1gLfyQ6TlVhXS1Uu5iTctDGQODngK rUoZ3Sv0YrbocuimLgCe43pQjV8byShB6WZ8r92Qn5+75tcV5z+SK7qhA5H7dgOlnVf6 vZB45aiQtDlUEUQIWa0u2X0K+/0URdrkRCcbqNeHD/Vr0Qpyyukcvs7sse1YA3ADKmpz 2JTu4F4ck7eZ2nQw4p5krT7MAfdR/79gg4U6VX5hu5WVSnW/ZMrPOFPo3aYN+T4NV7jW lnX5vT8qrS//A0tSscDj1CK3Ew5Rfx0PWou0C31zkRUbq37srcyOtoQsDN0PkUeaQkyh gH8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I95HKKRP504sZe/qZftz9n/3vTLKGpYuWrxg0OBzFco=; b=R0j9kkyXiHOqNIK3t0/uooettCXy0pXQA/5Eexzm69VtpodsFcI4Pts9xiCbtjwJka sMz8/i3yNy9Nfydanj9MWmWXWfEAE/WoIo3um8drpN9rCr9KowyTSuzioVH0pNfuQv6F vVXSaBoXxCMg5DP4ZKFCXui78SM/KsMvYO2ow2ZBp15X0Qd3jqCdoHfECupVkIJAbss8 4rgCsEw8Zg8iiyUOzoRaqfaGEGMlO6HD6BDAQUmcRSiGxpFX0G2JAPmQ8QC3wQFn7XPL a5x+uxg3gjsporY3v/g5YDLJDfu7+Fi7tWTQiBidKVb79bjFrwfrYfve5TJKBsuMpp7v 2rxQ== X-Gm-Message-State: AA+aEWbx9Qk/uaj8PT6GOUQTudAR5JM14FiUYWKd3xiapq8WbpitroPf 8gnIOPHZQELljH06Y4zXmW0cIFEInRvMf5Yt05Q= X-Google-Smtp-Source: AFSGD/Un9X9lc9+NGRhArvRHZvosPfONmLGGnH99Wgt7Gwf5ytV+rc3FJPYNk4PZFOULr7GvQyZViJGdEV6O28u5Mjg= X-Received: by 2002:a6b:ce01:: with SMTP id p1-v6mr1779870iob.129.1542765188277; Tue, 20 Nov 2018 17:53:08 -0800 (PST) In-Reply-To: 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:152608 Archived-At: --00000000000004e95d057b230349 Content-Type: text/plain; charset="UTF-8" OK, I skimmed through the trail on 29220 and it appears to me as though there was no definitive fix implemented - even though there was an acknowledgment that a problem existed. The annotation at the end indicates there have been no changes for 268 days, so I guess that is it. My object instances are definitely complicated and probably do have circularities. I think perhaps you might want to put more information/warnings in section 19 of the Elisp manual because it is obviously not true anymore that you can simply Print/Read any arbitrary Lisp Object. I'm going to trap the error in my extension and just force reading/"compiling" from the original text file instead of reading from the intermediate file created by the print process. This will just cause a small delay to the user the first time that a set of language templates get loaded in an edit session - probably not a big deal. Certainly, it is better than telling people my extension is "broken" and won't work with 26.1 and onwards. Thanks for the help and information. Regards Peter On Wed, Nov 21, 2018 at 8:19 AM Noam Postavsky wrote: > On Tue, 20 Nov 2018 at 16:09, Peter Milliken > wrote: > > > > Not sure what the reference to circular structures means in this > context. As I said, all versions of Emacs less than 26 it worked fine with > these same Lisp Objects. > > > > As I said: what changed? Are you trying to say something in 26.1 is now > "fixed" i.e. it should never have worked in versions less than 26? and what > I have been doing for years should have always failed? > > I think the difference is that in Emacs 25 and earlier the type of a > struct (or eieio class?) was encoded as a symbol, whereas in Emacs 26 > and later it is a record object with circular references. > > See also https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29220#47 and > replies. > --00000000000004e95d057b230349 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
OK, I skimmed through the trail on 29220 and it appears to= me as though there was no definitive fix implemented - even though there w= as an acknowledgment that a problem existed. The annotation at the end indi= cates there have been no changes for 268 days, so I guess that is it. My ob= ject instances are definitely complicated and probably do have circularitie= s.

I think perhaps you might want to put more informatio= n/warnings in section 19 of the Elisp manual because it is obviously not tr= ue anymore that you can simply Print/Read any arbitrary Lisp Object.
<= div>
I'm going to trap the error in my extension and just= force reading/"compiling" from the original text file instead of= reading from the intermediate file created by the print process. This will= just cause a small delay to the user the first time that a set of language= templates get loaded in an edit session - probably not a big deal. Certain= ly, it is better than telling people my extension is "broken" and= won't work with 26.1 and onwards.

Thanks for = the help and information.

Regards
Peter<= /div>

On Wed, Nov 21, = 2018 at 8:19 AM Noam Postavsky <np= ostavs@gmail.com> wrote:
On = Tue, 20 Nov 2018 at 16:09, Peter Milliken <peter.milliken@gmail.com> wrote: >
> Not sure what the reference to circular structures means in this conte= xt. As I said, all versions of Emacs less than 26 it worked fine with these= same Lisp Objects.
>
> As I said: what changed?=C2=A0 Are you trying to say something in 26.1= is now "fixed" i.e. it should never have worked in versions less= than 26? and what I have been doing for years should have always failed?
I think the difference is that in Emacs 25 and earlier the type of a
struct (or eieio class?) was encoded as a symbol, whereas in Emacs 26
and later it is a record object with circular references.

See also https://debbugs.gnu.org/cgi/bugrepo= rt.cgi?bug=3D29220#47 and replies.
--00000000000004e95d057b230349--