JDK8 cleanups?

A. Sundararajan sundararajan.athijegannathan at oracle.com
Wed Feb 5 00:48:02 PST 2014

* "init.js" is just internal name of the initialization script used by 
jrunscript. The functions, objects exposed by it are linked from here:



As I said, nashorn's 'jjs' does not run this resource script from 

* jjs -h talks about command line options like -strict, -scripting.

-strict is to enable ECMAScript "use strict" mode from command line 
option rather than including it in scripts.
See also http://es5.github.io/#x10.1.1



explains syntax and global extensions available only in -scripting mode. 
You may want to look for (-scripting mode only) sections.

* Object.getOwnPropertyNames lists all properties - enumerable or not. 
This is as per ECMAScript spec.

PS. As for jdk8 tool docs, I still don't see new tools like 'jdeps'. I'd 
assume tools page is to yet to be updated for jdk8 specific tools. As I 
said earlier, I'll notify.


On Wednesday 05 February 2014 01:51 PM, Bernd wrote:
> Oop sent before including list ... answers inline. Greetings
>   ---------- Weitergeleitete Nachricht ----------
> Von: "Bernd" <ecki at zusammenkunft.net>
> Datum: 05.02.2014 09:15
> Betreff: Re: JDK8 cleanups?
> An: "A. Sundararajan" <sundararajan.athijegannathan at oracle.com>
> Cc:
> Am 05.02.2014 08:26 schrieb "A. Sundararajan" <
> sundararajan.athijegannathan at oracle.com>:
>>> b) On the jrunscript documentation page is a sentence which I do not
>>> understand (or the content behind the link is missing):
> http://download.java.net/jdk8/docs/technotes/tools/windows/jrunscript.html
>>> #See Also
>>> #If JavaScript is used, then before it evaluates a user defined script,
>>> #the jrunscript command initializes certain built-in functions and
>>> #objects. These JavaScript built-ins are documented in JsDoc-Toolkit at
>>> #http://code.google.com/p/jsdoc-toolkit/
>> jrunscript runs "init.js" bundled in the tool itself. This is historical.
> "jjs" does not run that script.
> Did I miss the doc of this init.js under the link or should the link be
> fixed? I would add the startup description to its own section and reserve
> see also for references.
>>> Is this also true for nashorn, or where can I get this list?
> So for nashorn only the ecma script objects (like Math) are bound?
> -scripting is registering the documented extensions, what about -strict?
>>> c) this wiki page is broken:
>>> https://wiki.openjdk.java.net/display/Nashorn/Nashorn+Documentation
>> By "broken", do you say any information is missing? or you can't access
> it?
> Hm, I mean the formatting (and I had the impression the links did not work,
> but they actually do, so sorry for the false alarm)
>>> e) is there a documentation about a list of all built-in load()
>>> scripts of nashorn? I have only found a list for fx: in the user guide.
>> Same wiki page - left panel has link to this page:
>> https://wiki.openjdk.java.net/display/Nashorn/Nashorn+extensions
> It lists the prefixes (fx and nashorn) but not the available script names
> (or where to find the resources). Is nashorn: a resource loader scheme?
>>> f) both jjs and jrunscript should probably add the scripting guide
>>> homepage as a see also resource.
>> Scripting guide is meant for programmatic access for nashorn or any other
> javax.script compliant engines.
> Yes, I mean the scripting start page or directly the nashorn user guide,
> the section about the scripting extension is relevant (
> http://download.java.net/jdk8/docs/technotes/guides/scripting/nashorn/shell.html#sthref24
> )
>> There is no 'inspect'. But, you can do the following in 'jjs':
>> jjs> Object.getOwnPropertyNames(this)
> Ah cool, are there any synthetic objects hidden?
>> Hope this helps
> Indeed, thanks!
> Bernd

More information about the nashorn-dev mailing list