Callbacks, Synchronous and Asynchronous (2011)
blog.ometer.com
Callbacks, Synchronous and Asynchronous (2011)
1–4 of 4 posts
Re: Callbacks, Synchronous and Asynchronous (2011)
#2Terminology opinion: I'm not too fond of the term callback for "synchronous callback" as described in the post. First, it doesn't actually "call back", and secondly why not just use "function"?
Re: Callbacks, Synchronous and Asynchronous (2011)
#3Terminology opinion: I'm not too fond of the term callback for "synchronous callback" as described in the post. First, it doesn't actually "call back", and secondly why not just use "function"?
lambda, callback, function, closure, anonymous function, thunk
It's all pretty much the same.
I like "synchronous callback" because this tells you two things:
1. it's synchronous, no need to add memory barriers
2. it _is_ a callback, it is called after the fact.
Re: Callbacks, Synchronous and Asynchronous (2011)
#4Terminology opinion: I'm not too fond of the term callback for "synchronous callback" as described in the post. First, it doesn't actually "call back", and secondly why not just use "function"?
lambda, callback, function, closure, anonymous function, thunk It's all pretty much the same. I like "synchronous callback" because this tells you two things: 1. it's synchronous, no need to add memory barriers 2. it _is_ a callback, it is called after the fact.
Could also add "continuation" to the list perhaps, from continuation passing style (CPS). But that might not be a callback, as it never really goes back, but always goes forward.