Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Baking doens't work on Mint 12, reserved word "eval" #62

M1C opened this Issue Apr 23, 2012 · 3 comments


None yet
2 participants

M1C commented Apr 23, 2012

I'm experiencing 2 issues when baking jsrepl on Linux Mint 12 using coffee-script 1.3.1.
I'm not familiar with coffee. But I think it uses node, my node-version is 0.4.9
I got npm using curl http://npmjs.org/install.sh | sudo sh

This first error is: SyntaxError: In Cakefile, octal literal '0755' must be prefixed with '0o'.
It can be fixed by replacing all '0755's by '0o755's in the Bakefile.

The second error is: SyntaxError: reserved word "eval" can't be assigned on line 80
Full stacktrace (please look at the full log below):

Compiling extern/unlambda-coffee/unlambda.coffee.

      throw err;
SyntaxError: reserved word "eval" can't be assigned on line 80
    at SyntaxError (unknown source)
    at Lexer.error (/home/luto/jsrepl/node_modules/coffee-script/lib/coffee-script/lexer.js:686:13)
    at Lexer.literalToken (/home/luto/jsrepl/node_modules/coffee-script/lib/coffee-script/lexer.js:414:16)
    at Lexer.tokenize (/home/luto/jsrepl/node_modules/coffee-script/lib/coffee-script/lexer.js:35:220)
    at Object.compile (/home/luto/jsrepl/node_modules/coffee-script/lib/coffee-script/coffee-script.js:43:32)
    at /home/luto/jsrepl/Cakefile:49:21
    at /home/luto/jsrepl/Cakefile:181:9
    at /home/luto/jsrepl/Cakefile:134:20
    at /home/luto/jsrepl/Cakefile:140:14
    at /home/luto/jsrepl/Cakefile:154:16

Full log: http://pastebin.com/raw.php?i=ZCqpyMFm

It is possible that my coffe-script version is too new?
The changelog says that old-style octal literals and setting the value of eval are now forbidden, see http://coffeescript.org/#changelog

It posted this here because @replit told me to do so: https://twitter.com/?utm_content=profile#!/replit/status/194467443895312384

Thanks for your time,


M1C commented Apr 23, 2012

I added a pull-request for the first issue: #63


M1C commented Apr 23, 2012

Tried downgrading to 1.2.0 (the version before 1.3.1), now the 2nd bug is gone, too. Which means that my assumption of a too new coffe-script is right.
Downgrading works like this (in case someone who knows as much about npm as I do reads this):
npm install coffee-script@1.2.0

But I still think that this is an issue because it isn't documented anywhere and the newest version should be usable.

@amasad amasad closed this in 663333e Apr 25, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment