[petsc-dev] Registration implicitly collective on COMM_WORLD

Jed Brown jedbrown at mcs.anl.gov
Tue Feb 5 07:28:00 CST 2013


On Mon, Feb 4, 2013 at 11:33 PM, Matthew Knepley <knepley at gmail.com> wrote:

> I see nothing wrong with those tradeoffs, its just beginning to sound
> complicated to me (like the Fortran stuff I can never remember).
> I would say, if you split the libraries, you have to do everything
> manually, and we just error out if you don't. That is easy to remember,
> and I think its harder for a user to have a working code that breaks
> mysteriously when one thing changes, like the comm.
>

Okay, is this what you have in mind?

1. XXInitializePackage() grows a comm argument
2. PetscFunctionListAdd() loses the comm argument
3. XXCreate() stops calling XXInitializePackage() and instead just asserts
XXPackageInitialized.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130205/9b86bfa5/attachment.html>


More information about the petsc-dev mailing list