On May 9 2014, John Cowan wrote:
>David A. Wheeler scripsit:
>
>> This would mean that {* x *} would be interpreted *differently* by a
>> curly-infix reader (or a neoteric reader) compared to a sweet-expression
>> reader.
>
>I think that's a killer.
One could also argue that there are three tokens effecting whitespace
handling: (, { and {*
{* is only valid in sweet as <* is - as required by spec. It shifts to 0
indent.
{ shifts to curly. ( to noteric.
I'd say this is a fairly consistent and clear set of rules.
Frankly, I'd expect a dev to be a quite advanced one until the need to write
{* x -}
and want an infix operator "x" applied to * and -. By that time the dev
should easily see that in whitespace mode {* is a marker and not the begin
of a curly expr and figure a space would help. After all neoteric rule have
taught the lesses to look twice for spaces.
>
>Frankly, this is what CDATA sections were made for. Wrap your Lisp
>code in "<![CDATA[" and "]]>" brackets, and < is no longer magic.
>(Note that > is never magic, though there is an escape for it anyway.)
>
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Readable-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/readable-discuss
