C++ Iostreams Handbook
Books are like computer software.  After cycles of writing andtesting they reach a state where they are nearly finished, andthat state then persists for the rest oftheir lives.  It's alwayspossible to find points that could be better stated, sentencesthat could be better structured, and topics that could be addedor expanded.Despite any misgivings, the time has arrived to finish this bookand have it fixed in print.  The idea was originally conceivedbecause of the rather striking absence of published informtion onC++ IOStreams.  In that sense the book is long overdue.  I knowfrom numerous conversations that many C++ users are interestedinIOStreams, and can vaguely see its potential, but have more orless given up on the idea through lack of documentation.  Thisbook is for those C++ programmers; users who are already familiarwith the language, but who want to extend their view of itsidioms and areas of application.The intention of the book, quite probably an overambitious one,is that it should cover the whole spectrum of requirements forthose who need information on the subject.  So there are a numberof elements which I have tried to cover:An attempt to explain WHY IOStreamsA basic road map for the structure of the IOStreams systemExamples of straightforward and more devious usage of IOStreams in cookbook chaptersManual page style material which can be used for referenceThe mysteries of manipulatorsImplementation details to provoke future implementors into doing things betterStrategies, examples, and guidelines for the provision ofIOStreams facilities for user defined typesThere are a number of people who should share the credit for theC++ IOSTREAMS HANDBOOK.  The first is Jerry Schwartz, who createdthe IOStreams system, and was then too busy to do the book.  Ithank him for the opportunity even if only by default.  Next, Ishould acknowledge the roles of Paul Leathers and Walter Brightof Zortech, Inc.  They gave me a deadline date for a workingversion of IOStreams, and thus made me find out what the systemwas supposed to do.  I must also thank the language group ofSymantec Corporation, who gave me yet another opportunity to tryout my ideas on a real product.The next is my wife Lynn.  If I hadn't met her I would probablynot have ended up as a long-term visitor to the United Stateswith enough time on my hands to record the resulting expertise. The next is Debbie Lafferty of Addison-Wesley's computer sciencedivision, who has supported the project throughout, and whorecruited my formidable array of reviewers.  Both Lynn and Debbiewere kind enough to assume that I could actually come up with thebook given an appropriate combination of encouragement andarm-twisting.The reviewers, Stephen D. Clamage, Jim Coplien, Margaret A.Ellis, Stanley Lippman, Jerry Schwartz, Steve Vinoski, and NancyWilkinson all clearly spent a good deal of time and effort intheir contribution to the book.  My thanks to all of them.I'd also like to thank Helen Wythe for coordinating theproduction ofthe book.  My copy editor was Laura Michaels, and Ithank Laura for her patient work.  The cover was the brain-childof Peter Blaiwas, and I want to thank him for his sense offrivolity.  Perceptive collectors of Addison-Wesley computerscience books will notice that this book is participating in atrend or fashion, the "creatures" series.  You've seen the Dragonbook, and the Teddy Bear book, to name just a couple--well, thisis the Fish book.  I have to say that this is more of a pun thanan attempt at association.  Both the Dragon book and the TeddyBear book are objects of my greatest respect.  0201596415P04062001