Errata

Swift Pocket Reference

Errata for Swift Pocket Reference

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
PDF
Page 27
Section "Returning Multiple Values With Tuples"

(You've probably already spotted this one too.)

Both definitions of function getRange contain a spurious digit 0 before the arrow introducing the return type.

Note from the Author or Editor:
Corrected in QC2

Colin McPhail  Nov 12, 2014 
PDF
Page 28
Section "Function Types"

(1) In the partial definition of function sumOfInts the ellipses after the first Int seem to be in the wrong font (not fixed width).

(2) After "the types are, respectively" , the type of sumOfInts is missing an ellipses after the first Int (the one in brackets).

Note from the Author or Editor:
Corrected in QC2

Colin McPhail  Nov 12, 2014 
Printed
Page 46
fourth paragraph

arrayName.map()

The example uses filter() instead of map()

should be names.map()
NOT names.filter()

How about a pdf version of the book for this submission?

Note from the Author or Editor:
Errata confirmed, and corrected in the second edition manuscript.

Jolie  Feb 01, 2015 
Printed, PDF, ePub
Page 51
Final paragraph

In the discussion of inout function parameters, the paragraph states "Like variable references in C++, you must place an ampersand (&) before a referenced variable's name in a function call."

This is *not* true for reference parameters in C++. It is true for function parameters that are declared as pointers, however.

Note from the Author or Editor:
Change the following text near the bottom of page 51 of the PDF:

Like variable references in C++, you must...

to:

To call such a function, you must...

Nick Efford  May 23, 2015