public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Pretty-printing records
Date: Tue, 01 Jan 2019 20:42:00 -0000	[thread overview]
Message-ID: <CABgWrqpGUdTpeK2eGV3641FXwHsegEa2jxzwfv-N=JYkoj3J7w@mail.gmail.com> (raw)
In-Reply-To: <6d13d508-1739-191f-5c40-2a8b24be264f@bothner.com>

Ahh, I just tested out the change. Very cool.

The old output:

    #|kawa:2|# (import (mit-scheme pathname))
    #|kawa:3|# (define path2 (->pathname "/usr/morris"))
    #|kawa:4|# path2
    mit-scheme.pathname$pathname@7b53b1ad

The new output

    #|kawa:4|# path2
    #<<pathname> device: unspecific directory: (absolute usr) name:
morris type: false version: unspecific>

Like you wrote, it's not exactly pretty-printing, but at least the
fields of the record are visible in the REPL now.

I know that in Scheme48, they have a DEFINE-RECORD-DISCLOSER form, it
looks like this:
http://s48.org/1.9.2/manual/manual-Z-H-6.html#node_sec_5.9

In MIT Scheme, their DEFINE-STRUCTURE form is more complicated, and
includes a PRINT-PROCEDURE option.

SRFI 9 records are very close to S48 records, maybe
DEFINE-RECORD-DISCLOSER is the way to go?

Thanks and happy new year!


Duncan.

On Tue, Jan 1, 2019 at 3:05 PM Per Bothner <per@bothner.com> wrote:
>
> On 12/31/18 7:32 PM, Per Bothner wrote:
> > Something similar could be done for SRFI-9 records, but it might take some changes
> > in how they are implemented, to better support introspection.  Using Java
> > reflection is possible, though maybe expensive.
>
> It turned out to be relatively simple to change SRFI-9 records so they
> extend kawa.lang.Record.  This fixes printing of the resulting records.
>
> This doesn't accomplish pretty-printing, but that should also be fairly simple.
> Probably best by having kawa.lang.Record implement gnu.kawa.format.Printable.
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/



-- 
Duncan.

  reply	other threads:[~2019-01-01 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  2:59 Duncan Mak
2019-01-01  3:33 ` Per Bothner
2019-01-01 20:05   ` Per Bothner
2019-01-01 20:42     ` Duncan Mak [this message]
2019-01-01 21:37       ` Per Bothner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABgWrqpGUdTpeK2eGV3641FXwHsegEa2jxzwfv-N=JYkoj3J7w@mail.gmail.com' \
    --to=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.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.
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).