4 ms·
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 bit
by ArkyBeagle 11y ago
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.
- rayiner 11y agoNo 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.
- ArkyBeagle 11y agoI am having trouble identifying "the LKML thread."
- kecks 11y agoI think he meant this: https://lkml.org/lkml/2015/9/3/428 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.)
- ArkyBeagle 11y agoThanks so much! Agreed.
- m_mueller 11y agosorry for OT, but: g+ share: 0, reddit share: 1k. .. so I guess it becomes clear why Google is deemphasising this.
- deleted 11y ago[deleted]
- pjmlp 11y agoI 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.