From: Justin Veilleux <terramorpha@cock.li>
To: guile-user@gnu.org
Subject: #:printer filed in language specification.
Date: Fri, 17 Sep 2021 18:50:17 -0400 [thread overview]
Message-ID: <66ede8b9-6e56-cb7a-28d2-825dc93ef8cd@cock.li> (raw)
Hello, everyone.
To familiarize myself with guile's compiler tower, I implemented a
lambda calculus interpreter using guile.
It works relatively well. However, I also wanted it to print a human
readable version of the procedures created. (It is hard to tell whether
#<procedure 1e39a38 (s)> is a correct church encoding of the number 3)
With a lot of fiddling, I managed to write a function that turns a
procedure into an S-expression.
However, when I tell guile to use it as a pretty printer using the
#:printer keyword, the repl doesn't actually use it. What can I do to
fix this ?
next reply other threads:[~2021-09-17 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 22:50 Justin Veilleux [this message]
2021-09-18 14:47 ` #:printer filed in language specification Maxime Devos
2021-09-18 15:24 ` Justin Veilleux
2021-09-19 12:11 ` Zelphir Kaltstahl
2021-09-19 12:24 ` Maxime Devos
2021-09-20 8:04 ` Zelphir Kaltstahl
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=66ede8b9-6e56-cb7a-28d2-825dc93ef8cd@cock.li \
--to=terramorpha@cock.li \
--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).