Back to General and Gameplay Programming

Unnecessary C++ features?

null_pointer · 2000-07-18T17:59:18

I started this thread so that if anyone can think of an unnecessary feature in C++, something they do not understand how to use very well, or anything different between C and C++ that you could post here and someone might reply and explain it. Perhaps there are unnecessary features in C++. Perhaps C++ is worse than C. We''ll find out if we keep an open mind, right? I''ll try to answer what I can, but keep in mind I don''t know everything! There are other people here who know quite a bit more about C++ and the assembly it typically generates - I hope they''ll reply to this post. (I hope to avoid the tension of C vs. C++ posts, and make this post a bit more educational. Rather than saying "C is worse than C++" it would be good to see whether C++ really measures up as a language by itself. ) DISCLAIMER: I AM NOT GOD. DO NOT EXPECT ME TO BE PERFECT. Oh, before I forget! I''m looking for things like: C++ keywords (like if, else, etc.) STL classes/functions (like auto_ptr, list, etc.) Features that are not keywords (like operator overloading) C++ syntax (like "x += 7") I don''t want discussion about OOP vs. structural - it''s just too vague. Or programming methodology wars. Just the C++ language. You could ask about the class and virtual keywords if you want, though. Happy Coding! - null_pointer Sabre Multimedia

General and Gameplay Programming Programming

Started by null_pointer July 13, 2000 07:53 AM

70 comments, last by null_pointer 23 years, 9 months ago

Wilka

122

July 17, 2000 05:18 PM

quote:
Original post by foofightr

Maybe you haven't heard, but C doesn't have constructors.

C doesn't allow to create variables anywhere either, but since this is a C++ thread it doesn't matter

The example was in response to your statement:

quote:
The only use I can see of this C++ feature (declaring vars virtually anywhere) is that it helps code readability

Which is true for basic types, but most C++ programs have user defined types with sometimes complicated constructors.

quote:
However, you do have a point about the "slow resources" stuff. I wouldn't do things this way however.

I almost always use a construct to allocate resources (memory, files, etc) and free them in the destructor. It keeps my code exception safe and avoids any messy 'tidy up' code at the end of a function.

Edited by - Wilka on July 17, 2000 6:20:09 PM

null_pointer

289

Author

July 18, 2000 05:59 PM

Anonymous Poster:

I said that the compiler should remove a function from the final binary if it was never referenced (meaning called or its address taken).

Try this in a C++ compiler:


/////////////
// in one.cpp:
void myfunction1()
{
}

/////////////
// in two.cpp:
void myfunction2()
{
myfunction1(); // error
}

void main()
{
}

Since in C++ you must prototype all of your functions before using them in other modules, it is as if all functions are static until prototyped, no? Or perhaps I am misunderstanding the use of the C ''static'' keyword?

- null_pointer
Sabre Multimedia

Unnecessary C++ features?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Unnecessary C++ features?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines