> > I want to reiterate a statement I made a while back that any alternative > input format really needs to support references. This is a good reason to > prefer Yaml over JSON. Yaml is a superset of JSON, but offers a more readily > human-readable layout, example: http://www.yaml.org/start.html > > The important feature here is that references can be reused so it becomes > possible to define multiple solver configurations, then use each one > (perhaps with local modifications) in multiple places or not at all. If you > just do plain JSON, it's essentially the same expressiveness as current > options files, albeit easier to manipulate from other languages. >
I agree with Jed. My plan was for Weston (the summer student) to link with libyaml (being a superset of JSON) and implement using the bridge pattern. A pretty generic plan, but at least a starting point. It would handle the features mentioned above. Sean -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110314/17804e74/attachment.html>
