From: Brian I. <in...@tt...> - 2001-12-21 05:22:42
|
Hi fellas, I've been thinking over the use case of YAML for config files. Our current format is optimal for most data serialization and data dumping. But for config files, I might be a little adverse towards adopting YAML, if I didn't happen to be one its primary founders. It's not a hard sell per se, but it's not a slam dunk either. Here is what I would want out of YAML for configs: 1) No YAML header. 2) The ability to throw away blank lines. 3) More lax indentation rules A) 2, 3 or 4 space indentation B) Tab to nearest eight C) Varying indentation within a document. Here are the things in YAML that aren't really needed for config: 1) YAML Header 2) Multi-line string 3) Properties: (explicit transfer, alias, anchor) --- So I've been thinking if we should reserve a headerless YAML document for such a use case. It's really the only time where requiring a header would be a bad thing. I just wanted to throw this out for discussion. Cheers, Brian PS Got my first bug reports for YAML.pm :) |