From: dalanicolai <dalanicolai@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: How to retrieve a node from ewoc by data (extend library?)
Date: Tue, 29 Mar 2022 13:29:01 +0200 [thread overview]
Message-ID: <CACJP=3mngEzQhWmGjX1MT2_eTzQeyaePxRJSJyo3SSmbE+8PKg@mail.gmail.com> (raw)
In-Reply-To: <p91h77szrfs.fsf@google.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Sorry for this late reply, sometimes I get a bit too much distracted...
But anyway, just wanted to thank for your replies;
you can be sure, that the help here is always very appreciated.
I wanted to look a little more into it (which I partly did)... but there is
a bit too much other work to do also. Anyway, when I encounter this
again (e.g. when I do some code review/refactoring), then I already
have your 'opinion(s)', and can just go ahead...
On Sun, 20 Mar 2022 at 14:25, T.V Raman <raman@google.com> wrote:
> Speaking of ewoc, debugging elisp tools that ewoc can prove hard from
> experience because attempting to print an ewoc object ends up walking a
> complex chain of self-referential nodes; attempting to debug package
> jabber.el in the past comes to mind.
>
> Could ewoc perhaps define some ewoc-specific print functions that allows
> the developer to inspect the state of the ewoc graph?
>
>
> --
>
> Thanks,
>
> --Raman(I Search, I Find, I Misplace, I Research)
> ♈ Id: kg:/m/0285kf1 🦮
>
[-- Attachment #2: Type: text/html, Size: 1438 bytes --]
next prev parent reply other threads:[~2022-03-29 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 17:32 How to retrieve a node from ewoc by data (extend library?) dalanicolai
2022-03-20 2:49 ` Stefan Monnier
2022-03-20 13:25 ` T.V Raman
2022-03-29 11:29 ` dalanicolai [this message]
2022-03-29 21:00 ` Stefan Monnier
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='CACJP=3mngEzQhWmGjX1MT2_eTzQeyaePxRJSJyo3SSmbE+8PKg@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.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).