Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: toward null-safe cookie cutter Comparators Date: Tue, 15 Nov 2011 09:04:40 -0800 Organization: Canadian Mind Products Lines: 24 Message-ID: <6m65c71vv5qjcrjbguageos9ctd29m2vm2@4ax.com> References: Reply-To: Roedy Green NNTP-Posting-Host: Z2l1DcCELS0rATq8NqV4Sw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:9965 On Mon, 14 Nov 2011 10:55:11 -0800, Daniel Pitts wrote, quoted or indirectly quoted someone who said : >> >NPE is one of the best things that can happen I really enjoyed that post. It might have been composed by Mark Twain were he a computer programmer. Amen. One of the almost miraculous things about Java is once you get rid of the compile errors, and once you stop triggering NPEs, there very good chance you have nailed all the bugs. There are situations where null is expected and it is just a hassle to explicitly deal with it, and other places where its presence is a sign of pathology. Whatever changes you make to the language should not make you treat everything the same way. -- Roedy Green Canadian Mind Products http://mindprod.com I can't come to bed just yet. Somebody is wrong on the Internet.