On 02/01/2018 17:07, Tom De Wolf wrote:
:
What I don't understand is the reasoning why the
module.getDescription().version() then returns a version for an
automatic module like sprint.core? it is not an explicit module on
which javac can do its magic, so where is that version information
sto
Alan,
Thx for the reply. If javac does it then it would be solved transparently
in 1 place.
What I don't understand is the reasoning why the
module.getDescription().version() then returns a version for an automatic
module like sprint.core? it is not an explicit module on which javac can do
its ma
On 01/01/2018 18:14, Tom De Wolf wrote:
I am working out a proof of concept to use the module version property and
the version of a ‘requires’in a useful manner. Details and a link to
github can be found on:
https://devcreativity.wordpress.com/2017/12/29/semantic-versions-in-java-9-modules-a
I am working out a proof of concept to use the module version property and
the version of a ‘requires’in a useful manner. Details and a link to
github can be found on:
https://devcreativity.wordpress.com/2017/12/29/semantic-versions-in-java-9-modules-as-a-safety-net/
However, I stumbled on be
From JLS 9.6.4.5:
"For other kinds of warnings, compiler vendors should document the strings they
support
for @SuppressWarnings. Vendors are encouraged to cooperate to ensure that the
same
names work across multiple compilers."
Any suggestions, how we can engage in such cooperation?
In particu
On 06.06.2017 11:03, Alan Bateman wrote:
On 06/06/2017 09:40, Stephan Herrmann wrote:
This was viewed from the JLS p.o.v. But "read by M" is still not well-defined.
All we see in the documentation of the referenced method is:
"a readability graph is computed"
With some further searching, w
I didn't see an answer to this question:
On 30.04.2017 23:45, Stephan Herrmann wrote:
On 30.04.2017 17:47, Alan Bateman wrote:
On 30/04/2017 12:10, Stephan Herrmann wrote:
:
Java 9 could make "API leaks" either illegal or ineffective and thus rule out
an entire category of ill-formed progra
On 06/06/2017 09:40, Stephan Herrmann wrote:
This was viewed from the JLS p.o.v. But "read by M" is still not
well-defined.
All we see in the documentation of the referenced method is:
"a readability graph is computed"
With some further searching, we find "readability graph" explained in
On 06.06.2017 10:15, Stephan Herrmann wrote:
A quick editorial comment:
On 29.04.2017 01:25, Alex Buckley wrote:
> [...] I have changed 7.3 to state:
>
> "The host system must use the Java Platform Module System (as if by
execution of the '
A quick editorial comment:
On 29.04.2017 01:25, Alex Buckley wrote:
> [...] I have changed 7.3 to state:
>
> "The host system must use the Java Platform Module System (as if by execution
of the 'resolve' method of
> java.lang.module.Configuration) to determine
On 01.05.2017 20:47, Alex Buckley wrote:
On 4/30/2017 3:25 AM, Stephan Herrmann wrote:
For the question at hand, this is what we learn from that improved
reference:
"A readability graph is constructed"
Now we only need a link to the specification that *defines* what is a
readability graph an
rrmann"
À: jigsaw-dev@openjdk.java.net, "Remi Forax" , "Alex Buckley"
Cc: "Brian Goetz" , "Dan Smith"
Envoyé: Mercredi 3 Mai 2017 23:31:14
Objet: Re: Java Platform Module System
On 03.05.2017 20:55, Remi Forax wrote:
It's context-free because a
- Mail original -
> De: "Stephan Herrmann"
> À: jigsaw-dev@openjdk.java.net, "Remi Forax" , "Alex
> Buckley"
> Cc: "Brian Goetz" , "Dan Smith"
>
> Envoyé: Mercredi 3 Mai 2017 23:31:14
> Objet: Re: Java Platform M
quot;
, "Brian Goetz"
Cc: jigsaw-dev@openjdk.java.net
Envoyé: Mercredi 3 Mai 2017 19:46:54
Objet: Re: Java Platform Module System
On 5/2/2017 3:39 PM, Alex Buckley wrote:
On 5/2/2017 7:07 AM, Jayaprakash Arthanareeswaran wrote:
Chapter 2 in [1] describes context-free grammars. The add
l original -
> De: "Alex Buckley"
> À: "Jayaprakash Arthanareeswaran" , "Dan Smith"
> , "Brian Goetz"
>
> Cc: jigsaw-dev@openjdk.java.net
> Envoyé: Mercredi 3 Mai 2017 19:46:54
> Objet: Re: Java Platform Module System
> On
On 5/2/2017 3:39 PM, Alex Buckley wrote:
On 5/2/2017 7:07 AM, Jayaprakash Arthanareeswaran wrote:
Chapter 2 in [1] describes context-free grammars. The addition to "3.9
Keywords" defines "restricted keywords", which prevent the grammar for
ModuleDeclaration from being context-free. This prevents
On 5/2/2017 7:07 AM, Jayaprakash Arthanareeswaran wrote:
Chapter 2 in [1] describes context-free grammars. The addition to "3.9
Keywords" defines "restricted keywords", which prevent the grammar for
ModuleDeclaration from being context-free. This prevents compilers from
using common parser genera
On 5/2/2017 5:13 AM, Stephan Herrmann wrote:
Thanks, Alex, for promising improvements in various places of the spec.
Re: Multiple packages with the same name can be "visible" (helpful
terminology for program analysis) but exactly one of these packages must
be identified as the meaning of the
/jigsaw/spec/java-se-9-jls-pr-diffs.pdf>
(2017-02-22)
- Original message -
From: Stephan Herrmann
Sent by: "jigsaw-dev"
To: Alex Buckley , jigsaw-dev@openjdk.java.net
Cc:
Subject: Re: Java Platform Module System
Date: Tue, May 2, 2017 5:43 PM
Thanks, Alex, for promising impr
Thanks, Alex, for promising improvements in various places of the spec.
I recall several threads on this list ending in you saying "still being
clarified" [1][2]. Are those issues settled by now and just need to be
penned down? Otherwise it would be very helpful just to see the list of
open quest
r to discover modules etc.?
When you said
"The host system must use the Java Platform Module System (as if by
execution of the 'resolve' method of java.lang.module.Configuration)"
I read this as requesting a compiler to perform the same operation as is
specified in that API.
"The host system must use the Java Platform Module System (as if by
execution of the 'resolve' method of java.lang.module.Configuration)"
I read this as requesting a compiler to perform the same operation as is
specified in that API.
Was the intention behind "must use the J
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 d
On 5/1/2017 12:23 PM, Stephan Herrmann wrote:
Meanwhile I've come to the interpretation that the main weakness of JLS
concerns
handling of same-named packages in different modules.
Trouble seems to start at a difference between 6.5.5.2 and 6.5.3.1/2:
To identify a type, that type must be accessi
On 4/30/2017 4:10 AM, Stephan Herrmann wrote:
No. (B) may be true for your example, but it is not for the following
(which is similar to examples we had in our January thread):
//-- M/module-info.java
module M { exports pm; }
//-- M/impl/Other.java
package impl;
public class Other { }
//-- M/p
1.
Looking at 7.7.1:
[...]
I understand the point; when we clarify the API spec for readability, I'll make sure the
JLS usage of "depends" is explicitly aligned.
Thanks, this part resolved.
Revisiting other references to "Java Platform Module System"
On 29.04.2017 01:25, Alex Buckley wrote:
On 4/27/2017 12:38 PM, Stephan Herrmann wrote:
Let me add a friendly reminder, that we are still waiting for a
specification that unambiguously tells us which module system to implement.
For illustration:
(A) Is JPMS a module system that keeps the semant
"depends" a technical term rather than the general
(fuzzy)
English word).
I understand the point; when we clarify the API spec for readability,
I'll make sure the JLS usage of "depends" is explicitly aligned.
Revisiting other references to "Java Platform Modul
On 30.04.2017 17:47, Alan Bateman wrote:
On 30/04/2017 12:10, Stephan Herrmann wrote:
:
Java 9 could make "API leaks" either illegal or ineffective and thus rule out
an entire category of ill-formed programs, which to-date must unfortunately
be accepted by module-unaware compilers:
(A) Java
On 30/04/2017 12:10, Stephan Herrmann wrote:
:
Java 9 could make "API leaks" either illegal or ineffective and thus
rule out
an entire category of ill-formed programs, which to-date must
unfortunately
be accepted by module-unaware compilers:
(A) Java 9 has the opportunity to say that the
On 29.04.2017 01:25, Alex Buckley wrote:
On 4/27/2017 12:38 PM, Stephan Herrmann wrote:
For illustration:
(A) Is JPMS a module system that keeps the semantics of qualified names as
they are in Java 8 and only superimposes encapsulation boundaries?
(i.e., each type is globally uniquely identifie
types).
You're right. Still the degree of dependence has changed.
I have changed 7.3 to state:
"The host system must use the Java Platform Module System (as if by execution
of the 'resolve' method of
java.lang.module.Configuration) to determine which modules are read by
tform Module System (as if by
execution of the 'resolve' method of java.lang.module.Configuration) to
determine which modules are read by M (§7.7.1). It is a compile-time
error if the Java Platform Module System is unable to determine which
modules are read by M."
That is, if a
On 25.04.2017 19:02, Alex Buckley wrote:
On 4/25/2017 1:20 AM, Stephan Herrmann wrote:
On 25.04.2017 03:50, Alex Buckley wrote:
Dependency resolution in JPMS is accomplished by the static 'resolve'
method of java.lang.module.Configuration.
Interesting.
Are you saying the semantics of JPMS dep
On 4/25/2017 1:20 AM, Stephan Herrmann wrote:
On 25.04.2017 03:50, Alex Buckley wrote:
Dependency resolution in JPMS is accomplished by the static 'resolve'
method of java.lang.module.Configuration.
Interesting.
Are you saying the semantics of JPMS depends on the implementation
of one or more
n 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 requ
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 p
On 24.04.2017 18:18, mark.reinh...@oracle.com wrote:
2017/4/24 9:14:31 -0700, ja...@outlook.in:
The JLS makes references to the "Java Platform Module System" in
several places but we are not sure where this is specified. The
Eclipse JDT team has been making do with whatever informal
2017/4/24 9:14:31 -0700, ja...@outlook.in:
> The JLS makes references to the "Java Platform Module System" in
> several places but we are not sure where this is specified. The
> Eclipse JDT team has been making do with whatever informal documents
> we can get our hands on
Hello everyone,
The JLS makes references to the "Java Platform Module System" in several places
but we are not sure where this is specified. The Eclipse JDT team has been
making do with whatever informal documents we can get our hands on such as
"State of the Module System&
I've prepared a list of open issues in the proposed design, gathered from
this list and the JSR 376 e-mail lists (EG, comments, and observers) [1].
Comments and discussion are welcome here on jigsaw-dev, but the best way
to make sure that the EG sees any specific comment or suggestion is to
send it
FYI, I've set up the EG's primary web page, and the mailing lists:
http://openjdk.java.net/projects/jigsaw/spec/
- Mark
FYI: https://jcp.org/en/jsr/detail?id=376
- Mark
44 matches
Mail list logo
