I think I agree with Markus that it is in fact broken. It's easy to imagine dependency scenarios like this:

lambda <-- libA <-\ }--> App bind <-- libB <-/

The guy writing App shouldn't have to be aware of the dependency conflict between libA and libB.

Isn't this only a problem within translation units? I suppose lambda and bind might be included in headers from libA and libB into a single translation unit in App, but seems unlikely. ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------