Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pg 82 (pdf ) Closures and partial Application - why anonymous subroutine? #152

Open
legrady opened this issue Feb 28, 2011 · 1 comment
Open

Comments

@legrady
Copy link

legrady commented Feb 28, 2011

On pg 82 of the pdf version, Closures and Partial Application applies default arguments to a routine by invoking it from another routine. But making it an anonymous routine assigned to a variable is irrelevant to the topic. If anything, the addition of a de-referencing arrow between variable name and argument list confuses the topic

@chromatic
Copy link
Owner

I'm not sure how to explain partial application without using higher-order functions. Certainly you can perform partial application and install the results in a namespace, but you lose some genericity that way.

By this point in the chapter, I hope people understand closures well enough that closing over parameters to another function is sufficiently clear.

I wonder if I'm missing your point though (or if my edits to the second edition have rendered it moot). If so, can you clarify?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants