Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Extra libraries, Code snippets, applications etc. » C++ language problems and code snippets » Basic library interface and separation problem
Re: Basic library interface and separation problem [message #21876 is a reply to message #21873] Tue, 09 June 2009 00:25 Go to previous messageGo to previous message
Didier is currently offline  Didier
Messages: 736
Registered: November 2008
Location: France
Contributor
Usualy what is used for this is: "dependancy inversion"
In other words: make an interface (it will be the API) and make both librairies depend on it (solution 2 of koldo).

The result is B does not depend on lib A although it uses it !
You can now freely change lib A or B, as long as you keep the API stable. Smile

This is what APIs are made for Cool

 
Read Message
Read Message
Read Message
Read Message
Previous Topic: overloading operators rules
Next Topic: Ultimate++ possible adaptation to C++0x
Goto Forum:
  


Current Time: Sun Jul 06 19:21:20 CEST 2025

Total time taken to generate the page: 0.03657 seconds