"E. Gladyshev" <[EMAIL PROTECTED]> wrote in message
> What is exactly wrong with my solution that doesn't
> have the ONE OS limitations, doesn't have any
> compilation time problems
Do you mean link of incompatible library problems ?
If so ... as mentioned this is problem of boost build system
and it will be finally solved. Look at boost::regex, it doesn't have
such problems for compilers supporting "#pragma comment".
It means that correct library is linked automatically.
> and supports my toy OS (or
> any other OS) directly (w/o editing the boost::thread
> implementation)?
Because :
1. traits causes more complicated and more
error prone interface. In this case errors can
be caused by two incompatible thread
mechanicms used in one application.
BTW, have you any idea how two diffrent
thread models will collaborate in one
application ? And why you may want this mess ?
2. A lot of implementation code will be placed in headers,
which damages compile perfomance VERY
MUCH ... I hope you have already agreed
to this point. Do you ?
3. I haven't seen compiled application,
which is working with TWO OSes
or threading models at the same time.
Do you ?
Single/multi treaded is property
of whole application, but not of it's part.
Current boost::thread design is just
reflection for this statement.
regards,
bohdan
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
