Barry Smith <bsmith at mcs.anl.gov> writes: > That was my rationalization for ugly code; until a better solution > appeared and I no longer needed the rationalization :-)
Okay, are we removing _all_ those casts, or only for a few highly-used PetscObject functions? PetscObjectComm() is one we changed recently. Note that absorbing the cast into the macro is backward-compatible in that code with an explicit cast continues to work without a warning.
