[petsc-users] Redo PetscOptions From Commandline

[Jed Brown]

Dmitry Karpeev <karpeev at mcs.anl.gov> writes:

> On Fri, Apr 5, 2013 at 11:32 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>>
>> On Apr 5, 2013, at 10:18 AM, Dmitry Karpeev <karpeev at mcs.anl.gov> wrote:
>>
>> > Should PetscInitialize() take a comm argument, then?
>>
>>    No, this is such an uncommon case that it shouldn't be exposed to
>> everyone.
>
> It seems to me that the burden on the user is fairly small -- the
> boilerplate code becomes
> PetscInitialize(MPI_COMM_WORLD) instead of PetscInitialize().  From the
> library design
> perspective, making it more general by taking an initialization parameter
> also sounds (to me)
> like the right thing to do.

Users have always been able to set PETSC_COMM_WORLD _before_ calling
PetscInitialize().  Adding another parameter is not necessary or desirable.