[petsc-users] Any reason for API change: DMGetWorkArray()

[Matthew Knepley]

On Thu, Jan 10, 2019 at 5:31 PM Fande Kong <fdkong.jd at gmail.com> wrote:

> Thanks, Matt,
>
> And then what is the reason to remove PetscDataType? I am out of curiosity.
>

Occam's Razor: "one should not increase, beyond what is necessary, the
number of entities required to explain anything"

   Matt


> DMGetWorkArray is a little misleading. This may/might make people think
> the routine is related to MPI, but it does not have anything to do with MPI.
>
> Thanks,
>
> Fande,
>
> On Thu, Jan 10, 2019 at 3:22 PM Matthew Knepley <knepley at gmail.com> wrote:
>
>> We are trying to eliminate PetscDataType.
>>
>>   Matt
>>
>> On Thu, Jan 10, 2019 at 5:10 PM Fande Kong via petsc-users <
>> petsc-users at mcs.anl.gov> wrote:
>>
>>> Hi All,
>>>
>>> The second parameter is changed from PetscDataType to MPI_Datatype
>>> starting from PETSc-3.9.x
>>>
>>> Thanks,
>>>
>>> Fande Kong,
>>>
>>
>>
>> --
>> What most experimenters take for granted before they begin their
>> experiments is infinitely more interesting than any results to which their
>> experiments lead.
>> -- Norbert Wiener
>>
>> https://www.cse.buffalo.edu/~knepley/
>> <http://www.cse.buffalo.edu/~knepley/>
>>
>

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener

https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20190110/9c4a526f/attachment.html>