In the following days I'll send a number of chapter fragments for review. They are incomplete, but I expect the finished sections to be in reviewable form.

I'd appreciate feedback (send it to this list). The first section is complete, the second is unfinished. Let me know!


Andrei
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fragment.preview.pdf
Type: application/pdf
Size: 72487 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/dmd-concurrency/attachments/20100108/4dcc296b/attachment-0001.pdf>

Le 2010-01-08 ? 19:23, Andrei Alexandrescu a ?crit :

> In the following days I'll send a number of chapter fragments for review. They are incomplete, but I expect the finished sections to be in reviewable form.
> 
> I'd appreciate feedback (send it to this list). The first section is complete, the second is unfinished. Let me know!

I like it a lot. :-)

It's good to make the link with the physical constrains of today's processors. And it's interesting to see why different books can suggest very different strategies. That makes good introduction to concurrency in general.

One thing you might want to do is define "contention" somewhere before or soon after mentioning it as one assumption of Effective Java second edition.

-- 
Michel Fortin
michel.fortin at michelf.com
http://michelf.com/

Michel Fortin wrote:
> Le 2010-01-08 ? 19:23, Andrei Alexandrescu a ?crit :
> 
>> In the following days I'll send a number of chapter fragments for review. They are incomplete, but I expect the finished sections to be in reviewable form.
>> 
>> I'd appreciate feedback (send it to this list). The first section is complete, the second is unfinished. Let me know!
> 
> I like it a lot. :-)
> 
> It's good to make the link with the physical constrains of today's processors. And it's interesting to see why different books can suggest very different strategies. That makes good introduction to concurrency in general.
> 
> One thing you might want to do is define "contention" somewhere before or soon after mentioning it as one assumption of Effective Java second edition.

Thanks. Good point - I need to define terms thoroughly before using them. By the way, how would you guys define a thread?

Andrei

I love what paragraph 3 is saying, but the wording is a bit confusing.  I think it could bear a rewrite.  More comments to follow.

Andrei Alexandrescu wrote:
> In the following days I'll send a number of chapter fragments for review. They are incomplete, but I expect the finished sections to be in reviewable form.
>
> I'd appreciate feedback (send it to this list). The first section is complete, the second is unfinished. Let me know!
I like it over all, but from page 41 to the top of 43 it seems to be, from a software guy's point of view, all side issues: the hardware reasons why things are so. It's interesting, but takes a while to get to the punch line.

Andrei Alexandrescu wrote:
>
> Thanks. Good point - I need to define terms thoroughly before using them. By the way, how would you guys define a thread?

Something to do with a self contained processor state or sequence of actions? A virtual processor maybe?

Andrei Alexandrescu wrote:
>
> Thanks. Good point - I need to define terms thoroughly before using them. By the way, how would you guys define a thread?
>

I defined thread as an execution context.

I like what I see. Knowing nothing about concurrency I'll just snipe at the language, instead of the content. Sorry. :)



"As usually, it all depends."  (page 44)

Should probably read,

"As usual, it all depends."

or

"As is usually the case, it all depends."

Both of  which read much more naturally to my eye.




Keep up the good work,

-Bernard.

As usually, it all depends. => As usual, it all depends

I'm not sure the discussion about parallel being replaced with serial has much relevance to concurrency. Also, I never understood the problems with concurrency until I constructed a mental model of how the memory caches work. So I suggest less words about the parallel vs serial and heat generation, and more about the memory caches.

Andrei Alexandrescu wrote:
> In the following days I'll send a number of chapter fragments for review. They are incomplete, but I expect the finished sections to be in reviewable form.
>
> I'd appreciate feedback (send it to this list). The first section is complete, the second is unfinished. Let me know!
>
>
> Andrei
> ------------------------------------------------------------------------
>
> _______________________________________________
> dmd-concurrency mailing list
> dmd-concurrency at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-concurrency

Thanks! This is important, so please keep such fixes coming!

Andrei

Bernard Helyer wrote:
> I like what I see. Knowing nothing about concurrency I'll just snipe at the language, instead of the content. Sorry. :)
> 
> 
> 
> "As usually, it all depends."  (page 44)
> 
> Should probably read,
> 
> "As usual, it all depends."
> 
> or
> 
> "As is usually the case, it all depends."
> 
> Both of  which read much more naturally to my eye.
> 
> 
> 
> 
> Keep up the good work,
> 
> -Bernard.
> 
> _______________________________________________
> dmd-concurrency mailing list
> dmd-concurrency at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-concurrency