Author: jvporter
Date: 2011-02-16 16:38:33 -0600 (Wed, 16 Feb 2011)
New Revision: 4508
Modified:
MOAB/trunk/itaps/imesh/iMesh.h
MOAB/trunk/itaps/imesh/iMesh_MOAB.cpp
MOAB/trunk/itaps/imesh/testc_cbind.c
Log:
Mostly sync iMesh.h with standard version:
* Add/update comments
* Add iMesh_(get|set)ESHData and friends
Still left to do:
* Figure out whose num_hops comments are correct (I think ours)
* Do something about iMesh_setAdjTable
Modified: MOAB/trunk/itaps/imesh/iMesh.h
===================================================================
--- MOAB/trunk/itaps/imesh/iMesh.h 2011-02-16 21:59:14 UTC (rev 4507)
+++ MOAB/trunk/itaps/imesh/iMesh.h 2011-02-16 22:38:33 UTC (rev 4508)
@@ -7,7 +7,7 @@
/**\brief iMesh Interface Specification Minor Release Number
*/
-#define IMESH_MINOR_VERSION 0
+#define IMESH_MINOR_VERSION 1
/**\brief iMesh Interface Specification Patch Release Number
*
@@ -30,7 +30,7 @@
* to this interface, for example mesh smoothing, adaptive mesh refinement,
* and parallel mesh support.
*
- * \section DataModel Data Model
+ * \section ITAPS Data Model
*
* The ITAPS interfaces use a data model composed of four basic data types: \n
* \em Entity: basic topological entities in a mesh, e.g. vertices,
@@ -45,7 +45,7 @@
* \em Tag: application data associated with objects of any of the other
* data types. Each tag has a designated name, size, and data type.
*
- * \section TypeTopology Entity Type, Topology
+ * \section ITAPS Entity Type, Topology
* Each entity has a specific Entity Type and Entity Topology. The Entity
* Type is one of VERTEX, EDGE, FACE, and REGION, and is synonymous with
* the topological dimension of the entity. The Entity Topology denotes
@@ -54,14 +54,14 @@
* types, Entity Type in the iBase_EntityType enumeration, and
* Entity Topology in the iMesh_EntityTopology enumeration.
*
- * \section Access Entity-, Array-, and Iterator-Based Access
+ * \section ITAPS Entity-, Array-, and Iterator-Based Access
*
* The iMesh interface provides functions for accessing entities
* individually, as arrays of entities, or using iterators. These access
* methods have different memory versus execution time tradeoffs,
* depending on the implementation.
*
- * \section Lists Lists Passed Through Interface
+ * \section ITAPS Lists Passed Through Interface
*
* Many of the functions in iMesh have arguments corresponding to lists of
* objects. In-type arguments for lists consist of a pointer to an array and
@@ -79,7 +79,7 @@
* INTERFACE IMPLEMENTATIONS IS DONE USING THE C MALLOC FUNCTION, AND CAN BE
* DE-ALLOCATED USING THE C FREE FUNCTION.