C Programming for Engineering and Computer Science (B.E.S.T. Series) [Paperback]

H.H. Tan (Author), Tim D'Orazio (Author)

Book Description

ISBN-10: 0079136788 | ISBN-13: 978-0079136787 | Publication Date: September 17, 1998 | Edition: 1

Readers without a computer programming background will now be able to design programs and write efficient, structured applications in C--thanks to this thorough guide. Example programs are contained on a disk packaged with the book. An introduction to C++ is included that prepares the reader for learning this important language in the future.

Product Details

• Paperback: 600 pages
• Publisher: McGraw-Hill Science/Engineering/Math; 1 edition (September 17, 1998)
• Language: English
• ISBN-10: 0079136788
• ISBN-13: 978-0079136787
• Product Dimensions: 9.2 x 7.3 x 1.2 inches
• Shipping Weight: 2.6 pounds (View shipping rates and policies)
• Average Customer Review: 4.0 out of 5 stars  See all reviews (1 customer review)
• Amazon Best Sellers Rank: #48,176 in Books (See Top 100 in Books)
  • #50 in Books > Computers & Technology > Programming > C

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

3 of 5 people found the following review helpful:

4.0 out of 5 stars textbook_critic, March 15, 2003

By 

Gerard J. Sagliocca "gerard_socialcritic" (schenectady, ny United States) - See all my reviews
(REAL NAME)   

This review is from: C Programming for Engineering and Computer Science (B.E.S.T. Series) (Paperback)

This computer programming text will serve students well both as as a text or as a quick authoritative desk reference.

The authors'focus on answering the most common questions asked by beginning students in C computer programming is great. They also spend quite a bit of effort showing the differences among subtle symbology.

Note I think the people who invented C language did a huge injustice to all students of C by being very sloppy with their chosen set of symbols especially for "Pointers" -- which is often used in solving most intermediate and advanced programming problems.

This book tries to get to the root of all the confusion and sloppiness of the orignal inventors and thus end up greatly helping beginning students. Once students overcome all the sloppy terms and symbols carelessly adopted by the original designers then they can begin to enjoy the C langauge and make it do some wonderful things. But the learning curve is typically long and tedious to slowly overcome all the nuances in the language.

Sometimes I even feel that C language should be phased out completely and allow C++ to be the sole langauge for all beginning student computer programmers. But people are reluctant to change anything -- just like the '80's attempt trying to phase out English dimensional sytem with the Metric system.

Again this text understands all the areas of sloppiness that lead often to confusion and then goes to work at clearly explaining them all.

Normally it's a tough job to clear up others confusion but these 2 authors apparently were highly motivated and committed at trying to take a good stab at all inherent problems in communication -- which, in my view, most technical people don't pay enough attention to. They seem to think that after they design some complex system it's someone elses problem to figure out what they designed.

The original designers of C language certainly have caused a lot of unnecessary headaches for many beginning students trying to learn C; and this book focuses on being a Bridge to understanding this shadowy language which, in my view, again should be phased out altogether, or the designers should fix the confusing symbology and often unnecessary cryptic shorthand for almost everything in their C language. Note C was designed when computer memory was [more money] and limited, and the designers got very creative at working under this environment. But did they think about future students trying to learn this often confusing and thus, difficult langauge?

The only suggestion for the book is that the publisher should have used larger font for titles and subtitles and theoretically should have aimed for new page for each subsection. I could never undestand publisher's use of the bottom of a page for major subsection.

G. Jerry Sagliocca, P.E.
Schenectady, New York