Re: Question on s-l+flow-in-block

Addendum: Actually, if b-non-content is changed to:
  b-break | /* End of file */
...then perhaps this would be fixed without changing other behavior,
since this only happens when a stream stops without a trailing break.

On Sat, Apr 25, 2009 at 9:44 AM, Joshua Choi <[email protected]> wrote:
> To the YAML 1.2 spec writers,
>
> In the current draft, rule #196, s-l+flow-in-block, requires
> s-l-comments at the end. s-l-comments in turn requires either
> s-b-comment or the start of the line, and s-b-comment requires
> b-non-content. The required presence of b-non-content, which is
> equivalent to b-break, means the following two streams are invalid if
> they do not end with a break:
>
> I am a document. This stream is going to end abruptly with NO line break.
>
> I am a document. # This stream is still invalid if this stream halts
> without a break.
>
> ...while both of them are valid if they do end with breaks.
>
> Perhaps the s-l-comments in s-l+flow-in-block should be marked
> optional, or at least something should be changed to make
> b-non-content optional in the end it's not at the beginning of a line.
>
> Sincerely,
> Joshua Choi
>

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects