External representation taylanbayirli@xxxxxx (10 Sep 2015 15:21 UTC)
Re: External representation taylanbayirli@xxxxxx (10 Sep 2015 15:22 UTC)
Re: External representation Arthur A. Gleckler (10 Sep 2015 15:24 UTC)
Re: External representation taylanbayirli@xxxxxx (10 Sep 2015 20:10 UTC)
Re: External representation Arthur A. Gleckler (10 Sep 2015 20:44 UTC)
Re: External representation taylanbayirli@xxxxxx (11 Sep 2015 07:36 UTC)
Re: External representation John Cowan (11 Sep 2015 13:04 UTC)
Re: External representation taylanbayirli@xxxxxx (11 Sep 2015 13:25 UTC)
Re: External representation Per Bothner (11 Sep 2015 14:05 UTC)
Re: External representation taylanbayirli@xxxxxx (11 Sep 2015 14:21 UTC)
Re: External representation Kevin Wortman (11 Sep 2015 19:10 UTC)
Re: External representation taylanbayirli@xxxxxx (11 Sep 2015 21:48 UTC)
Re: External representation Shiro Kawai (12 Sep 2015 02:04 UTC)
Re: External representation John Cowan (10 Sep 2015 16:30 UTC)
Re: External representation taylanbayirli@xxxxxx (10 Sep 2015 18:12 UTC)
Re: External representation John Cowan (10 Sep 2015 19:02 UTC)
Re: External representation Per Bothner (10 Sep 2015 21:25 UTC)
Re: External representation John Cowan (10 Sep 2015 21:52 UTC)

Re: External representation taylanbayirli@xxxxxx 11 Sep 2015 07:36 UTC

"Arthur A. Gleckler" <xxxxxx@speechcode.com> writes:

> On Sep 10, 2015 1:10 PM, "Taylan Ulrich Bayırlı/Kammer"
> <xxxxxx@gmail.com> wrote:
>
>> Do you think it would hinder adoption that the reader syntax is
>> mandatory, or lead to other problems?
>
> Yes, particularly since it disagrees with the other SRFI John
> mentioned.

I would say it doesn't really disagree with it, since that one seems to
be focused on extending the syntax of source code without touching
pure-data representation.

Still, I guess I'll make it optional, along with weak/ephemeral
hashtables, so there's still some utility of the SRFI for those who
don't like all of it.

Taylan