Path: csiph.com!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: throw null investigation Date: Wed, 18 Jul 2012 15:55:15 -0700 Organization: A noiseless patient Spider Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 18 Jul 2012 22:55:16 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="61282af8d6595e8d991edb5ac03d6e00"; logging-data="9027"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19O3/I+SLoBulv9aHQ0YOYLqmn2Q2O5hf4=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: Cancel-Lock: sha1:AjXefjeu94kn0hm4ZOtzV/WJG4Y= Xref: csiph.com comp.lang.java.programmer:16095 On 7/18/2012 3:06 PM, Daniele Futtorovic wrote: > > But if what you say is correct, and Java does /not/ systematically wrap > nulls "thrown" from JNI (assuming it's possible), then it would be > technically possible to catch a null Exception in the Java runtime, > wouldn't it? I want to emphasize there than I'm speculating and extrapolating from barely remembered blogs. It's something for the OP to consider, but he's going to have to decide if I'm talking rubbish or not. Executive summary: I dunno.