3 ms·
By talking about, I was including on HN, and all of those books so qualify. For K&R, sure, I've talked about it, yes, orally. E.g., for that book, what's with
by graycat 12y ago
By talking about, I was including on HN, and all of
those books so qualify.
For K&R, sure, I've talked about it, yes, orally.
E.g., for that book, what's with the idiosyncratic syntax?
And why the case of x+++++y? And some cases of
declare statements can be real puzzles that can
need talking about -- there is even a sparse, too sparse, discussion
in the book. And to talk, should mention why the
language was designed to run in about 8 K bytes on
a DEC machine (helps explain y =+ x). And, in one
discussion, I got led to where in K&R actually can
find the actual memory allocation technique used
by MALLOC and FREE. We should talk about what
we are paying now, when we use C (or really C++ which
was originally just a preprocessor to C), due to the
original 8 KB constraint when now main memory
goes for about $10/GB and motherboards commonly
support 32 GB of ECC main memory. So, yes,
we do still talk about C and K&R.
C stands to
be around for a long time, and I'm sure that
students new to programming will do a lot of
talking about K&R. While in college, they may do the talking
in person at some social gatherings.