RFR(L): 8218628: Add detailed message to NullPointerException describing what is null.
mandy.chung at oracle.com
Tue Mar 19 23:21:48 UTC 2019
Sorry I have been busy on other time-critical things. I will
get to it hopefully next week.
On 3/15/19 3:55 AM, Lindenmaier, Goetz wrote:
> Hi everybody, Mark,
> I followed your advice and created a JEP:
> Please point me to things I need to improve formally, this is my first
> JEP. Also feel free to fix the administrative information in the
> Jira issue if it is wrong.
> And, naturally, you're welcome to discuss the topic!
> Best regards,
>> -----Original Message-----
>> From: mark.reinhold at oracle.com <mark.reinhold at oracle.com>
>> Sent: Donnerstag, 14. März 2019 22:38
>> To: maurizio.cimadamore at oracle.com; Lindenmaier, Goetz
>> <goetz.lindenmaier at sap.com>
>> Cc: mandy.chung at oracle.com; roger.riggs at oracle.com; core-libs-
>> dev at openjdk.java.net; hotspot-runtime-dev at openjdk.java.net
>> Subject: Re: RFR(L): 8218628: Add detailed message to NullPointerException
>> describing what is null.
>> 2019/3/14 8:00:20 -0700, maurizio.cimadamore at oracle.com:
>>> I second what Mandy says.
>>> First let me start by saying that this enhancement will be a great
>>> addition to our platform; back in the days when I was teaching some Java
>>> classes at the university, I was very aware of how hard it is to
>>> diagnose a NPE for someone novel to Java programming.
>>> I also think that the design space for such an enhancement is non
>>> trivial, and would best be explored (and captured!) in a medium that is
>>> something other than a patch. ...
>> Agreed, also.
>> Goetz -- if, per Mandy’s suggestion, you’re going to write something
>> up using the JEP template, might I suggest that you then submit it as
>> an actual JEP? Giving visibility to, and recording, such design-space
>> explorations is one of the primary goals of the JEP process.
>> - Mark
More information about the hotspot-runtime-dev