mirror of
https://github.com/HDFGroup/hdf5.git
synced 2024-11-21 01:04:10 +08:00
[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).
This commit is contained in:
parent
d7f580b7cc
commit
c3e6571ea5
@ -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
|
||||
|
@ -176,8 +176,7 @@
|
||||
CALL h5close_f(error)
|
||||
CALL check("h5close_types_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)
|
||||
|
||||
END PROGRAM FFLUSH2EXAMPLE
|
||||
|
@ -336,9 +336,8 @@
|
||||
|
||||
CALL h5close_f(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 exit (total_error)
|
||||
! if errors detected, exit with non-zero code.
|
||||
IF (total_error .ne. 0) CALL h5_exit_f (1)
|
||||
|
||||
END PROGRAM fortranlibtest
|
||||
|
||||
|
@ -112,7 +112,10 @@ DONE:
|
||||
|
||||
/*----------------------------------------------------------------------------
|
||||
* Name: h5_exit_c
|
||||
* Purpose: Call 'exit()' to terminate application
|
||||
* Purpose: Call 'exit()' to terminate application. Be careful not to
|
||||
* overflow the exit value range since UNIX supports a very
|
||||
* small range such as 1 byte. Therefore, exit(256) may end
|
||||
* up as exit(0).
|
||||
* Inputs: status - status for exit() to return
|
||||
* Returns: none
|
||||
* Programmer: Quincey Koziol
|
||||
|
@ -164,6 +164,9 @@
|
||||
!
|
||||
! Purpose: Exit application
|
||||
! It is a fortran counterpart for the standard C 'exit()' routine
|
||||
! Be careful not to overflow the exit value range since
|
||||
! UNIX supports a very small range such as 1 byte.
|
||||
! Therefore, exit(256) may end up as exit(0).
|
||||
!
|
||||
! Inputs:
|
||||
! status - Status to return from application
|
||||
@ -197,4 +200,3 @@
|
||||
CALL h5_exit_c(status)
|
||||
|
||||
END SUBROUTINE h5_exit_f
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user