No. His definition is correct. If you make the call, it's a library, that it might use threads during that call does not make it a framework. Libraries don't m

No. His definition is correct. If you make the call, it's a library, that it might use threads during that call does not make it a framework. Libraries don't mean you're in full control of everything, they only mean you invoke all interactions and get results back rather than you subclass something and plug a part into a framework. If you have to subclass something, it's a framework.