The meaning of braces in various Schemes
John Cowan
(05 Sep 2012 06:24 UTC)
|
Re: The meaning of braces in various Schemes
David A. Wheeler
(05 Sep 2012 11:50 UTC)
|
Re: The meaning of braces in various Schemes
John Cowan
(05 Sep 2012 17:20 UTC)
|
Do we NEED a marker at all?
David A. Wheeler
(05 Sep 2012 13:25 UTC)
|
Re: Do we NEED a marker at all?
Jens Axel Søgaard
(05 Sep 2012 20:42 UTC)
|
Re: Do we NEED a marker at all?
Shiro Kawai
(06 Sep 2012 04:27 UTC)
|
Re: Do we NEED a marker at all?
Alan Manuel Gloria
(06 Sep 2012 12:36 UTC)
|
Re: Do we NEED a marker at all? David A. Wheeler (06 Sep 2012 13:07 UTC)
|
Re: Do we NEED a marker at all?
John Cowan
(06 Sep 2012 17:09 UTC)
|
Re: The meaning of braces in various Schemes
Donovan Kolbly
(07 Sep 2012 02:12 UTC)
|
Re: The meaning of braces in various Schemes
David A. Wheeler
(07 Sep 2012 03:41 UTC)
|
Re: Do we NEED a marker at all? David A. Wheeler 06 Sep 2012 13:07 UTC
Alan Manuel Gloria: > I personally dislike #!srfi-105, but I won't actively oppose it. I'm no fan of the marker either. But in my mind *adoption* is the measure that matters. If including a marker in the spec will "make the medicine go down" then we need to do it. Hopefully in 10 years this marker's support will be a fossil in old readers :-). > Perhaps we should just generally encourage SRFI-105-by-default Oh, definitely. > , but > suggest that writers of Scheme code should use #!srfi-105 explicitly > if portability across Scheme's is a concern. I think we should make an even weaker statement: "Applications may include this marker before using any curly-infix expressions, typically near the top of a file." If, as we hope, everyone implements it anyway, then applications won't need the marker for portability... so let's not hamstring them with the requirement that they MUST do it. --- David A. Wheeler