On Sun, Mar 22, 2009 at 9:49 PM, Johan Hake <[email protected]> wrote: > Hello! > > Now that we have removed the read/write Function from/to file in the c++ > interface we have to change the python interface too. I haven't done this > yet. > > But before I do this I wonder if we _should_ add some logic in the python > interface that allow the functionality we previously had, i.e., writing and > reading Function to and from a file directly? > > We could perhaps extend the <</>> operator in the c++ wrapper so an xml file > with the vector, mesh and the FiniteElement signature will be saved in. Then > in python we can jit compile the FE, when reading the file. We should > probably have one constructor taking only the xml file but also one taking an > optional mesh argument, preventing the problems with duplications of meshes. > > Would this be desirable? I know Ola have made some thoughts about this.
Only for toy programs. We still need to share the function spaces between functions. Martin _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
