# C/C++: ABI stability and binary compatibility between "patch" versions

**URL:** <https://forum.hdfgroup.org/t/c-c-abi-stability-and-binary-compatibility-between-patch-versions/5312>\
**Category:** HDF5 Library\
**Created:** [January 21, 2019, 2:49pm UTC](https://forum.hdfgroup.org/t/c-c-abi-stability-and-binary-compatibility-between-patch-versions/5312 "2019-01-21T14:49:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paramon](https://forum.hdfgroup.org/letter_avatar_proxy/v4/letter/p/8491ac/32.png) [@paramon](https://forum.hdfgroup.org/u/paramon)\
**Post date:** [January 21, 2019, 9:24pm UTC](https://forum.hdfgroup.org/t/c-c-abi-stability-and-binary-compatibility-between-patch-versions/5312/2 "2019-01-21T21:24:36Z")

</div>

Hi Alexander,

HDF5 users share your disappointment!

I have reported the problem recently:

> [@HDFView 3.0 Pre-release - Newsletter #163 - The HDF Group](https://forum.hdfgroup.org/t/hdfview-3-0-pre-release-newsletter-163-the-hdf-group/4686/2):
>
> Hello! Just tried to update from HDF5 10.1 to HDF5 10.4 in my codebase, and apparently HDF5 release 10.3 did break library API compatibility. Specifically, functions H5Oget\_info, H5Oget\_info\_by\_idx, H5Oget\_info\_by\_name, H5Ovisit, H5Ovisit\_by\_name are now available either with new definition (suffixed with 2) or with original definition (suffixed with 1), but never by original name (without suffix). Older client code relying on original names will break, as confirmed by e.g. [https://github.com/…](https://github.com/JuliaIO/HDF5.jl/issues/508)

Hopefully it’s fixed in 1.10.5, so that lost symbols get back.

Best wishes,  
Andrey Paramonov

---

_[View the full topic](https://forum.hdfgroup.org/t/c-c-abi-stability-and-binary-compatibility-between-patch-versions/5312)._