title: Why is a function call called a "function call"?
body: <p>I know what a function call is. I know what it does. I've debugged it a lot. I do have <em>some</em> intuitive sense on why it makes sense to use the term "function call", but when it comes down to it, I can't explain this properly like I could with a <code>return</code> statement.</p>
  
  <p>For example, with a <code>return</code> statement the answer is: it's called a "return" because you return to where you came from. You return to the line from where the function was called. So it makes sense why the end of a function (implicitly or explicitly) returns.</p>
  
  <p>I've noticed that for people who speak English as their native language this easier to grasp (especially with more obscure words such as "cache"). However, for people like me (Dutch, learned English through videogames and subtitled television), it's harder to grasp.</p>
  
  <p>I googled for this question, but I get all kinds of entries what a function call is and how it works. I associate the word "call" a lot with telephones, since that's what I use it mainly for in English.</p>
  
  <p>I asked a similar question on what the "de-" means in the word "dereference" here: <a href="https://stackoverflow.com/questions/35372786/what-does-the-de-prefix-in-dereference-mean-is-there-a-linguistic-explanation">What does the de- prefix in dereference mean? Is there a linguistic explanation for it?</a></p>