To become a good C programmer (2011)

Re:To become a good C programmer (2011) by ArkyBeagle on Sunday May 01, 2016 @02:24PM (#11607258)

My guess is that liking/not liking 'C' depends on how interested you are in its representation model. If you're actively disinterested in how things work as bits in memory, then I can't blame you a ... bit.

[ Parent | on HN ]

Re:To become a good C programmer (2011) by rayiner on Sunday May 01, 2016 @03:30PM (#11607525)

No the representation model is fine. It's where C tries to be something other than portable assembly where it goes awry. E.g. C has more syntax for arrays than actually exists at runtime, which leads to surprising behavior. The problem with array arguments discussed in the LKML thread posted above is a great example.

[ Parent | on HN ]

Re:To become a good C programmer (2011) by ArkyBeagle on Sunday May 01, 2016 @03:57PM (#11607621)

I am having trouble identifying "the LKML thread."

[ Parent | on HN ]

Re:To become a good C programmer (2011) by kecks on Sunday May 01, 2016 @04:39PM (#11607768)

I think he meant this:

https://lkml.org/lkml/2015/9/3/428

(It's Torvalds on a bug made harder to spot by using array arguments in C, which you shouldn't do.)

[ Parent | on HN ]

Re:To become a good C programmer (2011) by m_mueller on Monday May 02, 2016 @03:34AM (#11609752)

sorry for OT, but:

g+ share: 0, reddit share: 1k.

.. so I guess it becomes clear why Google is deemphasising this.

[ Parent | on HN ]

Re:To become a good C programmer (2011) by ArkyBeagle on Sunday May 01, 2016 @08:36PM (#11608551)

Thanks so much! Agreed.

[ Parent | on HN ]

Re:To become a good C programmer (2011) by pjmlp on Monday May 02, 2016 @02:28AM (#11609509)

I was actively interested how bits and hardware work, using Z80, 80x86, 68000, GW Basic, Turbo Basic, Turbo Pascal, Modula-2 and Oberon.

No need for C and its flaws.

[ Parent | on HN ]