On Thu, 21 Aug 2003, jbritt@xxxxxxxxxxxx wrote:
> All the YAML examples I've seen are quite small. With a YAML file of,
> say, 200-1000 lines, it may be more difficulty to quickly scan a file
> and see how items nest or how far something needs to be indented. As
> with Python code, cutting and pasting can be a problem because of
There is a way in YAML to "outdent" things and tell it on the header
line to treat the next chunk as being indented by X, but I forget
the details. I consider the use of whitespace for this to be
suboptimal. But the choice is difficult: aversion to (lisp(style))
and <style>xml</style> is as common as aversion to python style.
> indentation. Whereas finding the end tag of an XML element is quite
> easy, and most decent editors can be set to highlight mismatched tags.
> So, YAML may be well suited for configuration files, and while it may be
> quite readable I'm not so sure large YAML files lend thmeselves to easy
> editing.
There is ONX
http://www.seairth.com/web/onx/
but I don't know who uses it, and other alternatives are listed
at
http://www.pault.com/pault/pxml/xmlalternatives.html
But these would need implementing in ruby.
>
> Overall it looks to be largely read-only, so using an editable format
> for data storage may be a non-issue.
If the primary source is RDoc then that is editable.
>
> James
>
Hugh
|
