Comments and favors on YAML 1.2 spec 2009-07-21
Osamu TAKEUCHI <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <[email protected]> |
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 While the spec allows the omission of the final comment line break (Sect. 6.6), it does not allow the omission of the final line break in a plain / literal / folded style text. Consequently, YAML stream "abc" can not be accepted by the YAML parser while "abc\n" can. If this is intended, please clarify it in the text. Otherwise, adding /* End of File */ in the b-chomped-last rule seems to allow such an input safely. I feel this is more human friendly. 2. Distinguish non-content white spaces from as-space white spaces The BNF syntax distinguishes whether a line break is non-content, as-space or as-line-feed. But it does not distinguish whether a white space is non-content or as-space. I felt it is helpful to distinguish it in the BNF rules. 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, is not allowed anywhere in a YAML 1.2 stream. If so, please add some comment on this issue. Thanks for taking time to think of my posts. Osamu Takeuchi ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july