Errata

URL should be updated for "�tudes for Elixir" placeholder present for "url goes here". Unable to click . Found the same from http://chimera.labs.oreilly.com/books/1234000001642

Note from the Author or Editor:
Replaced with URL.

It says "package manages" where I would expect "package managers".

Note from the Author or Editor:
This is correct, and fixed in the update.

iex(8)> and iex(9)> repeated twice.

should be 10 and 11 respectively.

Note from the Author or Editor:
Fixed in update.

Should be "lines <19 and 20>, all the values were assigned."

Note from the Author or Editor:
Fixed - will be in next update!

Consider quote marks around "yields" in "I like to read the -> as yields".

Note from the Author or Editor:
Added.

Looking at "The return value in the shell, #Fun<erl_eval.6.111823515>, isn�t especially meaningful by itself..."

Later in the text, fn returns values like "#Function<...>", rather than "#Fun<...>".

My shell returns "#Function<6.80484245/1 in :erl_eval.expr/5>".

It looks like the printed representation of the return value differs from one version of the shell to another (Function vs Fun, the numbers after erl_eval, and whether or not the arity of erl_eval.expr gets shown).

So you might add a sentence saying that the exact format of the return message will vary depending on the version of Elixir.

By the way, I would at least make the #Fun vs #Function consistent throughout the book.

Note from the Author or Editor:
Modified. Will check for consistency as Elixir settles.

Two periods at end of sentence "Elixir offers a shortcut style for defining anonymous functions using &, the capture operator. . "

Note from the Author or Editor:
Fixed.

Looking at "...module - this time starting with a capital letter - and..."

Hyphens should be em-dashes.

Note from the Author or Editor:
Em dashes will get fixed in production.

There are two problems in the first paragraph in this section:
1) The first word is "Elixirs's". I suspect it ought to be "Elixir's"
2) The second sentence ends with "as you need." I think this should probably be changed to something like "as needed" or "as you please" or something along those lines.

Note from the Author or Editor:
Fixed in update.

I noticed that after trying to set_elem in the tuple in the current Elixir version (0.14.1), there are no method set_elem

The new version is put_elem so the code should be:

newTuple = put_elem(tuple, 1, 40)

instead of:

newTuple=set_elem(tuple,1,40)

Note from the Author or Editor:
Fixed - thank you!

Looking at "The now more readable formula math:sqrt(2 * Gravity * Distance). is the last line..."

Neither Gravity nor Distance should be capitalized.

There should not be a period after the closing parenthesis.

Note from the Author or Editor:
Fixed!

Looking at "This allows you to write a catch-all clause�a guard matching true at the end if you would like, and often makes it easier to express logic based on broader comparisons than simple matching."

Not sure, but I believe this wants an em-dash, rather than a comma, right after "if you would like".

Note from the Author or Editor:
Broke the sentence into more coherent parts!

Looking at "...if your termination test relies on == or =:= for a..."

I don't find "=:=" in the table of comparison operators on p.165 (currently Table A-4, though I believe it should be Table A-5). Nor does a search on "=:" in the PDF turn up any instance other than the one on p.47.

I'm guessing this should be "===", but obviously I don't know for sure.

Note from the Author or Editor:
Fixed.

Variable "result" is lower-case "r", not upper-case "R". Occurs twice in this paragraph.

Note from the Author or Editor:
Fixed.

Variable name is "result" not "Result".

Note from the Author or Editor:
Fixed.

In sentence "You can put anything that returns a value in the interpolation - a variable, a function call, or an operation on parts."

The hyphen should be an em-dash.

Note from the Author or Editor:
Em dashes come from production later. Switched to colon.

iex(3)> repeated twice.

prompt sequence is not correct at lot of places.

Note from the Author or Editor:
Fixed in update.

Other section heads tend to capitalize all important words. Hence, "String Sigils" not "String sigils".

Similarly, on p.54, I expected "Multiline Strings" rather than "Multiline strings", but that one is less clear that the second word is "important" enough to capitalize.

