Re: PgJDBC: code reformat

On 28/12/15 03:03, Dave Cramer wrote:
> +1 for Gavin's suggestion
> and yes I think mandatory braces are required

When I started programming (back in 1968), I thought that indenting and
the like was a waste of time, as I had to explicitly punch every single
space onto punched cards,  But as my programs became more complicated, I
found my code hard to read (even with my then good eyesight). Later when
I started indenting, I found my code far easier to read & understand, so
I am extremely conscious of the value of white space - also very glad
the modern IDE's don't force you to type every single space and manually
assure that code is indented properly!!!

I always use brackets for if statements, as it make it much easier to
add additional lines without accidentally introducing a programming bug.


Cheers,
Gavin

>
> Dave Cramer
>
> davec@postgresintl.com <mailto:davec@postgresintl.com>
> www.postgresintl.com <http://www.postgresintl.com>
>
> On 27 December 2015 at 09:01, Gavin Flower
> <GavinFlower@archidevsys.co.nz <mailto:GavinFlower@archidevsys.co.nz>>
> wrote:
>
>     On 28/12/15 01:15, Dave Cramer wrote:
>
[...]
>
>     I much prefer to line the brackets up on the same side, it makes
>     the code a lot easier to read. Even in the days of screens with 25
>     lines of 80 characters - now with considerably larger monitors, it
>     makes even more sense.
>
>     So I very much prefer the style:
>
>     if (q)
>     {
>         do something
>     }
>
>
>     When I had poor eyesight it was easier, and after multiple eye
>     operations & my eyesight is much improved - I still prefer the
>     style with the brackets on separate lines.
>
>     If I want to understand someone else's code sample; I refactor a
>     copy of their code into this style, as it greatly increases the
>     ease of reading it. The other style looks cluttered, and is harder
>     to see the blocks of code clearly
>
>
>     Cheers,
>     Gavin
>
>
>
>