From: Ingy d. N. <in...@in...> - 2009-04-12 06:45:10
|
On Sun, Apr 12, 2009 at 1:22 AM, <78...@de...> wrote: > > From what I understand, > > You got it. > > But indenting the block as you suggest, I must avoid. Why must you avoid it? That was the > point. So, back to the point. > > YAML cannot handle real literal blocks. It needs whitespace > interpretation within literals. Correct. > 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. A count is imho a terrible idea. A human editing the scalar would easily make the whole document invalid. If it's a computer modifying it, it is just as easy to do indentation. > 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. Which, specifically, data formats are you referring to? XML and JSON have no such concept. These are the the closest formats to YAML. YAML is the *only* human readable cross programming language data serialization language, so it's already on outlier. ;) Cheers, Ingy 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 > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core > |