Yes. But I'd also recommend getting Stephen Prata's C Primer Plus. It covers C99, and talks about more complicated topics such as multiple pointer indirection and the preprocessor.

Those who can't afford a high dpi LCD screen?

I don't get this... I have a 90dpi monitor and subpixel antialiasing on Linux is beautiful.

I should also point out that antialiasing (and subpixel rendering in particular) is designed for low pixel densities. High pixel density monitors do not need antialiasing. (This is why printed font rasterizers such as Metafont do not perform antialiasing.)

I've noticed that on some monitors antialiasing looks fantastic, while on others not. My sister's laptop has a smaller screen and enabled antialiased fonts, and they really do look great. But on my Samsung 2232BW, which is a 22" 1680x1050 monitor, antialiased fonts just look really bad.

So maybe it has to do with more than just DPI, but generally I've read that high-DPI screens have no trouble at all with displaying antialiased fonts. (And yes, I have tried numerous calibration tools, with no luck).

It's likely they have a different pixel color order. If the subpixels are not in the order the algorithm expects, it will look worse than without aa.

Although you could probably use any OOP capable language with GoF, I think the D language fits really nicely for that book. D defines interfaces, abstract classes, subtyping, (class) mixins, templates, all in the language, and has a safe override mechanism for when inheritance is the preferred approach in an OOP pattern.

Interesting.. In what way does D seem like a severe step backwards to you? Is that assumption based on the library support or the language itself?

Interesting. I kept seeing some topics opened, closed, only to be reopened again. I thought the admins couldn't make up their minds.

Hmm, I've just tried it. It has potential, but it's very slow and sluggish on my machine (quad).

All of this because people are too lazy to install software? Why not just run compiled binaries in the operating system?

Because it's more fun to make the web do things it was never intended for and it's still the closest thing we have to a universal write once platform.

I'm not as worried about the UI as much as I am worried about '404' errors, which are pretty common.

I've only had a few months of experience with Python, but I had no trouble learning C (it only takes a week or two to get used to the syntax). I'm pasting this from my reply in a Reddit thread:

If you're going to read K&R, make sure you visit the Errata page. There are a bunch of examples that have typos (some of them are not on the Errata page though).

But reading one C book isn't going to teach you everything about C. A lot of the C code out there makes heavy use of macros and multiple pointer indirections, which isn't covered in much detail in K&R. And if you're interested in the newer C99 standard, The C Primer is a great book (but it's quite thorough, which imo, is a good thing).

If you're going to try out the examples from K&R, pass these arguments to gcc: -ansi -pedantic -Wall -Wextra -g

The -g flag is for debugging symbols. I think I still have most of the fixed examples from K&R that will compile, if you're interested in these. Also, make sure to bookmark these two links:

http://www.eskimo.com/~scs/cclass/krnotes/top.html

http://users.powernet.co.uk/eton/kandr2/

The first one gives you some better explanations of what has been said in the K&R book (divided by chapters). The second one has most answers to the exercises in the book.

I've just sent them an email asking this question. Waiting for the reply..

Update: Just got the reply, there will be Video. Yay!