From: Chris Vine <vine24683579@gmail.com>
To: guile-user@gnu.org
Subject: Re: Question about an error with ports
Date: Sat, 12 Mar 2022 00:27:17 +0000 [thread overview]
Message-ID: <20220312002717.2cd16e1974f90136f8ed3dfc@gmail.com> (raw)
In-Reply-To: <20220312001036.67ff583279623b9a02712045@gmail.com>
On Sat, 12 Mar 2022 00:10:36 +0000
Chris Vine <vine24683579@gmail.com> wrote:
> On Fri, 11 Mar 2022 20:49:53 +0100
> Maxime Devos <maximedevos@telenet.be> wrote:
> > Chris Vine schreef op vr 11-03-2022 om 18:13 [+0000]:
> > > code has changed. I have yet to re-equip my tests to test the write and
> > > display procedures,
> >
> > Those aren't rewritten in Scheme (yet?).
>
> I believe not. Unfortunately this kind of thing is not well
> documented: I think you are expected to read through the source code
> yourself. On doing so, the write and display procedures still seem to
> be implemented in write.c. Of course I could have missed something.
^^^^^^^
Correction: print.c
next prev parent reply other threads:[~2022-03-12 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 1:26 Question about an error with ports Zelphir Kaltstahl
2022-03-10 15:05 ` Olivier Dion via General Guile related discussions
2022-03-10 22:32 ` Zelphir Kaltstahl
2022-03-10 23:46 ` Olivier Dion via General Guile related discussions
2022-03-11 12:05 ` Chris Vine
2022-03-11 14:58 ` Olivier Dion via General Guile related discussions
2022-03-11 17:26 ` Chris Vine
2022-03-11 17:47 ` Olivier Dion via General Guile related discussions
2022-03-11 18:13 ` Chris Vine
2022-03-11 19:48 ` Maxime Devos
2022-03-11 19:49 ` Maxime Devos
2022-03-12 0:10 ` Chris Vine
2022-03-12 0:27 ` Chris Vine [this message]
2022-03-11 12:11 ` Maxime Devos
2022-03-11 15:06 ` Olivier Dion via General Guile related discussions
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220312002717.2cd16e1974f90136f8ed3dfc@gmail.com \
--to=vine24683579@gmail.com \
--cc=guile-user@gnu.org \
/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.
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).