On Thu, 22 Jan 2009, Tim Kroeger wrote:
> I see. My idea is, since the vector is anyway cleared and re-initialized in > operator=, why not use PETSc's VecDuplicate() function. Can that be sufficient? The manual page says VecDuplicate doesn't copy the vector, just allocates storage for it. I think a VecDuplicate followed by a VecCopy should do the trick, and I'll try that out on the examples and on our few unit tests today if I find time, but this is why I wanted other people looking at the problem; I'm not familiar enough with PETSc's APIs and I'm not a fan of trial-and-error coding and debugging. --- Roy ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
