When to stop?

So, while learning C++ from the stroustrup's book i often wandered this.

At some point of the book, "inline" keyword is introduced in the book, it is described a little with no examples.

So, should i just read the text about inline from the book, understand the text and stop there?

Or should i for example try and google "inline" keyword to see what more information can i find out about the topic? When exactly should i stop learning about the "inline" keyword in this case?

Is it best to just remember the basic idea of inline, and when in the future you need something like that, you just dig out documentation and read it then? The point is to know that something exists, and the details aren't that important?

I don't think that there is any absolute correct answer to this question. It really depends on your learning style and what strikes you at the moment. Do what works best for you; mix and match if you will.

In simplest terms, inline functions are meant to replace #defines.

I stopped using inline b/c there is no guarantee the compiler will or will not inline your code. The process to go through to figure out if the compiler will or will not inline your code is complex and varies from compiler to compiler. And on a modern processor the benefit between inline and non-inline may not be worth the hassle.

Quote:

---

Originally Posted by Bubba

I stopped using inline b/c there is no guarantee the compiler will or will not inline your code.

---

Hehe, my workmate uses the inline keyword on member function definitions to separate private from public member functions. Without looking back at class body, he can tell which member functions are private or public (his private functions get the inline keyword). That's how much he regards the inline keyword. :p