Clojure

Details

Type:
Defect

Status:
Closed

Priority:
Minor

Resolution:
Declined

Affects Version/s:Release 1.2

Fix Version/s:
None

Component/s:
None

Labels:

None

Description

From the new-to-Clojure but very excited about the language perspective, this seems simply seemed like low-priority-but-should-be-fixed-eventually bug. When I invoked ; as a function name by accident, I found that the REPL simply hung.

Activity

The semicolon comments out the rest of the line, including the close paren. The REPL then blocks waiting for the expression begun with the open paren to be completed with an (uncommented) close paren. If you type a second close paren on and press Enter, I think you'll see the REPL was not hung but just waiting for more input.

I don't know if it would be useful to provide a different prompt instead of no prompt at all when the REPL is waiting for the conclusion of an expression, but in any case that would be a feature request.

Chouser
added a comment - 26/Jan/11 12:30 AM The semicolon comments out the rest of the line, including the close paren. The REPL then blocks waiting for the expression begun with the open paren to be completed with an (uncommented) close paren. If you type a second close paren on and press Enter, I think you'll see the REPL was not hung but just waiting for more input.
I don't know if it would be useful to provide a different prompt instead of no prompt at all when the REPL is waiting for the conclusion of an expression, but in any case that would be a feature request.
The current behavior is as expected.