Thought Leadership
Video about a C++ “flaw”
My latest video blog is now available. This time I am looking at an interesting aspect of C++, where there seems to be a small design flaw. You can see the video here or here:
Future video blogs will continue to look at topics of interest to embedded software developers. Suggestions for topics are always welcome via comment, email or social networking.
Comments
2 thoughts about “Video about a C++ “flaw””
Leave a Reply
You must be logged in to post a comment.
Interesting! I suppose I’d never really thought to wonder about that, so I’m glad you did and had the opportunity to ask about it.
I also just now learned that it’s possible to explicitly call a constructor or destructor (and that this was intentional), which removes my previous assumption that the reason for the “flaw” you mention was that they couldn’t be explicitly called. So, I learned something new — thank you!
@Brooks – You may have put your finger on what was in BS’s mind when the requirement for no return type was introduced. Maybe he wanted to make it clear that constructors/destructors could not be called explicitly, but later changed his mind.