What book in 2012?

[Kevin1230]

I want to learn C, C# and C++ lol,

which book do you think I should get, can I get all these in one book, or which one do you think I should learn if I want to code a game and will be quite easy?

please help.

[Jackolantern]

That will be at least 2 different books (C# in one, C/C++ possibly in one, but probably not). No sane author would try to teach more than one language in one book, and really, no one should try to learn multiple languages at once either. You will just end up confusing yourself horribly, and they will all morph into one huge language in your head.

I would suggest learning C# first, particularly if that would be the first language you are learning. It is much clearer than C/C++. It also teaches OO in a much more structured way. If you are a new programmer, I would suggest Wrox Beginning Visual C# 2010. If you are an experienced programmer (and I do mean experienced) wishing to add these other languages, I would suggest Pro C# 4 and the .NET Platform, which is basically required reading for anyone wanting to do serious C# work (eventually at least, because this book will lose most beginner programmers by the end of the Introduction). If you are dead-set on going for C++, then I suggest Ivor Horton's Visual C++ 2010. It gives you the benefit of learning ANSI C++ and C++/CLI (managed C++ for .NET) at the same time. Most professional C++ development is done in Visual C++ anyway.

[hallsofvallhalla]

I agree C# and I have yet to find a really good book.

[Jackolantern]

Seriously? There are more C# books than any other language right now (.NET is over 50% of what Apress does, and they are a major leader in tech books). I guess if you have specific requirements from it, I could see that, but if you are just wanting a general book for an experienced developer, it is hands-down Pro C# and the .NET Platform by Troelson. It is about as in-depth and complete as you can get, you can pick and choose what you want to read in it (it is gigantic, so cover-to-cover isn't likely for most people), and Troelsen is an absolute master of .NET.

[hallsofvallhalla]

well I did say good book, I just haven't found one but I haven't tried them all

[Jackolantern]

Then Pro C# by Troelson is the one to try! It is a must-read for every C# developer. Some of the things in there, such as Assembly programming, you really don't get from any other book I have read.

[Still]

I would suggest Wrox Beginning Visual C# 2010.

Nice book. Helped me a lor while studying. Even in our university professors give us links to this book. Funny, isn`t it?

[Xaleph]

Why use a book if you can do it yourself? The best way to learn it is to just dive in! You`ll run in to errors while you didn`t know they exist, so you`ll start looking for solutions etc, that`s so much fun. That way you learn how to program it. Start small, use C#, create some WPF applications, a calculator, a text editor, that stuff, then move on to the more "advanced" stuff.

Also, in perspective, maybe it`s best to learn C++ first. It teaches both procedural programming as well as OO. It can do both. Jack will dislike me for saying this but C++ is also a lot faster on runtime ( if you use the right compiler + compiler options..... .. ) So if you want to learn how to program fast, try C++.

C is a way out of date, well.. not per se, but the differences between C and C++ are small in a way that C just doesn`t offer objects, and it handles pointers differently, but really, that`s information that`s not relevant right now. Well, unless you want to program fast in that case, C would be the "better" choice.

Oh well, i`m drunk, if possible, ignore my post..

[Jackolantern]

I like books because for one, while I don't remember 100% of everything in a read-through, it ingrains in my head where the info is I need when I need it, and it is quick to open the book and reference material as needed. And for two, books are much, much more in-depth than tutorials or just simple solution posts. In .NET for example, by reading Pro C# and .NET Platform, I know why the CLR is setup the way it is, the ideas behind it, and how best to work along side it. I also know how to stay CLS compliant while writing an application, which is something that is never hinted to the in the IDE or through any warnings. That gives you the benefit of interoping with other .NET language assemblies and COM components later, if needed. But if you just tear into it, you will have no idea what the CLS is, or what benefits staying CLS compliant brings you.

Of course, really learning to use a language is not something that is done in a book. You will have to set it down and "tear into it" as you say You will get errors, even on things that were told to you by the book, simply because you can't remember it all. But at least for me, I feel I have gotten to a workable stage faster and made up the time I spent in the book compared to just firing up the IDE and getting started with no knowledge of what I am doing. But that is me, and maybe not everyone's experience. Plus, I just like reading tech books Maybe some people see reading them as a chore, but I enjoy it, and almost always have my head stuck in one on my off-time.

As far as C++ goes, I have nothing against admitting C++ is faster, because it is lol. Even C++/CLI is faster in the .NET runtime because no GC is running in the background (even though it pulls very close in the CLR with C++/CLI). There really isn't a managed code platform available that can match speeds achieved by a highly-skilled native language programmer. But again, those gaps are pulling extremely close these days, and in some cases, native code can even be slower since the runtime can compile on demand as needs and the platform suits, which natively compiled applications cannot.