Poll: Do you know C?
31–40 of 208 posts
Re: Poll: Do you know C?
#32Re: Poll: Do you know C?
#33I used to know it very well. Now, not as much. Even when I wrote C++, I basically wrote "C, with classes."
Why write C-with-classes if you can just write C-with-structures-and-function-pointers instead?
Re: Poll: Do you know C?
#34but i know objective-c pretty well.
Re: Poll: Do you know C?
#35Re: Poll: Do you know C?
#36I know C(#), it counts right? ;)
Re: Poll: Do you know C?
#37I used to know it very well. Now, not as much. Even when I wrote C++, I basically wrote "C, with classes."
Why write C-with-classes if you can just write C-with-structures-and-function-pointers instead?
Re: Poll: Do you know C?
#38Re: Poll: Do you know C?
#39Earlier quoted context omitted.
Why write C-with-classes if you can just write C-with-structures-and-function-pointers instead?
What would be the advantage of doing that?
That's probably a really big one in terms of reliability.
Also, the weird C++ behavior of calling copy constructors in the most unexpected places can have a very detrimental effect on performance.
Personally, I think the nature of C++ class definition leads people down the primrose path of trying to provide all potentially useful methods, of which only a tiny fraction get used. Tons of dead code appears in most C++ projects.