I agree with everything below implicitly. (I proposed single spacing in
the first place, and I still think it rocks) I am just trying to provide
us with an alternative path if we need one. The proposal I put forth
does that nicely. It simply says that if there is no header, the
application is responsible for supplying the directives. This makes a
lot of sense. In the short term, nothing changes because there are no
directives to play with. If and when we add directives, we'll want to be
able to use them in headerless documents.
I just read the spec. There is currently no wording to how a parser must act
on a headerless stream. We could leave it that way, keeping in mind my
potential future intent, or we could make the wording explicit now.
On 21/12/01 17:37 -0500, Clark C . Evans wrote:
> Over the last month I've grown very much accustom to the
> single space indenting. So much that I don't want to turn back.
> That said, I tried indenting my Python code to four spaces, and
> it didn't look as good. Let me postulate.
> Most progamming language have multiple things going
> on in a single line, and expressions can spill over to
> the next line. Furthermore, the "branch" nodes typically
> have an branch expression on them, which further serves
> to clutter things up. In these cases, a single space
> just doesn't cut it.
> However, YAML is different. In YAML branches are typically
> very simple, sometimes just a stand-alone "-" or a "key:"
> with nothing following it. Thus, it is easy to see branches.
> Secondly, YAML constructs are simpler, only one thing is
> going on on any given line. And if the construct is multi-line,
> we _force_ it to start on the following line; clearly showing
> the hierarchy. It is due to these characteristcs that
> YAML is _very_ readable with one space indentation where
> a normal programming language would be convoluted.
> Thus, most of our initial users, familar with programming
> languages with complicated branching constructs and multi-line
> possibilities will take their assumed background and insist
> that single line spacing is unworkable. We must simply
> remind those users that the problem domain is different,
> there are different constraints imposed by YAML, and that
> these limitations make YAML much more readable with single
> space indentation than one would extrapolate from experience
> with programming languages.
> Simply put, in programming languages, multiple space indenting
> is needed since the contstructs of the language can be very
> complicated. In YAML, we only need a single space indent since
> our constructs are so much simpler.
> Kind Regards,
> Clark C. Evans Axista, Inc.
> http://www.axista.com 800.926.5525
> XCOLLA Collaborative Project Management Software