Re: Example 6.23 and 6.24 in YAML 1.2 spec dated 2009-07-21

Osamu TAKEUCHI <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <[email protected]>
Oren,

> On Thu, 2009-09-03 at 04:05 +0900, Osamu TAKEUCHI wrote: 
>> Dear the YAML spec writers,
>>
>> Regarding to the YAML 1.2 spec dated 2009-07-21:
>>
>> I think it is clearer to have separated rules for the block 
>> collection with properties and that without properties.
>> The following is my suggestion.
>>
>> s-l+block-collection(n,c) ::= s-l+block-collection-with-properties(n,c)
>>                             | s-l+block-collection-without-properties(n,c)
>>
>> s-l+block-collection-with-properties(n,c) ::= 
>>              ( s-separate(n+1,c) c-ns-properties(n+1,c) )?
>>              s-l-comments
>>              s-l+block-collection-without-properties(n,c)
>>
>> s-l+block-collection-without-properties(n,c) ::= 
>>                    l+block-sequence(seq-spaces(n,c)) 
>>                  | l+block-mapping(n) 
> 
> That _arguably_ may be better - but at this point we are only fixing
> errors (even if these of omission) and not continuing to re-polish the
> spec. "All good things come to an end; so do the bad things" :-)

Note the following description in Chapt. 4:

> Optional (?), zero-or-more (*) and one-or-more (+) patterns are 
> always expected to match as much of the input as possible. 

If you think the current spec accepts the example 6.23 and 6.24,
please clarify how.

For me, some correction seems necessary.

Best,
Osamu TAKEUCHI

------------------------------------------------------------------------------
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.