[petsc-dev] not everything belongs in PETSc; thread/task management etc

[Jed Brown]

Matthew Knepley <knepley at gmail.com> writes:
> My questions would be:
>
>  - does it help development if it is independent
>
>  - does it help adoption if it is independent
>
> I am not sure the answer to either of these is yes.

We have to interoperate "easily" with other systems regardless.  If it's
independent, I think it's a tough case to put context into MPI_Comm
attributes because many other projects don't like to depend on MPI so
deeply.  Otherwise, I don't think that being part of PETSc makes
anything easier except for consistency of the build process.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140926/7d35ebe8/attachment.sig>