Moving from C# to C++
-
Nickolay Karnaukhov wrote:
Books - are only books. Books are just reference and "swap storage". Most important is to start real project, join any opensource for example, and get all that experience.
But it's also important, especially with C++, to learn good practice which you will get from the better books.
Kevin
Kevin McFarlane wrote:
But it's also important, especially with C++, to learn good practice which you will get from the better books.
Sure it is! And you're absolutely right!
------------------------------------------------------------ Want to be happy - do what you like!
-
I already know C# and I'm trying to learn C++ (it seems to be more required by employers.) All the reference material I have on C++ is geared to learning from absolute basics and I get tired of reading about the difference between ++x and x++ etc (I still read it in case there happens to be something subtle that I wouldn't already know.) So can anybody recommend any good resources that are comprehensive, but won't re-cover stuff thats the same in C#? Thanks, Chris
Hi Chris - Those are some good responses you received. Effective C++ by Meyers is indeed excellent! Also an excellent book along those same lines is the "C++ Coding Standards" by Andrei Alexandrecu and Herb Sutter. The critical component is understanding the object model differences. C++ is based on deep copy (value model) semantics. Implies user defined object conbstruction, copy and assignment semantics (implies object identity preservation). C#/java is based on shallow reference semantics (everything is a reference to an object on the managed heap -- object identity is lost). C++ carries its servers type information "#includes" for compilation which affects how you structure code using well known OOD principles (Interface Segregation), (Dependency Inversion) so on an do forth which make use of object factories or whatever. c# uses metadata for compilation which is great. c++ uses rich memory model, static, stack, heap etc. i.e you determine object lifetime C# uses a more spartan model... all objects reside on managed heap... lifetime is non-deterministic. There's more of course... but in short, don't try to write C++ the C#/Java way because you'll get frustrated. Check out the following link for good content and book information: http://www.ecs.syr.edu/faculty/fawcett/handouts/webpages/CSE687.htm good luck, Mike
-
The best one that I found is http://msdn.microsoft.com/pt-br/library/ms235630.aspx#MtViewDropDownText have fun! :laugh:
-
C++ From The Ground Up (Third Addition) by Herbert Schildt, Osborne Publications If you are developing for Windows, read up on MFC until you get board and then study with Win32 and Win64 API's. There are several API Bibles available - all read about he same.
-
Not read Schildt myself but (although popular) he's widely detested by C++ gurus.
Kevin
-
"C++ FAQ" by Cline, Lomow, and Girou, second edition. Herb Sutter's books, "Exceptional C++", "More Exceptional C++", and "C++ Coding Standards" The "C++ FAQ" is excellent about explaining why things work the way they do in C++ so you'll get the subtle differences. "C++ Coding Style" is also excellent in the 'Do it this way because that way is going to hurt.' The Exceptional * books are more advanced, deeper dives into specific features.
-
I have found that companies doing 3D modeling, like CAD, use C++. But, beware of pointers. They can bite you badly. Under C#, they are managed for you. Under C++, you need to manage them. Learn about smart pointers. The BOOST C++ Libraries have really good smart pointers and make using pointers much like using C# references. (Go to: www.boost.org for more information.)
-
Hi, man! I wish to recommend You the Bruce Eckel's C++ books; you can download them free, and as I know, there was the whole standard C++ language described. The right studio supporting it is VS2005 or 2008; in Visual Studio 6, there is no full support for C++ language, for example, You can't use multiple templates as parameters in templates. So, try with Bruce Eckel's C++. You can find Eckel's site using google or like. Btw, I'm somehow impressed with Your expression that it seems C++ is more wanted by employeers than C#. Although personally I preffer C++ programming, I thought that C# was most wanted. OK, this is a nice news for me! Best regards!
-
In addition to others mentioned I also found the Wrox book Professional C++ and C++ Coding Standards by Herb Stutter and Andrei Alexandrescu helpful. If you want to apply to Windows, you can't go past Jeff Richter's Programming Windows via C/C++.
-
I'd strongly recommend the Learn C++[^] site, it does cover the basics but you can skip ahead to more interesting stuff. I found myself in the same position as you a few months back and this is how I got going. I'd also recommend at least skimming over the basics again as your likely to pick up subtle differences between the two languages and possibly remind yourself of things you may have forgotten. Book wise, I've got a copy of the C++ Pocket Reference Guide by O'Reilly (ISBN: 978-0-596-00496-5) which is great as a quick reference, I also picked up a second hand copy of Stroustrup's "The C++ Programming Language" which I don't use as much but is useful if your not sure why something is happening in a particular way. Once you get into it it's fairly good fun, some things will annoy you and you'll be longing for a C# project but then some things are actually easier in C++ (such as manipulating byte arrays).
-
you could try : www.freecomputerbooks.com/langCppBooks.html
-
I like "Thinking in C++" by Bruce Eckel. He assumess a reader working from C to C++, so it might be pedantic on OO concepts, but at least it won't spend much time on fundamental C syntax.
-
If you want something more advanced, an option are Herb Sutters books. A lot of the material from those books comes from http://www.gotw.ca/gotw/[^] Also if you want to read more than you ever cared about templates, C++ Templates The Complete Guide by Vandevoorde and Josuttis. To see how far templates can be taken, read Modern C++ Design, by Andrei Alexandrescu.
-
Hi Chris - Those are some good responses you received. Effective C++ by Meyers is indeed excellent! Also an excellent book along those same lines is the "C++ Coding Standards" by Andrei Alexandrecu and Herb Sutter. The critical component is understanding the object model differences. C++ is based on deep copy (value model) semantics. Implies user defined object conbstruction, copy and assignment semantics (implies object identity preservation). C#/java is based on shallow reference semantics (everything is a reference to an object on the managed heap -- object identity is lost). C++ carries its servers type information "#includes" for compilation which affects how you structure code using well known OOD principles (Interface Segregation), (Dependency Inversion) so on an do forth which make use of object factories or whatever. c# uses metadata for compilation which is great. c++ uses rich memory model, static, stack, heap etc. i.e you determine object lifetime C# uses a more spartan model... all objects reside on managed heap... lifetime is non-deterministic. There's more of course... but in short, don't try to write C++ the C#/Java way because you'll get frustrated. Check out the following link for good content and book information: http://www.ecs.syr.edu/faculty/fawcett/handouts/webpages/CSE687.htm good luck, Mike
Hi Mike,
Mike Corley wrote:
Those are some good responses you received
Yeah - with the number of things I will need to look at before deciding which ones to read first, I'm not sure I saved any time at all getting suggestions... I hadn't realised yet that C++ uses deep copy semantics - I think knowing this now will save me quite a bit of frustration! Thanks for taking the time to write such a complete answer. Thanks, Chris
-
It's easy - real languages are based on the endless struggle between flexibility and efficiency. In this case C, C++ is real languages. As long as Perl, PHP, Basic, Pascal, etc... All these languages were developed by developers for developers of students who are willing to be developers. In most cases these languages are developed by one, two or three bearded guys in old shabby jeans like Stroustrop, Richie or Wirth. They were (and are) scientists acted for good and with all good in their minds. In other hand we have not real languages - build by marketing departments with all these wise guys with one thing in their mind - "Attract as much developers as possible". This languages are designed by companies and their software frameworks. There's no soul in these languages as they weren't built by one, two or three bearded scientists. And in this list we have Java and C#. Javascrip, Actionscript could also be listed here as they are only some kind of derivatives designed for specific purpose. So final idea is - if something is designed by one bearded scientist - it will live much longer than shaved greedy hired servant. You can treat it in any way you want - it is joke and truth same time. Now you've got definition!
------------------------------------------------------------ Want to be happy - do what you like!
-
I'll third the Meyers book(s). They are on the shelves of every good C++ programmer I know. If you already know C# well I would go ahead and get the Meyers books whether you think you are ready or not. Then as you read them and if he talks about a topic you don't understand in C++, go back to a C++ reference to understand it. By the time you are done you will have a much deeper understanding of how to use the language than if you just read a primer etc. For a comprehensive reference I like the C++ In a Nutshell O'Reilly book by Ray Lischner.
-
c2423 wrote:
This is the second reccomendation for Stroustrup
It's a book you should have at some point, but I'm not sure it's an appropriate first C++ book. I wouldn't know what a good starting-point is these days though.
Kevin
-
The problem these days, especially in the Microsoft world is that you'll struggle to find pure C++ roles. It will be C++ and some .NET-based technology. Don't know what it's like in the *nix world though. Maybe C++ + Java + some scripting language?
Kevin
Yeah you can kind of see why though, there are very few projects that benefit from the speed or control over the system to warrant C/C++ - most software is just boring data entry stuff and it makes sense to use something like C# for maintainability and less chance of bugs caused by typos.