Skip to content
Prev 51209 / 63424 Next

Changed behaviour when passing a function?

On 22/10/2015 5:44 PM, Gabriel Becker wrote:
It comes down to the order of operations:  we need to bind something to 
FUN, and we need to look up a function named FUN.  Since the binding 
comes first, it fails.  If it happened in the other order: look for a 
function named FUN,
find an unresolved binding to "round", look in the caller frame for a 
function named round, we wouldn't get the error.  But that's not how we 
do it.

Duncan Murdoch