Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Martin Gregorie <martin@address-in-sig.invalid>
Newsgroups: comp.lang.java.programmer
Subject: Re: Java blunders
Date: Thu, 24 Jul 2014 07:36:51 +0000 (UTC)
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <lqqd2j$l2m$2@dont-email.me>
References: <jvbts91r2f9onj1e3dbr5lvqp70hmofkum@4ax.com> <lqn53i$huq$1@dont-email.me> <53d0629b$0$291$14726298@news.sunsite.dk> <lqpthp$ccv$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 24 Jul 2014 07:36:51 +0000 (UTC)
Injection-Info: mx05.eternal-september.org; posting-host="e5160e2be48f1ea550cf61512446f525"; logging-data="21590"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX194/gPG0oETNX6j5CAyULER5N5RGIfkD/8="
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2)
Cancel-Lock: sha1:LbALFjYPEGERgElim2qifejIHRE=
Xref: csiph.com comp.lang.java.programmer:29261

On Wed, 23 Jul 2014 22:11:35 -0500, Joshua Cranmer 🐧 wrote:

> On 7/23/2014 8:34 PM, Arne Vajhøj wrote:
>> On 7/22/2014 10:02 PM, Joshua Cranmer 🐧 wrote:
>>> C. On the balance, I think matching curly braces is superior to
>>> begin/end-ish constructs. If you're spending too much time trying to
>>> figure out where you have an extra or a missing curly brace, then,
>>> quite frankly, your IDE is defective. My IDE points out matching curly
>>> braces and can even fold them based on appropriate matching, and it
>>> has been able to do so since before Java was invented. Possibly since
>>> before I was born, even.
>>
>> To me having an IDE make up for something missing in the language does
>> not excuse that the feature is missing.
>>
>> An IDE is just not always present when reading code.
>>
>> (and I think the readability is more of a problem than the fixing one
>> too few or one too many problems)
> 
> If you're arguing that begin/end is superior for readability... it's
> not. It's no better, and could potentially be worse.
>
Yes - and you can always use comments if thye code is that complex:

    for (int i = 0; i < n; i++)
    {
        Deeply nested complex stuff, 
        eventually coming to and end.
    } /* end outer loop */
 


-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |