Alan Manuel Gloria:
> Summarize (for any objections or comments, please reply to their own
> threads rather than here - this is just a summary thread to make it
> easier to write/modify specs/implementations):
Nice summary.
> 1. i.e. () {} [] postfixes anything: Accepted: Any expression can be
> postfixed with () {} [], with meaning as specified currently.
I've modified the [Solutions] Wiki page to reflect this, and the implementation
in git implements this.
> 2. i.e. "." as indentation: Modified slightly: "." in indentation is
> the same as space. Provisionally accepted, pending decision regarding
> "."-by-itself as GROUP.
Yes. I hesitate to implement this until we resolve GROUP/SLICE/SPLIT/ENLIST,
which may change it all anyway.
> 3. i.e. GROUP, SPLICE, SPLIT, END, ENLIST: discussion heavily on-going
This is the big one, discussions ongoing.
> 4. i.e. FORMAL parser spec: Some formal parser spec is already
> existing - it has recent discussion #1 #6 and #7 integrated, but not
> much else.
GROUP/SLICE/SPLIT/ENLISTwill heavily impact this, too.
> 5. i.e. QUOTE whitespace: discussion on-going.
> 6. i.e. blank line ENDS expression: Accepted.
Yes. This is implemented in git.
> 7. i.e. indent at top level: Accepted: indentation at the top-level
> DISABLES indentation processing.
Yes. This is implemented in git.
--- 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
