> functions and variables live in different namespaces, so you could assign 4 to foo and then call it.
The two namespace approach makes it harder to assign 4 to foo and then call it, so I don't understand this comment.
You can assign 4 to foo and try to call it in a language that has one namespace.
;; Scheme, one namespace:
(let ((foo 4))
(foo) ;; oops
;; Common Lisp, two spaces:
(let ((foo 4))
(foo) ;; still calls the foo function,
;; not related to or shadowed by the above variable.
(funcall foo)) ;; oops
The usual valid complaint about two namespaces is that funcall is required all over the place in code that works with higher-order functions, which uglifies the code, and that an operator like (function foo) or its abbreviation #'foo is required to lift references to functions as values instead of just writing foo, which likewise uglifies code.
The two namespace approach makes it harder to assign 4 to foo and then call it, so I don't understand this comment.
You can assign 4 to foo and try to call it in a language that has one namespace.
The usual valid complaint about two namespaces is that funcall is required all over the place in code that works with higher-order functions, which uglifies the code, and that an operator like (function foo) or its abbreviation #'foo is required to lift references to functions as values instead of just writing foo, which likewise uglifies code.