[petsc-dev] The "type" field in PetscObject

[Jed Brown]

This seems to be equal to either 0 or -1 for every type in PETSc.  The
comments for PetscHeaderCreate suggest that it no longer has any meaning,
but we still have PetscCheckSameTypeAndComm.  What was the intent of this
field?  Is it to have a faster way than strcmp to check whether two
implementations match?

I'm thinking about how to handle Vec operations of heterogeneous type which
I don't think it is a short-term priority.

Jed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101126/4cae4a29/attachment.html>