> On Jul 12, 2016, at 2:00 PM, Paul Benedict wrote:
>
> Mandy, perhaps there is a JVM technicality here I'm unfamiliar with. My
> understanding of loading a class has always been that it's coupled with
> running its static initializers.
Loading, linking, and initializing are separate parts sp
On 12/07/2016 4:00 PM, Paul Benedict wrote:
Mandy, perhaps there is a JVM technicality here I'm unfamiliar with. My
understanding of loading a class has always been that it's coupled with
running its static initializers.
Loading, linking (resolution) and initialization are all distinct parts
o
Hi Paul,
On 7/12/16 8:00 AM, Paul Benedict wrote:
Mandy, perhaps there is a JVM technicality here I'm unfamiliar with. My
understanding of loading a class has always been that it's coupled with
running its static initializers. So my inference was that the class does
not get loaded into memory be
Mandy, perhaps there is a JVM technicality here I'm unfamiliar with. My
understanding of loading a class has always been that it's coupled with
running its static initializers. So my inference was that the class does
not get loaded into memory because the latter no longer occurs with
--dry-run.
On
> On Jul 12, 2016, at 10:35 AM, Paul Benedict wrote:
>
> Mandy, can you please give a look to the first email in this thread and see
> if you believe the enhanced message I suggested is helpful? I think it would
> be.
>
>
Your Suggestion:
"create VM but do not load mainclass or execute main
Mandy, can you please give a look to the first email in this thread and see
if you believe the enhanced message I suggested is helpful? I think it
would be.
On Jul 11, 2016 8:32 PM, "Mandy Chung" wrote:
>
> > On Jul 12, 2016, at 6:13 AM, Paul Benedict wrote:
> >
> > Alan, I wish I found this be
> On Jul 12, 2016, at 6:13 AM, Paul Benedict wrote:
>
> Alan, I wish I found this before I responded to you, but, anyway, here you
> go:
>
> https://bugs.openjdk.java.net/browse/JDK-8160698
> "java --dry-run should not cause main class be initialized”
>
Yes this has been fixed.
Mandy
> Cheer
Alan, I wish I found this before I responded to you, but, anyway, here you
go:
https://bugs.openjdk.java.net/browse/JDK-8160698
"java --dry-run should not cause main class be initialized"
Cheers,
Paul
On Mon, Jul 11, 2016 at 5:09 PM, Paul Benedict wrote:
> So I just tested "--dry-run" and I se
So I just tested "--dry-run" and I see it does load the class. My
apologies. I was following the commit trail but somehow the loading of the
class escaped me. I swore at one point it wasn't loading, but my error,
nevertheless.
Was there any debate on this issue? The problem I currently see with
lo
On 11/07/2016 22:01, Paul Benedict wrote:
The current help of --dry-run is this:
"create VM but do not execute main method"
But I think it's pretty important to note that the class is also not even
loaded.
The main class should be loaded. The original intention was that it do
everything except
10 matches
Mail list logo
