Last modified: 24 May 2009
Name: H5Epush
Signature:
  herr_t `H5Epush`( const char *`file`, const char *`func`, unsigned `line`, H5E_major_t `maj_num`, H5E_minor_t `min_num`, const char *`str` )

  herr_t `H5Epush`( hid_t `estack_id`, const char *`file`, const char *`func`, unsigned `line`, hid_t `class_id`, hid_t `major_id`, hid_t `minor_id`, const char *`msg`, ...)
Purpose:
  Pushes a new error message onto an error stack.
Description:
  `H5Epush` is a macro that is mapped to either `H5Epush1` or `H5Epush2`, depending on the needs of the application.

  Such macros are provided to facilitate application compatibility. Their use and mappings are fully described in “API Compatibility Macros in HDF5”; we urge you to read that document closely.

  When both the HDF5 Library and the application are built and installed with no specific compatibility flags, `H5Epush` is mapped to the most recent version of the function, currently `H5Epush2`. If the library and/or application is compiled for Release 1.6 emulation, `H5Epush` will be mapped to `H5Epush1`. Function-specific flags are available to override these settings on a function-by-function basis when the application is compiled.

  Specific compile-time compatibility flags and the resulting mappings are as follows:

  Compatibility setting | `H5Epush` mapping
  --- | ---
  Global settings
  No compatibility flag | `H5Epush2`
  Enable deprecated symbols | `H5Epush2`
  Disable deprecated symbols | `H5Epush2`
  Emulate Release 1.6 interface`` | `H5Epush1`
  Function-level macros
  `H5Epush_vers = 2` | `H5Epush2`
  `H5Epush_vers = 1` | `H5Epush1`

Fortran90 Interface:
  None.

History:

  Release | C
  1.8.0 | The function `H5Epush` renamed to `H5Epush1` and deprecated in this release. The macro `H5Epush` and the function `H5Epush2` introduced in this release.