summaryrefslogtreecommitdiffstats
path: root/c++/test/th5s.cpp
diff options
context:
space:
mode:
authorDana Robinson <43805+derobins@users.noreply.github.com>2023-04-22 06:25:12 (GMT)
committerGitHub <noreply@github.com>2023-04-22 06:25:12 (GMT)
commit7707859279a60b32d2b6c915442a7c04d44445b4 (patch)
tree890d16aa2408b270368b36ea4f05ca20fe2f16f6 /c++/test/th5s.cpp
parenta4371b6fce577852691dfdeac642dec1dd4b9453 (diff)
downloadhdf5-7707859279a60b32d2b6c915442a7c04d44445b4.zip
hdf5-7707859279a60b32d2b6c915442a7c04d44445b4.tar.gz
hdf5-7707859279a60b32d2b6c915442a7c04d44445b4.tar.bz2
Merge with develop (#2790)
Diffstat (limited to 'c++/test/th5s.cpp')
-rw-r--r--c++/test/th5s.cpp45
1 files changed, 0 insertions, 45 deletions
diff --git a/c++/test/th5s.cpp b/c++/test/th5s.cpp
index 3651aa3..b9a84e1 100644
--- a/c++/test/th5s.cpp
+++ b/c++/test/th5s.cpp
@@ -87,16 +87,6 @@ int space5_data = 7;
* Programmer Binh-Minh Ribler (using C version)
* Mar 2001
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
- * April 12, 2011: Raymond Lu
- * Starting from the 1.8.7 release, we allow dimension
- * size to be zero. So I took out the test against it.
*-------------------------------------------------------------------------
*/
static void
@@ -223,13 +213,6 @@ test_h5s_basic()
* Programmer Binh-Minh Ribler (using C version)
* Mar 2001
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
*-------------------------------------------------------------------------
*/
static void
@@ -287,13 +270,6 @@ test_h5s_scalar_write()
* Programmer Binh-Minh Ribler (using C version)
* Mar 2001
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
*-------------------------------------------------------------------------
*/
static void
@@ -348,13 +324,6 @@ test_h5s_scalar_read()
* Programmer Raymond Lu (using C version)
* May 18, 2004
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
*-------------------------------------------------------------------------
*/
static void
@@ -402,13 +371,6 @@ test_h5s_null()
* Programmer Binh-Minh Ribler (using C version)
* Mar 2001
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
*-------------------------------------------------------------------------
*/
static void
@@ -470,13 +432,6 @@ test_h5s_compound_scalar_write()
* Programmer Binh-Minh Ribler (using C version)
* Mar 2001
*
- * Modifications:
- * January, 2005: C tests' macro VERIFY casts values to 'long' for all
- * cases. Since there are no operator<< for 'long long'
- * or int64 in VS C++ ostream, I casted the hssize_t values
- * passed to verify_val to 'long' as well. If problems
- * arises later, this will have to be specifically handled
- * with a special routine.
*-------------------------------------------------------------------------
*/
static void