Pointers on C

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

Pointers on C helped me really understand pointers like no other book was able to do. http://www.amazon.com/Pointers-C-Kenneth-Reek/dp/0673999866/...

…tbooks how to avoid using fixed-sized buffers and arrays, and instead use dynamic allocation of string buffers, arrays, and dynamic list structures. Kenneth Reek's book "Pointers on C" is excellent for understanding this in vivid detail. You can not read that book and then claim to be confused by pointers ever again.

If you can program well in C, everything else seems like both a blessing and a compromise. While K&R is great, my copy is far less used than Pointers on C by Ken Reek. If you can find a cheap copy I highly recommend it. If you are working through K&R make sure to do each of the sample problems. The text is just the support to let you figure out how to do them.

Today, I just finished a book called "Pointers on C" by Kenneth Reek. I read it to come up to speed on pointers and now feel comfortable with that. That's why I posted today, I am now at the fork in the road...