From: Clark C . E. <cc...@cl...> - 2002-04-10 15:40:36
|
| That is, we can convert any YAML file to a block just by prefixing it with a | header line. I think this is pretty useful. I can't think of one use case where I'd need that ability and where indenting the two files would not be adequate. As for stream concatination, 99% of the use cases here will be merging log files / transaction journals. And in this case conversion to block is not part of the operation. Now, I do see the use case to include an entire YAML block or text files having -- as a map or seq value. However, the prefix hack doesn't help you here as it only applies at the document level. I claim that this isn't a useful feature beacuse it seems to be only useful in the cross product of two uncommon requirements: (a) converting a free-standing file into a *document* and not a leaf value, and (b) concatinating a stream of arbitrary files to get a sequence of YAML documents, each document with only one block. The whole reason for the --Unique block MIME hack was so that we could have top level scalars including "--" in column one. Before our flexible indenting we needed this hack... now with flexible indenting we don't. The cost vs benifit just isn't there, it is a high cost feature and the return on our investment is very little. To this effect, I had actually removed this feature from my "mental copy" of the YAML spec several months ago. Best, Clark |