SRFI 243: Unreadable Objects Arthur A. Gleckler (20 Nov 2022 23:39 UTC)
Re: SRFI 243: Unreadable Objects Marc Nieper-Wißkirchen (21 Nov 2022 13:00 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 13:39 UTC)
Re: SRFI 243: Unreadable Objects Marc Nieper-Wißkirchen (21 Nov 2022 13:47 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 14:39 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 14:59 UTC)
Re: SRFI 243: Unreadable Objects Marc Nieper-Wißkirchen (21 Nov 2022 15:51 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 16:04 UTC)
Re: SRFI 243: Unreadable Objects Marc Nieper-Wißkirchen (21 Nov 2022 16:19 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 16:32 UTC)
Re: SRFI 243: Unreadable Objects Marc Nieper-Wißkirchen (21 Nov 2022 16:50 UTC)
Re: SRFI 243: Unreadable Objects Lassi Kortela (21 Nov 2022 17:01 UTC)

Re: SRFI 243: Unreadable Objects Lassi Kortela 21 Nov 2022 14:59 UTC

>> You haven't answered the point about the XXX#YYY syntax, have you?
>
> I don't understand it.

Were you referring to the examples in the SRFI?

Chicken
#<procedure (scheme#write x . rest)>
#<procedure (tween#quadratic-ease direction123 percent124)>

scheme#write and tween#quadratic-ease are valid symbols in Chicken.

 > (symbol->string 'scheme#write)
"scheme#write"

Gambit
#<procedure #2>
#<procedure #3 fold>
#<promise #6>
#<output-port #2 (stdout)>

The #<number> syntax is valid in Gambit. It refers to an object in the
same process by its "serial number", an auto-incrementing integer.

As you noticed, there is some prior art of using angle brackets
inconsistently.

Gauche
#<subr #<<parameter> 0x102ae8800>>

I'll add remarks about these to the next draft of the SRFI.