From: Brian I. <in...@tt...> - 2001-11-13 05:46:00
|
On 12/11/01 22:49 +0200, Oren Ben-Kiki wrote: > What is standing between us and a spec at this point: > > - Scalar forms. I summerized the new proposal, which requires 5 separate > scalar types. We can go with it, keep things as they are today, or try to > simplify it further. I like the syntax & semantics of these 5 types *exactly* as you posted. > > - References. OK, Alias != Pointer. Fine. Now, how does YAML serialize > "\$a->[0]"? I posted an example showing why this is hard (and how > Data::Dumper gets it wrong). I also showed how it can be done given some > creative use of the '!ref' type. We need to decide on this. I'll handle Perl with what we have. Enough said. > - Info model. If Clark comes up with a reformulation of the info model that > JAP can grok, I'd be happy to include it into the spec, and more than happy > to re-work the simpler productions :-) OK > - Pipelining. Let's leave it out for now - right? I just want to know how to serialize: print YAML->Emit(bless [], "Foo::Bar"); --- !seq !!Foo::Bar # This is an empty seq --- !seq!!Foo::Bar # This is an empty seq --- !!Foo::Bar!seq # This is an empty seq --- !!Foo::Bar=seq # This is an empty seq I can always get away with the last one as a trick, since '=' would never be in a Perl class name. > - YPATH, APIs. Let's not go there yet. I couldn't if I wanted to. > Did I miss anything? > > At any rate, we are very close. Let's finish it. Yaml Baby, Yeah! Hey, final note. What's going to keep us from mucking around with it when it's finished? I think we should all agree on some kind of frozen period, where nobody is allow to suggest major changes until we get a few implementations completed and though an alpha test phase. Cheers, Brian |