[petsc-dev] Remove calls to XXXReset() in XXXDestroy()
Barry Smith
bsmith at mcs.anl.gov
Fri May 13 10:03:47 CDT 2011
On May 13, 2011, at 8:26 AM, Lisandro Dalcin wrote:
> On 13 May 2011 15:50, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>
>> On May 13, 2011, at 7:01 AM, Lisandro Dalcin wrote:
>>
>>> On 13 May 2011 01:51, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>>>
>>>> On May 12, 2011, at 4:48 PM, Lisandro Dalcin wrote:
>>
>
> Again, this is because in PETSc you do not care about error recovery,
> you just MPI_Abort() in normal cases, or offer no guarantees about
> continuing execution after errors.
True.
> I'm not blaming PETSc for this, it
> is just like MPI-2!.
Yes, it is so totally baked into the MPI model so why would I try to do anything better with PETSc on top of MPI.
Ironically, while writing the MATLAB interface to PETSc I suddenly started to care, just like you care with python, because MATLAB users don't like to restart MATLAB every three minutes :-)
> BTW, Writing a REALLY good destructor in C++ is a
> pain. What's happens if an exception is thrown in the middle of object
> destruction and you still have things to delete[]?
Then I would argue that something is wrong with C++ in this regard.
Barry
>
>
> --
> Lisandro Dalcin
> ---------------
> CIMEC (INTEC/CONICET-UNL)
> Predio CONICET-Santa Fe
> Colectora RN 168 Km 472, Paraje El Pozo
> 3000 Santa Fe, Argentina
> Tel: +54-342-4511594 (ext 1011)
> Tel/Fax: +54-342-4511169
More information about the petsc-dev
mailing list