Path: csiph.com!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Why does Java argue about making a class instance
Date: Mon, 28 Mar 2016 09:50:17 -0400
Organization: Aioe.org NNTP Server
Lines: 19
Message-ID: <ndbcqp$or3$1@gioia.aioe.org>
References: <nd6orl$k7m$1@reader1.panix.com> <nd6pps$ee3$1@dont-email.me> <ndbb9g$k7m$3@reader1.panix.com>
NNTP-Posting-Host: ANasIS7Js9OyLQwgloeBLQ.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:34039

On 3/28/2016 9:24 AM, Popping mad wrote:
> 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.

Yes.

But that is not the case here, so ...

Arne