2 ms·
Except he doesn't know his FP, e.g. he doesn't know about TCO and how you can use that to avoid having recursion blow the stack. WRT to 2, your scoping discipl
by hga 17y ago
Except he doesn't know his FP, e.g. he doesn't know about TCO and how you can use that to avoid having recursion blow the stack.
WRT to 2, your scoping discipline is pretty orthogonal to your typing discipline. E.g. dynamically typed mainline LISP was dynamically scoped before Common Lisp adopted Scheme static scoping. And I'm sure there are dynamically scoped statically typed languages out there (if I ever learned about one, I would have tried to forget it as soon as possible (worst of both worlds)).
- froydnj 17y agoFinding a dynamically scoped statically typed language would be quite a trick: dynamic scope doesn't seem to have caught on outside the Lisp community. (I remember reading academic papers (separately for C++ and Haskell) that tried to explain why you would even want dynamic scoping and "look, wow, here's how to implement it.")
- jbert 17y agoIt's obviously not statically typed, but Perl has dynamic scoping (and that was the preferred way to have a local variable in perl4, before lexically scoped vars were introduced in perl5). Whether perl is part of the lisp community is another matter :-)
- shaunxcode 17y agoExactly - his point is that he doesn't care how map is implemented but really it should be a matter of not caring how recursion/tco is implemented so long as it does not blow the stack.