How to explain callbacks in plain english? How are they different from calling one function from another function?

by

I am going to try to keep this dead simple. A “callback” is any function that is called by another function which takes the first function as a parameter. A lot of the time, a “callback” is a function that is called when something happens. That something can be called an “event” in programmer-speak.

Imagine this scenario: you are expecting a package in a couple of days. The package is a gift for your neighbor. Therefore, once you get the package, you want it brought over to the neighbors. You are out of town, and so you leave instructions for your spouse.

You could tell them to get the package and bring it to the neighbors. If your spouse was as stupid as a computer, they would sit at the door and wait for the package until it came (NOT DOING ANYTHING ELSE) and then once it came they would bring it over to the neighbors. But there’s a better way. Tell your spouse that ONCE they receive the package, they should bring it over the neighbors. Then, they can go about life normally UNTIL they receive the package.

In our example, the receiving of the package is the “event” and the bringing it to the neighbors is the “callback”. Your spouse “runs” your instructions to bring the package over only when the package arrives. Much better!

This kind of thinking is obvious in daily life, but computers don’t have the same kind of common sense. Consider how programmers normally write to a file:

fileObject = open(file)
# now that we have WAITED for the file to open, we can write to it
fileObject.write("We are writing to the file.")
# now we can continue doing the other, totally unrelated things our program does

Here, we WAIT for the file to open, before we write to it. This “blocks” the flow of execution, and our program cannot do any of the other things it might need to do! What if we could do this instead:

# we pass writeToFile (A CALLBACK FUNCTION!) to the open function
fileObject = open(file, writeToFile)
# execution continues flowing -- we don't wait for the file to be opened
# ONCE the file is opened we write to it, but while we wait WE CAN DO OTHER THINGS!

It turns out we do this with some languages and frameworks. It’s pretty cool! Check out Node.js to get some real practice with this kind of thinking.

More Related Contents:

  1. “Parameter” vs “Argument” [duplicate]
  2. Understanding how recursive functions work
  3. What is the difference between a “function” and a “procedure”?
  4. Arguments or parameters? [duplicate]
  5. What’s the difference between a method and a function?
  6. Table name as a PostgreSQL function parameter
  7. What is a callback function?
  8. What’s the difference between faking, mocking, and stubbing?
  9. Define table and column names as arguments in a plpgsql function?
  10. Is there a way to use two ‘…’ statements in a function in R?
  11. What decides if a value is returned from a PowerShell function?
  12. How to alias a function name in Fortran
  13. How to profile methods in Scala?
  14. jQuery Plugin: Adding Callback functionality
  15. Return a list from the function using OUT parameter
  16. “Identifier Expected” or “Invalid Prototype” when implementing a scripted constant in Inno Setup
  17. Exporting a function in shell
  18. D3 Key Function
  19. What is an opaque value in C++?
  20. Callback function tkinter button with variable parameter [duplicate]
  21. What is opinionated software?
  22. Haskell operator vs function precedence
  23. Scala Functional Literals with Implicits
  24. Does dart support operator overloading
  25. Return multiple values from a function in swift
  26. Why can’t ‘kotlin.Result’ be used as a return type?
  27. How to evaluate functions in GDB?
  28. Matlab ode45. How to change a parameter inside it while calling it?
  29. How do you strip the unit from any number in SASS?
  30. In R, what exactly is the problem with having variables with the same name as base R functions?

Leave a Comment