summaryrefslogtreecommitdiffstats
path: root/fortran/test/fflush1.f90
diff options
context:
space:
mode:
authorAlbert Cheng <acheng@hdfgroup.org>2005-01-09 06:19:16 (GMT)
committerAlbert Cheng <acheng@hdfgroup.org>2005-01-09 06:19:16 (GMT)
commitc3e6571ea5f53ae37ef28aa74f7d6e48ca52e15f (patch)
tree9430da9b4448c5d92031fdcdb57c351511d7e0c3 /fortran/test/fflush1.f90
parentd7f580b7cc80d53cfba366e2f7c3865d46833030 (diff)
downloadhdf5-c3e6571ea5f53ae37ef28aa74f7d6e48ca52e15f.zip
hdf5-c3e6571ea5f53ae37ef28aa74f7d6e48ca52e15f.tar.gz
hdf5-c3e6571ea5f53ae37ef28aa74f7d6e48ca52e15f.tar.bz2
[svn-r9786] Purpose:
bug fix and document. Description: Unix and probably other systems too, has a small exit value range such as 1 byte. So, exit(256) may end up the same as exit(1). Added caution message to the exit wrappers and changed test programs to exit(1) when errors detected. Platforms tested: tested in copper. verified here that exit(256) was treated just like exit(0).
Diffstat (limited to 'fortran/test/fflush1.f90')
-rw-r--r--fortran/test/fflush1.f905
1 files changed, 2 insertions, 3 deletions
diff --git a/fortran/test/fflush1.f90 b/fortran/test/fflush1.f90
index 52efb21..bace5f9 100644
--- a/fortran/test/fflush1.f90
+++ b/fortran/test/fflush1.f90
@@ -143,9 +143,8 @@
CALL H5fflush_f(file_id, H5F_SCOPE_GLOBAL_F, error)
CALL check("h5fflush_f",error,total_error)
- ! if errors detected, exit with non-zero code. This is not truly fortran
- ! standard but likely supported by most fortran compilers.
- IF (total_error .ne. 0) CALL h5_exit_f (total_error)
+ ! if errors detected, exit with non-zero code.
+ IF (total_error .ne. 0) CALL h5_exit_f (1)
001 STOP