Preface

Conventions Used in This Book

The following typographical conventions are used in this book:

4 comments

  1. Keith Fahlgren Posted 3 months, 6 days and 5 hours ago

    The paired comments below don't work.

  2. vari Posted 17 days and 17 hours ago

    i found this informative and interesting blog so i think so its very useful and knowledge able.I would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well.... http://www.play-roulette-free.net

  3. vari Posted 17 days and 17 hours ago

    i found this informative and interesting blog so i think so its very useful and knowledge able.I would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well..Play roulette for free

  4. Ram R. Posted 2 hours ago

    Can you also please add a section on who the target audience for the book is? E.g. experienced Java programmer etc.

Add a comment

Italic
Indicates new terms, URLs, email addresses, filenames, and file extensions. Many italicized terms are defined in the Glossary.
Constant width
Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.
Constant width bold
Shows commands or other text that should be typed literally by the user.
Constant width italic
Shows text that should be replaced with user-supplied values or by values determined by context.

Tip

This icon signifies a tip, suggestion, or general note.

Caution

This icon indicates a warning or caution.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: “Programming Scala by Dean Wampler and Alex Payne. Copyright 2009 O’Reilly Media, Inc., 978-0-596-15595-7.”

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at [email protected].

Getting the Code Examples

You can download the code examples from TODO. Unzip the files to a convenient location. See the README.txt file in the distribution for instructions on building and using the examples.

1 comment

  1. Keith Fahlgren Posted 3 months, 6 days and 5 hours ago

    TODO, huh?

Add a comment

Some of the example files can be run as scripts using the scala command. Others must be compiled into class files. Some files contain deliberate errors and won’t compile. We have adopted a file naming convention to indicate each of these cases, although as you learn Scala it should become obvious from the contents of the files, in most cases.

*-script.scala
Files that end in -script.scala can be run on a command line using scala, e.g., scala foo-script.scala. You can also start scala in the interpreter mode (when you don’t specify a script file) and load any script file in the interpreter using the :load filename command.
*-wont-compile.scala
Files that end in -wont-compile.scala contain deliberate errors that will cause them to fail to compile. We use this naming convention, along with one or more embedded comments about the errors, so it will be clear that they are invalid. Also, these files are skipped by the build process for the examples.
sake.scala
Files named sake.scala are used by our build tool, called sake. The README.txt file describes this tool.
*.scala
All other Scala files must be compiled using scalac. In the distribution, they are used either by other compiled or script files, such as tests, not all of which are listed in the book.

Safari® Books Online

Note

When you see a Safari® Books Online icon on the cover of your favorite technology book, that means the book is available online through the O’Reilly Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you easily search thousands of top tech books, cut and paste code samples, download chapters, and find quick answers when you need the most accurate, current information. Try it for free at http://safari.oreilly.com.

How to Contact Us

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc
1005 Gravenstein Highway North
Sebastopol, CA 95472
800-998-9938 (in the United States or Canada)
707-829-0515 (international or local)
707 829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:

http://www.oreilly.com/catalog/CATALOGPAGE

To comment or ask technical questions about this book, send email to:

mailto:[email protected][[email protected]]

For more information about our books, conferences, Resource Centers, and the O’Reilly Network, see our web site at:

http://www.oreilly.com
You must sign in or register before commenting