"Douglas Gregor" <[EMAIL PROTECTED]> writes:

>     3) There is an alternative solution: Boost.Threads presents a single,
> non-template interface to the user and hides all of the platform-specific
> details using the pImpl idiom. The same approach can be applied here, and I
> think we'll find that it has all of the same advantages.

Not quite.  pImpl is really bad when you have multiple interacting
concrete types.  I think you'll find yourself doing a lot of
polymorphic_downcast<>s.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to