Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Think Java - How to Think Like a Computer Scientist - Allen B Downey

Think Java - How to Think Like a Computer Scientist - Allen B Downey

Ratings: (0)|Views: 37|Likes:
Algoritmi Java
Algoritmi Java

More info:

Categories:Types, School Work
Published by: Ionel Alexandru Hosu on Feb 05, 2014
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Think Java
How to Think Like a Computer Scientist
Allen B. Downey5.1.2
 2012 Allen Downey.Permission is granted to copy, distribute, transmit and adapt this work undera Creative Commons Attribution-NonCommercial-ShareAlike 3.0 UnportedLicense:
If you are interested in distributing a commercial version of this work, pleasecontact Allen B. Downey.The original form of this book is L
TEX source code. Compiling this L
TEXsource has the effect of generating a device-independent representation of thebook, which can be converted to other formats and printed.The L
TEX source for this book is available from:
This book was typeset using L
TEX. The illustrations were drawn in xfig. Allof these are free, open-source programs.
“As we enjoy great Advantages from the Inventions of others, weshould be glad of an Opportunity to serve others by any Inventionof ours, and this we should do freely and generously.”—Benjamin Franklin, quoted in
 Benjamin Franklin 
 by EdmundS. Morgan.
Why I wrote this book
This is the fifth edition of a book I started writing in 1999, when I wasteaching at Colby College. I had taught an introductory computer scienceclass using the Java programming language, but I had not found a textbookI was happy with. For one thing, they were all too big! There was no way mystudents would read 800 pages of dense, technical material, even if I wantedthem to. And I didn’t want them to. Most of the material was too specific—details about Java and its libraries that would be obsolete by the end of thesemester, and that obscured the material I really wanted to get to.The other problem I found was that the introduction to object-oriented pro-gramming was too abrupt. Many students who were otherwise doing well just hit a wall when we got to objects, whether we did it at the beginning,middle or end.So I started writing. I wrote a chapter a day for 13 days, and on the 14thday I edited. Then I sent it to be photocopied and bound. When I handed itout on the first day of class, I told the students that they would be expectedto read one chapter a week. In other words, they would read it seven timesslower than I wrote it.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->