理解回调机制(国外英文资料).docVIP

理解回调机制 After the first pan, shallow to deep the truth but easier said than done, small details so often will give on entanglement, get dizzy dizzy, which callback is one of them, although reuse, but always do not understand the meaning of many books also speak obscure. It was not until long before I saw an article that I understood it more clearly. To sum up, the callback mechanism consists of two parts: the service executor and the service method maker. 1. service executives make service specifications first; 2. the service method maker then formulates the service manner according to the standard; 3. then the executor provides services in this manner. The callback function passes the function pointer as a parameter, so the specification is the parameter type of the agreed function, and the number of arguments. The article is as follows: The call (calling) mechanism has been used extensively since the assembly era: preparing a piece of ready-made code, the caller can jump to the starting address of the code at any time, and then return to the subsequent address of the jump when executed. CPU prepares ready - to - use call instructions for this purpose. When called, the stack can be pressed to protect the site, and the site address is ejected from the stack after the call is called so that it can be returned automatically. Borrow stack protection is really a wonderful scene of invention, it makes the callers and callees may not know each other, Yu Shicai became the function and components, we programming so relaxed and happy. If the selection of the greatest impact on mankind, after the fire and the wheel, I push the stack when the call. That said, this invocation mechanism is not perfect. The callback function is one example. A function like this is a delicious meal for the caller, whose cook is familiar with the diners, but thats not the case. For example, write a quick sort function for someone else to call, which must contain the size of the comparison. Heres th