Arne can best give the wisp answer, but here is what I would expect:
1.:
foo bar
. aaa bbb ccc
. ddd eee
=>
(foo bar aaa bbb ccc ddd eee)
2.:
foo bar
. aaa bbb . ccc
. ddd eee
Error. Period after leading period.
Perhaps more interestingly, I would expect this:
foo bar
aaa bbb ccc
. ddd eee fff
ggg hhh
=>
(foo bar (aaa bbb ccc) ddd eee fff (ggg hhh))
On November 28, 2014 5:59:14 AM EST, "Jörg F. Wittenberger"
<joerg.wittenber...@softeyes.net> wrote:
>Am 27.11.2014 um 20:03 schrieb Arne Babenhauserheide:
>> Am Donnerstag, 27. November 2014, 08:47:49 schrieb David A. Wheeler:
>>>> However within "normal" s-expressions or neotheric expressions I'd
>have
>>> second thoughts. How would this be parsed?:
>>>
>>>> foo bar
>>>> . aaa . bbb ccc
>>>
>>> I agree, that should be an error. It doesn't really make any sense
>to me either. I expect this would continue to be ok:
>>>
>>> aaa bbb . ccc
>>> =>
>>> (aaa bbb . ccc)
>>>
>>> And the following would still be an error:
>>> aaa bbb . ccc ddd
>
>+1
>
>>
>> That’s also what wisp does: The leading dot is interpreted as
>> continuation if it’s the first character in a line in
>> indentation-sensitive code.
>>
>> It would be cool to see sweet and wisp move closer together here!
>
>+1
>
>How does wisp deal with these?
>
>1.:
>
>foo bar
> . aaa bbb ccc
> . ddd eee
>
>2.:
>
>foo bar
> . aaa bbb . ccc
> . ddd eee
--- David A.Wheeler
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss
