Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    What you say is true, but not relevant because as the programmer it's not your decision whether to inline or not. You put the keyword, you might or might not get your functions inlined. You don't put the keyword, you still might or might not get them inlined. It's pointless to have ANY rules for when you put the keyword, what with the compiler being the one actually making the decision. Commented Jan 19, 2011 at 15:05
  • How isn't this relevant if it says exactly the same as you? There are no simple answers. Commented Jan 19, 2011 at 15:10
  • It's not relevant because it doesn't answer the OPs question. He's not asking "what does inline do", he's asking "whats the point". And your answer just reiterates what we all already know about inline. Commented Jun 11, 2011 at 19:46
  • @Davor: "What's the point?" doesn't adhere to the FAQ, so I'm answering the questions posed within the question. I'm telling the point of inline by reiterating the knowledge as the OP seems to miss a part so which is the core reason why he doesn't get the point. For one to get a point he needs to have an understanding of what's beneath that point... Commented Jun 11, 2011 at 19:50
  • Why the hell wouldn't it adhere to the FAQ? Standard describes syntax and semantics of inline keyword, and OPs question is what is the purpose, when should it be used, what problems is it supposed to solve? I don't see how that doesn't adhere to the FAQ. Commented Jun 11, 2011 at 22:00