Re: C Books and algorithm books

On 12 Apr, 17:02, Eric Sosman <esos...@xxxxxxxxxxxxxxxxxxxx> wrote:
istillsh...@xxxxxxxxx wrote:

Questions for the major contributors to comp.lang.c.

What C  books do you have?

     "The C Programming Language," Kernighan and Ritchie (original)
great book

     "C: A Reference Manual," Harbison and Steele
great book. I think it is better for the standard library
than K&R and I've heard the latest edition a good reference for
C99 (if you are interested in it).

     "C Traps and Pitfalls," Koenig
never got on with this.


     "The Standard C Library," Plauger
great book! Not only does it document the library and
provide you with an implementation but it also guides
you through the design of a C library.

Lots of stuff on writing portable C.


What C books have you read?

     As above.

Which algorithm book is your favorite?

     "The Art of Computer Programming," Knuth

If you want more of a recipe book (less theory)
try Sedgewick


What resources that you find particularly useful, beside comp.lang.c
and its FAQ?

http://www.dinkumware.com/manuals/


     The wide world and all therein.  (Really, the question
is too broad to admit of a useful answer.)

I ask the above questions mainly to see what I lack.  And the answer
may help other newbies as well by letting people know what "weapons"
have been proved to be useful.  I might have asked too many questions
these days, but I promise I will reduce them to less than 2 daily from
now on.

     Learn Lisp.  You may not use it much, but it will improve
your use of other programming languages.


--
Nick Keighley

"There are two ways of constructing a software design: One way is to
make it so simple that there are obviously no deficiencies, and the
other way is to make it so complicated that there are no obvious
deficiencies. The first method is far more difficult."
-- C.A.R. Hoare
.

Relevant Pages

  • Re: [fw-wiz] PIX Dual line Internet HDSL and ADSL
    ... > the secondary router - and it's bound to be the shortest route from ... even to other locations within that ISP. ... There are two ways of constructing a software design. ... And the other way is to make it so complicated that there are no obvious deficiencies. ...
    (Firewall-Wizards)
  • RE: [fw-wiz] Re: Ethics, morality and the industry
    ... yourself they act like you can't possibly understand the vunerability. ... > There are two ways of constructing a software design. ... > is to make it so complicated that there are no obvious deficiencies. ...
    (Firewall-Wizards)
  • Re: [PATCH 1/5] pid: Implement task references.
    ... There are two ways of constructing a software design. ... And the other way is to make it so complicated that there are no obvious deficiencies. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Des Glückes Unterpfand
    ... Redewendung nur "einen Hals kriegen". ... There are two ways of constructing a software design. ... is to make it so complicated that there are no obvious deficiencies. ...
    (de.etc.sprache.deutsch)
  • Re: using iso_c_binding
    ... interface for P in the module: ...    End type T ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)