>> If you use them correctly, the hypothetical problem you're talking about simply doesn't exist.
But if you use them correctly and somebody else uses them incorrectly, the problem resurfaces.
Printable View
>> If you use them correctly, the hypothetical problem you're talking about simply doesn't exist.
But if you use them correctly and somebody else uses them incorrectly, the problem resurfaces.
http://groups.google.com/group/comp....368ab790df5336Quote:
Originally Posted by siavoshkc
But then it's not your problem, is it?Quote:
Originally Posted by Daved
It isn't your fault, but can most definitely be your problem. If you use code from libraries that do this, then your code can have issues and you are the one who has to deal with it.
Now the discussion is out of scope.
Don't use bad libraries, then ...Quote:
Originally Posted by Daved
(Yeah, I know. Company policy, blablabla. Still ... I think a using declaration/statement in a header is such bad code practice that it should be possible to convince your dev team and managers not to use the library.)
And if your manager wrote the library?
Oh man! I so much know what that means!
Not with C++ where I'm just a newbie. But I also had to endure that pain. And god forbid me of ever have said anything against his code.
Quit? :DQuote:
Originally Posted by Daved
Tell us where you work so we don't buy your products? ;)Quote:
Originally Posted by Daved
Of course this is all purely hypothetical.