Alan Manuel Gloria:
> We also have to be extra-careful here: ! is whitespace only in
> sweet-expressions. Here's another failing counterexample:
>
> define foo(x y)
> ! #|Okay, so this line
> ! does one thing
> ! |#
> ! do-one-thing x y
>
> The above example fails because neoteric does *not* treat ! as whitespace.
True, but as you noted, ;-comments solve the problem nicely:
define foo(x y)
; ! Okay, so this line
; ! does one thing
; !
! do-one-thing x y
I think ;-comments become far more useful when indentation is semantically
meaningful; it's now a lot easier to find where an expression begins and ends.
Also, we already have a similar issue with {...} and !, since this doesn't work
either:
; BAD:
define foo(x y)
! calculate { a +
! b}
! do-one-thing x y
The modified # semantics I'm proposing would make the example above "not work",
but it would be clearly *defined* as "not working". Furthermore, users of
#|...|# at the top level (outside an expression) or within a line would see no
change at all:
#| Comments...
#|
define ...
define x #| comments... |# 5
I think that the handling of #|...|# in the other cases is really an edge case;
few people will notice all they complicated gyrations we go through to make
that work.
--- David A. Wheeler
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Readable-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/readable-discuss
