Errata

Hi,

The return value i got is different from the book.
#Fun<erl_eval.6.111823515>

the one i got as follows, #Fun<erl_eval.6.52032458>

Erlang/OTP 19 [erts-8.2] [source] [64-bit] [smp:2:2] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V8.2 (abort with ^G)
1> FallVelocity = fun(Distance) -> math:sqrt(2 * 9.8 * Distance) end.
#Fun<erl_eval.6.52032458>
2>

the return value on the book is #Fun<erl_eval.6.111823515>

i got the following return values:-
6> Mps_to_mph =fun(Mps) -> 2.23693629 * Mps end.
#Fun<erl_eval.6.52032458>

values return #7,8, and 9 are correct.

value from the book is #Fun<erl_eval.6.111823515>

the one i got is

10> Mps_to_kph =fun(Mps) -> 3.6 * Mps end.
#Fun<erl_eval.6.52032458>

There is two function to get
The module "erlang" has two functions to get the tuple size. So I think we need to mention them. The author mentioned only one - "tuple_size" at the paragraph:
"... find out how many items are in a tuple with the tuple_size function."

The second is "size". It returns the same value and behave the same.

I think it would be nice to add the link to Erlang documentation in the book when the author mention some function name (at least one time).

The name of a project looks like a typo. I think it would be clear to rename this project "ch03/ex5-tuplesMore" (provide another one).

(You can find this at ch03/ex5-tuplesMore.)

Even ch03/ex5-tuples2 would be better.

I think there is no need to place a space between the io:format() function and the ";" in the code examples:

io: format ("Look out below! ~ n") ;
io: format ("Look out below! ~ w is too high. ~ n", [Distance]) ;
io: format ("Look out below! ~ w is too high on ~ w. ~ n", [Distance, Planemo]) ;

It would be clear to remove these spaces.

The compiler reports an unused variable in a function (count.erl: 9: Warning: variable 'From' is unused
)

A good solution would be to put an underscore in front of the name of an unused variable:

countdown (_From) ->
io: format ("blastoff! ~ n").

The explanation of what is happening is not very clear. (or maybe author wanted to say something that I did not understand). Therefore, other readers might have a misunderstanding of what is happening all the same.

My version of what is happening:

The shell sent a message to Pid1, the process identifier for mph_drop:mph_drop/0:

3> Pid1=spawn(mph_drop,mph_drop,[]).

If this were so, then such a process would have to be launched in this way:

3> Pid1=spawn(mph_drop,convert,[Drop]).

But in the example, it is not so. There is no process that is be identified by mph_drop:convert/1.

Inside this process Pid1, another process was created (It identifier for drop:drop/0). pid of it is stored in the Drop variable and passed to the mph_drop:convert/1 function.

The function mph_drop:convert/1 is function that receives messages which reported them to standard output, in this case the shell.

When the process with id Pid1 receives a response, receive message functionality of the mph_drop:convert/1 function prints a message to the console.

In paragraph above Figure 8-2 has mph_drop:mph_drop/0 instead of drop:drop/0.

When we select a module to analyze “Module” ➜ “Interpret ...” while debugging, we must select the module source code file.

I think, when we simply say "select drop module" it is not precise and unclear.

In the "Interpret Modules" window select the source code file (drop.erl) and click on the "OK" button.

The "Choose" button on the "Interpret Modules" window does not exist.

Note that after you clicked on the “OK” button, the module selection window was closed (“Intepret Modules” window). There is no “Done” button that you would have to click to close the “Intepret Modules” window and return to the “Monitor” window.

Everything is much simpler.

I think that it would be correct to move the Figure 9-12. The function call complete to the end of part "Debugging through a GUI" as the last picture of serias of section's example.

I think it would be would be clear to move Figure 9-12. The function call is completed to the end of the “Debugging through the GUI” part, as the last of the sequence of figures.

Placing it in the part "Tracing Messages" (at the page 124) looks strange .

Initially, directory with a name like Mnesia.nonode@nohost holds a FALLBACK.BUP file. There are no a LATEST.LOG file and a schema.DAT file.

The link to github projects written in Erlang is broken (old)

https://github.com/languages/Erlang

To achive that action, please, use advanced search form of Github

https://github.com/search/advanced

Select the language (for instance Erlang) and/or any other parameters and serf

https://github.com/search?utf8=%E2%9C%93&q=language%3AErlang&type=Repositories&ref=advsearch&l=Erlang&l=