Path: csiph.com!news.swapon.de!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Never using booleans as parameters
Date: Sun, 29 Nov 2015 15:55:35 -0500
Organization: Aioe.org NNTP Server
Lines: 15
Message-ID: <n3foo4$g3$2@speranza.aioe.org>
References: <87lh9tysy8.fsf@Equus.decebal.nl> <boolean-20151120181620@ram.dialup.fu-berlin.de> <564f55e3$0$23775$e4fe514c@news.xs4all.nl> <n2o1vd$os2$1@dont-email.me> <mcmurtrie-D46785.21553023112015@news.sonic.net>
NNTP-Posting-Host: 1lM8B9/qdtKBc/uIRK2Gjw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; 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.4.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:33230

On 11/24/2015 12:55 AM, Kevin McMurtrie wrote:
> Or you can go with an IDE and well documented code so that you always
> know what parameters and methods do just by pointing to them.  You gotta
> have the proper tools of the trade.

Yes. But it can be dangerous to rely too heavily on them.

Imagine getting a printout of the code.

"Sorry I can't read this due to no mouse over"

:-)

Arne