My Most Important C++ Aha Moments (2006)
artima.com
My Most Important C++ Aha Moments (2006)
1–10 of 84 posts
Re: My Most Important C++ Aha Moments (2006)
#2Yep the beauty (and maybe curse) of C++ iterators is that they are a faithful abstraction of pointers.
Re: My Most Important C++ Aha Moments (2006)
#3I love C and Objective-C. I can't stand C++.
Is that common among programmers?
Re: My Most Important C++ Aha Moments (2006)
#4I love C and Objective-C. I can't stand C++. Is that common among programmers?
Coming from C++ and iOS world I would say recent C++ has evolved a lot. And I think its better than Objective-C.
Re: My Most Important C++ Aha Moments (2006)
#5Yep the beauty (and maybe curse) of C++ iterators is that they are a faithful abstraction of pointers.
some people would argue that pointers themselves are a type of iterator
Re: My Most Important C++ Aha Moments (2006)
#6I love C and Objective-C. I can't stand C++. Is that common among programmers?
What has always bugged me about C++, but maybe I am overlooking some reason why this generally cannot work, is that it does not resolve circular dependencies such as this one:
// file: A.h
class A {
B* _b;
};
// file: B.h
class B {
A* _a;
};
Re: My Most Important C++ Aha Moments (2006)
#7I love C and Objective-C. I can't stand C++. Is that common among programmers?
What has always bugged me about C++, but maybe I am overlooking some reason why this generally cannot work, is that it does not resolve circular dependencies such as this one: // file: A.h class A { B* _b; }; // file: B.h class B { A* _a; }; I mean a pointer has a fixed size, so couldn't the compiler just leave some sort of type placeholder in class A until class B is eventually defined.
This can be done, check the end of this answer: http://stackoverflow.com/a/628079/429972
// file: A.h
class B;
class A {
B* _b; // or any of the other variants.
};Re: My Most Important C++ Aha Moments (2006)
#8Earlier quoted context omitted.
What has always bugged me about C++, but maybe I am overlooking some reason why this generally cannot work, is that it does not resolve circular dependencies such as this one: // file: A.h class A { B* _b; }; // file: B.h class B { A* _a; }; I mean a pointer has a fixed size, so couldn't the compiler just leave some sort of type placeholder in class A until class B is eventually defined.
This can be done, check the end of this answer: http://stackoverflow.com/a/628079/429972 // file: A.h class B; class A { B* _b; // or any of the other variants. };
You can also do this
class A {
class B* _b;
};Re: My Most Important C++ Aha Moments (2006)
#9I love C and Objective-C. I can't stand C++. Is that common among programmers?
C programmer here; I don't like C++ much because every library tends to reinvent the whole stack (or maybe that's just my impression from using MFC and Qt, which are notorious in that regard).
RAII and scope based construction/destruction is actually quite nice.
Re: My Most Important C++ Aha Moments (2006)
#10I love C and Objective-C. I can't stand C++. Is that common among programmers?
The more I learn C++, the more I can't stand it. Its ever-increasing complexity keeps being a distraction from the actual problem you're trying to solve.