create/destroy name change proposal

James Porter jvporter at wisc.edu
Thu May 6 17:39:00 CDT 2010


On Wed, 2010-05-05 at 10:16 -0400, Carl Ollivier-Gooch wrote:
> On 10-04-29 09:30 PM, Mark Miller wrote:
> > Proposal:
> > ---------
> > Change the name(s) of a few iMesh functions to make the API a little
> > more consistently named. For convenience, I list below the names of many
> > fuctions that add/remove or create/destroy things.
[snip]

While we're on the subject of renaming, I think we should look at the
consistency in abbreviations. For instance, "child"/"children" is
spelled three different ways in iMesh: "iMesh_isChildOf",
"iMesh_getNumChld"/"iMesh_addPrntChld", and "iMesh_getChldn". Likewise
with "parent(s)". In most of these cases, we're only saving a couple
characters (at most 4 for "iMesh_getNumChld"), at the expense of
memorizing what abbreviation is used where.

I think we could just remove these abbreviations entirely, especially
since the unabbreviated versions would by no means be the longest
function names in iMesh.

Maybe it would also be worth looking at the iMesh_(get|set)Arr*Data
functions. It looks like these are the only places in iMesh that still
use "Arr" to refer to entity arrays (everywhere else uses "EntArr").

It would probably also be worth looking at naming consistency for iGeom,
but that's a whole other can of worms.

- Jim



More information about the tstt-interface mailing list