Re: [Yaml-core] Fixing bools in 1.0 and 1.1

[<in...@tt...>]

On 07/06/06 08:57 -0600, why the lucky stiff wrote:
> Well, so, I can't remember where we stand with the 'y' and 'n' booleans.  Syck
> hasn't supported them because they conflict with other parts of the spec.  (See
> examples 2.21 and 2.24 in either version.)
> 
> Which of the following works?
> 
>   true: y
>   false: n
> 
>   x: 73
>   y: 129

FWIW, I think the y/n boolean implicits are a little bit cute and could
be removed.

But there are a few points I would like to remind people of:

1) The implicit type repository is not part of the spec. So it follows
   that they have no relation to 1.1 or 1.2.
2) The types are really a recommendation. Domain specific YAML
   processors are free to define their own implicits.
3) The default of a generic YAML processor should be to treat all
   scalars as strings.
4) A good generic processor should not only have an interface to
   turn implicits on and off, but also to turn each specific
   implicit on and off.

In my opinion the type repository definition is a little backwards. It
/should/ be the set of types commonly supported by the implementations.
But that creates a chicken/egg problem, so it is a decent starting
point. The repository is a journey not a destination. :)

Cheers, Ingy