Re: Nashorn parser directives

2015-11-27 Thread Anthony Vanelverdinghe
Hi Jim, Sundararajan, Thanks for your invitation and welcoming response. My spare time will be scarce in December, but I would love to contribute to improving Nashorn in the new year. Kind regards, Anthony On 27/11/2015 17:50, Sundararajan Athijegannathan wrote: In addition, setting parser [

Re: Nashorn parser directives

2015-11-27 Thread Sundararajan Athijegannathan
In addition, setting parser [or other] options locally inside a script may not work - at least with the current model of option handling. Currently, options are parsed and a class with final fields (ScriptEnvironment) is initialized during engine initialization. This allows for efficient option

Re: Nashorn parser directives

2015-11-27 Thread Jim Laskey (Oracle)
Anthony, Your argument is not unreasonable, but given the resources we have available to work on features (including full ES6 support), it is simpler for us to be binary on this. If, on the other hand, you sign an OCA and submit the necessary changes, we might consider integrating after review

Nashorn parser directives

2015-11-27 Thread Anthony Vanelverdinghe
Hi Recently I filed an issue [1] requesting to "Allow to run shebang script with --no-syntax-extensions". This was closed as "Won't Fix" with "Can't support because # is an extension." While this is true, I meant to say "Allow to run shebang script without allowing any other syntax extensions