

Carregando... Introduction to Algorithmsde Thomas H. Cormen, Charles E. Leiserson (Autor), Ronald L. Rivest (Autor), Clifford Stein
![]()
Nenhum(a) Ainda não há conversas na Discussão sobre este livro. This book is like an encyclopedia of algorithms. The algorithms are presented with pseudo code so it doesn’t matter what your favorite programming language is. A very rigorous mathematical approach is used for the analysis of for instance performance. Normally I wouldn't review a textbook, but reading this one is enjoyable. It's one of the very best textbooks I've ever used. Unbelievably well written. Well organized. Great examples and pictures. Clearly explained proofs. It is easy to read and learn from. I'm surprised I was able to get an already-used copy of this book; I'll be keeping mine for a very long time. The definitive graduate or upper-level undergraduate computer science textbook. This is the place to go to learn basic algorithms, data structures, proofs of correctness, and big-O notation. I prefer it to Knuth's three-volume opus, because it's shorter and doesn't get bogged down in the details of an artificial assembly language. Cormen et al. also makes for a fine self-study guide. If you're reading it on your own, check out the MIT Open Course Introduction to Algorithms class, which has a full set of online lectures and problem sets based on this book. sem resenhas | adicionar uma resenha
Pertence à série
Referências a esta obra em recursos externos.
|
![]() Capas popularesAvaliaçãoMédia:![]()
É você?Torne-se um autor do LibraryThing. |
an interesting feature, with respect to the exercises and especially problems for each chapter, is that i think cormen subscribes to a methodology where the solution to a problem should often require information or intuition not found in the chapter, nor even necessarily in the preceding chapters. you find yourself driving towards solutions that are used in later sections, or revisiting old problems once you find a better solution later on.
and, of course, cormen is here at dartmouth. one should probably always have a copy handy when writing code. (