通常，我们将变量发送给函数:function1(var1, var2)。

假设，你想在它被作为参数给出之前处理它:

这是一种回调类型，其中function2执行一些代码并将变量返回给初始函数。

编辑:回调这个词最常见的意思是一个函数作为参数传递给另一个函数，并在稍后的时间点被调用。这些思想存在于允许高阶函数的语言中，即将函数视为一等公民，通常用于异步编程中。onready dosomething()。在这里，只有当它准备好了，事情才会发生。

通常，我们将变量发送给函数:function1(var1, var2)。

假设，你想在它被作为参数给出之前处理它:

这是一种回调类型，其中function2执行一些代码并将变量返回给初始函数。

编辑:回调这个词最常见的意思是一个函数作为参数传递给另一个函数，并在稍后的时间点被调用。这些思想存在于允许高阶函数的语言中，即将函数视为一等公民，通常用于异步编程中。onready dosomething()。在这里，只有当它准备好了，事情才会发生。

A callback is a function that will be called by a second function. This second function doesn't know in advance what function it will call. So the identity of the callback function is stored somewhere, or passed to the second function as a parameter. This "identity," depending on the programming language, might be the address of the callback, or some other sort of pointer, or it might be the name of the function. The principal is the same, we store or pass some information that unambiguously identifies the function.

当时间到来时，第二个函数可以调用回调，根据当时的情况提供参数。它甚至可以从一组可能的回调中选择回调。编程语言必须提供某种语法，允许第二个函数调用回调函数，并知道它的“标识”。

这种机制有许多可能的用途。通过回调，函数的设计者可以通过调用所提供的任何回调来定制函数。例如，排序函数可能将回调函数作为参数，而这个回调函数可能是用于比较两个元素以决定哪个元素先出现的函数。

顺便说一下，根据编程语言的不同，上面讨论中的“函数”一词可能会被“块”、“闭包”、“lambda”等取代。

我很震惊地看到这么多聪明的人都没有强调“回调”这个词已经有了两种不一致的用法。

这两种方法都涉及到通过向现有函数传递附加功能(匿名或命名的函数定义)来定制函数。ie。

customizableFunc(customFunctionality)

如果自定义功能只是插入到代码块中，则您已经自定义了该函数，如下所示。

    customizableFucn(customFunctionality) {
      var data = doSomthing();
      customFunctionality(data);
      ...
    }

虽然这种注入的功能通常被称为“回调”，但它并不是偶然的。一个非常明显的例子是forEach方法，其中提供了一个自定义函数作为参数，应用于数组中的每个元素以修改数组。

But this is fundamentally distinct from the use of "callback" functions for asynchronous programming, as in AJAX or node.js or simply in assigning functionality to user interaction events (like mouse clicks). In this case, the whole idea is to wait for a contingent event to occur before executing the custom functionality. This is obvious in the case of user interaction, but is also important in i/o (input/output) processes that can take time, like reading files from disk. This is where the term "callback" makes the most obvious sense. Once an i/o process is started (like asking for a file to be read from disk or a server to return data from an http request) an asynchronous program doesn't wait around for it to finish. It can go ahead with whatever tasks are scheduled next, and only respond with the custom functionality after it has been notified that the read file or http request is completed (or that it failed) and that the data is available to the custom functionality. It's like calling a business on the phone and leaving your "callback" number, so they can call you when someone is available to get back to you. That's better than hanging on the line for who knows how long and not being able to attend to other affairs.

异步使用本质上涉及到一些侦听所需事件的方法(例如，i/o进程的完成)，以便当它发生时(且仅当它发生时)执行自定义的“回调”功能。在明显的AJAX示例中，当数据实际从服务器到达时，“回调”函数将被触发，以使用该数据修改DOM，从而重新绘制浏览器窗口。

回顾一下。有些人使用“回调”这个词来指代任何可以作为参数注入到现有函数中的自定义功能。但是，至少对我来说，这个词最合适的用法是异步使用注入的“回调”函数——仅在等待通知的事件发生时执行。

说白了，回调就是承诺。乔、简、大卫和萨曼莎拼车去上班。乔今天开车。简，大卫和萨曼莎有几个选择:

每五分钟查看一下窗户，看看乔是否出去了 继续做他们的事，直到乔按门铃。

选项1:这更像是一个轮询示例，Jane将被困在一个“循环”中，检查Joe是否在室外。在此期间简不能做其他事情。

选项2:这是回调示例。简告诉乔当他在外面时按她的门铃。她给了他一个按门铃的“功能”。Joe不需要知道门铃是如何工作的，也不需要知道它在哪里，他只需要调用那个函数，即当他在那里时按门铃。

回调是由“事件”驱动的。在这个例子中，“事件”是乔的到来。例如，在Ajax中，事件可以是异步请求的“成功”或“失败”，并且每个事件都可以有相同或不同的回调。

In terms of JavaScript applications and callbacks. We also need to understand "closures" and application context. What "this" refers to can easily confuse JavaScript developers. In this example within each person's "ring_the_door_bell()" method/callback there might be some other methods that each person need to do based on their morning routine ex. "turn_off_the_tv()". We would want "this" to refer to the "Jane" object or the "David" object so that each can setup whatever else they need done before Joe picks them up. This is where setting up the callback with Joe requires parodying the method so that "this" refers to the right object.

希望有帮助!

为了教授回调，你必须先教授指针。一旦学生理解了指向变量的指针的概念，回调的概念就会变得更容易。假设您使用的是C/ c++，可以遵循这些步骤。

First show your students how to use and manipulate variables using pointers alongside using the normal variable identifiers. Then teach them there are things that can be done only with pointers(like passing a variable by reference). Then tell them how executable code or functions are just like some other data(or variables) in the memory. So, functions also have addresses or pointers. Then show them how functions can be called with function pointers and tell these are called callbacks. Now, the question is, why all these hassle for calling some functions? What is the benefit? Like data pointers, function pointer aka callbacks has some advantages over using normal identifiers. The first one is, function identifiers or function names cannot be used as normal data. I mean, you cannot make a data structure with functions(like an array or a linked list of functions). But with callbacks, you can make an array, a linked list or use them with other data like in dictionary of key-value pairs or trees, or any other things. This is a powerful benefit. And other benefits are actually child of this one. The most common use of callbacks is seen in event driver programming. Where one or more functions are executed based on some incoming signal. With callbacks, a dictionary can be maintained to map signals with callbacks. Then the input signal resolution and execution of corresponding code become much easier. The second use of callbacks coming in my mind is higher order functions. The functions which takes other functions as input arguments. And to send functions as arguments, we need callbacks. An example can be a function which take an array and a callback. Then it performs the callback on each of the item of the array and return the results in another array. If we pass the function a doubling callback, we get a doubled valued array. If we pass a squaring callback, we get squares. For square roots, just send appropriate callback. This cannot be done with normal functions.

可能还有更多的事情。让学生参与进来，他们就会发现。希望这能有所帮助。