From 103bb5eae8106b68f62a1defa9aa7b35e3b78b52 Mon Sep 17 00:00:00 2001 From: ageay Date: Fri, 5 Apr 2013 07:37:03 +0000 Subject: [PATCH] MEDMEM suppression --- doc/doxygen/interpkernel.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/doxygen/interpkernel.dox b/doc/doxygen/interpkernel.dox index ba00404f0..ccb1c3a78 100644 --- a/doc/doxygen/interpkernel.dox +++ b/doc/doxygen/interpkernel.dox @@ -60,7 +60,7 @@ rules : -# \code void releaseTempArrays() \endcode - Formats of arrays - the array returned by \c getCoordinatesPtr must be a \b full \b interlace array. - - the arrays returned by \c getConnectivityPtr and \c getConnectivityIndexPtr must be with the same principle as it is \ref MEDCouplingUMeshNodalConnectivity "MEDCouplingUMesh does". Of course the numbering format may change according to \a My_numPol policy. + - the arrays returned by \c getConnectivityPtr and \c getConnectivityIndexPtr must be with the same principle as it is \ref MEDCouplingUMeshNodalConnectivity "implemented in MEDCouplingUMesh". Of course the numbering format may change according to \a My_numPol policy. Note that the array format for connectivity is kept close to MED. It is close to VTK format too but slightly different. So it may require for the VTK side a copy @@ -82,4 +82,4 @@ As already said, the matrix returned by interpolator is typically a sparse matri Note that \c std::vector\c < \c std::map > is a candidate for \c MatrixType. -*/ \ No newline at end of file +*/ -- 2.39.2