Envjs envjs → 1.2.x

Comments and changes to this ticket

• You flagged this item as spam.
  

  Eric Clemmons January 13th, 2010 @ 05:09 PM

  Solution:

  I had to turn on Optimization:
  java -cp env-js/dist/env-js.jar org.mozilla.javascript.tools.envjs.Main -opt -1 script.js

• You flagged this item as spam.
  

  Brian Landau January 27th, 2010 @ 05:09 AM

  I can confirm that adding the -opt -1 flags solves this problem.

  It seems like though if there's some way to not need to add these flags that would be more ideal.

• 

  Thatcher February 3rd, 2010 @ 05:02 PM

  • Milestone set to “1.2.x”
  • State changed from “new” to “open”
  • Assigned user set to “Thatcher”

  We are going to build in a env.rhino.js context patch in javascript. It will only apply itself if the parser.js module is included. It's now more a mystery than ever why this occurs and I'll be following up with the rhino team to try to figure it out.

  The bottom line is that we will patch internally so you wont notice.

  Thatcher

• 

  Thatcher February 6th, 2010 @ 07:04 AM

  • State changed from “open” to “resolved”
  • Tag set to “optimization, parser, rhino”

  ok this is fixed in trunk.

  http://github.com/thatcher/env-js/commit/cd34da2405e2d5f6904cbf1651...

• You flagged this item as spam.
  

  Doug McInnes May 17th, 2010 @ 01:34 PM

  This still appears to be happening in the latest on trunk.

  Adding -opt -1 to the java call does works around the problem.

  Using the same script as above:

  load('env-js/dist/env.rhino.js');
  print(typeof Envjs);
  
  
  $ java -jar env-js/rhino/js.jar script.js
  undefined
  
  $ java -jar env-js/rhino/js.jar -opt -1 script.js
  [  Envjs/1.6 (Rhino; U; Mac OS X x86_64 10.5.8; en-US; rv:1.7.0.rc2) Resig/20070309 PilotFish/1.2.13  ]
  function