Path: csiph.com!feeder.erje.net!2.us.feeder.erje.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail
From: Popping mad <rainbow@colition.gov>
Newsgroups: comp.lang.java.programmer
Subject: Re: Why does Java argue about making a class instance
Date: Mon, 28 Mar 2016 13:24:00 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 11
Message-ID: <ndbb9g$k7m$3@reader1.panix.com>
References: <nd6orl$k7m$1@reader1.panix.com> <nd6pps$ee3$1@dont-email.me>
NNTP-Posting-Host: www.mrbrklyn.com
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: reader1.panix.com 1459171440 20726 96.57.23.82 (28 Mar 2016 13:24:00 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Mon, 28 Mar 2016 13:24:00 +0000 (UTC)
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2)
Xref: csiph.com comp.lang.java.programmer:34037

On Sat, 26 Mar 2016 16:04:07 -0400, Eric Sosman wrote:

> f the nested class is truly supposed to be an inner class (belonging to
> a Main instance), then you'll need a Main:
> 
> 	Main my_main = new Main(); CollectVarsVisitor my_visitor
> 	    = my_main.new CollectVarsVisitor();


Calling for a Class instance from within a class constructor seems like a 
sure fire way to make an infinite loop.