Anders Logg wrote: > This looks a like a non-optimal solution. Are you returning the mesh > by value? That will lead to creation of a temporary and copying of the > entire refined mesh. >
So they used say ;). Apparently modern compilers are all clever enough not to. Garth > What if we have > > FooRefinement::refine(old_mesh, new_mesh) > > or similar? > > -- > Anders > > > On Sun, Feb 07, 2010 at 10:13:15PM -0000, [email protected] wrote: >> ------------------------------------------------------------ >> revno: 4461 >> committer: Garth N. Wells <[email protected]> >> branch nick: dolfin-nompi >> timestamp: Sun 2010-02-07 21:53:42 +0000 >> message: >> Work on mesh refinement interface. >> >> Do not overwrite old mesh inside refinement functions belonging to static >> classes. Need to keep old mesh to peform update in adapative methods, so >> previously the mesh had to be copied before calling refine(...). >> modified: > _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : [email protected] Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
