How to explain method calls?

let's consider a small method:

int MyFunction(string foo, int bar)
{
  ...
}

and some calls:

MyFunction("",0)
int x = MyFunction(foo1,bar1)

How would you explain this to a non-technical persons? Has anybody a nice metaphor?

I tried to explain method calling (or function application) several times, but I failed. Seems I can't find the right words here.

Regards, for开发者_运维知识库ki

UPDATE: It is important for me to explain how the parameters are passed / matched.

---

(Highly non-technical solution)

It's like making an order:

• Calling the method = dialing the right number
• Passing the arguments = giving your details
• the method does is job
• Getting a return value = getting what you ordered

---

You could tell function is a process available into an object that could be called by other. Lets say "You" is an object with function "Work". Your "Boss" is the caller object. Your Boss then can call you to Work with different type (which is parameter).

In the end Your "Boss" can ask "You" to Work("encode this") or Work("check email") or Work("finish deadline"), etc.

---

How about delegating a task? Imagine you’re baking a cake and ran out of flour. Instead of buying some yourself you could just send your kid with instructions to buy flour. Input: money, output: flour.

---

It's difficult to understand the "method call" concept if you don't understand first the
flow of control.

A simple explanation is that methods, or routines, is a construct for packeting instructions
in order to reuse them and make the code more readable.
Calling a method, temporarily, switches the execution flow to that method.

---

C:: do(a ,b)

You are telling C to do something , given the condition a and b.

---

The best approach is probably to come up with a domain specific example which the person you are explaining to can relate to. If she is working with the post office, you should describe the function "send letter with this text to this recipient", where recipient is a parameter (containing the address) and message is the parameter for the textual content.

Parameter order is not important as long as you have a name for each parameter. Trying to explain why order is important in some arcane programming language is fruitless.

---

How about

• Calling a function: Ask the software to perform xxx task
• Returning value type function: Ask your software to perform xxx task and tell you the outcome of the operation
• Calling a function with param: Given X is this value and Y is thisvalue, ask your software to perform xxx task (and tell you the outcome of the operation)

---

Think of the system as a teller at a desk. To call a function you fill in a form to ask the system to do something, hand it to the teller. They go off and do the work, then hand you back a piece of paper with the result written on it. Depending on what you want the system to do, you pick an appropriate form.

The form for MyMethod says:

MYMETHOD REQUISITION FORM:
String _______
int    _______

This analogy can be extended in all kinds of ways. Wouldn't it be handy if the form told you what the purpose of the String and int were? That's where languages with named parameters come in.

For OO, instead of having one desk for the whole system, each object is its own teller, you hand a form to them, and in order to get the job done, they hand a lot more forms back and forth between each other. Etc.