Now, let me just conclude with a, with a, a, a nice new feature in
C++11, and that's the introduction of the term final,
contextually, to indicate that you don't want any further inheritance.
Again, it's a way of announcing objectives.
It's a way of maintaining control of your software.
You can always retract that, but you don't necessarily.
You may want to design something, for its own
purposes and not have anything that needs further development.
It can allow
the compiler to be in some ways more efficient.
If you know that a class doesn't have any ability
to be inherited from. So, here is that feature.
And here's where it shows up syntactically.
This says the 3d point is going to be by itself a final.
Nothing is going to derive for 3d point. That's a unique thing.
You might say in the taxonomy something
like a platypus would be an endpoint, and you're
not going to be sub-categories, derivative categories and platypus.
Again its contextual keyword, it's sort of a little tricky,
if you want (though it's probably not a good practice)
final can be used as an ordinary identifier elsewhere in your program.
I wouldn't recommend it.
I would stay away from anything that has special meaning.