Re: example 7.17 in YAML 1.2 spec 2009-07-21

On Thu, 2009-10-01 at 22:15 +0900, Osamu TAKEUCHI wrote:
> Do you really think the following?
> 
> {abc}      is obviously      { "abc" : null }
> {abc:}     is obviously      { "abc" : null }

Yes.

> {abc::}    might be read as  { "abc::" : null }\
> {abc:: a}  might be read as  { "abc::" <missing> "a" }

No. In my rule this would be an error. I never suggested this would be
what you show above.

> I do not see how you got this idea. :(
> Could you please explain why the last ":" character in "abc::" can 
> be read as a non indicator character?

No, I can't, because I think it should be an error.

> So, it was very surprizing for me that you suddenly decided not to 
> accept {abc:: } any more.

Yes, you got me there. I guess I'll have to back up from it, to maintain
compatibility :-(

> If you still think your new rule is superior,

I do, but not enough to break compatibility at this point :-(

So basically the new rule should be:

	/* Followed by (ns-char - c-flow-indicator) */

Instead of:

	/* Followed by ns-char */ (originally)
	/* Followed by ns-plain-char(c) */ (my rule)

This should be compatible with today's rule and do the (almost :-) right
thing. Sigh.

Have fun,

    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