Deal of the Day

Home » Main » Manning Forums » 2010 » Scala in Depth

Thread: Errors and Corrections

Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 69 - Pages: 5 [ 1 2 3 4 5 | Next ] - Last Post: Mar 18, 2014 11:55 AM by: MarkElston
luke.bace

Posts: 66
Registered: 7/7/09
Errors and Corrections
Posted: Jan 4, 2011 9:40 PM
  Click to reply to this thread Reply

Please post all Errors and Corrections here. Thanks.

ellisbben

Posts: 1
From: Fairfax, VA
Registered: 1/24/11
Re: Errors and Corrections
Posted: Jan 24, 2011 10:00 PM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Possibly already caught by others or transparently in need of fixing, but

Section 3.3: needs another look; inconsistent capitalization of "Fourier" in paragraph 2, presumably there should be a character pi and Scala should be capitalized in paragraph 3.

Paragraph 5, I see "duality of => and for defining closures and pattern matching" and it looks like there should be some sort of symbol before "for", humorously illustrating one of the difficulties of Unicode that the author has been discussing. Viewing with OS X's Preview which in my experience is a rock solid PDF viewer.

Reading further, it looks like all unicode is straight up missing.

Section 3.3.1, 2nd para after listing 3.6: deifning -> defining, capitalize Scala.
2nd para after listing 3.7: oridnal -> ordinal.

Rather than addressing this subject with a "don't do these things that you should never want to do because you'll break Scala" narrative, you might go with "Scala has some rough corners related to the implementation of some of its magic; here's how it works under the hood and how you might possibly (though implausibly) break them on accident" sort of tone. It isn't unreasonable to put this stuff in the style chapter but you're taking a major digression from discussing style to address why the internals make use of $ inadvisable.

1st para after listing 3.8: interested -> interesting, actaully -> actually

Are these really the most interesting and important points about style? A lot of this strikes me as gotcha avoidance or, in the case of the annotations, less a matter of style and more of performance. It's all useful information, I'm just not sure about the organization.

lutzhank


Posts: 62
Registered: 11/15/10
Re: Errors and Corrections
Posted: Jan 29, 2011 6:24 AM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Just typos:

p. 25 4th last line: "...the details for continuous compilation or located.." typo, should be "... are located..."

p. 26 last paragraph 4th last line "..must evaluate to an value..." typo, should be "...to a value..."

p. 31 second line "where expresison oriented programming" typo, should be "...expression oriented..."

p.33. section 2.3.1 third last line "...during the lifetime an object..." should be "of an object..."

p.40 last paragraph 6th line "Due to the uncertaintly of...", typo should be "uncertainty of..."

p.56 3.1.1 second line "Code blocks are sections of code the execute.." should be "...of code which execute..."

Just wrong font:
p. 50 "canEqual" in "The canEqual method is used to allow subclasses..." should be monospace

Wrong code:
Listing 4.5
"trait NetworkEntity" must be "trait NetworkEntity extends SimulationEntity".

Listing 4.8
"val logger = new Logger" must be "val logger = new Logger{}" to compile.

"case _ => super.handleMessage(msg)" must be "case _ => super.handleMessage(msg, ctx)"

Wrong entity:
After Figure 4.2
“This means that the behavior in NetworkEntity is never called because the MixableParent does not call its super!” must be “Router” rather than “NetworkEntity”.


-------------------------------------------
added Listing 4.8
Message was edited by: lutzhank

pedrofurla

Posts: 1
From: Brasil
Registered: 5/5/11
Re: Errors and Corrections
Posted: May 5, 2011 6:49 PM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

p. 40 First line below the graph: "The y-axis is the exeuction time of running"

lutzhank


Posts: 62
Registered: 11/15/10
Re: Errors and Corrections
Posted: Jun 5, 2011 4:56 PM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Meap v7 after Figure 6.1

orig: "The randomElement method takes a List of some element type, named A"

should be "The randomElement method takes a Seq of some element type, named A"
reasoning: The the code in Fig. 6.1 use Seq and "List" is written in code font.

erikvanoosten

Posts: 5
Registered: 6/19/11
Re: Errors and Corrections
Posted: Jun 19, 2011 8:01 AM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Section 2.4.1. "Scala provides a factory method on the Object companion object that will convert from a Java style reference": 'Object' should be 'Option'

chapter 3: I am missing all the 'special' characters

joshua.suereth


Posts: 57
From: Pittsburgh, PA
Registered: 9/18/10
Re: Errors and Corrections
Posted: Jun 19, 2011 12:14 PM   in response to: erikvanoosten in response to: erikvanoosten
  Click to reply to this thread Reply

Thanks. For Chapter 3, I think you'll see these characters fixed in a few MEAPs from now. Right now the tooling that generates MEAP PDFs doesn't support those unicode characters directly, an irony considering the topic of the section :)

amacleod

Posts: 1
From: Rhode Island
Registered: 6/21/11
p. 4
Posted: Jun 21, 2011 2:01 PM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Page 4:
in the table
"Defered side effects" should be "Deferred side effects"

after the table
"beans which tend to models the nouns" should be "beans which tend to model the nouns"

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 9:33 PM   in response to: luke.bace in response to: luke.bace
  Click to reply to this thread Reply

Actors and I/O should interleaved carefully.

Looks like you accidentally a word.

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 9:44 PM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

The next sentence has a few errors too:
Asynchronous I/O and actors are a naturally pairing, as they execution models for these are very similar

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 9:45 PM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

Let s look at a cannonical eample
Let's look at a canonical example

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 10:03 PM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

Let s start by creating a SearchQuery message that can be sent amongs the
actors.
Let's start by creating a SearchQuery message that can be sent amongst the
actors.

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 10:21 PM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

In the code example for the HeadNode actor, shouldn't the messages be sent using !!! in order to avoid blocking?

val futureResults = nodes map (n => n !! s)

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jun 30, 2011 10:22 PM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

The HeadNode wait for SearchQuery messages.

The HeadNode waits for SearchQuery messages.

motlin

Posts: 13
Registered: 6/26/11
Re: Errors and Corrections
Posted: Jul 1, 2011 7:08 AM   in response to: motlin in response to: motlin
  Click to reply to this thread Reply

When it receives one, it
sends it to all the SearcNode children awaiting a future result.

The headNode can block until the reply is received by cally
the apply method on the Future .

This is exactly what it does in teh foldLeft
over these futures.

It supports sending messages vai three methods

Legend
Gold: 300 + pts
Silver: 100 - 299 pts
Bronze: 25 - 99 pts
Manning Author
Manning Staff
Manning Developmental Editor