Note from the Author or Editor:
Fixed.

Looking at "The two variables separated by a vertical bar (|), or cons, for list constructor..."

Consider putting "cons" in quotes, or italicizing it.

Note from the Author or Editor:
Fixed.

"(�| list constructor operator�)))" doesn't seem like it belongs there.

Note from the Author or Editor:
Fixed in new update.

"(((�lists�, �lists of �))" is out of place. I'm guessing this is for generating the index? There may be other similar cases elsewhere.

Note from the Author or Editor:
Fixed in update.

Looking at "This function divides its first argument�to be the value coming from the list�by second, the accumulator passed to it by the function doing folding."

Should be "by the second" or "by its second argument".

Note from the Author or Editor:
Fixed.

Looking at "You�ve been working within a single process throughout this book so far, the Erlang shell."

In the past, you've described it as the "Elixir shell."

Note from the Author or Editor:
Fixed.

Looking at "iex(4)> send)pid, :test2)"

Need "send(" rather than "send)".

Note from the Author or Editor:
Fixed.

Looking at "feed your process some bad data, an atom (zoids) instead of a number..."

"zoids" needs a colon to be an atom-- ":zoids"

Note from the Author or Editor:
Fixed.

Looking at "Save this is as file drop_bad.ex."

"is as" --> "as"

Note from the Author or Editor:
Fixed.

earth is not defined. it should be :earth (an atom).

line is defrecord Tower, location: "", height: 20, planemo: earth, name: ""

Note from the Author or Editor:
Fixed in update.

'delcarations' - should be declarations

Note from the Author or Editor:
Fixed in update.

Looking at declaration of record type Planemo.

First instance, just under subhead "Setting Up Records", assigns field "name" the default value ":nil".

Second instance, in Example 10-1, assigns field "name" the default value "".

Might be better if these were consistent.

Note from the Author or Editor:
This appears to be fixed already in latest QC version.

"defrecord Planemo, name: :nil, gravity: 0, diameter: 0, distance_from_sun: 0

That defines a record type named Planemo, containing fields named name, gravity, and
distance_from_sun with their default values."

The description leaves out 'diameter'.

Note from the Author or Editor:
Fixed in update.

"For example, to find out how which planemo tower5 is on, you could write:"
has an extraneous 'how'.

It shhould probably read:
"For example, to find out which planemo tower5 is on, you could write:"

Note from the Author or Editor:
Fixed in update.

'the hd/1 function, which Example 5-2 showed for use with user inputs'

The hd/1 function isn't used previously in the book (it might be in the code distributed separately, but not in the text) as far as I can tell with a quick text search. Could have missed something though.

Note from the Author or Editor:
Removed in update. Was left from Erlang version.

'/// (If you want to change where Mnesia stores data, you can start Elixir with some extra options:
erl -mnesia dir " path " . The path will be the location Mnesia keeps any disk-based
storage.) ///'

Extraneous '///'s.

Note from the Author or Editor:
Removed in update.

Is there any particular reason this note is rendered with the all-caps "NOTE:", rather than using the bird "note" symbol like all the others?

Note from the Author or Editor:
Had to do with index entries. Fixed.

spelling: remmeber -> remember

Note from the Author or Editor:
Will be fixed in next update.

There seems to be a word missing after "Process Manager or" below

"""
You can also open the Process Manager or and whack away at work&#8208; er processes through the Kill option on the Trace menu and watch them reappear.
"""

Note from the Author or Editor:
It was a stray 'or'. Deleted, fixed in update.

Looking at "As in the previous example, the condition and options must remain +unquote+d, as they are already in internal form."

The plus signs around "unquote" appear just like that in my PDF.

Note from the Author or Editor:
Formatting madness. Fixed.

Table caption says ".Logical (Boolean) Operators"

The "." that starts this should go away.

Furthermore, I think this is a table caption. Thus it should be in italics, and should read "Table A-4. Logical (Boolean) Operators" (and all subsequent tables should have their table number incremented).

Note from the Author or Editor:
Fixed.