create/destroy name change proposal

[James Porter]

On Thu, 2010-05-06 at 15:55 -0700, Mark Miller wrote:
> At this point, I don't think it hurts to at least get all the name
> changes on the table so we can at least see 'em. So, I would ask you,
> Jim, to send me a list of old --> new function name changes on the
> 'child' issue as you see 'em so that I can maybe combine them with my
> proposal and draft a larger proposal on this topic.

Here are the changes I would propose for the parent/child stuff. I know
I mentioned the inconsistency with iMesh_getArrData and friends, but I
would probably be ok leaving them as-is (especially since it would
require changing iMesh_getData and friends too).

    iMesh_addPrntChld -> iMesh_addParentChild
    iMesh_rmvPrntChld -> iMesh_rmvParentChild
    iMesh_getNumChld  -> iMesh_getNumChildren
    iMesh_getNumPrnt  -> iMesh_getNumParents
    iMesh_getChldn    -> iMesh_getChildren
    iMesh_getPrnts    -> iMesh_getParents

All that said, I think iGeom is in more urgent need of an audit, since
even some of the functions that have iMesh equivalents have different
names (e.g. iMesh_getEntArrAdj vs. iGeom_getArrAdj).

- Jim