http://www.merlot.org:80/merlot/ A search of MERLOT materials Copyright 1997-2013 MERLOT. All rights reserved. Wed, 19 Jun 2013 13:26:43 PDT Wed, 19 Jun 2013 13:26:43 PDT http://www.merlot.org:80/merlot/images/merlot.gif http://www.merlot.org:80/merlot/ 44 34 http://www.merlot.org/merlot/viewMaterial.htm?id=335560 Covers the key features of the C language and its usage. The first five chapters help in thoroughly understanding the C syntax. The latter chapters focus on more complex concepts of the C language. http://www.merlot.org/merlot/viewMaterial.htm?id=313494 This book unites two approaches to teaching programming languages, one based on a survey of languages and the other on writing definitional interpreters. It has been used as a textbook at over fifteen institutions worldwide, and is referenced by non-academic users on the Web. The book is updated approximately every year. http://www.merlot.org/merlot/viewMaterial.htm?id=335524 eXtensible Markup Language (XML) is a widely-used computer language for creating and designing pages on the World Wide Web, and for defining other languages with more specialized purposes. This Wikibook provides a detailed description of XML, its origins, its programming, and its uses on the Internet today. This book also provides exercises with which to test the knowledge you have gained through the deliberate study of its contents. http://www.merlot.org/merlot/viewMaterial.htm?id=468429 According to the site, "The goal of this book, and this class, is to teach you to think like a computer scientist. I like the way computer scientists think because they combine some of the best features of Mathematics, Engineering, and Natural Science. Like mathematicians, computer scientists use formal languages to denote ideas (specifically computations). Like engineers, they design things, assembling components into systems and evaluating tradeoffs among alternatives. Like scientists, they observe the behavior of complex systems, form hypotheses, and test predictions. The single most important skill for a computer scientist is problem-solving. By that I mean the ability to formulate problems, think creatively about solutions, and express a solution clearly and accurately. As it turns out, the process of learning to program is an excellent opportunity to practice problem-solving skills. That's why this chapter is called 'The way of the program.' On one level, you will be learning to program, which is a useful skill by itself. On another level you will use programming as a means to an end. As we go along, that end will become clearer.״ http://www.merlot.org/merlot/viewMaterial.htm?id=468426 According to the author, "How to Think Like a Computer Scientist was not just an excellent book, but it had been released under the GNU public license, which meant it could be used freely and modified to meet the needs of its user. Once I decided to use Python, it occurred to me that I could translate Allen’s original Java version of the book into the new language. While I would not have been able to write a textbook on my own, having Allen’s book to work from made it possible for me to do so, at the same time demonstrating that the cooperative development model used so well in software could also work for educational materials.Working on this book for the last two years has been rewarding for both my students and me, and my students played a big part in the process. Since I could make instant changes whenever someone found a spelling error or difficult passage, I encouraged them to look for mistakes in the book by giving them a bonus point each time they made a suggestion that resulted in a change in the text. This had the double benefit of encouraging them to read the text more carefully and of getting the text thoroughly reviewed by its most important critics, students using it to learn computer science.For the second half of the book on object-oriented programming, I knew that someone with more real programming experience than I had would be needed to do it right. The book sat in an unfinished state for the better part of a year until the open source community once again provided the needed means for its completion.״