i am storing most of my stuff in yaml these days and using ruby, but it would be GREAT if i could use php with yaml too

last time i tried (some php yaml binding) it was so incredibly slow, that parsing it with a quick-built php parser was faster :/

Reporting Bugs- Please create a ticket (or tickets) in the Horde Framework Packages queue on http://bugs.horde.org/. Our main goal is compatibility with the YAML spec, but we’ll certainly resolve differences with syck where they’re our fault (which is entirely possible).

Where can we report bugs / inconsistencies Horde_Yaml? I’m assuming that since the library prefers Syck if it is available that that implies Syck is the defacto standard of YAML to implement. In that case I’ve so-far noticed three differences between Syck and Horde_Yaml. I think it is important that differences are either eliminated or at least emulated since otherwise it makes little sense to allow switching parsers since doing so can lead to behavioral changes.

1) An empty keyed element must be terminated by a newline in Syck if it is the last line in the file. Horde_Yaml does not require this.

2) Horde_Yaml parses unquoted text strings as text even if they contain (but do not start) with a hash marker (ie: a brace): Syck does not.

eg:
foo: This fails in Syck { but not in Horde_Yaml.
bar: “This works in both { Syck and Horde_Yaml.”
foobar: {this fails everywhere

3) Syck seems to require whitespace after a key, at least for unqouted data whereas Horde_Yaml is just as happy without the whitespace.

eg:
foo:this fails in Syck but works in Horde_Yaml

Thanks for the good work!