> Any affect on tests at all? > If it's heckled (intentionally modified to produce incorrect results) tests fail, so we know it's being used. As is, the tests pass. I didn't explore the extent of our present yaml test coverage, but there is some. (I did this patch last fall & haven't revisited it since except to dust it off & send it).
> >> +class Object >> + def to_yaml >> + p [self,:to_yaml,ZAML.dump(self)] >> > > I assume this should be removed. > Doh. Yes. +# >> +# ZAML -- A partial replacement for YAML, writen with speed and code >> clarity >> +# in mind. ZAML fixes one YAML bug (loading Exceptions) and >> provides >> +# a replacement for YAML.dump() unimaginatively called >> ZAML.dump(), >> +# which is faster on all known cases and an order of magnitude >> faster >> +# with complex structures. >> +# >> +# http://github.com/hallettj/zaml >> +# >> +# Authors: Markus Roberts, Jesse Hallett, Ian McIntosh, Igal Koshevoy, >> Simon Chiang >> +# >> > > Is there a license for this? GPL 3+ & MIT; 95+% of the code is mine if we need something else for some reason (e.g. GPL 2+). -- Markus -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
