Re: Comments and favors on YAML 1.2 spec 2009-07-21

Oren Ben-Kiki <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <1254288744.5043.39.camel@nero>
On Thu, 2009-09-03 at 04:21 +0900, Osamu TAKEUCHI wrote: 
> Dear the YAML spec writers,
> 
> The rest are less important comments or favors regarding to 
> the YAML 1.2 spec dated 2009-07-21.
> 
> 1. Omission of line break at the end of YAML stream

Nice catch! I fixed this in the errata and the updated spec.

> 2. Distinguish non-content white spaces from as-space white spaces

Nice idea, but that would require a major renaming of productions. I
looked over the existing ones and there's explicit text next to the
productions stating whether they are/not content (the names of the
productions containing them are also pretty clear). There are no cases
(that I saw) where we mix non-content spaces and content characters in
the same production without going through an clear intermediate
production. I think we can live with the current state, although again I
agree it may have been clearer to split the names at a lower level.

> 3. Form feed (#x0C) in YAML 1.2 stream
> 
> There is a note that "YAML 1.2 processors parsing a version 
> 1.1 document should therefore treat these line breaks as non-break 
> characters, with an appropriate warning" in Sect. 5.4. But it 
> seems that the form feed (#x0C), which was a line break in YAML 1.1,

Form feed never was a valid line break character. Not in YAML 1.1 and
not ever.

Thanks for your review of the spec!

Oren Ben-Kiki


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.