Re: Better block literals
7845330-4/[email protected]
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <[email protected]> |
> From what I understand, You got it. But indenting the block as you suggest, I must avoid. That was the point. So, back to the point. YAML cannot handle real literal blocks. It needs whitespace interpretation within literals. So try the line-count idea instead of terminators. There is already a document terminator ... so I don't understand your issues, but line counts also work. Every other data format uses a variation of one or the other. The actual buffers in RAM do the same: byte count or terminator. YAML is the outlier. You can also have character-count equivalent in addition to line-count. Most people would prefer line-count I think, but both are easy. Given the present YAML, what about just using two separate docs in the same disk file? Is that viable? The idea being to separate the block literal into a stand-alone stanza without indentation. --- fieldA: value fieldB: value ... --- nstringskey: |+ very long literal string etc. etc. etc. ... -- http://www.fastmail.fm - mmm... Fastmail... ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com