17 Feb
2016
17 Feb
'16
5:06 p.m.
Robert Ramey wrote:
All these cases relate to two coupled libraries.
If by "coupled" you mean interdependent, that is, library X depends on Y and Y depends on X, then no. The typical case is this: - your library X uses Y - you propose a new feature for Y - ... which you use in X - the new feature of Y is in develop - ... and so is your use of it - therefore, X's develop depends on Y's develop Y is often Boost.Config and it's not coupled to anything. If you have to test against Y's master, you need to wait until the new feature is merged into master before being able to make use of it.