[petsc-dev] (no subject)

[Barry Smith]

   I cannot remember why this was required. I have removed this requirement, let's see how it goes; if we need to put it back make sure we add a developer note to the manual page explaining why.

   Note that it still requires the type and sizes to be set before calling to insure the function setoptions() for that type is set in the function table.

    Barry

On Feb 23, 2012, at 1:15 PM, Lisandro Dalcin wrote:

> MatSetOption() seems to require previous preallocation (I mean, it has
> the MatCheckPreallocated() call). Isn't it too much? Do we really need
> a previous preallocation in order to set an option? I agree that many
> options are tightly related to nonzero pattern and memory allocation,
> but many options can be safely set before preallocation.
> 
> -- 
> 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