Structured COBOL Methods 1997 [Paperback]

Paul Noll (Author)

Book Description

Publication Date: January 1997

This little book doesn't teach COBOL itself. Instead, it teaches you how to design, code, and test your COBOL programs so they're easier to debug, document, and maintain. Just open up to any page, and picture what a difference these methods can make in the program you're working on right now. Then, start experimenting. You'll be delighted at the results.

Editorial Reviews

About the Author

Paul Noll

Product Details

• Paperback: 208 pages
• Publisher: Mike Murach & Associates (January 1997)
• Language: English
• ISBN-10: 0911625941
• ISBN-13: 978-0911625943
• Product Dimensions: 10 x 8 x 0.6 inches
• Shipping Weight: 1.3 pounds
• Average Customer Review: 3.5 out of 5 stars  See all reviews (2 customer reviews)
• Amazon Best Sellers Rank: #3,164,097 in Books (See Top 100 in Books)

More About the Author

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

Customer Reviews

Most Helpful Customer Reviews

3.0 out of 5 stars A Foot in the Past, July 3, 2002

By A Customer

This review is from: Structured COBOL Methods 1997 (Paperback)

While just about every other COBOL textbook has adopted the use of scope terminators (such as END-IF) in COBOL programs, Paul Noll still prefers the old periods. Now that COBOL has scope terminators, the use of periods should be discouraged because they are known to make program changes more bug-prone. After all, the original intent of structured programming methods was to make programs less bug-prone.

4.0 out of 5 stars Structured COBOL Methods, January 31, 2002

By 

Russell C. Bartlett (MI United States) - See all my reviews
(REAL NAME)   

This review is from: Structured COBOL Methods 1997 (Paperback)

I've read a number of books that purport to teach structured methods. This book is the best one I've found. It not only explains the theory behind it but also goes on to explain its practical appication. There is a section on top- down testing as well as various worked examples from batch to interactive applications. I liked the reference to the three critical coding principals. This book is definitely written by a programmer for programmers. It's easy to read and packed with valuable tips and techniques. A must for anyone wanting to write better, less error prone and more easily maintainable code.