They are not exactly equivalent though. It is not possible to completely abstract away state changes with objects. You always end up with at least two calls that you have to keep track of.
foo.DoSomething()
... // remember not to return
// without foo.Done() called
// (EDITed for clarity:
// foo is the state, that changes,
// so you have to keep track of
// its changes)
foo.Done()
DoSomething (func(){
... // don't have to remember
// a thing, no side-effects,
// equivalent of .Done() is
// called afterwards for you
})
DoSomething(func() { ... })
DoSomething(new Runnable() {
public void run() { ... }
});
class MyAction implements Runnable {
public void run() { ... }
}
DoSomething(new MyAction());If you're considering a language deficient of functions then we can take advantage exactly of the idea that objects can embed functions by having a "callable" thing.
foo#doSomething (object
method call : unit -> unit =
...
end)