On 25.04.2017 03:50, Alex Buckley wrote:
On 4/24/2017 5:22 PM, Stephan Herrmann wrote:
Obviously, defining JPMS is not done in index.html itself but delegated
to individual documents.
One of the linked documents is a version of JLS with changes on behalf
of JSR 376.
Jay's question was triggered by the observation that this exact version
of JLS contains references like these:
- "the host system must use the Java Platform Module System to
determine ..."
- "A 'dependency' is the module resolved by the Java Platform Module
System
for a given requires directive."
- "The Java programming language does not distinguish between named
modules
specified explicitly in module declarations versus named modules
specified by the
Java Platform Module System when it detects a JAR file on the
modulepath
('automatic modules')"
This creates the impression that for implementing a compiler for JPMS
another document must be consulted in addition to JLS, but the
reference "specified by the JPMS" gives no clue were to look, as it
appears inside the specification ofJPMS.
Dependency resolution in JPMS is accomplished by the static 'resolve' method of
java.lang.module.Configuration.
Alex
Interesting.
Are you saying the semantics of JPMS depends on the implementation
of one or more methods in java.lang.module.Configuration and friends?
Are all mentions of JPMS inside JLS intended as references into JDK API?
How are compiler engineers expected to use this information?
Stephan
