[Paraview] Where do I send Xdmf bugs/patches?

Dominik Szczerba dominik at itis.ethz.ch
Thu Dec 15 12:50:52 EST 2011


> General consensus was that the Xdmf library was not very consistent in the way it was written -specifically when XdmfGeometry/Topology/other objects were created, some sub-objects were owned/parented and others simply referenced and when complex hierarchies of these objects were being used (as it typical in something like the vtk-reader/writer classes), it because difficult to manage things well and cleanly and know who was responsible for deleting things. leading to a lot of crashes and memory leaks if you got it wrong (and quite a lot of duplicated checks on objects too, but that's an aside).
>
> The Xmdf chaps have completely rewritten the library using a much nicer C++ type approach using smartpointers etc and this means the API has changed significantly. The XML part remains essentially the same.
>
> I would like to stop using the rather crufty Xdmfs in paraview (which you keep finding bugs in - and so do we - and nobody is supporting) and instead incorporate the new Xdmf into paraview (via the reader).

Sounds like a plan. Where do I start? I can directly try to integrate
it into my project and shower you with bug reports and perhaps a few
patches...

Dominik


More information about the ParaView mailing list