Re: [Yaml-core] A Clean Proposal Revisited

[trans. (T. Onoma) <tra...@ru...>]

On Tuesday 21 September 2004 04:00 pm, you wrote:
> Oren and I prefer #1, however, enough people spoke up on the list
> to keep the distinction between 23 and '23'.  Some decisions have
> to be made and be final.  This is one of them.

I know, if you recall, I was  one of those people. I felt the idea of #1 was 
right, but was against it only b/c I didn't have a simple way back if I 
wanted it. A simple TAG directive solves that.

> | > R4(.1) requires that by default
> | > there will be a difference between 23 and "23", without the need for
> | > directives.
> | >
> | > I appreciate the cleanliness of #1, but it just isn't going to happen.
> |
> | And the rest of it?
>
> Just beacuse the parser will report ? and ! doesn't mean your
> applications have to treat them the same.  See Tim's post about
> how to configure your parser, I'm sure Syck has, or will have
> a similar mechanism.

Well, that's not my point at all. My point was that the untagged nodes are the 
YAML types but with an implicit indication, not separate types. The current 
standing propsal makes them different and mixes in kind. It's fairly ugly and 
very redundant. Consider the information being passed from the parser:

  type, kind
  ----------
  ?, scalar
  !, scalar
  !, sequence
  !, mapping
  tag:yaml.org,2002:str, scalar
  tag:yaml.org,2002:map, mapping
  tag:yaml.org,2002:seq, sequence
  !mystr, scalar
  !mymap, mapping
  !myseq, sequence

Compared to what I am proposing:

  type, implicit-flag
  --------------------------
  tag:yaml.org,2002:str, ?
  tag:yaml.org,2002:map, ?
  tag:yaml.org,2002:seq, ?
  tag:yaml.org,2002:str, !
  tag:yaml.org,2002:map, !
  tag:yaml.org,2002:seq, !
  !mystr, !
  !mymap, !
  !myseq, !

> But, we've got closure on this issue. It may not be the perfect
> solution; but given what we know at this time, it is a local
> maximum, and its important we continue with implementation.

Sure.

T.