Re: [PIC] Learning C

  David C Brown, <[email protected]> wrote

>
> Onew of the problems I have with trying to understand code examples in C
is
> that so many of them are incomprehensibly dense.
>

There is a faction among programmers who seem to enjoy swinging their
appendages by writing the most impenetrable, dense code to somehow show off
their "prowess" and sneer at anyone who can't decode their drivel.

Tabs, spaces, empty lines cost nothing and it makes me think a lot less of
the people who create code intended to make other people's lives harder.


On Thu, 14 Nov 2024 at 12:35, RussellMc <[email protected]> wrote:

>  David C Brown, <[email protected]> wrote
>
> >
> > Onew of the problems I have with trying to understand code examples in C
> is
> > that so many of them are incomprehensibly dense.
> >
>
> When writing C++ code I formatted in a way which to me makes it far more
> > readable than the normal manner of presentation.
>
>
> I place  { on the line following and then indent code following an Indian
> it again for any other functions such as if / while / case ... .
> The end result is code who's structure leaps out and grabs you. I started
> off being somewhat surprised that this wasn't standard practice come to
> accept that most people prefer density and obfuscation.
> Apart from taking more space I can see no disadvantages and this approach
> and for me the gains are substantial.
>
> I spent many decades working mainly in assembler and
>  actually find it generally easier to see what's going on than in most
> higher level languages.
>
>
> Russell.
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> https://mailman.mit.edu/mailman/listinfo/piclist
>


-- 
Clint. M0UAW IO83

*No trees were harmed in the sending of this mail. However, a large number
of electrons were greatly inconvenienced.*