Hey, sorry if you took it the wrong way. I'm just pointing out some flaws I see in the text, and I fully acknowledge it's a work in progress and these may be solved over time.
However, I will repeat.
K&R is an excellent text. If you disagree, I dispute your credibility.
I also stand by my comment. Smart people have created strong type systems like gobjects and ctypes in C.
As a programmer, you should unequivocally _never_ do this yourself. C is about reuse, and not reinventing the wheel. Sure, if you want to use a strong type system instead of C++, do so. Do not write one yourself.
> As a programmer, you should unequivocally _never_ do this yourself.
Bullshit. You guys going around throwing your platitudes, shoulds, and nevers at people rarely have any evidence supporting your claims, and usually it just hides a lack of real knowledge.
However, I will repeat.
K&R is an excellent text. If you disagree, I dispute your credibility.
I also stand by my comment. Smart people have created strong type systems like gobjects and ctypes in C.
As a programmer, you should unequivocally _never_ do this yourself. C is about reuse, and not reinventing the wheel. Sure, if you want to use a strong type system instead of C++, do so. Do not write one yourself.