GNU logs - #30070, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#30070: 27.0.50; cl-print sometimes prints self-referencing objects as #1=#<thing>
Resent-From: Michael Heerdegen <michael_heerdegen@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 10 Jan 2018 19:40:01 +0000
Resent-Message-ID: <handler.30070.B.15156131882196 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 30070 <at> debbugs.gnu.org
Cc: Stefan Monnier <monnier@HIDDEN>
From: Michael Heerdegen <michael_heerdegen@HIDDEN>
Date: Wed, 10 Jan 2018 20:39:03 +0100
Message-ID: <87fu7dtsfc.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>


Hi,

my use case is like this:

--8<---------------cut here---------------start------------->8---
;; -*- lexical-binding: t -*-

(require 'cl-lib)
(require 'cl-print)

(cl-defstruct thing
  thing-object)

(cl-defmethod cl-print-object ((_object thing) stream)
  (princ "#<thing>" stream))

(let ((print-circle t))
  (cl-prin1-to-string
   (letrec ((me (make-thing :thing-object (lambda () me))))
     me)))
--8<---------------cut here---------------end--------------->8---

That gives me "#1=#<thing>".  That's weird because the printed
representation of the thing doesn't refer to itself.  This can happen in
real life: that the thing-object in the example is a closure referencing
the thing itself might be coincidence, so one can't assume that the
printed representation of a self-referential object always includes a
reference to the top-level object.


TIA,

Michael.


In GNU Emacs 27.0.50 (build 11, x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
 of 2018-01-10 built on drachen
Repository revision: bf38966965384b07621839db892b90932b8754a6
Windowing system distributor 'The X.Org Foundation', version 11.0.11905000
System Description: Debian GNU/Linux testing (buster)

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Michael Heerdegen <michael_heerdegen@HIDDEN>
Subject: bug#30070: Acknowledgement (27.0.50; cl-print sometimes prints
 self-referencing objects as #1=#<thing>)
Message-ID: <handler.30070.B.15156131882196.ack <at> debbugs.gnu.org>
References: <87fu7dtsfc.fsf@HIDDEN>
X-Gnu-PR-Message: ack 30070
X-Gnu-PR-Package: emacs
Reply-To: 30070 <at> debbugs.gnu.org
Date: Wed, 10 Jan 2018 19:40:01 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 30070 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
30070: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D30070
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#30070: 27.0.50; cl-print sometimes prints self-referencing objects as #1=#<thing>
Resent-From: Stefan Monnier <monnier@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 10 Jan 2018 20:37:01 +0000
Resent-Message-ID: <handler.30070.B.15156165817292 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Michael Heerdegen <michael_heerdegen@HIDDEN>
Cc: 30070 <at> debbugs.gnu.org
From: Stefan Monnier <monnier@HIDDEN>
Message-ID: <jwvr2qxqwq9.fsf-monnier+emacsbugs@HIDDEN>
References: <87fu7dtsfc.fsf@HIDDEN>
Date: Wed, 10 Jan 2018 15:39:46 -0500
In-Reply-To: <87fu7dtsfc.fsf@HIDDEN> (Michael Heerdegen's message of "Wed, 10
 Jan 2018 20:39:03 +0100")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> That gives me "#1=#<thing>".  That's weird because the printed
> representation of the thing doesn't refer to itself.

Yes, it's a known misfeature (to me at least).  I don't know how we
could fix it, tho: the cycle-detection is done in a preprocessing phase
which doesn't know about any print format (nor about cl-print), so by
the time we learn the the object will be printed as "#<thing>", we have
already printed "#1=".

To fix it, I have the impression that we'd have to make cl-print a lot
more complex, and potentially its API as well (e.g. add a matching
cl-preprocess method additionally to cl-print-object).

        Stefan

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#30070: 27.0.50; cl-print sometimes prints self-referencing objects as #1=#<thing>
Resent-From: Michael Heerdegen <michael_heerdegen@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 11 Jan 2018 14:46:01 +0000
Resent-Message-ID: <handler.30070.B.151568195030671 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Stefan Monnier <monnier@HIDDEN>
Cc: 30070 <at> debbugs.gnu.org
From: Michael Heerdegen <michael_heerdegen@HIDDEN>
References: <87fu7dtsfc.fsf@HIDDEN> <jwvr2qxqwq9.fsf-monnier+emacsbugs@HIDDEN>
Date: Thu, 11 Jan 2018 15:45:26 +0100
In-Reply-To: <jwvr2qxqwq9.fsf-monnier+emacsbugs@HIDDEN> (Stefan Monnier's
 message of "Wed, 10 Jan 2018 15:39:46 -0500")
Message-ID: <87r2qw1mk9.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Stefan Monnier <monnier@HIDDEN> writes:

> > That gives me "#1=#<thing>".  That's weird because the printed
> > representation of the thing doesn't refer to itself.
>
> Yes, it's a known misfeature (to me at least).  I don't know how we
> could fix it, tho: the cycle-detection is done in a preprocessing phase
> which doesn't know about any print format (nor about cl-print), so by
> the time we learn the the object will be printed as "#<thing>", we have
> already printed "#1=".
>
> To fix it, I have the impression that we'd have to make cl-print a lot
> more complex, and potentially its API as well (e.g. add a matching
> cl-preprocess method additionally to cl-print-object).

Yes, that's what I expected.

Would it make sense to cache what is being printed, post-process it, and
print it at once?


Michael.

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#30070: 27.0.50; cl-print sometimes prints self-referencing objects as #1=#<thing>
Resent-From: Stefan Monnier <monnier@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 11 Jan 2018 15:11:02 +0000
Resent-Message-ID: <handler.30070.B.1515683448855 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 30070
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Michael Heerdegen <michael_heerdegen@HIDDEN>
Cc: 30070 <at> debbugs.gnu.org
X-Debbugs-Original-Cc: bug-gnu-emacs@HIDDEN
Received: via spool by submit <at> debbugs.gnu.org id=B.1515683448855
          (code B ref -1); Thu, 11 Jan 2018 15:11:02 +0000
Received: (at submit) by debbugs.gnu.org; 11 Jan 2018 15:10:48 +0000
Received: from localhost ([127.0.0.1]:52328 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1eZeVC-0000Di-Sy
	for submit <at> debbugs.gnu.org; Thu, 11 Jan 2018 10:10:48 -0500
Received: from eggs.gnu.org ([208.118.235.92]:54696)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <monnier@HIDDEN>) id 1eZeVA-0000DU-Un
 for submit <at> debbugs.gnu.org; Thu, 11 Jan 2018 10:10:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1eZeV4-0001aQ-Qk
 for submit <at> debbugs.gnu.org; Thu, 11 Jan 2018 10:10:39 -0500
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_05 autolearn=disabled
 version=3.3.2
Received: from lists.gnu.org ([2001:4830:134:3::11]:60367)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <monnier@HIDDEN>)
 id 1eZeV4-0001aK-NN
 for submit <at> debbugs.gnu.org; Thu, 11 Jan 2018 10:10:38 -0500
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45633)
 by lists.gnu.org with esmtp (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1eZeV3-00026N-OS
 for bug-gnu-emacs@HIDDEN; Thu, 11 Jan 2018 10:10:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1eZeUz-0001Xc-4q
 for bug-gnu-emacs@HIDDEN; Thu, 11 Jan 2018 10:10:37 -0500
Received: from pruche.dit.umontreal.ca ([132.204.246.22]:46577)
 by eggs.gnu.org with esmtp (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1eZeUy-0001XH-Pp
 for bug-gnu-emacs@HIDDEN; Thu, 11 Jan 2018 10:10:33 -0500
Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242])
 by pruche.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w0BFAU1W011657;
 Thu, 11 Jan 2018 10:10:31 -0500
Received: by pastel.home (Postfix, from userid 20848)
 id DAA876231F; Thu, 11 Jan 2018 10:10:30 -0500 (EST)
From: Stefan Monnier <monnier@HIDDEN>
Message-ID: <jwvlgh45t7e.fsf-monnier+emacsbugs@HIDDEN>
References: <87fu7dtsfc.fsf@HIDDEN>
 <jwvr2qxqwq9.fsf-monnier+emacsbugs@HIDDEN> <87r2qw1mk9.fsf@HIDDEN>
Date: Thu, 11 Jan 2018 10:10:30 -0500
In-Reply-To: <87r2qw1mk9.fsf@HIDDEN> (Michael Heerdegen's message of "Thu, 11
 Jan 2018 15:45:26 +0100")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level: 
X-NAI-Spam-Threshold: 5
X-NAI-Spam-Score: 0.1
X-NAI-Spam-Rules: 3 Rules triggered
 GEN_SPAM_FEATRE=0.1, EDT_SA_DN_PASS=0, RV6198=0
X-NAI-Spam-Version: 2.3.0.9418 : core <6198> : inlines <6305> : streams
 <1775757> : uri <2568056>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
 recognized.
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Received-From: 2001:4830:134:3::11
X-Spam-Score: -4.0 (----)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -4.0 (----)

> Would it make sense to cache what is being printed, post-process it, and
> print it at once?

We could try, but we'd have to somehow distinguish the "#N=" and "#N#"
that are used for such sharing references from those that may appear as
part of "normal user output".


        Stefan

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.