Author: janehu Date: 2013-02-28 11:43:02 -0600 (Thu, 28 Feb 2013) New Revision: 6018 Modified: cgm/trunk/itaps/iBase.h Log: Updated iBase.h according to moab's changes. Modified: cgm/trunk/itaps/iBase.h =================================================================== --- cgm/trunk/itaps/iBase.h 2013-02-27 21:47:35 UTC (rev 6017) +++ cgm/trunk/itaps/iBase.h 2013-02-28 17:43:02 UTC (rev 6018) @@ -9,10 +9,10 @@ * Technically speaking, there is not much practical value in patch digit * for an interface specification. A patch release is typically only used * for bug fix releases. Although it is rare, sometimes a bug fix - * necessitates an API change. So, we define a patch digit for iMesh. + * necessitates an API change. So, we define a patch digit for iBase. * * Although each interface in ITAPS has been designed to support its own - * uniqe version numbers, apart from other ITAPS interfaces, as currently + * unique version numbers, apart from other ITAPS interfaces, as currently * used, we require all ITAPS interfaces to use the same ITAPS-wide version * number derived from the version number defined by these three digits. ******************************************************************************/ @@ -102,12 +102,6 @@ typedef struct iBase_EntityIterator_Private* iBase_EntityIterator; typedef struct iBase_EntityArrIterator_Private* iBase_EntityArrIterator; -struct iBase_Error -{ - int error_type; - char description[120]; -}; - enum iBase_EntityType { iBase_EntityType_MIN = 0, /**< facilitates iteration over all values */ @@ -120,7 +114,7 @@ iBase_REGION, /**< A topological dimension 3 entity */ iBase_ALL_TYPES, - /**< used only in queires to request information about all types */ + /**< used only in queries to request information about all types */ iBase_EntityType_MAX = iBase_ALL_TYPES /**< facilitates iteration over all values */ }; @@ -337,6 +331,9 @@ * NOT include the null character and implementations must be coded to * accommodate this. This requirement is primarily due to differences in how * Fortran and C/C++ handle passing of strings as function arguments. + * Furthermore, because of the way Fortran clients pass strings (Fortran always + * passes the length of the string as declared in the source code), there + * may be trailing spaces in the string that need to be truncated. * * \page numhops Indirection in Set-Inclusion and Parent-Child structures * @@ -412,6 +409,152 @@ * Note that iMesh itself currently does not define any options. In order