Free PDF Software Tools, by Brian W. Kernighan, P. J. Plauger
Software Tools, By Brian W. Kernighan, P. J. Plauger. Let's review! We will certainly typically figure out this sentence anywhere. When still being a childrens, mommy used to get us to always review, so did the teacher. Some books Software Tools, By Brian W. Kernighan, P. J. Plauger are fully read in a week and also we require the obligation to assist reading Software Tools, By Brian W. Kernighan, P. J. Plauger Just what about now? Do you still enjoy reading? Is reading only for you who have obligation? Absolutely not! We below provide you a brand-new e-book entitled Software Tools, By Brian W. Kernighan, P. J. Plauger to review.
Software Tools, by Brian W. Kernighan, P. J. Plauger
Free PDF Software Tools, by Brian W. Kernighan, P. J. Plauger
Software Tools, By Brian W. Kernighan, P. J. Plauger. Give us 5 mins and also we will reveal you the very best book to read today. This is it, the Software Tools, By Brian W. Kernighan, P. J. Plauger that will be your finest choice for much better reading book. Your 5 times will not spend wasted by reading this web site. You could take the book as a source to make much better concept. Referring guides Software Tools, By Brian W. Kernighan, P. J. Plauger that can be positioned with your needs is sometime hard. Yet right here, this is so simple. You could discover the most effective thing of book Software Tools, By Brian W. Kernighan, P. J. Plauger that you could review.
When some individuals checking out you while reviewing Software Tools, By Brian W. Kernighan, P. J. Plauger, you could really feel so proud. Yet, rather than other people feels you need to instil in yourself that you are reading Software Tools, By Brian W. Kernighan, P. J. Plauger not due to that factors. Reading this Software Tools, By Brian W. Kernighan, P. J. Plauger will offer you greater than people admire. It will guide to understand greater than individuals looking at you. Already, there are several resources to knowing, reviewing a publication Software Tools, By Brian W. Kernighan, P. J. Plauger still ends up being the first choice as an excellent means.
Why must be reading Software Tools, By Brian W. Kernighan, P. J. Plauger Again, it will depend on exactly how you really feel and also think of it. It is surely that of the perk to take when reading this Software Tools, By Brian W. Kernighan, P. J. Plauger; you could take much more lessons directly. Also you have actually not undergone it in your life; you can obtain the experience by checking out Software Tools, By Brian W. Kernighan, P. J. Plauger As well as currently, we will certainly introduce you with the on the internet book Software Tools, By Brian W. Kernighan, P. J. Plauger in this site.
What kind of publication Software Tools, By Brian W. Kernighan, P. J. Plauger you will choose to? Currently, you will certainly not take the printed book. It is your time to obtain soft data publication Software Tools, By Brian W. Kernighan, P. J. Plauger instead the printed papers. You can appreciate this soft data Software Tools, By Brian W. Kernighan, P. J. Plauger in any time you anticipate. Even it remains in expected place as the various other do, you could check out the book Software Tools, By Brian W. Kernighan, P. J. Plauger in your gizmo. Or if you desire more, you could continue reading your computer or laptop computer to obtain full display leading. Juts find it right here by downloading and install the soft data Software Tools, By Brian W. Kernighan, P. J. Plauger in link web page.
- Sales Rank: #364363 in Books
- Published on: 1976-01-11
- Original language: English
- Number of items: 1
- Dimensions: 9.20" h x .90" w x 6.20" l, 1.11 pounds
- Binding: Paperback
- 352 pages
From the Back Cover
With the same style and clarity that characterized their highly acclaimed book, The Elements of Programming Style, the authors have written Software Tools to teach how to write good programs that make good tools. The programs contained in the book are not artificial, but are actual programs ae tools which have proved valuable in the production of other programs.
Modern programming techniques such as structured programming and top-down design are emphasized and applied to every program. The programs are presented in a structured language called Ratfor ("Rational Fortran") which can be easily understood by anyone familiar with Fortran or PL/I, Algol, PASCAL, or similar languages. (Ratfor translates readily into Fortran or PL/I. One of the tools presented is a preprocessor to translate Ratfor into Fortran). All of the programs are complete and have been tested directly from the text. The programs are available in machine-readable form from Addison-Wesley.
Software Tools is ideal for use in a "software engineering" course, for a second course in programming, or as a supplement in any programming course. All programmers, professional and student, will find the book invaluable as a source of proven, useful programs for reading and study. Numerous exercises are provided to test comprehension and to extend the concepts presented in the text.
020103669XB04062001
About the Author
Brian W. Kernighan works in the Computing Science Research Center at Bell Laboratories, Lucent Technologies. He is Consulting Editor for Addison-Wesley's Professional Computing Series and the author, with Dennis Ritchie, of The C Programming Language.
P.J. Plauger is President of Whitesmiths, Ltd., New York. Dr. Plauger received a Ph.D. in Nuclear Physics from Michigan State University. He is a member of ACM, the American Physical Society, and the Science Fiction Writers of America.
020103669XAB04062001
Most helpful customer reviews
11 of 11 people found the following review helpful.
It's what's under the hood
By Brian Connors
The tools you will find in this book are ancient. They're written in a cockeyed hybrid of C and Fortran, and they're almost hilariously user-hostile by modern definitions. If this intimidates you, look at it this way -- you're looking under the hood of modern applications. Much modern word processing, page layout, and language implementation can be built by putting a nice, shiny coating on what you find in this book.
Kernighan and Plauger set out in this book to document what they used in their labs at the time it was written, and show how to build them. Ratfor was chosen because C was not as widespread then as it is now, and for those who didn't have it, a translator to standard Fortran '77 was one of the major parts of the book. A simplified version of the nroff text formatter and a version of ed are also included for text file processing (then as now one of the major uses for computers), the result being both a toolkit and a practical education in the ins and outs of applications development.
The environment given is not Unix-based inherently, but this book is a natural companion to Kernighan and Rob Pike's The Unix Programming Environment and John Lions' Commentary on Unix 6th Edition. It should be required reading for anyone who wants to do software development.
9 of 10 people found the following review helpful.
A classic text on software engineering
By You Xu
In a certain way, software engineering is an art. In the past few decades, we have found some best practices. Nowadays there are tons of buzzwords out there -- agile, BDD, TDD, KISS... It's easy to get lost in the jungle of "software engineering methodologies". There is no silver bullet though. Instead of chasing those buzzwords in the hope of finding the best way to write software, my personal experience tells me that we should go back to the root of software engineering: why we are writing software, and what is the relationship between software developer, software, and machine. I think Software Tools answered those fundamental questions elegantly. Or, at least it brought up those questions.
This book covers almost every aspect of programming, in the context of writing practical command line tools for UNIX. At that time, FORTRAN was the de facto programming language. There was a big cognitive gap between the programming language at hand (unstructured, messy, low-level), and the programming model in our head (structured, clean, abstract, high-level). To address this problem, the authors proposed to build software "into" the programming language, instead of "in" the programming language. This insight is still valid today, because we still haven't found a programming language that can match the thought pattern of human brain directly. We still have to manually translate our high-level thoughts into low-level program statements. Software engineering about conquering not only the complexity of the outside world (e.g. the inherent complexity of the task that software want to handle), but also the complicity of the programming language itself (e.g. the language itself is not as neat as our thoughts). After all, there is little software engineering concern if the task at hand can be done with a domain-specific language (very high-level usually) in 100 lines. Complexity comes in when we cannot have a language that is high-level enough to match the task at hand, so we need to organize the code to better match the tasks.
The idea of programming into language is so old, yet so new. It was first proposed by the generation of early LISP programmers. They would build their own LISP from ground-up, up till the level where they can use the new LISP to solve the problem. The problem is, your language is not LISP. In fact, your language sucks. I am sure that there are good features in every programming language, but you can hardly find all your favorite language features or high-level constructions/libraries in one language. The fact that there is no silver bullet language calls us to patch up, to enhance our language, until it matches the abstraction level of our mental model, or the tasks at hand.
Software tools is the book that teaches you how to use your language to build clean and useful blocks and then get things done. It does so by building some of the most useful tools in the UNIX programming environment. Once you followed the idea of building into a language, language will not be your obstacle, and all the best practices are in fact ways to enhance the language (e.g. design patterns).
I also enjoy the writing style of this book. There are hands-on examples across the book. There is no checklist/dogma, but examples and tips drawing from those examples. You can get a lot from it if you actually try to build those software tools in C.
Anyway, do not miss this classic if you really wants to craft good software. For me, it is the missing manual for me to conquer my stupid programming language. Programming languages are and will always be stupid, and that's why I need to transform them to be MY language. Using this book to guide that transformation today, and you will be more productive when using your language.
26 of 26 people found the following review helpful.
Classic on software design
By A Williams
Elsewhere on Amazon I reviewed Kernighan's "Elements of Programming Style." To quote one paragraph from that review -
Brian Kernighan has co-authored three books almost essential to learning our craft, this volume, "Software Tools" and "The Unix Programming Environment". "Elements of Programming Style" spells out the fundamental rules, "Software Tools" shows you how to apply them to a number of simple projects and extends the rules to software design and finally "The Unix Programming Environment" shows you how to use them in an operating system designed to reward you for your effort.
It could be said that "Elements" teaches programming and "Software Tools" teaches software design. Rules such as "do just one thing, do it well" seem to seep in through the pores as you read and work through this book.
It presents a number of projects starting with a word count program and progressing through some filters to some fairly complex tasks culminating in a RatFor pre-processor for Fortran. All the examples are written in RatFor, a version of Fortran that adds some more structured elements to that early language.
Don't be put off by the use of RatFor, the language is easily understood and the style of programming so clear that the algorithms are easily understood. I've personally translated a fair number of them to both BASIC and C and the RatFor pre-processor design became the basis for an AppleSoft BASIC pre-processor written by a close friend.
I've relied on this book so much for the last ten years, after writing "Hello World" I drag it out and translate a couple of the tools into every new language I've learnt. I then spend a day or two thinking about and implementing a design optimised for the new language. After that I find I have a good handle on a language and how to design for it.
This volume is not for those who want a book that gives them pre-written tools, a fair number of the tools are standard issue on any Unix derivative and the code is only tersely commented, relying on the exaplanatory text. However I recommend this book to all software designers and programmers because as you work through these examples you will learn a great deal about honing your craft.
Software Tools, by Brian W. Kernighan, P. J. Plauger PDF
Software Tools, by Brian W. Kernighan, P. J. Plauger EPub
Software Tools, by Brian W. Kernighan, P. J. Plauger Doc
Software Tools, by Brian W. Kernighan, P. J. Plauger iBooks
Software Tools, by Brian W. Kernighan, P. J. Plauger rtf
Software Tools, by Brian W. Kernighan, P. J. Plauger Mobipocket
Software Tools, by Brian W. Kernighan, P. J. Plauger Kindle
Tidak ada komentar:
Posting Komentar