I just got off the phone with Brian I. about all these changes.
I had some issues, but he convinced me on every point. I'm
very happy with these ideas, especially since they are similar
to stuff I was about to propose anyway. :)
On Wed, Jul 18, 2001 at 01:15:44AM -0700, Brian Ingerson wrote:
> 1) No tabs allowed in indenting. It is invalid YAML.
> 2) All indenting is mandatory 4 spaces.
I was a bit worried about this since tabs are such a common
way of indenting things. However we can avoid the endless
problems python et al. have with mixed tabs and spaces if we
get strict now.
Any programmer's editor should be able to expand tabs.
My one remaining concern is for nonprogrammers using
Notepad or Word. At a 4-level indent, counting out 16
spaces might be be tedious and error-prone.
However, at this time I think it's more important to get
implementations out in the field. Then we'll see what the
Deep indents may turn out to be rare in hand-edited files.
> 3) Blocks are represented like:
I like all these changes. Solves most of the problems *and* is
more intuitive and flexible.
> 4) Top production is a list of maps, but the list separator is "---\n"
> instead of "\n".
> 5) Multi-line map keys may only be quoted (and possibly escaped). No
> block mode allowed.
Neil Kandalgaonkar, ActiveState
ASPN - ActiveState Programmer Network