From: Noam Postavsky <npostavs@gmail.com>
To: Peter Milliken <peter.milliken@gmail.com>
Cc: 33441@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1?
Date: Tue, 20 Nov 2018 16:19:38 -0500 [thread overview]
Message-ID: <CAM-tV-8ajipaWOrMqbUtbuxOO3vaKgqxNSqSe2JsR24COoQzVw@mail.gmail.com> (raw)
In-Reply-To: <CAA0nDNv35nU3zZf8aZszcbQ1jZXAgrn3AV8FRw+_BMMq0cBUSA@mail.gmail.com>
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 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.
next prev parent reply other threads:[~2018-11-20 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 7:21 bug#33441: reading and printing Lisp Objects - what changed from 25.3.1 to 26.1? Peter Milliken
2018-11-20 20:56 ` Paul Eggert
2018-11-20 21:02 ` Noam Postavsky
2018-11-20 21:09 ` Peter Milliken
2018-11-20 21:17 ` Paul Eggert
2018-11-20 21:19 ` Noam Postavsky [this message]
2018-11-21 1:52 ` Peter Milliken
2018-11-21 3:27 ` Basil L. Contovounesios
2018-11-21 3:46 ` Eli Zaretskii
2018-11-21 4:21 ` Peter Milliken
2018-11-23 7:12 ` Paul Eggert
2019-04-01 23:55 ` Noam Postavsky
2019-04-02 2:51 ` Peter Milliken
2019-04-02 13:29 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8ajipaWOrMqbUtbuxOO3vaKgqxNSqSe2JsR24COoQzVw@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=33441@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=peter.milliken@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).