I checked in a change this morning that fixes this.
On Wednesday, August 17, 2011 11:25:54 AM UTC-4, Mark McGranaghan wrote:
>
>
>
> On Jul 28, 4:50 pm, Anthony Grimes wrote:
> > Oh! I apologize. I was replying via the google interface and didn't
> realize
> > it wasn't quoting. Here is a link
Hi people! i am experimenting with clojurescript and node.js in windows too
and i cant to access public node.js vars like __dirname. I had to use (js*
"__dirname") but i think it would be neat that cljs.nodejs had all the
global vars of node.js
Thanks for clojurescript and keep on it!
--
You
On Jul 28, 4:50 pm, Anthony Grimes wrote:
> Oh! I apologize. I was replying via the google interface and didn't realize
> it wasn't quoting. Here is a link to the topic for
> context:https://groups.google.com/d/topic/clojure/ZyVrCxmOFTM/discussion
>
> I've also filed a bug here:http://dev.clojur
Thank you for tracking it down and doing the legwork, Anthony :)
On Thursday, July 28, 2011 5:50:37 PM UTC-6, Anthony Grimes wrote:
>
> Oh! I apologize. I was replying via the google interface and didn't realize
> it wasn't quoting. Here is a link to the topic for context:
> https://groups.googl
Oh! I apologize. I was replying via the google interface and didn't realize
it wasn't quoting. Here is a link to the topic for
context: https://groups.google.com/d/topic/clojure/ZyVrCxmOFTM/discussion
I've also filed a bug here: http://dev.clojure.org/jira/browse/CLJS-43
Sorry. :)
On Thursday,
Could you please use quoting in your messages? Otherwise they have no
context.
Thanks,
Rich
On Jul 28, 2011, at 7:10 PM, Anthony Grimes wrote:
Actually, it seems to be caused by this commit:
https://github.com/clojure/clojurescript/commit/954e8529b1ec814f40af77d6035f90e93a9126ea
If I chec
Actually, it seems to be caused by this
commit:
https://github.com/clojure/clojurescript/commit/954e8529b1ec814f40af77d6035f90e93a9126ea
If I checkout before that, everything is peachy. I guess I'll submit a bug
report.
--
You received this message because you are subscribed to the Google
Gro
I'm all of a sudden getting this exact same error on OS X 10.6.8. And I do
mean all of a sudden. I actually updated to this version of OS X last night
and today it isn't working. Is this happening to any OS X users on an older
Snow Leopard? This is the only thing that has changed in my setup, so
I seem to have fixed this by editing
closure/library/closure/goog/base.js and rebuilding lib/goog.jar.
The relevant line is "goog.global = this;" somewhere at the top where
"this" should be replaced by
"(function(){return this})();"; the bootstrap script contains the
command to create the jarfile.
I also experience this problem; switching nodejs versions (0.4.11-pre
== v0.4 branch, 0.4.10 and 0.5.2) did not have any effect.
When compiling with:
bin/cljsc samples/nodehello.cljs '{:target :nodejs :optimizations
:simple :pretty-print true}' > nodehello.js
the (first) relevant line for this er
Thank you for your response, Urlik. It's good to know someone else saw the
same error, on a non-Windows platform, no less. Sean Corfield, responding
to an earlier failed attempt by me to post about the problem, said that he
was able to use Node with ClojureScript on OSX after following the
in
I have the same problem, using an unmodified clojurescript checkout
(08db38f) with nodejs 0.4.10 on MacOSX 10.6.8.
$ cat nodehello.cljs
(ns nodehello)
(defn -main [& args]
(println (apply str (map [\ "world" "hello"] [2 0 1]
(set! *main-cli-fn* -main)
$ bin/cljsc nodehello.cljs
'{:optimiza
I should add that I did have to make one change to closure.clj in order to
compile nodehello.cljs; I changed the following line in the ns->file-name
function:
path (string/replace (munge ns) \. java.io.File/separatorChar)]
To:
path (string/replace (munge ns) \. \/)]
--
You received this
I'm experimenting with the latest build of ClojureScript from github on
Windows. I can get as far as compiling nodehello.cljs from the Quick Start
guide, but I get the following error when trying to run the compiled .js
file with Node:
node.js:195
throw e; // process.nextTick error, or
14 matches
Mail list logo
