What is an easy way to learn C plus plus?

Answer 1

Simplest but possibly the hardest way to learn: 1. Buy a book that can teach you how to use C Programming language 2. Get a program to process C programming language in, so as to have practical experience.

Answer 2

There is no easy way to learn C++. Its like any other computer language. You have to put the effort into learning it. You read the book and/or listen to the teacher, you do the exercises, you write code, you debug code, you practice, practice and practice. You cannot do this by just reading and listening - you must reinforce the lessons by real practice. Oh, and did I say practice?

Just to give you a perspective, I'm a C++ master. It comes easy for me, but that's because I've got 20 years of practice doing it, and nearly 20 years in other languages before that. That does not mean it will take you 20 years, but my point is that it will probably take you more than 2 weeks, or even 2 months, unless you are some kind of genius. Sorry, but that is the way it is.

Answer 3

You can learn C++ at school, college or university. Or you can teach yourself. However, the learning curve is steep so it's best to learn at least one other language first. Basic is good for absolute beginners, but an object-oriented language such as Java would be better.

Answer 4

The easiest way is to learn C++ first. The C language was designed to map very closely with the underlying architecture, but we humans prefer to work at a much higher level of abstraction. While low-level abstractions do give the programmer a great deal of control over the resultant machine code, the programmer has to constantly think in terms of the machine rather in terms of the problem, and it's that attention to detail that makes C a frustratingly difficult language to work with. Worse, C does not actively encourage good programming practices and we inevitably take advantage of this, taking shortcuts that can often leave our code brittle and difficult to maintain.

The same can be true of C++, to a lesser degree, however the higher-level abstractions provided by resource handles and smart pointers allow us to produce high-quality code with little to no cost in terms of performance and resource consumption. This, in turn, allows us to produce quality machine code much more quickly.

When programming, managing low-level resources is one of the hardest concepts we have to deal with. Whenever we allocate a resource we must keep a handle on it and that handle must outlive the resource it refers to. But a handle does not "own" the resource it refers to and this makes it difficult to manage shared resources, because we inevitably create many handles to the same resource. If we release the resource through one handle, every other handle to that resource is immediately invalidated, and there's no way to tell how many other handles there might be. The onus of responsibility lies entirely upon the programmer to keep track of the resource and, in particular, the resource "owner".

C++ doesn't suffer these problems because we can use resource handles that either own the resource outright or hold shared ownership over the resource. If a handle has outright ownership over a resource and falls from scope, the resource is released automatically. But a shared resource handle only releases the resource when it is the only remaining handle referring to that resource. Either way, the onus of responsibility over the management of that resource lies entirely with the resource handle, and thus with the language, not the programmer. Handles with outright ownership come at no additional cost, but while shared resource handles do have a cost, manually managing shared resources has a far higher cost.

Error-handling is another area that can be extremely difficult to keep a lid on in C. It is not unusual for the majority of code in a program to be entirely dedicated to handling errors. The problem with errors is that the point at which an error is detected is not always the best place to actually deal with it, which means we must pass information about the error from one place to another, and this is rarely done in a consistent manner. The C standard library is no exception; some functions return an error code while others set a global error variable. C++, on the other hand, encourages us to use a global exception-handling mechanism. By following good programming practices, we ensure that when an exception is thrown, all resources allocated up the point when the exception was detected back to the point where the exception can be handled are released, automatically. This gives us certain guarantees about the machine's "state" at the point where the exception can be handled, thus minimising the amount of manual cleanup we need to perform -- to the point we often need do nothing more than log the exception and (in some cases) notify the user. Again, this facility doesn't come at no cost, but the alternatives aren't free either.

Although it's fair to say that C++ "holds your hand" far more than C does, this does not mean to imply you are any less in control over the resultant code. All it means is that we don't have to worry about all the low-level stuff that can be easily handled as efficiently, if not more efficiently, by the language itself. But if we really need to get our hands dirty and deal with the low-level stuff, we can do that as well. The difference is we only do that when we have to. With C, we have to do it all the time, and low-level coding is nothing if not tedious -- and that alone greatly impedes our ability to learn.

Once you have learnt C++, you will find very few occasions where you actually need to resort to a lower-level language like C. But when you attain the level of ability where you can identify the specific problems in C++ that can only be addressed by C programming, you will already have the skills required to use C, but without having spent any time learning it from scratch. Remember, C++ evolved from C. It doesn't replace it entirely, but it does make it very much easier to work with. And things that are easy to work with are easier to learn.

Answer 5

Based on your question, I think you should work on learning English first. C language should come second, but do not try to learn it quickly, or you will wind up being as bad in C language as you are in English.

Answer 6

Look up a tutorial until you find one you like, or look in the computers/programming section of a bookstore/library.

Answer 7

Study the following book...

Let us C by Yashavant kanetkar.

The book is easy to learn.

Answer 8

"The C Programming Language" is a well-known computer programming book written by Brian Kernighan and Dennis Ritchie and is probably still the fastest and best way to learn C.