Introduction to Computer Science : A Structured Programming...

Features

• Cover Type: Paperback with 8900 pages
• Published by: West Publishing Company; 001 edition 1997
• Written in: English
• ISBN 10 Number: 031409573X
• ISBN 13 Number: 978-0314095732
• Book Dimensions: 10.2 x 8.5 x 1.2 inches
• Weighs: 3.5 pounds

Book Description
Computer Science: A Structured Programming Approach Using C presents both computer science theory and its implementations in the C language with a depth-first approach. It follows a clear organizational structure supplemented by easy to follow charts and tables. All programs and functions are developed in a consistent and readable style based on the authors' extensive academic and industry experience. The first half of the book builds a firm understanding of expressions, introducing pointers only to the extent necessary to cover pass-by-reference and arrays. Beginning with Chapter 9, the text develops the concept of pointers ending with a simple introduction to linked lists.

Reader Reviews
Forouzan and Gilberg attempt to teach structured programming using the C language as their vehicle. They have produced a book which does justice to neither purpose. As a textbook on C, it is marred by hundreds of errors. Some are typographical, but significant: a "9" instead of a "(" in a sample program, for instance. Some misuse C: an example of the getc() routine shows it returning a char, when it in fact returns an int; this is an especially nasty bug which every experienced C programmer has encountered sometime. Some errors are conceptual, such as the Byzantine instructions given for decoding complex type declarations with a so-called "right-left rule," which is no simpler than the correct way of reading complex types. Many exercises are given, which is good, but the answers provided for the odd-numbered exercises contain so many errors that students quickly become frustrated. As a textbook in structured programming, this book is too specific to C. It also espouses design and programming methodologies which are in some cases irrelevant (of what use is a taxonomy of various forms of module cohesion?) and in other cases obsolete (why include an appendix on drawing flowcharts, which encourage goto-ridden programs?). I have used this textbook in my C programming class, under duress, and have found it to be more of a distraction than an asset. Comment | | (Report this)