[MOAB-dev] r4559 - MOAB/trunk/itaps/imesh

[James Porter]

Should we do the same for iGeom? I have patches for that and iRel ready
to go.

- Jim

On Wed, 2011-03-09 at 11:58 -0600, kraftche at cae.wisc.edu wrote:
> Author: kraftche
> Date: 2011-03-09 11:58:51 -0600 (Wed, 09 Mar 2011)
> New Revision: 4559
> 
> Modified:
>    MOAB/trunk/itaps/imesh/iMesh.h
>    MOAB/trunk/itaps/imesh/iMesh_MOAB.cpp
>    MOAB/trunk/itaps/imesh/testc_cbind.c
> Log:
> sync with latest official iMesh.h
> 
> Modified: MOAB/trunk/itaps/imesh/iMesh.h
> ===================================================================
> --- MOAB/trunk/itaps/imesh/iMesh.h	2011-03-09 16:27:07 UTC (rev 4558)
> +++ MOAB/trunk/itaps/imesh/iMesh.h	2011-03-09 17:58:51 UTC (rev 4559)
> @@ -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.