About the bug(or issue) I mentioned before on cljs.core.async/timeout.
Several days ago, I have tried core.async and then got sucked... Google gave me two links: . "cljsbuild :simple optimization breaks cljs.core.async timeout on Node.js" [1] . "ASYNC-110 0.1.346, using >! crashes with no method 'setTimeout', when targeting node" [2] none of them could solve my problem(at that time)... So I worried about the support on nodejs: . there are much fewer people use clojurescript on nodejs than on browsers, isn't it? . Is the bug still exist after one year? . Is there someone use it seriously? and then came here for some help. After got more familiar with clojurescript, I realized that ASYNC-110 fully described(and gave several working solutions!)[3] this issue. But if "goog.global" was used before "goog.global = global"(the solution used in clojurescript[4]), the same problem will occur. This is the exactly situation I have encountered several days ago: I wrote '(go (<! (timeout 1212)) ...)' in top level. Now, with the troubleshooting tips(externs, pseudo-names and pretty-print, source map, ...) I have learned these days and positive experiences heard from here, I have more confidence than before and will try more on clojurescript+nodejs. [1]: https://groups.google.com/forum/#!topic/clojurescript/5yrg7T2wSz8 [2]: http://dev.clojure.org/jira/browse/ASYNC-110 [3]: http://dev.clojure.org/jira/browse/ASYNC-110#comment-37658 [4]: http://dev.clojure.org/jira/browse/ASYNC-110#comment-37793 -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/clojurescript.
