Clojure

(;) causes repl to hang in Clojure 1.3-0-alpha3 on Mac OS X 10.6.3 Intel

Details

  • Type: Defect Defect
  • Status: Closed Closed
  • Priority: Minor 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.

jaten@host151:~$ uname -a
Darwin host151.wifi.epochcoffee.com 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386

jaten@host151:~$ java -server -cp "/home/jaten/pkg/clojure/jars/*" clojure.main
Clojure 1.3.0-alpha3
user=> ( ; causes REPL to hang forever...???

Also happens in clojure 1.2.0. I didn't try any other versions.

Activity

Hide
Chouser added a comment -

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.

Show
Chouser added a comment - 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.
Chouser made changes -
Field Original Value New Value
Status Open [ 1 ] Closed [ 6 ]
Resolution Declined [ 2 ]

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: