-XstartOnFirstThread causes silent exit.

2008-04-13T01:14:56Z

I was hoping to use Clojure to develop SWT applications on the Mac.

On the Mac, the SWT Display has to be created on the first thread, and in the Mac version of Java this can be forced using the "-XstartOnFirstThread" command line option.

Unfortunately, running...
java -XstartOnFirstThread -cp clojure.jar clojure.lang.Repl
... seems to simply return to the command prompt.

Note that running...
java -cp clojure.jar clojure.lang.Repl
... does start a REPL as expected.

(I have been able to use SISC to develop SWT applications, by adding -XstartOnFirstThread. It's not clear why this fails in Clojure.)

doc strings consistent naming (e.g., "doseq")

2008-02-27T16:17:42Z

Doc strings should use names that are consistent with argument lists. As an example, here are the docs for "doseq" in SVN 702:

user=> (doc doseq)
-------------------------
clojure/doseq
([item list & body])
Macro
Repeatedly executes body (presumably for side-effects) with binding-form bound to successive items from coll.
Does not retain the head of the sequence. Returns nil.
nil
user=>

The arguments refer to "item" and "list", the docs refer to "binding-form" and "coll". These should be brought into line in this case and in any other cases where they're not in agreement.

One might also consider a convention (as in emacs) where words that represent literals are distinguished somehow (as in all-caps) so they can be represented in some special way (as in italics) when the doc string is presented by a pretty printer.

For example:

user=> (doc doseq)
-------------------------
clojure/doseq
([item coll & body])
Macro
Repeatedly executes BODY (presumably for side-effects) with ITEM bound to successive items from COLL.
Does not retain the head of COLL. Returns nil.
nil
user=>

Recent changes to bugs

-XstartOnFirstThread causes silent exit.

doc strings consistent naming (e.g., "doseq")