On 5/1/2017 12:40 PM, Stephan Herrmann wrote:
Asked differently: when it says
"Generally, the rules of the Java programming language are
more interested in dependences than dependencies."
which are the aspects where the rules of the Java programming language
*are* interested in dependencies?
I'm sorry that this attempt to be helpful -- to distinguish the popular
term "dependency" from the actual term "dependence" used by the JLS --
is causing so much confusion. The JLS has always contained rather
open-ended text intended to add color rather than to specify an
implementation. But to answer your question: When we fix up readability
in the API, I expect the JLS will then speak more about the dependencies
which result from resolution and are more numerous than the dependences
expressed with static 'requires' directives.
- Another reference links "automatic modules" into JLS and will probably
link to ModuleFinder.of(Path...), right?
This text is also an informative note. Automatic modules are
discovered through ModuleFinder.of, sure, and they appear in other
places in the java.lang.module API too -- but none of that is the
point of the note. The point of the note is that the developer
doesn't specify 'requires' any differently for an automatic module
than for an explicit module.
You make it sound as if automatic modules are relevant only at runtime.
Huh? The JPMS is assumed to be present at compile time, not just run
time. And automatic modules are a feature of the JPMS.
Alex
