Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!feeder.erje.net!newsfeed.straub-nv.de!texta.sil.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: calling own methods from constructor References: <9t3rp6l38hju8at618b4nub16s90pdqn8d@4ax.com> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: 07 Apr 2011 11:32:44 GMT Lines: 15 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1302175964 tunews.univie.ac.at 60386 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:2926 Roedy Green wrote: > On 06 Apr 2011 20:48:41 GMT, Andreas Leitgeb > wrote, quoted or indirectly quoted > someone who said : > >> Is there any *good* use of having the constructor call a method >> that actually *can* be overridden in a subclass? > > I have accidentally nailed myself by overriding a method used in a > constructor. I have yet to find a legitimate use for it. It is too > bad the compiler does not complain about it. I haven't (yet) been bitten by it, myself. I just recently came to think about it.