I've been working as C (not C++) programmer a few years back, and since then been working in QA.
Finally I got a new job as (R&D) RT Embedded C++ programmer, which I'll start in a month from now.
I'm following a C++ course book I got, and of course using the web (I avoid reading a book due to the short time).
I'm left to learn the main OO subjects - Inheritence, Polymorphism, Virtual functions, Templates (and also Exceptions handling which is not really OO concerned)
My main concern is how to get also a practical experience in addition to studying, during this short time.
Could you offer me advises how to practice Object Oriented Design?
Additionally, if you have any tips to share for how to be a good Developer in general, and good C++ Programmer.
I'm left to learn the main OO subjects - Inheritence, Polymorphism, Virtual functions, Templates (and also Exceptions handling which is not really OO concerned)
I think templates have less to do with OO than exceptions do. Anyway, learning the above is quite easy (Google and this forum will help with that), the difficulty will be applying that knowledge (and that's the whole problem with OOP) to painstakingly designing your OO program.
Templates are for generic programming. Exceptions are for error handling and I don't know many programmers that actually use them. Some of the newer programmers claim they are just as bad as OOP, but I think it is a bad idea to ignore any feature of C++.
Now Inheritance, Polymorphism and Virtual functions are OO.
Templates are for generic programming. Exceptions are for error handling and I don't know many programmers that actually use them. Some of the newer programmers claim they are just as bad as OOP, but I think it is a bad idea to ignore any feature of C++.
You must not know a lot of programmers. I use exceptions, and I've seen multiple projects that use them as well.
@Lumpkin
As always you missed the point of that post, which was
ME wrote:
but I think it is a bad idea to ignore any feature of C++.
As for your question, yes I do know a lot of programmers. The only ones I know that like exceptions are system programmers. The game programmers I know prefer to using functions that return either bool or enumerations and if statements to check for errors while the ones that prefer to do apps use cerr, assert, and exit.
If it wasn't for the programmers I do know I would have walked away from programming a long time ago and not being ready to celebrate my 20th year doing it.
As for your question, yes I do know a lot of programmers. The only ones I know that like exceptions are system programmers. The game programmers I know prefer to using functions that return either bool or enumerations and if statements to check for errors while the ones that prefer to do apps use cerr, assert, and exit.
Strange... 90% of recent C++ source I've seen uses them.
Apparently the 13 year old knows many professional programmers...
Yeah, also 90% for all we know could be 9 out of 10 source code so that number with no context proves nothing to his point.
As for all the reporting, I'm guessing either troll or thread derailment because of the nitpicking over exceptions which adds no useful information to help the OP with his question.
Catfish666 gave him links which answered his questions, I clarified what templates and exceptions were used for, and Mats recommended doing projects that stress OOD. Outside of that the other posts have been fluff and no real substance to this thread.