21st Century C: C Tips from the New School

st Century C C Tips from the New School Throw out your old ideas of C and relearn a programming language that s substantially outgrown its origins With st Century C you ll discover up to date techniques that are absent from every other

  • Title: 21st Century C: C Tips from the New School
  • Author: Ben Klemens
  • ISBN: 9781449327149
  • Page: 249
  • Format: Paperback
  • Throw out your old ideas of C, and relearn a programming language that s substantially outgrown its origins With 21st Century C, you ll discover up to date techniques that are absent from every other C text available C isn t just the foundation of modern programming languages, it is a modern language, ideal for writing efficient, state of the art applications Learn to dThrow out your old ideas of C, and relearn a programming language that s substantially outgrown its origins With 21st Century C, you ll discover up to date techniques that are absent from every other C text available C isn t just the foundation of modern programming languages, it is a modern language, ideal for writing efficient, state of the art applications Learn to dump old habits that made sense on mainframes, and pick up the tools you need to use this evolved and aggressively simple language No matter what programming language you currently champion, you ll agree that C rocks.Set up a C programming environment with shell facilities, makefiles, text editors, debuggers, and memory checkersUse Autotools, C s de facto cross platform package managerLearn which older C concepts should be downplayed or deprecatedExplore problematic C concepts that are too useful to throw outSolve C s string building problems with C standard and POSIX standard functionsUse modern syntactic features for functions that take structured inputsBuild high level object based libraries and programsApply existing C libraries for doing advanced math, talking to Internet servers, and running databases

    One thought on “21st Century C: C Tips from the New School”

    1. All engineering students take a one semester course fairly early in their education. My experience as a professor is that most of them promptly forget it and never make use of it again. I get alternately amused and discouraged at the lengths some of the students I work with go to avoid programming again. Because that one semester course teaches a programming language, but does not teach someone how to program. This book is meant to take someone through that step. It is sometimes hard to follow ( [...]

    2. This book is awesome. The author is experienced, clear and funny. Klemens' tactic is to give a crash course in the various tools needed to produce usable, portable, up-to-date C code without getting into boring minutiae that can be googled when needed. To me this book means the difference between being able to compile an executable and being able to write software. I'm actually excited to write some C after this, but also a little scared.Word of warning: at least a little knowledge of C is requi [...]

    3. The idea of this book is that the C programming language has been quietly evolving, while C++ and Java took all the glory. But those languages are a mess, C++ in its syntax and gotchas and Java in its resource abuse. In its recent standards and libraries, C has many of the same features, rendering the newer languages mere syntactic sugar. C doesn't candy coat. Or, as this book puts it, it's the "punk rock of programming languages." Fast, messy, and dangerous.I thought it was an interesting idea, [...]

    4. 21st Century C is one of those rare technical books that is truly what I would consider to be an intermediate level book. It is a pity that more books aren't written at this level, as this is where I feel like I currently am in my career.This is not an "Into to Programming" book that happens to use C. Instead it is a book that a moderately experienced non-C programmer can use to learn some C. Not everything is spelled out step-by-step. You'll need to look up the documentation to some of the libr [...]

    5. If you want to learn to program in C, the time-honoured recommendation is Kernighan & Richie's venerable and succinct text "The C Programming Language". Like the language itself, that book is now getting a bit long in the tooth, and fails to cover the more recent revisions to the language (C99 and C11), not to mention the evolution in operating systems and development environments."21st Century C" steps in to fill this decades-long gap and provides an up-to-date perspective on programming in [...]

    6. Nice idea, poor implementation.This book contains two parts: tools supplementary to C programming and a collection of C tips on pointers, macros, functions returning multiple items, functions that take a variable number of parameters.The first part -tools useful for C programming such as makefile, debugger (gdb), memory profiling (Valgrind), version control (git)- is an ambitious move, that is trying to cover all these tools. These tools are mostly from past century, they are powerful yet someti [...]

    7. This was bad. There was nothing new for me in there, except probably asprintf() (and with a title like this I expected a lot more), and all the stuff explained was brief, non-systematic and mostly an explanation of the author's mode of work. Everyone would be better by reading the unix network programming books by Stevens, and a few manuals for whatever he/she sees used in any medium-sized project.

    8. Lots of very good information that it took me years working professionally to figure out. Source control, libtool, automake, doxygen, this book covers them all.

    9. I liked the book's premise, and it has some interesting snippets and gems, but unfortunately it falls short in a couple of areas.Having information and examples on the surrounding tooling is certainly practical, but the git chapter felt really unnecessary. Git is so ubiquitous nowadays, that I hardly see the point. Including the other tools, however, makes more sense (valgrind, doxygen, make, autotools, etc.). Instead of Git, the author could have played with some of the available static analysi [...]

    10. Half of this book is an enjoyable up-to-date primer on the C programming language. The other half covers 3rd party libraries and tools which are needed to plug gaps in C's built-in capabilities, undermining the author's claim that C is still viable as a development platform. I haven't coded much in C for decades, having moved on to full-featured platforms built around other languages . As a relatively easy-to-read refresher on C, the book works well. As an argument in favor of using C for genera [...]

    11. I've read it all and I keep reading parts of this great little book. Probably the best,most helpful book I've read about programming in the C language right after "The C Programming Language," 2nd edition, by Kernighan and Ritchie.// just a snippet of an imaginary program I didn't write. I think it's correct - I used stuff from the // book to write it. I didn't know about the brackets, f'rinstance./* the double slash is a new way of commenting in C, to annotate the program and the other, establi [...]

    12. o trecere în revistă a ceea ce-ți trebuie pentru a programa în C. Nu intră în amănunte dar e bună ca să-ți dea câteva idei de ce ar trebui să cauți mai departe, iar pe alocuri chiar o poți folosi ca pe un "quick guide" (în special partea de source control - git). În plus se concentrează pe "noul C": C99/C11 care are câteva lucruri pe care eu (programator C/C++ de 11 ani) nu le știam (cum ar fi keyword-ul "restrict").

    13. Tons of great ideas for writing modern, flexible C. In all honesty, I'm not sure if my disappointments with some of the tips regarding makefiles and dependency management have to do with the book or the ecosystem itself. It seems very difficult to set up a C project compared to Python, Ruby, or other languages luckily, Xcode takes care of a lot of the process, but it would have been nice if the author presented a similarly convenient set of tools. Maybe I'm just being picky.

    14. With my background this is a very useful book! I learned C++ about 10 years ago but was always advised to use STL-vectors and strings instead of arrays so I did not give those topics the attention they deserved. Now I work in a project with C and this book quickly got me up to speed on some of the things I had forgotten. The one thing I did not like about the book is that a big part of it isn't C-related, like version control, etc.

    15. I had much more expectations and expected to find something useful for myself – I did not. This book, however, would do a good job showing just-after-K&R beginners how to give birth to C code and stay sane. Another thing to be aware of: like most tutorial-type books this one already is outdated and does not overview some of useful tools available today.

    16. An enjoyable read, great to get you pumping for some low-level hacking - now with proper library use and great external interface. I'd recommend it as a second or third C book to read, for me personally there were very few technical things I didn't already know, but a wealth of encouragement to use things I knew about but wasn't sure were worth using in practice.

    17. Apart from a couple of useful tricks that could have been described on ten pages at most, this book is mostly a waste of time. Skim through it, to get a hold on some of the macros and maybe the Glib section, but don't devote too much time on the rest.

    18. This book is filled with tips on how to use non-intuitive build tools and pick up some very bad coding habits while you're at it. I suppose it could be useful as a reference if you really need to know the intricate details of makefiles for some project.

    19. Lots of interesting info, but some really bad advice for anyone who is building production quality applications. If you're an oldschool(ish) c coder, this will introduce you to a lot of the new features of modern c.

    20. I have some doubts about the goodness of a C book that claims that given the great amout of memory on modern machines, memory leaking ain't a problem.

    21. It seems that some (most?) tips are more useful when writing small programs, because there is a lot of indirection in the code.

    Leave a Reply

    Your email address will not be published. Required fields are marked *