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
How do we verify the API stability since it is not tested at all at the moment. One approach would be to write a simple cpp file which uses every function and method available in the public API. If the file does not compile we have an API change and with the git history of the file we even know first hand how the user code which uses iceoryx has to be adapted.
If we have proven the stability of the API we can prove the ABI stability with a setup of three applications: sender, receiver and roudi. Each of the applications is using iceoryx as a shared library once with the newest and once with the oldest minor version. Then we run a mixed setup and everything should work fine.
How do we verify the API stability since it is not tested at all at the moment. One approach would be to write a simple cpp file which uses every function and method available in the public API. If the file does not compile we have an API change and with the git history of the file we even know first hand how the user code which uses iceoryx has to be adapted.
If we have proven the stability of the API we can prove the ABI stability with a setup of three applications: sender, receiver and roudi. Each of the applications is using iceoryx as a shared library once with the newest and once with the oldest minor version. Then we run a mixed setup and everything should work fine.
Originally posted by @elfenpiff in #918 (comment)
The text was updated successfully, but these errors were encountered: