Gambit v4.5.2 OSX 10.5
Of course, I do know that x should not be evaluated. For that have to type (x 3). But its still annoying, and very unnecessary. In DrScheme/PLT I get a: > x #<procedure:x> Explicitly telling me its a procedure.
Gambit v4.5.2 OSX 10.5
Of course, I do know that x should not be evaluated. For that have to type (x 3). But its still annoying, and very unnecessary. In DrScheme/PLT I get a: > x #<procedure:x> Explicitly telling me its a procedure.
However, a segfault is really not acceptable. I'll file a report for this.
[1] http://www.iro.umontreal.ca/~gambit/doc/gambit-c.html#Debugg...
Relevant section: "Note that some special forms (define in particular) can only be evaluated in the global interaction environment."
The crash was caused by printing the value of the procedure in the nested REPL. Using define in nested REPLs works, but you'll get a warning about it.
You're not at the top level of the repl, for some reason, defining things at a lower nesting level of the repl sometimes produces crashes, it's annoying yes, but it's not a huge disaster :)
if you use ",t" to get back to the top level after an error, you shouldn't see those crashes.