 | 1 | initial version |
Is backwards compatibility guarenteed between micro versions
It's supposed to be, as noted by @Jaap.
Unfortunately, it's not guaranteed to be, as non-compatible changes may unintentionally be made. As @carl-robert noted, a non-binary-compatible change was made between 4.0.3 and 4.0.4 - a field was added to the middle of a public data structure, which means that any code that depends on the offsets of any fields that are after the inserted field will not work.
| | 2 | No.2 Revision |
Is backwards compatibility guarenteed between micro versions
It's supposed to be, as noted by @Jaap.
Unfortunately, it's not guaranteed to be, as non-compatible changes may unintentionally be made. As @carl-robert @Carl Robert noted, a non-binary-compatible change was made between 4.0.3 and 4.0.4 - a field was added to the middle of a public data structure, which means that any code that depends on the offsets of any fields that are after the inserted field will not work.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
