3 ms·
> If you're spawning threads implicitly then you're no longer a library, you're a framework. That't not what makes a framework. It's all about inversion of con
by 2trill2spill 10y ago
> If you're spawning threads implicitly then you're no longer a library, you're a framework.
That't not what makes a framework. It's all about inversion of control, you call a library and a framework calls you.
http://stackoverflow.com/questions/3057526/framework-vs-toolkit-vs-library http://stackoverflow.com/questions/3057526/framework-vs-tool...
- lmm 10y agoIf it's spawning threads, it's controlling the control flow. Either it's calling you, or the control flow is out of control.
- gnaritas 10y agoNo. 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.