On 28/10/01 08:58 +0200, Oren Ben-Kiki wrote:
> At any rate, Brian wrote:
> > YAML syntax. Strings starting with '-', or containing ':' will also need
> > be quoted. See my pain?
> Well, unquoted scalars also can't start with indicators or quotes, so I
> don't see this as a big deal. One can always quote them, after all. Just
> don't define an implicit type starting with '--' or '#'.
> Oops, wait a minute, we already did: the '#' key for "in the model"
> # This is a throwaway comment,
> # But what about this:
> # : Is this a key/pair value?
> after :
> all : this is
> # : A comment
This is easily solvable by the same rule you just stated above. Any key
starting with '#' will need to be quoted. Right? So comments *will* work.
> # This is a throwaway comment.
> key : value
> // : By convention, this is a comment
Seems reasonable. I'm not entirely sure about round-tripping comments
yet. No language has "comment" as an in memory data type. And YAML *is*
a data serialization language primarily.
> Also, about the sparse list syntax. I find:
> -55 fifty five
> As opposed to:
> - 55 fifty five
> To be too subtle a difference.
> I'd much rather have an explicit indicator
> there. How about this: if we use '//' instead of '#' for in-the-model
> comments, how about using '#' for indices:
> - #55 fifty five
> After all, '#' is also called a "number sign", right? Note there's no chance
> of confusion with throwaway comments because there's always a preceding '-'.
> Also, making '#' an indicator will remove the temptation for people to
> define an implicit type starting with it, so we'll avoid any possible
> confusion with throwaway comments forever.
'#' is reasonable. But I think I like a grouping operator in this
instance. Like '', '()', or '<>'. And using one of these, does not
preclude us from also using it for something else in the future (as you
have shown above with '#'). I prefer:
since most languages use square brackets for indices of arrays.
> About IRC etc.: I have it installed on both home and work machines. Of
> course there's the time zone problem, and IRC doesn't give you logs of the
> conversation (AFAIK).
I could write an IRC robot to log everything and email the result to the
I am setting up a test system for YAML that will also serve as an
online dictionary of YAML examples. For each example I'll have a YAML
file, a Perl script that can create that file using YAML.pm, and an
equivalent serializtion using Perl's Data::Dumper module (which is
When I turn this into a website, I'll let you know.