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

[jvporter at wisc.edu]

Author: jvporter
Date: 2011-04-26 17:43:09 -0500 (Tue, 26 Apr 2011)
New Revision: 4777

Modified:
   MOAB/trunk/itaps/imesh/iMesh.h
   MOAB/trunk/itaps/imesh/iMesh_MOAB.cpp
Log:
Update iMesh.h to be in sync with ITAPS repo


Modified: MOAB/trunk/itaps/imesh/iMesh.h
===================================================================
--- MOAB/trunk/itaps/imesh/iMesh.h	2011-04-26 18:57:10 UTC (rev 4776)
+++ MOAB/trunk/itaps/imesh/iMesh.h	2011-04-26 22:43:09 UTC (rev 4777)
@@ -1,25 +1,25 @@
 #ifndef _ITAPS_iMesh
 #define _ITAPS_iMesh
 
-  /**\brief iMesh Interface Specification Major Release Number
+  /* iMesh Interface Specification Major Release Number
     */
-#define IMESH_MAJOR_VERSION 1
+#define IMESH_VERSION_MAJOR 1
 
-  /**\brief iMesh Interface Specification Minor Release Number
+  /* iMesh Interface Specification Minor Release Number
     */
-#define IMESH_MINOR_VERSION 1
+#define IMESH_VERSION_MINOR 3
 
-  /**\brief iMesh Interface Specification Patch Release Number
+  /* iMesh Interface Specification Patch Release Number
     *
     * Technically speaking, there is not much practical value in
     * a 'patch' digit for an interface specification. A 'patch'
     * release is typically only used for bug fix releases. That
     * is unlikely to apply to an interface specification such as
-    * iMesh. Nonetheless, there is non-technical value in having
-    * a bit finer grained control over version numbers that a patch
-    * digit affords. So, we define one for iMesh.
+    * iMesh. On the other hand, there are indeed ways of interpreting
+    * some interface changes as bug fixes. So, we define a patch
+    * digit for iMesh.
     */
-#define IMESH_PATCH_VERSION 0
+#define IMESH_VERSION_PATCH 0
 
   /** \mainpage The ITAPS Mesh Interface iMesh
    *
@@ -30,9 +30,9 @@
    * to this interface, for example mesh smoothing, adaptive mesh refinement,
    * and parallel mesh support.
    *
-   * \section ITAPS Data Model
+   * \section iMesh Data Model
    *
-   * The ITAPS interfaces use a data model composed of four basic data types: \n
+   * The iMesh interface use a data model composed of four basic data types: \n
    * \em Entity: basic topological entities in a mesh, e.g. vertices, 
    * triangles, hexahedra. \n
    * \em Entity \em Set: arbitrary grouping of other entities and sets.