On 05-09-12 14:12, David A. Wheeler wrote:
svanleent:
From a pragmatic side, wouldn't it be better to just have a marker like
#!curly-infix. The number 105 doesn't say much when reading the code,
which is the whole reason for the existence of curly-infixing.
There are advantages either
David,
From a pragmatic side, wouldn't it be better to just have a marker like
#!curly-infix. The number 105 doesn't say much when reading the code,
which is the whole reason for the existence of curly-infixing.
Also, a file extension might change the folding mode. This could by
something
svanleent:
From a pragmatic side, wouldn't it be better to just have a marker like
#!curly-infix. The number 105 doesn't say much when reading the code,
which is the whole reason for the existence of curly-infixing.
There are advantages either direction. I agree with you on the advantage
Hi David,
David A. Wheeler dwhee...@dwheeler.com skribis:
Guile support for curly-infix-expressions is very important to me.
Yet obviously guile has different semantics for #!, namely, #!...!#.
Clearly #!srfi-105 could be handled by a special case, but could
people live with that? I even
Help! I'm currently drafting SRFI-105, curly-infix-expressions:
http://srfi.schemers.org/srfi-105/
and trying to please everyone (ha!).
Can you tell me if the most recent draft is something guile could live with?
In particular, since SRFI-105 is a reader modification, some comments indicated
