You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PaHostApiInfo, PaDeviceInfo and PaStreamInfo structures have a structVersion field. Other structures don't. It has been proposed (and generally agreed) that we should remove these fields because the versioning capabilities they provide are not easily usable.
Instead, a global library versioning mechanism will be provided (documented in ticket: #173)
Richard Ash suggested that it wasn't a big deal to break compatibility since we can bump package version numbers. http://music.columbia.edu/pipermail/portaudio/2008-February/008324.html
In the same basis Richard also provides the analysis to support removing the struct version numbers. He concludes:
On this basis I would suggest that structure version numbering is just
not worth it - almost no application developer is going to jump through
the kind of complexity you describe to support multiple library versions
at runtime.
Since this change breaks binary structure compatibility and should be performed in conjunction with the following tickets that also alter struct layout
Issue created by @RossBencina
PaHostApiInfo, PaDeviceInfo and PaStreamInfo structures have a structVersion field. Other structures don't. It has been proposed (and generally agreed) that we should remove these fields because the versioning capabilities they provide are not easily usable.
Instead, a global library versioning mechanism will be provided (documented in ticket: #173)
We discussed whether breaking binary compatibility was a good idea. Bjorn started here:
http://music.columbia.edu/pipermail/portaudio/2008-February/008318.html
Richard Ash suggested that it wasn't a big deal to break compatibility since we can bump package version numbers.
http://music.columbia.edu/pipermail/portaudio/2008-February/008324.html
In the same basis Richard also provides the analysis to support removing the struct version numbers. He concludes:
Since this change breaks binary structure compatibility and should be performed in conjunction with the following tickets that also alter struct layout
The text was updated successfully, but these errors were encountered: