Internal procedures are not directly exposed to interpreter environment

[justinethier]

Procedures that are built into the evaluator are not directly exposed. For example, in bigloo the apply function can be referenced directly:

1:=> apply
#<procedure:295740.-3>
1:=> (procedure? apply)
#t

On husk this currently results in an error:

huski> apply
Getting an unbound variable: apply
huski> (procedure? apply)
Getting an unbound variable: apply

Many functions are affected, including:

• apply
• call-with-current-continuation
• call/cc (which should be part of stdlib with this change)
• others?

[justinethier]

Moved the following functions out of eval:

                ("apply", evalfuncApply)
              , ("call-with-current-continuation", evalfuncCallCC)
              , ("call-with-values", evalfuncCallWValues)
              , ("eval", evalfuncEval)
              , ("load", evalfuncLoad)

Unfortunately it is much more difficult to move set! style functions out of eval, due to the fact that these functions need unevaluated symbols in order to get/set a variable.

[justinethier]

Moved some set! based functions into stdlib as macros, however the rest of these functions (6 total) will have to remain for now.