
	Where results make sense

Topic: The Elements of Programming Style (book)

Related Topics

comic book

Domesday Book

Book of Mormon

Book of Revelations

Books of Kings

Books of Chronicles

Books of Samuel

The Jungle Book

Guinness Book of Records

Book of Genesis

Book of Judges

National Book Award

In the News (Mon 28 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Brian Kernighan - Wikipedia, the free encyclopedia
		Brian Wilson Kernighan (pronounced Ker'-ni-han; the 'g' is silent; born 1942) is a computer scientist who worked at the Bell Labs and contributed to the design of the pioneering AWK and AMPL programming languages.
		Kernighan's name became widely known through co-authorship of the first book on the C programming language with Dennis Ritchie.
		The Elements of Programming Style (1982 with P.
	en.wikipedia.org /wiki/Brian_Kernighan (337 words)

	Manning: Elements of Programming with Perl
		Elements of Programming with Perl is a general introduction to programming, using Perl as the implementation language.
		Elements of Programming with Perl is designed for the new programmer who needs to know Perl, and for the regular Perl user who would like to improve his or her programming skills.
		Elements of Programming with Perl communicates the basics of the language without the smarty-pants tone that the O'Reilly book slips into from time to time.
	www.manning.com /johnson (874 words)

	SOME CLASSIC READS
		Representative of most large programming efforts, the OS/360 project was fraught with difficulties and this book was intended as a post-op dissection of the problems faced and mistakes made.
		Given the diverse programming styles contained in these languages, it was clear that I needed to learn certain language-independent habits which could be carried over to any and all programming languages.
		At the time this book was written, the debate over structured programming had already been resolved and the authors were free to espouse these precepts.
	www.tprthai.net /reads.htm (1335 words)

	Blogger: Email Post to a Friend
		They started out the book mired in the hell of FORTRAN, an environment which many programmers of that day, including even the bulk of the Computer Science Majors at Georgia Tech, were stuck in.
		And they shared their work with the world, by making all of the programs in the book available by nine-track tape, letting computer centers the world over bootstrap themselves into a dramatically better environment in a matter of hours.
		Most amazing was the collection of complete, significant, highly-readable programs that had been written by the end of the book, including a text editor, a word processor, and the Ratfor preprocessor itself.
	www.blogger.com /email-post.g?blogID=6942756&postID=108426590722202656 (473 words)

	Book Guide - Elements of Programming with Perl (Site not responding. Last check: 2007-11-01)
		This book is a general introduction to programming, using Perl as the implementation language.
		It covers all the fundamental elements of Perl (e.g., pattern matching and text processing) and proceeds to advanced concepts, including modular programming, abstract data structures, and object oriented programming.
		This book is designed for new programmers who need to know Perl and for regular Perl users who would like to improve their programming skills.
	archive.devx.com /free/books/bookview.asp?content_id=1620 (116 words)

	Textbooks, CSC 209
		It is targetted at people with a good understanding of computer programming in general, but no knowledge of C or unix.
		This book does have some redeeming features, but when we used this as a 209 textbook we knew we were still looking.
		This is not a very 209-relevant book, but actually it doesn't fit any course in our curriculum because it's based on a rather different curriculum structure (and the book's use at the authors' university involved a curriculum restructuring).
	www.dgp.toronto.edu /~ajr/209/textbooks.html (807 words)

	Look Toward the Past
		Because programming in Clipper is not significantly different from programming in C, Pascal or BASIC nor would I imagine particularly different from programming in Ada, COBOL, Forth, FORTRAN or SmallTalk.
		In the book, The C Programming Language a very simple example is used to illustrate C syntax and program structure.
		Books that present code on UNIX tools and general computer science books on stacks, queues, linked-lists and b-trees are filled with great information.
	www.leylan.com /app.asp?pg=look (2329 words)

	Book Review of the Week (Site not responding. Last check: 2007-11-01)
		What these three books have in common is a list of rules, each with a brief explanation and examples of correct use.
		This little book is more a compendium of common wisdom that has been distilled from years of programming practice.
		Nevertheless, a little book like this is a good way to pass on the distilled "common sense" to novices to whom the rules do not yet sound familiar.
	archive.devx.com /free/books/bookreview.asp?bookid=454 (668 words)

	Book: The elements of programming style [by] Brian W. Kernighan [and] P. J. Plauger. (Site not responding. Last check: 2007-11-01)
		Book: The elements of programming style [by] Brian W. Kernighan [and] P. Plauger.
		The elements of programming style [by] Brian W. Kernighan [and] P. Plauger.
		Title: The elements of programming style [by] Brian W. Kernighan [and] P. Plauger.
	www.csclub.uwaterloo.ca /office/books/73020165__.html (79 words)

	The programming style
		The programming style is -- shortly stated -- the style of organizing the program.
		The program for example should begin with the keyword begin and when begin is not present, it is a syntax error.
		The compiler "thinks" that all the rest of the program is a part of that loop and compiles nearly all without detecting an error and stops only when the period after the final end is detected.
	cs.felk.cvut.cz /~berezovs/vtp_a/eps.htm (2214 words)

	Steven Augart's Reading, June, 2003 (Site not responding. Last check: 2007-11-01)
		At the time I read this book, I was interested in it almost exclusively for help with English Language phonetics, as part of my study of the Shaw Alphabet.
		This book discusses some of the things that former Secretary of Defense McNamara learned as a result of having open discussions with his former enemies, to wit, his Vietnamese counterparts.
		I got this book from the LA Public Library (LAPL) because it was quicker to get it than to get one of the English-language copies.
	augart.com /Books/through-2003-June.html (2181 words)

	Rich Burridge's Blog : Weblog
		The Elements of Programming Style by Brian Kernigan and P. Plauger.
		The Elements of Style by William Strunk Jr.
		Object oriented programming being the norm was still many years off (I still remember the special August 1981 Smalltalk issue of BYTE magazine that got me interested in it).
	blogs.sun.com /roller/page/richb/20050522 (406 words)

	Notes on Programming in C (Site not responding. Last check: 2007-11-01)
		But sometimes I feel its concise rules were taken as a cookbook approach to good style instead of the succinct expression of a philosophy they were meant to be.
		A classic example of this is parsing tables, which encode the grammar of a programming language in a form interpretable by a fixed, fairly simple piece of code.
		One of the reasons data-driven programs are not common, at least among beginners, is the tyranny of Pascal.
	www.csl.cornell.edu /courses/ece699/pike_C.htm (2213 words)

	Programming style (Site not responding. Last check: 2007-11-01)
		Programming style is a term used to describe the effort a programmer should take to make his or her code easy to read and easy to understand.
		Here are styles and conventions to help any reader to understand what the program does and why.
		There is also a summary I found in the book The Elements of Programming Style, Kernighan & Plauger, McGraw-Hill, 1978.
	www.uow.edu.au /~hasan/buss110/progrm1/style.htm (365 words)

	ERCB: DDJ Programmer's Bookshelf June 1999
		The way we program might not change in the next two decades, but the hardware our programs run on is bound to.
		Programming a massively parallel machine is still no easy task, as the failure of the parallel computing start-ups of the last two decades shows.
		The style is academic -- there are a lot of references, and a lot of proofs and lemmas -- but the book will be a rich mine of ideas for anyone who is trying to persuade a computer to turn data into dots, boxes, lines, and arrows.
	www.ercb.com /ddj/1999/ddj.9906.html (1099 words)

	Notes on Programming in C
		Although many people think programs should look like the Algol-68 report (and some systems even require you to edit programs in that style), a clear program is not made any clearer by such presentation, and a bad program is only made laughable.
		Most programs are too complicated -- that is, more complex than they need to be to solve their problems efficiently.
		Finite state machines are particularly amenable to this form of attack, but almost any program that involves the `parsing' of some abstract sort of input into a sequence of some independent `actions' can be constructed profitably as a data-driven algorithm.
	pantransit.reptiles.org /prog/pikestyle.html (2220 words)

	[No title] (Site not responding. Last check: 2007-11-01)
		The main factor has been the shift to block-structured programming languages and the development of block-structured discipline (to which tEoPS was a large contributor): using Pascal or C, it takes a determined weasel to write really bad programs (indeed only about half the points from Kernighan and Plauger are relevant to you as C programmers).
		This style is self-consistent: the rules for BEGIN/END's or {}'s around function bodies is the same as for if's, switch/case, data structure declarations, etc. The END's or close-curlies unwind uniformly at the bottom of nested structures (so that a missing one stands out).
		Users of his program are occasionally disappointed when the program prints out an internal error check message and dies; they can usually figure out how to change their input so they won't hit the bug, and having done so, they have confidence that they're back on safe ice.
	www.glenn.delahoy.com /blog/Taxonomy.htm (4099 words)

	Barnes & Noble.com - Software Tools - Brian W. Kernighan - Paperback
		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.
		All of the programs are complete and have been tested directly from the text.
	btobsearch.barnesandnoble.com /BookSearch/isbnInquiry.asp?isbn=020103669X (275 words)

	Rich Cohen's 'Books I Wish I Had Written'
		On the other hand there are books that had a major impact on my life and outlook and which I take pride in showing and giving to others.
		These are books that I hope others will remember "Rich Cohen got me to read this book and I'm glad he did." Over the years I've given perhaps 50 books as gifts to clients and fellow professionals.
		This book focuses on the Macintosh, but it's real value is the insight it gives on the outlook, attitudes and methods of a world-class user interface designer.
	www.systemsguild.com /GuildSite/Books/Cohen.html (942 words)

	Taking Common Sense to the Extreme
		Although Elements of Programming Style is a classic, its RATFOR (rational Fortran) examples made me hesitant to recommend it to colleagues and students.
		To keep the volume of the book manageable, many concepts and ideas are presented in a cursory style and some examples are rather contrived.
		Although the books I mentioned in the first paragraph and Andrew Koenig's C Traps and Pitfalls (Addison Wesley, 1988) are unfortunately missing, the annotated bibliography can serve as a shopping list for populating a budding programmer's bookshelf.
	www.spinellis.gr /pubs/Breview/2000-IEEESW-Pragmatic/html/review.html (1121 words)

	Kernighan and Plauger's Rules (Site not responding. Last check: 2007-11-01)
		The Elements of Programming Style is a fairly old book -- it was published in 1974, and deals with FORTRAN and PL/I, "since these languages are widely used".
		Its guidelines are pretty much timeless, though, with a few changes needed to account for, for instance, the proliferation of debuggers and languages that don't rely on GOTO for branches.
		That way, people are motivated to fix their broken input, rather than trusting the program to hack around it -- often with subtle and unpleasant bugs resulting from programs that don't respond to bad input quite the way you expect.
	www.cs.sfu.ca /~mjolson/personal/sw-eng/rules/k-and-p.html (714 words)

	Brian Kernighan's Programming Style Tips (Site not responding. Last check: 2007-11-01)
		Here is a summary of the very important programming style tips from Brian Kernighan's 1994 guest CS50 lecture.
		Don't use conditional expressions as a substitute for a logical expression.
		Note: this book is still well worth reading- even though most of the examples are in languages that you probably haven't heard of, the principles are universal.
	www.eecs.harvard.edu /~ellard/CS50-95/programming-style.html (160 words)

	Preface
		This book is not an introduction to programming or Java.
		This book is modeled after the 1978 classic The Elements of Programming Style.
		The authors confessed in their preface, "We have no doubt that a few of our 'good' programs will provide 'bad' examples for some future writer." I believe the same can be said about this book.
	home.earthlink.net /~huston2/thebook/0a_Preface.html (481 words)

	Linux Weekly News
		The Art of Unix Programming is a book which will "explain the Zenlike 'special transmission, outside the scriptures' that distinguishes Unix gurus from ordinary mortals." Eric is seeking to write this book in a highly peer-reviewed manner; each chapter will go up separately and Eric will accept comments before putting up the next.
		These principles are to be combined with some relatively modern views of programming ("use interpreted languages") to make a sort of design handbook for the next round of cool applications.
		We have never pushed books too hard on our readers, but it is possible to get through to Amazon via our book reviews page.
	lwn.net /1999/1223 (1219 words)

	... 'Elements of C Programming Style' by Jay Ranade - at Loanspage.co.uk books for s.
		'Elements of C Programming Style' by Jay Ranade - at Loanspage.co.uk books for s.
		I recommend this book to anyone who understands C code but is unsatisfied with how readable thier code is. This book is lik
		Similar Music to 'Elements of C Programming Style' available at Psychohelp.co.uk...
	www.loanspage.co.uk /book/0070512787 (256 words)

	Neato Tech Books (J. Blustein)
		These are some books about computer programming that I think everyone should read.
		The best book about programming and programming style I have ever seen.
		This book helps to prevent such problems by showing how C programmers get themselves into trouble.
	www.csd.uwo.ca /~jamie/.Refs/tech-books.html (494 words)

	The Elements of Cache Programming Style
		The object of cache programming style is to increase this locality.
		Linux is written in the gcc programming language and a careful study of the gcc standards document, "Using and Porting GNU CC" [Stallman00], is therefore necessary: no one embraces and extends quite like Richard Stallman.
		As the number of elements increases and approaches the number of cache lines available, cache misses will gradually increase to the point of thrashing.
	www.linuxshowcase.org /2000/2000papers/papers/sears/sears_html (6220 words)

	Programming Style (Site not responding. Last check: 2007-11-01)
		The book Elements of Programming Style, Kernighan and Plauger (McGraw-Hill), is a classic guide to computer programming.
		Using another classic, Elements of Style (see English) for inspiration, the authors set out to demonstrate good programming styles.
		The book uses PL/I and FORTRAN for examples, but the code should be clear, even for COBOL programmers.
	www.robelle.com /library/smugbook/program.html (207 words)

	Rich Burridge's Blog : Weblog
		As the book suggests, I fired up the Abe Lincoln character and gave it some simple questions, but the answers were not responsive.
		I wish they'd been allowed to put better content on the CDROM for the book, although there is a footnote stating that by the time you read this Yapanda Intelligence Inc. will have a site setup where you'll be able to go and create your own heads in 3D using photos of yourself and friends.
		After the huge book I'd just finished reading previously, I wanted something shorter this time, so quickly picked this, off the bookshelf by the bed, full of the books I haven't read yet.
	blogs.sun.com /roller/page/richb/20040720#writing_good_code (4150 words)

	Softpanorama Computer Books Review / Classic Computer Science Books
		This book provides an interesting historical perspective that you can never obtain elsewhere: Unix at one time was an elegant small OS that grow into a huge monster, but somewhere under this tremendous complexity of the contemporary Unixes, there are still elegant solutions of the initial versions.
		The book stresses the issues that we know, but all too often forget: small is beautiful, every program should do one thing well.
		Likewise, a scaling-up of a software entity is not merely a repetition of the same elements in larger sizes; it is necessarily an increase in the number of different elements.
	www.softpanorama.org /Bookshelf/classic.shtml (2091 words)

Try your search on: Qwika (all wikis)