It's much easier to avoid collisions when you have a list of all the names you're using at the top of each source file. It's also easier when each of those imported names can be renamed with the same declaration.
/dpt/ - Daily Programming Thread
You are using two libraries called Foo and Bar:
using namespace foo;
using namespace bar;
Everything works fine, you can call Blah() from Foo and Quux() from Bar without problems. But one day you upgrade to a new version of Foo 2.0, which now offers a function called Quux(). Now you've got a conflict: Both Foo 2.0 and Bar import Quux() into your global namespace. This is going to take some effort to fix, especially if the function parameters happen to match.
If you had used foo::Blah() and bar::Quux(), then the introduction of foo::Quux() would have been a non-event.
Or you could just using foo::Blah; and using bar::Quux; and have the best of both worlds.
Gitlab or Bitbucket for free private repos?
fuck namespaces
I am doing real shit organizing my growing python application. I hate what I have made and it's only 228 lines. Fucking shouldn't have tried OOP because I'm terrible at it and Python makes it worse
Also getting a strong feeling I can't fucking apply the Single Responsibility Principle
updating to iOs 11 on the new iPhone purchased via Swappa
int i = 42, *p = &i;
decltype(*p) c;//error: c is int& instead of int and must be initialized
Fuck this language
there's nothing wrong with goto