preface.htm

This is the second part of that lab manual to teach you how to make real-time programme and how to d

downloading the text version of the book and running the program
<B>ExtractCode</B> (from Volume 2 of this book), the source for which is also
provided on the Web site. The program will create a directory for each chapter
and unpack the code into those directories. In the starting directory where you
unpacked the code you will find the following copyright notice:</FONT><BR></P></DIV>

<BLOCKQUOTE><FONT SIZE = "+1"><PRE>//:! :CopyRight.txt
Copyright (c) MindView, Inc., 2001
Source code file from the book 
"Thinking in C++, 2nd Edition, Volume 2."
All rights reserved EXCEPT as allowed by the
following statements: You can freely use this file
for your own work (personal or commercial),
including modifications and distribution in
executable form only. Permission is granted to use
this file in classroom situations, including its
use in presentation materials, as long as the book
"Thinking in C++" is cited as the source. 
Except in classroom situations, you cannot copy
and distribute this code; instead, the sole
distribution point is http://www.BruceEckel.com 
(and official mirror sites) where it is
freely available. You cannot remove this
copyright and notice. You cannot distribute
modified versions of the source code in this
package. You cannot use this file in printed
media without the express permission of the
author. Bruce Eckel makes no representation about
the suitability of this software for any purpose.
It is provided "as is" without express or implied
warranty of any kind, including any implied
warranty of merchantability, fitness for a
particular purpose or non-infringement. The entire
risk as to the quality and performance of the
software is with you. Bruce Eckel and the
publisher shall not be liable for any damages
suffered by you or any third party as a result of
using or distributing software. In no event will
Bruce Eckel or the publisher be liable for any
lost revenue, profit, or data, or for direct,
indirect, special, consequential, incidental, or
punitive damages, however caused and regardless of
the theory of liability, arising out of the use of
or inability to use software, even if Bruce Eckel
and the publisher have been advised of the
possibility of such damages. Should the software
prove defective, you assume the cost of all
necessary servicing, repair, or correction. If you
think you've found an error, please submit the
correction using the form you will find at
www.BruceEckel.com. (Please use the same
form for non-code errors found in the book.)
///:~</PRE></FONT></BLOCKQUOTE>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">You may use the code in your projects and
in the classroom as long as the copyright notice is
retained.</FONT><A NAME="_Toc312373776"></A><A NAME="_Toc462305072"></A><A NAME="_Toc519041873"></A><BR></P></DIV>
<A NAME="Heading12"></A><FONT FACE = "Verdana, Tahoma, Arial, Helvetica, Sans"><H2 ALIGN="LEFT">
Language standards</H2></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">Throughout this book, when referring to
conformance to the ANSI/ISO C standard, I will generally just say
&#8216;<B>C<A NAME="Index3"></A><A NAME="Index4"></A></B>.&#8217; Only if it is
necessary to distinguish between Standard C and older, pre-Standard versions of 
C will I make the distinction.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">At this writing the ANSI/ISO C++
committee <A NAME="Index5"></A><A NAME="Index6"></A><A NAME="Index7"></A>was
finished working on the language. Thus, I will use the term <I>Standard
C++<A NAME="Index8"></A><A NAME="Index9"></A></I> to refer to the standardized
language. If I simply refer to C++ you should assume I mean &#8220;Standard
C++.&#8221;</FONT><A NAME="_Toc312373777"></A><A NAME="_Toc462305073"></A><A NAME="_Toc519041874"></A><BR></P></DIV>
<A NAME="Heading13"></A><FONT FACE = "Verdana, Tahoma, Arial, Helvetica, Sans"><H3 ALIGN="LEFT">
Language support</H3></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">Your compiler may not support all the
features discussed in this book, especially if you don&#8217;t have the newest
version of your compiler. Implementing a language like C++ is a Herculean task,
and you can expect that the features will appear in pieces rather than all at
once. But if you attempt one of the examples in the book and get a lot of errors
from the compiler, it&#8217;s not necessarily a bug in the code or the compiler
&#8211; it may simply not be implemented in your particular compiler
yet.</FONT><A NAME="_Toc312373778"></A><A NAME="_Toc462305075"></A><A NAME="_Toc519041875"></A><BR></P></DIV>
<A NAME="Heading14"></A><FONT FACE = "Verdana, Tahoma, Arial, Helvetica, Sans"><H2 ALIGN="LEFT">
Seminars, CD Roms &amp; consulting</H2></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">My company, MindView, Inc., provides
public hands-on training seminars based on the material in this book, and also
for advanced topics. Selected material from each chapter represents a lesson,
which is followed by a monitored exercise period so each student receives
personal attention. We also provide on-site training, consulting, mentoring, and
design &amp; code walkthroughs. Information and sign-up forms for upcoming
seminars and other contact information can be found at
<B>http://www.BruceEckel.com</B>.</FONT><A NAME="_Toc312373779"></A><A NAME="_Toc462305076"></A><A NAME="_Toc519041876"></A><BR></P></DIV>
<A NAME="Heading15"></A><FONT FACE = "Verdana, Tahoma, Arial, Helvetica, Sans"><H2 ALIGN="LEFT">
Errors<BR><A NAME="Index10"></A><A NAME="Index11"></A><A NAME="Index12"></A></H2></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">No matter how many tricks a writer uses
to detect errors, some always creep in and these often leap off the page for a
fresh reader. If you discover anything you believe to be an error, please use
the correction form you will find at <B>http://www.BruceEckel.com</B>. Your help
is
appreciated.</FONT><A NAME="_Toc312373780"></A><A NAME="_Toc462305077"></A><A NAME="_Toc519041877"></A><BR></P></DIV>
<A NAME="Heading16"></A><FONT FACE = "Verdana, Tahoma, Arial, Helvetica, Sans"><H2 ALIGN="LEFT">
Acknowledgements</H2></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">The ideas and understanding in this book
have come from many sources: friends like Chuck Allison, Andrea Provaglio, Dan
Saks, Scott Meyers, Charles Petzold, and Michael Wilk; pioneers of the language
like Bjarne Stroustrup, Andrew Koenig, and Rob Murray; members of the C++
Standards Committee like Nathan Myers (who was particularly helpful and generous
with his insights), Tom Plum, Reg Charney, Tom Penello, Sam Druker, and Uwe
Steinmueller; people who have spoken in my C++ track at the Software Development
Conference; and very often students in my seminars, who ask the questions I need
to hear in order to make the material clearer.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">I have been presenting this material on
tours produced by Miller Freeman Inc. with my friend Richard Hale Shaw.
Richard&#8217;s insights and support have been very helpful (and Kim&#8217;s,
too). Thanks also to KoAnn Vikoren, Eric Faurot, Jennifer Jessup, Nicole
Freeman, Barbara Hanscome, Regina Ridley, Alex Dunne, and the rest of the cast
and crew at MFI.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">The book design, cover design, and cover
photo were created by my friend Daniel Will-Harris, noted author and designer,
who used to play with rub-on letters in junior high school while he awaited the
invention of computers and desktop publishing. However, I produced the
camera-ready pages myself, so the typesetting errors are mine.
Microsoft<SUP>&reg;</SUP> Word for Windows 97 was used to write the book and to
create camera-ready pages. The body typeface is [Times for the electronic
distribution] and the headlines are in [Times for the electronic
distribution].</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">A special thanks to all my teachers, and
all my students (who are my teachers as well).</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">Personal thanks to my friends Gen Kiyooka
and Kraig Brockschmidt. The supporting cast of friends includes, but is not
limited to: Zack Urlocker, Andrew Binstock, Neil Rubenking, Steve Sinofsky, JD
Hildebrandt, Brian McElhinney, Brinkley Barr, Larry O&#8217;Brien, Bill Gates at
Midnight Engineering Magazine, Larry Constantine &amp; Lucy Lockwood, Tom
Keffer, Greg Perry, Dan Putterman, Christi Westphal, Gene Wang, Dave Mayer,
David Intersimone, Claire Sawyers, Claire Jones, The Italians (Andrea Provaglio,
Laura Fallai, Marco Cantu, Corrado, Ilsa and Christina Giustozzi), Chris &amp;
Laura Strand, The Almquists, Brad Jerbic, Marilyn Cvitanic, The Mabrys, The
Haflingers, The Pollocks, Peter Vinci, The Robbins Families, The Moelter
Families (&amp; the McMillans), The Wilks, Dave Stoner, Laurie Adams, The
Penneys, The Cranstons, Larry Fogg, Mike &amp; Karen Sequeira, Gary Entsminger
&amp; Allison Brody, Chester Andersen, Joe Lordi, Dave &amp; Brenda Bartlett,
The Rentschlers, The Sudeks, Lynn &amp; Todd, and their families. And of course,
Mom &amp; Dad. </FONT><BR></P></DIV>
<HR><DIV ALIGN="LEFT"><P><A NAME="fn1" HREF="#fnB1">[1]</A><FONT FACE="Georgia" SIZE=2>
Bjarne Stroustrup, <I>The C++ Programming Language</I>, Addison-Wesley, 1986
(first edition).</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><A NAME="fn2" HREF="#fnB2">[2]</A><FONT FACE="Georgia" SIZE=2>
<I>Using C++</I>,<I> </I>Osborne/McGraw-Hill 1989.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><A NAME="fn3" HREF="#fnB3">[3]</A><FONT FACE="Georgia" SIZE=2>
<I>Using C++</I> and <I>C++ Inside &amp; Out</I>,<I> </I>Osborne/McGraw-Hill
1993.</FONT><BR></P></DIV>

<DIV ALIGN="CENTER">
    <FONT FACE="Verdana, Tahoma, Arial, Helvetica, Sans" size = "-1">
     [ <a href="FrontMtr.htm">Previous Chapter</a> ] 
    
    [ <a href="SimpCont.htm">Short TOC</a> ] 
    [ <a href="Contents.htm">Table of Contents</a> ] 
  
        [ <a href="DocIdx.htm">Index</a> ]
        
     [ <a href="Part1.htm">Next Chapter</a> ] 
    </FONT>
    <BR>
 Last Update:09/26/2001</P></DIV>

</BODY>

</HTML>