From: Brian I. <in...@tt...> - 2002-05-03 18:46:22
|
On 03/05/02 14:38 -0400, Clark C . Evans wrote: > | > | > - I fix the graph model to include keyed/series > | > | > in the distinctio > | > | > - We forget about (and remove from the spec) all of the cuteness > | > | > regarding the !seq transfer method and keyed (for sparse arrays). > | > | > - We introduce !sparse for sparse arrays if necessary. > | > | I'm perfectly agreeable to this. I always thought the "!seq {}" was a stupid > | pet trick anyway. Make it so. > > Cool. > > | PS If you ever think of a real world example, I'd be intrigued. > > Ok. Let's be imaginative. Suppose that I'm an employee of > Big Motor Co. and I'm writing an application to handle defects > at particular location in a steel casting for an engine. A > casting may have over 100 identifyable locations, often > numbered 0,...,100. To save space, I use a decide to use > a sparse array; and being a good programmer and following the > YAML specification, I use the {} trick. I disagree with this case. If you use the !seq trick, both Loaders will do the same thing. It's only when you create objects of type !http://bm.com/cast-defect that you might have an issue. My reply is that the owner of that class must make sure that both the Perl and Python implementations agree. Either both handle sparsity or both don't. Both can handle both (sparse and normal). See. It's the domain's issue, not ours. We just have to do the !seq/!sparse trick correctly. Next. Cheers, Brian |