--- Bohdan <[EMAIL PROTECTED]> wrote: > If you mean your threads snipped: Yes i've seen it. > IMO it is more complicated and YES it has compile > time problems, unless you put traits implementation > in cpp files and move #include <OS headers> to > cpp files, but in this case you have
Yes, it was my suggestion. I have put traits implemenations in cpp file in my proposal. #include <OS headers> are in cpp files as well. Sorry if my description was not clear. I hope you agree that in this case, there are not any performance issues? > link-to-correct-library problems again. We have it anyway. My solution didn't claim to resolve it completely, did it? However if I use thread_core.h directly and provide my own trait (my toy OS), it resolves the link-to-correct-library problems automatically, does it? > Let me guess ... part of application is using > threads > and part is woring as always in main thread ? > > "Models" term was wrong, sorry. > Under models i meant REALLY diffrent functionality > for threads. Like ToyOSThreads and Win32threads. > More correct is "Thread Implementation". Win32 has really different thread models. I have mentioned it several times in my posts. They have normal threads and fibers, do they? > I'm still trying. Hope you too. same here :) Eugene __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
