I posted about "(.)" and friends.

John Cowan:
> I say, don't spend a single moment getting that to work.  If anyone wants
> such an identifier, |.| will do perfectly well for them, and nothing else
> can be even vaguely portable.  I expect systems that treat . as an identifier
> do so because it falls out of some more general behavior, not because their
> implementers think it's a significant special case.

Fair point. You're absolutely right that there are bigger fish to fry.

So intend to focus on two areas:
1. Extending "#" handling.
2. Add a bunch to tests to really give the Scheme implementation a workout.
    (I'd like help here especially!)


Here's what I plan to add support for... any strong objections?:
1. #!DATUM, e.g., #!sweet, #!fold-case
2. "#!"+space, per SRFI-22.
3. "#!"+ slash-or-dot matching to !#, matching guile + clisp + some others
4. #u8(...)
I may fiddle with "." more later anyway, but that's after the more-important 
stuff is done.

I really want to give the code a workout.
If anyone wants to add more test cases to tests/sweet-testsuite ... or suggest 
some ...
that'd be awesome.  The format for a test case in tests/sweet-testsuite is:
CORRECT-VALUE-AS-S-EXPRESSION
SWEET-EXPRESSION
BLANK-LINE+

The advantage of this format is that even if Schemes vary in their output (and 
they do!),
we can still compare them char-by-char by reading in & writing out the 
s-expression first
and see if the two forms match.  It also makes it easy to see what you're 
testing,
because the expected answer and the question are adjacent.
The order is weird, but it's intentional; I expect reading s-expressions to be 
better
tested, so reading that first reduces the risk of misreading the expected 
answer.

--- David A. Wheeler

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to