: "This is not very good writing. It's difficult to read and the style
: fault ratio is well above average. The author has little grasp of
: clear writing."
Well, whether or not it's a grammatical masterpiece really doesn't matter.
Someone new to the language has trouble because some ideas are introduced
with advanced examples. I think if he introduced concepts using simple
examples and moved onto more complicated examples, it'd be fine. I'm
still reeling from the jump he makes in section 16. He introduces 'in
scope' then jumps to an advanced programming example which is pretty
unkind to a reader who is being introduced to these concepts for the
first time. Instead it'd be better to have a couple of simple examples
illustrating each concept. THEN an advanced one if he feels it's necessary.
My impression is that people have to skip parts, study the
games, and then come back. One guy said he read the manual 20 times, and
I believe him. Well, if I ever succeed in programming a decent game, I'll
go back and write an introduction to the language (though I'd need
permission to do that?!).