View source for Touch of class typos

You do not have permission to edit this page, for the following reasons:
The action you have requested is limited to users in one of the groups: Autoconfirmed users, emailconfirmed, editors.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page:
__NOTOC__
Typos for "Touch of Class" draft

===How to report a typo===
Report it under the appropriate chapter title below. Make sure the extract is easy to find (often locating the place of a correction is the most time-consuming part). If you copy-paste the relevant text, highlight the faulty word(s), for example by **...**. 

As errors get corrected I <strike>strike them out</strike>.

===Preface etc.===
<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page v, section Preface.
 in the 'note' clause of the class PREFACING.
 replace:
   "]
 by:
   ]"
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xiii, section student_preface/Abstraction.
 middle of second paragraph.
 replace:
   you'll been encouraged
 by:
   you'll be encouraged
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xv, section instructor_preface.
 second paragraph, third bullet.
 text:
   Eiffel and Design by Contract
 action:
   put the last letter of "Contract" in bold.
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xxi, section student_preface/OUTSIDE-IN: THE INVERTED CURRICULUM/The supporting software.
 middle of second paragraph.
 replace:
   In the seond week
 by:
   In the second week
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xxv, section student_preface/TECHNOLOGY CHOICES/Eiffel and Design by Contract.
 right margin.
 replace:
   at tinyurl.com/cq8gw..
 by:
   at tinyurl.com/cq8gw.
 action:
   remove extra dot.
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xxix, section student_preface/TECHNOLOGY CHOICES/Why not Java?.
 replace:
   university context,it is meant
 by:
   university context, it is meant
 action:
   space after comma.
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page xxxiv, section student_preface/TOPICS COVERED.
 paragraph starting with "Part III"
 text:
   It makes no attempt at
 action:
   missing end of sentence.
 -- Eric Bezault, 12 December 2008
</strike>


Student preface recommendations given by Raphael Meyer 23-02-2009.

<strike>Dedication Page: Shouldn't the name "C.A.R" be written with a period at the end, i.e. "C.A.R."?

Student Preface, first page, second paragraph: (formatting problem) The paragraph should be indented.

Student Preface, first page, paragraph starting with "By going into": (missing the word "and") "conferences, journals, magazines" should read "conferences, journals, and magazines"

Student preface, page xiv, paragraph starting with "Although more": (missing the word "the") "Ability to do computing" should read "The ability to do computing"

Student preface, page xv, paragraph starting with "On the other hand": (awkward wording) In the sentence starting with "In particular", there is no need to repeat "particularly" later in the sentence, and that word should be removed.

Student preface, page xv, same paragraph, final sentence: (unnecessary word "in" should be removed) "look like they typed in their" should read "look like they typed their"

Student preface, page xvi, paragraph starting with "Object-Oriented": (I suggest changing the wording) "for example circles or polygons" should read "such as circles or polygons"

Student preface, page xvii, paragraph starting with "Formal methods are": (awkward wording, I suggest rewording) "To learn formal methods in" should read "Learning formal methods to"

Student preface, page xvii, paragraph starting with "Formal methods can": (missing a comma for clarity and flow) "the idea of Design by Contract" should read "the idea of Design by Contract,"

Same paragraph: (missing the word "and") "correct, robust, durable" should read "correct, robust, and durable"

Student preface, page xviii, paragraph starting with "The expertise": (awkward wording, I suggest rewording "you will be just relying" should read "you will simply be relying"

Student preface, page xviii, paragraph starting with "The expertise": (various words in the list are not parallel, and a comma is necessary) "graphical visualization, simulations, computing routes, animating the routes etc." should read "graphical visualization, simulations, computing routes, route animation, etc."

Student preface, page xviii, paragraph starting with "The expertise": (sentence missing the word "or" or "and") "problems, learn" should read "problems, or learn"

Student preface, page xix, paragraph starting with "Basing your work": (reword the end of this sentence) "that, as a consumer, you need." should read "that you need as a consumer."

Same paragraph: (reword and change "which states" to "stating") "description of the purpose of a software module, which states only its functions," should read "description of a software module's purpose, stating only its functions,"

Student preface, page xix, paragraph starting with "This technique": (I would reword this phrase for clarity and efficiency) "Every professor and textbook of software development" should read "Every software development professor and textbook"

Student preface, page xx, paragraph starting with "This book teaches": ("requires" should be "require" to match up tenses) "and requires" should read "and require".</strike>

Done by Raphael meyer, 25-02-2009

<strike>
Page xiv, paragraph starting with "It is important": (awkward wording; replace "that we" with "to") "in inappropriate demands that we teach the specific" should read "in inappropriate demands to teach the specific"

page xiv, same paragraph: ("ads" is too casual and should read "advertisements" or "postings") "job ads" should read "job postings"

page xxvi, top paragraph: (sentence missing two commas for clarity) "Reuse is from the beginning one" should read "Reuse is, from the beginning, one"

page xxvii, first paragraph: (intro should read introductory) "in an intro course" should read "in an introductory course"

page xxvii, paragraph starting with "This approach gives": (reword for clarity and conciseness) "is not sufficient any more today;" should read "is no longer sufficient;"

page xxvii, paragraph starting with "This approach gives": (reword for clarity and conciseness) "many people who are not professional software developers" should read ""many non-professional software developers"

page xxvii, paragraph starting with "From the outset": (I would replace "specially" with "specifically") "produced specially for" should read "produced specifically for"

page xxvii, paragraph starting with "From the outset": (add "where" to keep the two clauses parallel) "and the basic layers" should read "and where the basic layers"

page xxvii, paragraph starting with "From the outset": (re-order words for clarity and remove "right") "are able right from the start to produce interesting applications," should read "are able to produce interesting applications from the start,"

page xxviii, last paragraph: (reorder words) "but then we would" should read "but we would then"


page xxxi, paragraph starting with "Many intriductory": (add comma for clarity) "modern technology students" should read ""modern technology, students"


page xxxii, third bulletpoint under "We rely on Eiffel": (reorder wording) "Eiffel is easy to learn for a beginner." should read "Eiffel is easy for a beginner to learn."


page xxxii, next bulletpoint: (add the word "and" to finish the sentence) "software metrics, leading-edge" should read "software metrics, and leading-edge"


page xxxii, final bulletpoint: I would separate each of the topics in the last sentence (Eiffel Base, Eiffel Time, EiffelVision, etc.) with semicolons (;) rather than commas (,) since there is so much in that sentence.


page xxxiii, first bulletpoint: (reword for clarity and correctness) "designed for education only," should read "designed exclusively for education,"


page xxxiii, same bulletpoint: (reword for correctness) "billions of dollars of investment" should read "billions of dollars in investments" OR "billions of investment dollars"


page xxxiv, paragraph starting with "This is full of": (reword for clarity and conciseness) "For the teacher this means engaging far too often in injunctions" should read "For the teacher this means repeatedly engaging in injunctions"


page xxxiv, paragraph starting with "the object-oriented": (add "a" or "its" for correctness) "uses as main program a static function," should read "uses a static function as its main program" OR "uses a static function as a main program"


page xxxv: it seems like the spacing on this page is different from the other pages, i.e. there is more space in between lines. please check.


page xxxv, paragraph starting with "Inconsistencies": (verb needed to complete the sentence) "why, along with full words like “static”, abbreviations such as “args” and “println”?" should read "why, along with full words like “static”, include abbreviations such as “args” and “println”?" OR "why, along with full words like “static”, require abbreviations such as “args” and “println”?"


page xxxv, paragraph starting with "To cite": (comma needed for clarity) "motivating examples I was" should read "motivating examples, I was"


page xxxv, paragraph starting with "the Java notion": (reword for correctness) "This is particularly useful to teach design" should read ""This is particularly useful for teaching design""


page xxxvii: (page label typo) the page number is "xxxvi" but should read "xxxvii"


page xxxvii, first paragraph: (ads is not a real word) "ads" should read "advertisements"


page xxxvii, paragraph starting with "Java, C#": (add a comma for clarity and write "introductory" completely) "In any case no intro" should read "In any case, no introductory"


page xxxviii: (page label typo) the page number is "xxxvi" but should read "xxxviii"


page xl, paragraph starting with "Looking around": (change wording for clarity) "leads to identifying" should read "leads to the identification of"

page xl, paragraph starting with "The first approach": (change wording for clarity) "probably nowadays the most common." should read "probably the most common today."

same paragraph: (remove comma, since it is unnecessary and clutters the sentence): "of the chosen language, at the" should read "of the chosen language at the"

page xlii, bulletpoint starting with "Fundamental data structures": (typo, missing the word "as") "structures such arrays," should read "structures such as arrays,"

page xlii, paragraph starting with "The description of": NEEDS TO BE COMPLETED.

page xlii, towards the bottom of the page: (reorder and reword for clarity) "It is an essential part of the abstraction-focused approach to make sure" should read "An essential part of the abstraction-focused approach is making sure"

page xlii, paragraph starting with "Part III": (typo) "includes an detailed" should read "includes a detailed"

page xlii, paragraph starting with "Part IV": (add "and" to complete the sentence) "agents (function objects), event-driven design." should read "agents (function objects), and event-driven design."

page xlv, first paragraph: (typo) "appendices is" should read "appendices are"

page xlv, second to last paragraph: (i suggest changing the second "online" for readability) "keep an online version of this section online," should read "keep an online version of this section on the web," OR SIMPLY "keep an updated version of this section online,"

page xlvii, first paragraph: (reword for clarity) "and of course will have to be" should read "and will naturally need to be"

page xlvii, bulletpoint starting wtih "chapter 8": (i THINK you should add a "the", but am not certain; please double-check) "of undecidability" should read "of the undecidability"

page xlvii, bulletpoint starting with "In chapter 9": (reword for clarity) "9.6 about the difficulty" should read "9.6, regarding the difficulty"

page xlvii, bulletpoint about chapter 10: (unnecessary comma) "on computers, depends" should read "on computers depends"

page xlvii, bulletpoint about chapter 11: (add the word "the" for clarity) "I suggest covering at least sections up" should read "I suggest covering at least the sections up"

page xlviii, bulletpoint about chapter 14: (i would add an "and" for clarity) "recursive syntax productions, recursive proofs." should read "recursive syntax productions, and recursive proofs."

page xlviii, next sentence: (reorder for clarity, conciseness, and correctness) "The core material is the beginning of the chapter:" should read "The beginning of the chapter is the core material:"

page xlviii, bulletpoint about chapter 16: (add commas for clarity) "plus 16.9 on the role of contracts which" should read "plus 16.9, on the role of contracts, which"

page xlviii, bulletpoint about the appendices: (awkward wording, needs to be changed) "devote some time to e.g. Java" should read "devote some time to languages such as Java"

page xlviii, final paragraph: (add "but" for clarity and correctness) "magic, with" should read "magic, but with"

Stopped at Table of Contents
</strike>

===1 The industry of pure ideas===
<strike> page 5, section 1.1: ''Computers and related devices are called hardware, indicating that — although they are getting ever 
 lighter — computers are the kind of machine that will hurt your feet. Programs **and all that relates to them** are by contrast
 called software, a word made up in the 1950s when programs emerged as topic of interest.''
 Comment: one may argue that hardware may relate to hardware (depending on the definition of the relation). 
 As the point is to separate the two concepts, to avoid confusion I would drop **and all that relates to them**.
 -- MP, 8/2/2009

 page 11, picture caption: **(d) GPS navigation system**. For consistency with the iPhone, you  may consider adding that it is a Garmin 
 gps.   
 -- MP, 8/2/2009

 page 13, towards the end: ''This book emphasizes throughout, along with practices that 
 **make your programs good for the computer**  — for example, designing programs so that they will run fast enough —, 
 practices that make them good for human readers.''
 Remark:   The way in which the sentence is formulated is not smooth and crystal clear to me. A suggestion could be: 
 ''This book emphasizes throughout, along with programming practices that put to good use a computer processing power, practices 
 that make programs understandable by human readers.''
 -- MP 8/2/2009

 page 14, at the end of box Touch of folk history: This did not deter **the programmer**: “See the holes? They are the software.”
 Could be: This did not deter one of the programmers: “See the holes? They are the software.”
 -- MP 8/2/2009

 page 16, exercise 1-E.3, third bullet point:  ''The exact set of letters does not**,** matter but'' 
 Comment: Move the comma after the word ''matter''.
 -- MP 8/2/2009
</strike>

Comments by Raphaël Meyer
<strike>
Page 6, paragraph starting with "the immaterial": (replace semicolon with comma, since the clause after the comma is not a complete sentence) "steps; and the" should read "steps, and the"

same paragraph: (replace multiple repetitions of "or" with commas) "You do not need wood or clay or iron or a hammer or anything that could" should read "You do not need wood, clay, iron, a hammer, or anything that could"

Page 7, paragraph starting with "In any experience": (remove unnecessary "seems") "that state in which seems everything seems" should read "that state in which everything seems"

Page 7, paragraph starting with "You cannot": (unnecessary comma; remove for flow) "yours, or someone" should read "yours or someone"

Page 8, first paragraph: (reword for clarity and correctness) "but let us see their fundamental properties" should read "but let us take a look at their fundamental properties"

Page 8, same paragraph: (reword for clarity) "fundamental properties, as they" should read "fundamental properties, since they"

page 10, paragraph starting with "This is the human view": (replace comma with semicolon to make the sentence more readable) "manipulate information, they" should read "manipulate information; they"

page 10, paragraph starting with "The data will be": (reword sentence; currently using akward wording) "It is the task of the communication devices" should read "The communication device's task is to"

page 11, paragraph starting with "The familiar picture": (replace "really" with "essentially" to sound less casual) "which today are really pocket computers" should read "which today are essentially pocket computers"

page 11, same paragraph: (replace "..." with "etc.") "(physics, weather prediction...)" should read "(physics, weather prediction, etc.)"

page 12, paragraph starting with "The computers": (incorrect wording) "The computers you will use for exercises of this book" should read "The computers you will use for the exercises in this book

page 12, paragraph starting with "The stored-program": (replace ";" with ",") "data; but this" should read "data, but this"

page 12, paragraph starting with "The ability of computers": (reword for clarity and readability) "programs were going, through repeated self-modification, to become" should read "programs would, through repeated self-modification, become"

page 12, final line: (unnecessary comma) "written program, whose execution might" should read "written program whose execution might"

page 16, paragraph starting with "That is to say": (add "how" for correctness) "know to apply" should read "know how to apply"

page 16, paragraph starting with "the problem calls": (redundant "etc."; not necessary since you already included the ...) "otherwise...' etc. is not" should read "otherwise ...'  is not"

</strike>

=== 2 Dealing with objects ===
<strike>page 18, second line: ''The book**,** applies systematic typesetting conventions'' 
Comment: comma should be dropped
<br>-- MP, 15/2/08

page 18, in box Touch of style: (sometimes bold or italics according to precise rules**)
<br>Comment: I would add: (sometimes bold or italics according to precise rules that will be specified)
<br>-- MP, 15/2/08

page 18, line after box on class Preview: ''The first line says you are looking at a **small** “class”''
<br>Comment: as the first line does not say that the class is "small", I would drop the word "small":
''The first line says you are looking at a “class”''
<br>-- MP, 15/2/08

page 19, box title "**Magic?". Did you considered the title "Touch of magic?"?  
<br>-- MP, 15/2/08

page 25, after the first code box: ''Paris.display''
<br>Comment: you use the term "object", and then again many times in the same page. As you will define it on page 27, I would put a reference here, or give an informal definition,
especially because you use it in the Touch of Semantics box (page 25) to define a feature call.  
<br>-- MP, 15/2/08

page 27, sub-section "Objects you can and cannot kick", first bullet point, two lines before the end: ''...your foot. **(Buying this book does not
entitle you to a refund of medical expenses.)**''. 
<br>Comment: punctuation before and after the parentheses (or parentheses themselves) is (are) misplaced. Suggestion: ''...your foot. Please be aware of the fact that buying this 
book does not entitle you to a refund of medical expenses.''.   
<br>-- MP, 15/2/08

pages 27 and 28: Comment: there are many references to "**Notre-Dame**" (I counted 5), but the figure on page 27 shows "Saint-Michel" as metro station. I would keep Saint-Michel
everywhere to avoid confusion (not everybody may know that the real stop is  "Saint-Michel Notre-Dame")
<br>-- MP, 15/2/08

page 28: last bullet list: first bullet "**or any other specified by its index**"
<br>Comment: you did not defined an index of a leg. Here you could drop the sentence fragment above without conceptually losing anything: ''Remove the first leg of the route, or the 
last leg, or any other.'' 
<br>-- MP, 15/2/08

page 28: last bullet list: second bullet: ''**for example a metro leg from Notre-Dame to Jussieu (4 stations, see map on the previous page); the route will be changed to involve 3 
legs, 3  metro lines, and 8 stations; the result now starts at Louvre and ends at Jussieu.**''
<br>Comment: where is Jussieu? The "map on the previous page" does not help, nor the one on page 24. 
<br>-- MP, 15/2/08

page 28: last bullet list: third bullet: ''For example we can make Route1 start with a leg going from Opéra to Louvre;''
<br>Comment: It would be nice to locate on a map Opéra.
<br>-- MP, 15/2/08

page 29: line 3: ''**With a remove query**, it would be one less.''
<br>Comment: It should be something like: "If you remove a leg, the same query above would report one less."  
<br>-- MP, 15/2/08

page 31: box "Definitions: Feature, Query, Command", second bullet: ''A feature that may **modify** an object is called a command''
<br>Comment: you don't define "modify". At the bottom of page 28 there was a definition of "change" of an object. I would use the same word in both cases, 
or put a  reference here to the previous definition, or repeat the definition.   
<br>-- MP, 15/2/08

page 31, 4 lines before the end: ''are **defined** for you''
<br>Comment: as how to "define" an object has not been defined, I would use  ''are created for you'' instead.
<br>-- MP, 15/2/08

page 33, first line: "**Palsis**" should be "Palais"
<br>-- MP, 15/2/08

page 34, Exercise 2-E.2, 3 lines before the end. There is a parenthesis to drop.
<br>-- MP, 15/2/08

page 35, 3rd bullet; ''**If either of the previous two relations holds between two terms “relies on” also holds**''
<br>Comment: a comma is missing:  ''If either of the previous two relations holds between two terms, “relies on” also holds''   
<br>-- MP, 15/2/08

page 35, exercise 2-E.3, point 2. **my_paragraph_remove_last**.
<br>Comment: my_paragraph_remove_last_word is a better name
<br>-- MP, 15/2/08

page 36, exercise 2-E.3, point 5. **my_paragraph.character_count (i)** seems a bit confusing example to me.
<br>Comment: looking at the semantics, I would suggest my_paragraph.word (i), to get the i-th word in a paragraph; then we can apply to the resulting word feature 
''character_count'', a query that should be a feature of class WORD.
-- MP, 15/2/08

page 36, exercise 2-E.4 **Assume that you are building an MP3 player entirely software.** I am confused by the phrasing.
<br>Comment: "Assume you are building a software model of a MP3 player." looks better to me.
<br>-- MP, 15/2/08 
</strike>



<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page 31, section 2.3 WHAT IS AN OBJECTS/Objects: a definition.
 second paragraph.
 replace:
   It is also s good
 by:
   It is also good
 -- Eric Bezault, 12 December 2008
 </strike>
    I don't see this, so I assume the sentence was removed.

Comments by Raphaël Meyer
<br><strike>
page 18, paragraph starting with "The first two lines": (unnecessary "to) "so all you have to do is to include" should read "so all you have to do is include"

page 19, "Touch of Magic" box: ("specially" is an awkward word, consider replacing) "prepared specially for this" should read "prepared specifically/especially for this"

page 19, same paragraph: (unnecessary comma) "concepts, and practice them" should read "concepts and practice them"

page 19 final paragraph: (awkward comma) "line as here, to explain" should read either "line, as here, to explain" OR "line as here to explain"

page 20, first paragraph: (incorrect grammar) "All we want the program to do is some display on the screen:" should read "All we want the program to do is display something on the screen:"

page 20, final paragraph: (add comma for clarity) "avoid any confusion note" should read "avoid any confusion, note"

page 21, paragraph starting with "Also note that": (typo) "Also note that do not actually need to type everything" should read "Also note that you do not actually need to type everything"

Page 22, first paragraph: (typo) "The completion menu automatically appear" should read "The completion menu automatically appears"

Page 22, same paragraph: (the following sentence is correct but very long and confusing; i suggest rewriting it if possible) "if at any point it does not show up by itself but you want to get it, to know the set of valid completions of what you typed so far and choose one from them, just type CTRL-Space". i would reword it as "if at any point you are looking for help and need this menu to appear with the list of valid completions, just type CTRL-Space"

Page 22, paragraph starting with "You will now run": (awkward concept) "you will find more details of the interaction with EiffelStudio" (the interaction between Eiffelstudio and what? There cannot be the interaction with something; it must be the interaction of something with something else)

Page 22, paragraph starting with "Click the Run button": (missing the word "and" to make the sentence complete) "looks like this —you will actually get" should read "looks like this — and you will actually get"

page 28, paragraph starting with "All these operations": (add "and" for clarity and correctness) "route, hence" should read "route, and hence"

page 28, final paragraph: (reword for correctness) "means that a command 'changes' an object" should read "means for a command to 'change' an object"

page 30, paragraph starting with "Perhaps you find this": (add "and" to close the first half of the sentence) "next track, stop playing" should read "next track, and stop playing"

page 30, paragraph starting with "The figure evokes": (grammar) should "yellow elliptic buttons on" read "yellow elliptical buttons on"?

page 30, point 1 starting with "The object covers": (add a comma) "station “Louvre” etc." should read "station “Louvre”, etc."

page 31, paragraph starting with "Examples of commands": (replace comma with "and") "such as Paris, spotlight" should read "such as Paris and spotlight"

page 31, paragraph starting with "Queries and commands": (I think you need to add the word "how") "will learn to create" should read "will learn how to create"</strike>


<strike>
page 32, first paragraph: (missing the word "will) "We now look at some" should read "We will now look at some"

page 32, same paragraph: (i would recommend starting a new sentence after the "Route1.origin" box. As it is written currently, the entire sentence is incorrect grammatically) i would suggest that "which is a feature call, like the calls to commands" be written "This is a feature call, like the calls to commands ..."

page 32, paragraph starting with "which is a feature call": (add comma for clarity and correctness) "In this case since the feature is a query the call does" should read "In this case," since the feature is a query the call does"

page 33, paragraph starting with "where some": (replace "it" with the noun for clarity) "because it needs it" should read "because it needs the value"

page 33, same sentence. (in addition to previous recommendation, add "in order to" for clarity) "it needs it to do its job" should read "it needs it in order to do its job"

page 33, final line: (add comma) "argument (separated by commas) although" should read "argument (separated by commas), although"

page 34, third bulletpoint: (consider rewording for correctness) "results of applying" should read "results when applying"

page 35, four bulletpoints: (need to have consistent formatting and style) the "For example" in each bulletpoint should always be followed by the same punctuation (either a ":", a "," or nothing.) There is currently no continuity in this list.

page 35, paragraph starting with "In software for creating": (need parallel construction) "assume a class WORD that describes a notion of word, and a class PARAGRAPH, describing a notion of paragraph." should read "assume a class WORD that describes a notion of word, and a class PARAGRAPH that describes a notion of paragraph."

page 35, same paragraph: (replace "say" with "determine") "PARAGRAPH, say whether" should read "PARAGRAPH, determine whether"
</strike>

===3 Program structure basics===
<strike>page 39, line 5 of section 3.3: "...natural languages, like English or French, that we use for ordinary communication."
<br>Comment: some readers may not be using French for ordinary communication, not even English (in spite of the fact 
<br> that they are reading a book written in English). I would suggest not to commit to any language:  
<br>"...natural languages that we use for ordinary communication." 
<br>Marco P, 23/2/2009

<br>page 40 line 2: "In English or French you do not invent". Comment: again, I would choose a language-neutral approach: 
<br>In a natural language you do not invent..."
<br>Marco P, 23/2/2009

<br>Page 40, box Touch of style: title. Same issue as above ("English"). I suggest:
<br>"Putting some natural language into your programs"
<br>Marco P, 23/2/2009

<br>Page 40, box Touch of style: line1. "Natural language has a place in programs: in comments"). 
<br>Comment: maybe is also worth mentioning that natural language has a place also in class and feature names?
<br>Marco P, 23/2/2009

<br>Page 46, section "Levels of language description". In bullets 2 and 3 you use the terms "syntax rules", but in the picture
<br> you use "syntactic rules". 
<br>Marco P, 23/2/2009

<br>Page 46, picture: the picture of a tree on the right is not clear to me. It would be preferable to explain it or remove it altogether.   
<br>Marco P, 23/2/2009

<br>Page 47, box Touch of style, line 5: " ...; the few seconds that you might save by omitting**a letter**..."
<br>Comment: this could be interpreted as: "a few seconds to type a single letter? I am not that slow!", so maybe it could be rephrased as:
<br> " ...; the few seconds that you might save by omitting one or more letters in one or more identifiers..."
<br>Marco P, 23/2/2009

<br>Page 47, section Break and Indentation, line after the third bullet: "It makes no difference to the syntax..."
<br>Comment: "It makes no difference to the Eiffel syntax..."
<br>Marco P, 23/2/2009

<br>Page 47, line 5 of the part in smaller font before the end of the page: "The “carriages” in question are not the horse-and-buggy kind, 
<br>although today they seems almost as old** — **a delightful and nostalgic reminder of the time when we typed our programs on typewriters. 
<br>The print head was lodged in a little mechanical “carriage”, which at the end of a line we would “return” to the leftmost
<br>position to start typing the next line."
<br>Comment: the sentence does not flow smoothly to me.  A possibility could be: "... almost as old. They are instead a delightful and nostalgic remainder..."
<br>Marco P, 23/2/2009
</strike>


<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page 43, section 3.5 NESTING AND THE SYNTAX STRUCTURE.
 in the gragh.
 replace:
   -- Show city info including a monument..
 by:
   -- Show city info including a monument.
 action:
   remove one dot.
 -- Eric Bezault, 12 December 2008
</strike>

<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page 48, section 3-E.1 Vocabulary.
 in right margin.
 text:
   The definition of "class" may be less precise than the others.
 action:
   remove this text. It's copy/pasted from 2-E.1
 -- Eric Bezault, 12 December 2008
</strike>

Raphaël Meyer
<strike>
page 39, paragraph starting with "Earlier on": (confusing end of the sentece) "program, to do something for us, which may change objects." should read "program, to do something for us, while maybe changing one or more objects."

page 41, paragraph starting with "a typical": (typo) "with three component, each" should read "with three components, each"

page 46, bottom of the page: (add the word "an") "an example of identifier" should read "an example of an identifier"
</strike>

===4 The interface of a class ===
<strike>page 50, first two lines: "As an example of a user interface, consider a Web browser as shown 
<br>(top part only) on the next page.
<br>Comment: this was probably originally on the previous page, but now it is not, so has to be 
<br>fixed accordingly. Also, a general comment about the printscreens: they all seem blurry on my 
<br>monitor, and also when I print them.  
<br>Marco P. 25/2/2009

<br>page 52, line after box with class definition: "In program texts..."
<br>Comment: may be it is worth specifying "In Eiffel program texts..."
<br>Marco P. 25/2/2009

<br>page 53, section 4.3, line 5: " We use Paris because it is the top tourist destination in the world..."
<br>Comment: it would nice to put a ref on the side to reassure people that this is true 
<br>Marco P. 25/2/2009

<br>page 53, section 4.3, line 7: " it simply reads in an XML file describing..."
<br>Comment: even if you briefly explain XML on the side, I would say that at this point detailing the  
<br>technology is not essential. I would just say: " it simply reads in a file describing..."
<br>Marco P. 25/2/2009

<br>Page 54, line 4 after the box: "...— but still far less precise and complete than what we expect from 
<br>the “requirements document” of a software project in industry. It is good enough for our current 
<br>purpose of discovering a few classes." 
<br>Comment: The last sentence seems to be missing a "Anyway" at the beginning, or a "though", like in:
<br> "It is good enough, though, for our current purpose of discovering a few classes." 
<br>Marco P. 25/2/2009

<br>Page 55, line 2: ";a route is made of legs from different lines."
<br>Comment: ";a route is made of legs from potentially different lines." seems more precise.
<br>Marco P. 25/2/2009
<br>Page 55, box on Conventions. The term "library" is used here and immediately after the box. 
<br> Comment: I have found an explanation in the introduction. You might consider briefly define it again,
<br>or having a ref as a side note, etc.
<br>Marco P. 25/2/2009

<br>Page 58, line after box ""Programming time!": (in directory in the subdirectory 04_interface)"
<br>Comment: looks like something is missing here: adirectory name?
<br>Marco P. 25/2/2009

<br>Page 60, picture. The "Line end" station, put alone on the right, looks a bit confusing to me. As
<br>it does not seem essential to me to understand the text, you may consider removing it.
<br>Marco P. 25/2/2009

<br>Page 61, after the code box: "Don’t even think of reading any further unless you understand these two lines
<br>perfectly."
<br>Comment: here the word line is used to mean line of text, and immediately before the box to mean metro line. 
<br>This may be slightly confusing, so I would specify "lines of code" or "in the box above" or the like. 
<br>Marco P. 25/2/2009

<br>Page 65: "as in non-programming uses of this concepts (“there is enough snow”, as in a condition to decide 
<br>whether you can go skiing) a condition either holds or not.)
<br>Comment: maybe it is worth adding that in the given example we implicitly assume that we know 
<br>what the truth value is, and that if it is not true it has to be false, the so-called closed-world assumption. 
<br>Marco P. 25/2/2009

<br>Page 68, line 7: "The invariant, to be seen in the next section, will tell us that north_end must be equal
<br>to i_th (count), so this clause is in fact redundant, but it doesn’t hurt."
<br>Comment: as invariant has not been defined yet, I would rather move the sentence, appropriately rephrased, to
<br>the next sub-section on class invariants. In general I think that back-referencing is easier to follow than forward-referencing.
<br>Marco P. 25/2/2009

<br>Page 71, New vocabulary: you might consider adding "library", in case you accepted a previous suggestion
<br>Marco P. 25/2/2009
</strike>


<strike>
 from Draft 22.02, 23 August 08 19:15 (Santa Barbara)
 page 52, section 4.2 CLASSES.
 in sixth paragraph, second bullet.
 text:
   there some names such as Paris and Route1
 action:
   The 's' in 'such' should not be in italic.
 -- Eric Bezault, 12 December 2008
</strike>


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 57, section 4.4 QUERIES, "How long is this line?".
 in the header comment of attribute `count'.
 text:
   -- Number of stations in this line.
 action:
   Remove the period.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 57, section 4.4 QUERIES, "How long is this line?".
 last word of the second to last paragraph.
 text:
   to which we will apply the feature count.
 action:
   `count' should be displayed in blue.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 60, section 4.4 QUERIES, "The stations of a line".
 last paragraph.
 text:
   denoting the ends of a line .
 action:
   put a colon instead of a period at the end of the line.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 61, section 4.4 QUERIES, "Properties of start and end lines".
 in the title itself.
 action:
   shouldn't it be: "Properties of start and end stations of a line"?
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 62, section 4.5 COMMANDS, "Build a line".
 text:
   Our program will use it under the form
 action:
   add a colon at the end of the line.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 62, section 4.5 COMMANDS, "Build a line".
 text:
   you may add a station st at its end through
 action:
   add a colon at the end of the line.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 64, section 4.6 CONTRACTS, "Preconditions".
 text:
   We could of course add the information to the header comment, as in
 action:
   add a colon at the end of the line.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 end of page 64, section 4.6 CONTRACTS, "Preconditions".
 text:
   We may omit the assertion tags and colons
 action:
   I think that tags are not optional anymore in ECMA Eiffel.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 65, section 4.6 CONTRACTS, "Preconditions".
 first paragraph after the Boolean definition.
 text:
   i >= 1 is unambiguously true or false
 action:
   The letter 'i' in "is" should be in black (it is currently in blue).
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 end of page 65, section 4.6 CONTRACTS, "Preconditions".
 text:
   as it appears in the interface
 action:
   I think I miss something on the logic to whether to add a colon or
   not at the end of line preceding a code snippet. Sometimes there is
   one, and sometimes there is none. So far I tried to systematically
   report when one was missing, but there are so many missing that I
   now realize that this must be on purpose. So I'll stop reporting that
   from now on, although I didn't discover yet why colons are added in some
   cases and not in others.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 end of page 71, section 4-E.5 "Postcondition vs invariant"
 action:
   The title says "Postcondition" but in the exercise text it is
   mentioned "routine's precondition".
 -- Eric Bezault, 7 March 2009

=== 5 Just Enough Logic ===
<strike>
Page 82, theorem box.
<br>Remark: the theorem text seems to take for granted that in "e" one can replace at least an occurrence of u by v.
<br>As explained in the proof sketch, it may be the case that u does not occur in e. For clarity, I would add to the theorem 
<br> text: "For any boolean expressions u, v and e, with u that can occur in e from 0 to n times,... "        
<br>Marco P. 26/2/2009

<br>Page 82, box at bottom. Remark: here and in the following box, you use the notation "/XYZ/" to express a comment that you later use 
<br>also as a label. Have you considered using "--XYZ", the Eiffel notation, for consistency? After all it is valid Eiffel code.   
<br>Marco P. 26/2/2009

<br>Page 83, Proof after box about De Morgan's laws. Remark: you might consider having a simple exercise at the end of the chapter about
<br>proving the theorem using the already seen principles.  
<br>Marco P. 26/2/2009

<br>Page 85, line 2: "...since the precedence rule making and bind tighter than or is arbitrary." Remark: it would be nice to have a reference
<br>or some more detail here.
<br>Marco P. 26/2/2009

<br>Page 88, sentence 6 in the list. Remark: In this list, as specified immediately before,  you seem to be considering the case in which "a" is false. 
<br>Sentence 6 refers to the case in which "b" is true instead. I think it would be clearer if the sentence 6 is moved from the list to the end of the page, 
<br>as an example in which the consequent holds and yet this does not suffice to determine the truth of the implication.
<br>Marco P. 26/2/2009

<br>Page 88, lines 1 and 2 after the 6 sentences. Remark: depending on what you decided to do with the previous sentence (6), this should be changed.
<br>In any case, if you leave it like it is, and don't explain what is explained at the end of the page about the consequent, it is not immediate to understand
<br>why today's weather does not affect the truth of the implication.
<br>Marco P. 26/2/2009

<br>Page 88, bottom line: "cases in which the consequent holds (I2), do not suffice to determine the truth of the implication as a whole."
<br>Remark: I find the expression "truth of the implication as a whole" a bit confusing. Something like: "cases in which the consequent holds (I2),
<br>do not suffice to determine all the cases in which the implication would be True." would be clearer for me. 
<br>Marco P. 26/2/2009

<br>Page 89, the picture is blurred. I cannot read the comic strip.
<br>Marco P. 26/2/2009

<br>Page 90, last box, and 91, first line: same observation as for page 82 before (/REVERSE/)
<br>Marco P. 26/2/2009

<br>3 lines after beginning of section 5.3: "This is all the more remarkable that modern logic was established..."
<br>Remark: This is all the more remarkable in that modern logic was established..." maybe?
<br>Marco P. 26/2/2009

<br>Page 93, 6 lines from the bottom: "...like death in video games, where you can get new lives (as long as you continue paying)"
<br>Remark: as you can have different mechanisms, "...like death in certain video games, where you can get new lives (as long as you continue paying)" 
<br>is slightly more precise.
<br>Marco P. 26/2/2009

<br>Page 94line 2 and 3: "The second way would be to decide that and as we understand it in programming is not commutative any more (the same would, 
<br>for duality, hold of or)." Remark: a couple of commas seem to be missing. I suggest: "The second way would be to decide that and, as we understand it in
<br>programming, is not commutative any more (the same would, for duality, hold of or)."
<br>Marco P. 26/2/2009

<br>Text in small font 10 lines from the top: "Such improvement of execution speed, known as optimization, is generally not carried out not by programmers"
<br> One "not" is redundant.
<br>Marco P. 26/2/2009

<br>Text in small font close to the bottom, line 4 after the box: "An operator is “non-strict” on an operand if it may in some cases yield a meaningful result 
<br>even that operand does not have a defined value." Remark: I think a "when" is missing: "An operator is “non-strict” on an operand if it may in some cases 
<br>yield a meaningful result even when that operand does not have a defined value."
<br>Marco P. 26/2/2009

<br>Page 95, line 2: "The same holds for or else relative to or". Remark: for consistency with the previous case, it should be: "The same holds for or relative to or else"
<br>Marco P. 26/2/2009

<br>Page 98, 2 lines after the second bullet: "If Stations8 denotes...". Remark: the name may induce some confusion: I would suggest Line8_stations.
<br>Marco P. 26/2/2009

<br>Page 100, lines 2 and 3 from the top: "This is not quite precise enough, however, because of the case of an empty set.". 
<br>Remark: as you explain the empty set case in detail later, I would put a forward reference here. 
<br>Probably a similar reference should go after the box at the bottom of page 98. 
<br>Marco P. 26/2/2009

<br>Page 100, 8 lines after the box: Remark: a comma is missing in the set definition, between 9 and 11. 
<br>Marco P. 26/2/2009

<br>Page 100, lines before U1 towards the end: "(compare with those for existential quantification, E2 and E1 above)"  
<br>Remark: you may consider replacing "above" with "in the previous page"
<br>Marco P. 26/2/2009

<br>Picture of exercise 5-E.11 is blurred.
<br>Marco P. 26/2/2009
</strike>


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 84, section 5.1 BOOLEAN OPERATIONS, "De Morgan’s laws"
 in the box "Theorems: Distributivity of boolean operators"
 text:
   (a or (b and c))
 action:
   `c' should be in blue, not in black.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 86, section 5.2 IMPLICATION, "Definition"
 paragraph after the truth table
 text:
   It’s the same as the table for or, with True and False values for b switched.
 action:
   I guess you meant "with True and False values for a switched"
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 90, section 5.2 IMPLICATION, "Getting a practical feeling for implication"
 in the second code snippet box
 text:
   (a implies b) = ((not ) implies (not a)) -- REVERSE
 action:
   the last parenthesis should not be in italic.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 92, section 5.3 SEMISTRICT BOOLEAN OPERATORS
 first 3 paragraphs (as well as in page 97 later in this chapter)
 action:
   in chapter 4, the function `i_th' returns a STATION, not a METRO_STATION.
 -- Eric Bezault, 7 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 100, section 5.4 PREDICATE CALCULUS, "Precise definition: universally quantified expression"
 text:
   V n: X | n.is_prime means that all members of x are prime numbers
 action:
   x should be in upper-case
 -- Eric Bezault, 8 March 2009


 from Draft 27.02, 3 March 09 16:55 (Zürich)
 page 100, section 5.4 PREDICATE CALCULUS, "Precise definition: universally quantified expression"
 text:
   (compare with those for existential quantification, E2_and E1_on the previous page):
 action:
   no underscore after E2 and E1
 -- Eric Bezault, 8 March 2009

===6 Creating objects and executing systems===
===7 Control structures===
Corrections by Raphaël Meyer

<strike>Page 142: the four bulletpoints are not parallel. bulletpoint 3 refers to its while the first two start with "the". the fourth one is completely different than the first 3.

Page 143: addition box towards the top. there is an error in the calculation. the sum of the two numbers should be 729 (not 29)

Page 144: paragraph underneath heading "Precision and explicitness: algorithms vs recipes": The word "follow" on the third line should be "following".

Page 145: First paragraph that starts with "In German and French": At the end of the first sentence, I would say "heat the thing up at some point" rather than "heat up the thing at some point".

The final sentence of the first paragraph is not grammatically correct: "Only the Italian version
mentions this detail — 'cook according to the times given' — without which
the pictures would be meaningless." I would say "Only the Italian version mentions this detail - cook according to the times given - which gives meaning to the pictures."

Page 145: The paragraph that starts with "For algorithms, as opposed to informal recipes": The second clause should read "as opposed to for informal recipes"

Page 147: In the first bulletpoint: The final sentence is a little long and confusing. I would change the second half of it to the following: "... software elements, this book tends to use the word system rather than the word 'program' (which may still suggest the idea of doing just one task)'"

Page 147: The second bulletpoint: The first sentence is confusing. I would say "The
description of the data structure—in the object-oriented approach of this book, the object structure — to which processing steps apply is as important to a program as the steps themselves."

Page 148: Under the "sequence" bulletpoint, final sentence: "would executed" should be "would execute" or "would be executed"

Page 150: final paragraph, bottom of the page, first sentence: "not any more get" should be "no longer receive" or "no longer be given"

Page 151: Textbox with "Touch of Style" as its header: the bulletpoints are formatted strangely. Shouldn't the first line be aligned with the second line for each bullet?

Page 152: Paragraph beginning with "Even on separate lines ...": "put two version of the same ..." should be "put two versions of the same ..."

Page 153, first paragraph starting with "Note that the syntax ...": The sentence "but it is useful to allow it for when a sequence appears as part of a larger structure." is unclear. REvise the first part to clarify between "it" and "it".

Page 154, textbox entitled "Correctness": the word "compound" in the second bulletpoint should be capitalized.

Page 154, bottom of the page, final 3 lines: the formatting seems incorrect. The final sentence should all be on one line.

Page 155, paragraph starting with "A typical example of loop": the sentence should read "A typical example of a loop ..."

Page 155, middle of the page: There appears to be a diagram or picture missing next to the tagline "Highlighting a station"

Page 157, first paragraph that starts with "This ensures that ...": the clause "the third step to I2 for i = 3" should read "the third step to I3 for i = 3 ..."

PAge 158, last sentence of the paragraph starting with "the 'maximum' example ...": The last sentence reads "and the invariant INV (s), where s is a subset N1, N2, ..., Ni of DS, is
that we have found the maximum of s." This should be reworded since it is not clear grammar.

Page 158: first bulletpoint under "Note - in the general case ...": Typo: "sufficently" should be "sufficiently"

Page 163: second bulletpoint underneath the paragraph starting with "The loop postcondition principle ... ": The fist part of the sentence reads "Sufficiently flexible to let us extend it from ..." I think it would be clearer if it read "Sufficiently flexible that we can extend it from ..."

Page 164, textbox entitled "Loop Variant": Typo: "Afterexecution" should be "After execution"

PAge 165, final paragraph that starts with "You may well feel ...": The third sentence reads "If you have ever try ..." but should read "If you have ever tried ...". Further, the sentence then reads "it might very well be the result of such ..." but should read "it might very well have been the result of such ..."

Page 168, final paragraph starting with "... for successive values of i ...": The second sentence reads " ... used for iterating over object structures such as list." Is this correct grammar? Should it not be " ... used for iterating over object structures such as lists."?
</strike>

===8 Routines, functional abstraction and information hiding===
<strike>Page 211, section 8.4, lines 1 and 2 after the second box. "The first line gives the name of the routine, as well as its signature: 
<br>the list of its formal arguments, if any, and their types."
<br>Remark: according to the ecma standard, page 38, the signature of a feature does not include the names of the arguments,
<br>which seems to be suggested here.         
<br>Marco P. 26/2/2009

<br>Page 213, section "Interface vs implementation", first bullet:  
<br>Remark: "Text View" should be "Basic Text View". That's how it is in EiffelStudio.   
<br>Marco P. 26/2/2009

<br>Page 213, section "Interface vs implementation", 3 lines from the bottom:  
<br>Remark: "Text View" should be "Basic Text View". Same as above.   
<br>Marco P. 26/2/2009

<br>Page 216, lines 6 to 9. "We saw how the signature of a procedure is characterized by a name and an optional list of formal arguments 
<br>with their types,". Remark: not consisted with th edefinition of signature in the ecma standard, page 38. The signature of a feature does not include 
<br>neither the arguments names nor the feature name.         
<br>Marco P. 26/2/2009

<br>Page 219, side note: "The format is a variant of XML"
<br>Remark: to my understanding, it is plain XML, not "a variant" of XML. Of course adheres to its own XML schema, but this is how it usually is. 
<br>Marco P. 26/2/2009

<br>Page 219, end of text in small font: 'as in “Decision Problem”, Entscheidungsproblem'
<br>Remark: may be Entscheidungsproblem should be double-quoted too, like in 'as in "Decision Problem”, or "Entscheidungsproblem"?'
<br>Marco P. 26/2/2009

<br>Page 221, Section 8.10, 5th bullet point from the start of the section: "A routine has a name, a signature defining the types of arguments and result
<br>if any, a contract, and a body describing its algorithm."
<br>It should probably made clearer that "if any" refers to both the types of argument and the result. Maybe this is the correct way to express this. 
<br>Please just doublecheck.
<br>Marco P. 26/2/2009
</strike>

===9 Variables, assignment and references===
Corrections by Annie Meyer<br><strike>
Page 234


We saw in the discussion of creation that an object, as it exists at run time in the
memory of your computer, consists of a number of fields, some references,
some expanded:

some referenced, non?

Page 242

The principle shields client software from the these
changes: 

retirer le the


Page 243

Itisnot OK, however, to let clients assign directly to it, as in the illegal
Line8.index := new_value, since (among other problems) this would reveal
it is an attribute.

... this would reveal that it is ....

Page 244

A procedure such as set_a or go_ith which has as its principal effect to set the
value of an attribute is called a setter procedure (or setter command).

Rajouter un peu de ponctuation. ... which has, as its principal effet, to .....

Why would ever need something like this since we clients can simply use index
is the attribute is exported?

Rajouter mots et punctuation

Why would we ever ...... since we, clients, can

Page 245

Exporting an an attribute is legitimate and lets clients access (but not modify)
the corresponding field values.

Retirer un des an au debut de la phrase.


To client authors, both
kinds simply appear as queries

Ajouter un . après queries

Page 260

and should handled in classes that deal with object structures in general.

Should be handled non?

Page 262

that an operation that an operation that does not
name a variable cannot affect associated properties.

Retirer that an operation puisque c'est la deux fois.

Page 263

Fin de la page 

any manipulations that
could cause sneaky aliasing and produce surprising effects.

Pourquoi un s à manipulation?

Page 264

But the effect would
probably worse,

be worse

Page 266


make things more difficult since you cannot assign
to a formal routine argument,

Je ne comprends pas. Question de punctuation peut-être
</strike>

===PART II: HOW THINGS WORK===
===10 Just enough hardware===
Corrections by Raphaël Meyer<br><strike>

page 269, final paragraph, first sentence: typo: "formating" should be "formatting"

page 270, middle of the page: it seems like there should be a diagram or drawing next to the left-caption "A bit (low-tech version)", but there is nothing there.

page 271, second to last paragraph starting with "Early on, the ...": is this formatting correct? Shouldn't this paragraph have the same formatting as the one below it? (or at least the bulletpoint above it?)

page 272, second bulletpoint under "For the basic units:": "... is on the order of four billions" should read "is on the order of four billion"

page 272, next paragraph: "For example if" should read "For example, if"

page 272, same paragraph, sentence starting with "256 possibilities ...": "on your keyboard — ~, !, @ etc. —, the ..." should read "on your keyboard —, ~, !, @, etc., the ..."

page 272, paragraph starting with "For languages ...": "such a Cyrillic, ..." should read "such as Cyrillic, ..."

page 272, same paragraph: this does not make sense to me: "which uses two or more commonly four bytes for a character" ... consider revising/clarifying

page 273, paragraph starting with "The starting position ...": "(in these cases one byte, four bytes and eight)" sounds awkward. It should either be written as "(in these cases one byte, four bytes and eight bytes)", or (worse) "(in these cases one byte, four and eight)"

page 274, table: "4 billions" should be "4 billion"

page 275, paragraph starting with "Having a binary interpretation ...": "1.44 megabyte" should read "1.44 megabytes"

page 275, paragraph starting with "In most practical cases ...": "what’s a few millions?" should be "what’s a few million?"

page 276, first bulletpoint under the paragraph starting with "These properties affect ...": "it reads it" ... I would specify at least one of the "it" to make the sentence more clear.

page 278, paragraph starting with "Some programmers ...": "but this not necessarily true" should read "but this is not necessarily true"

page 279, first paragraph, final sentence: it currently reads "Let’s see what memories can do for us.", but shouldn't it read "Let’s see what memory can do for us."?

page 279, first paragraph under the "Persistence" heading: "powering off the memory unit will lose the data." is not correct. It should read something to the effect of "powering off the memory unit will result in a loss of data."

page 279, second sentence of the paragraph that starts with "Words like ...": the sentence "As rough estimates in technology that is current at the time of writing:" is very confusing. Consider rewording.

page 279, first bulletpoint underneath aforementioned sentenced: "The time to access a character might around 50 nanoseconds, ..." should read "The time to access a character might be around 50 nanoseconds, ..."

page 280, paragraph underneath the "RAM" bulletpoint, final sentence: "such as disks presented below" should read "such as the disks presented below"

page 280, "Core memory" bulletpoint, first sentence: "This term to points back ..." should read "This term points back ..."

page 280, there is no photograph or diagram next to the caption "A memory chip" underneath the paragraph starting with "The photograph below ..."

page 281, first bulletpoint starting with "Others are meant ...": The final sentence ends with a close parentheses that was never opened: "'Storage' is just a synonym for memory.)"

page 281, next paragraph: "all rotating a speed of" should read "all rotating at a speed of"

page 281, same paragraph: "If power is switched off the heads ..." should read "If power is switched off, the heads ..." for clarity.

page 283, paragraph starting with "Computer operations ...": "Most architecture offer at most a few dozen registers" should read "Most architecture offers at most a few dozen registers"

page 281, paragraph about halfway down the page: "The order of magnitude of typical access times at the time of writing are" should read "The orders of magnitude of typical access times at the time of writing are"

page 284, paragraph starting with "The reason this policy ...": "... is that program typically use, ..." should read "is that programs typically use, ..."

page 284, next paragraph: "each programs sees a" should read "each program sees a"

page 284, same paragraph, same sentence: "contiunous" should be spelled "continuous"

page 285, halfway down the page: "Computers offers instructions of three main kinds:" should read "Computers offer instructions of three main kinds:"

page 285, final paragraph, final sentence: I believe "PowerPC" should read "Power PC" (it shows up 2 other times on page 285 as "Power PC")

page 286, first paragraph, third sentence: "at much higher level of abstraction." should read "at a much higher level of abstraction."

page 286, same paragraph, next sentence: once again, "PowerPC" should read "Power PC"

page 286, first paragraph: since we are talking about hardware power (a thing) and not a person, I think the following sentence "hardware power, whose most popular formulation was first presented" should be changed to "hardware power, the most popular formulation of which was first presented"

page 287, paragraph starting the "The basic Moore's Law": "as this is its the last section):" should read "as this is the last section):"

page 288, first paragraph: "(turning off the computer loses the values)." should read "(turning off the computer results in a loss of values)."

page 288, under "Further Reading": "John Markoff, has for many years covered ..." The comma (,) after "Markoff" is unnecessary.
</strike>

===11 Describing syntax===
All of chapter 11 done by Raphael Meyer

<strike>page 293, bottom of the page on the right: the blurb starting with "We'll see an example ..." gets cut off at the end of the sentence, i.e. you can't tell what page number it is referring to.

page 297, first paragraph, first sentence: "of specimens of each the constructs" should read "of specimens of each of the constructs"

page 303, towards the top of the page: "we have to apply to another construct B" should read "we have to apply it to another construct B"

page 304, Second bulletpoint underneath "Applying the same process again ...": "heads tail stop" should read "heads tails stop" to be consistent with the other bulletpoints

page 314: underneath the "Touch of History" textbox: There is a sentence ("Another recent text, up to date on many important compiler techniques.") that is a bit out of place since it should come before the textbox, immediately underneath the Muchnick's book. Consider reformatting in some way.

Finished on 3 Feb 2009 at page 316.
</strike>

===13 Programming languages and tools===
Corrections by Annie Meyer<br><strike>
Page 318

 

Section manquante

 

Survey of programming language styles

 

Page 329

 

The following figure shows a typical state of the EiffelStudio debugger.

 

Je trouve cela genant que la figure soit a la page suivante.

 

This dynamic view does not

replace careful static analysis, since an execution is only one of a myriad possibilities, but complements it by giving you a practical, concrete feel for what happens at run time.

 

A myriad of possibilities, non?

 

Page 330

 

To enter program modules and other software elements (such as design documents and other documentation), upi may use text editors—the programs that enable us to type and format documents.

 

 

What is upi?

 

Page 336

 

Version control tools help you keep track of successive versions of an individual module: in our three-dimensional picture, it corresponds to a horizontal plane as shown, or in the case of a single developer to a horizontal line.

 

A horizontal plane or an horizontal plane?

 ...................................... Line?
</strike>



===PART III: ALGORITHMS AND DATA STRUCTURES ===
===13 Fundamental data structures, genericity, and algorithm complexity===



Corrections by Stephan v S:

<strike> p. 353, "naming conventions for features of reusable components" does not really belong under the bullet "Algorithm complexity"

p. 357, "safety and flexibility," --> "safety and flexibility."

p. 359, "non -generic" --> "non-generic".

p. 360, "and hash tables —, all" --> "and hash tables — all"

p. 361 top, "find if a part" --> "determine if a part" or "find out if a part"

p. 361 middle, "G will denotes" --> "G will denote" or "G denotes"

p. 369, "complexity. assessing" --> "complexity. Assessing"</strike>

<strike>

p. 370, "throws a dice to decide" --> "throws a die to decide"

p. 370, "2^33 - 1" --> "2^31 - 1"

p. 371, "People will think of (and test for) cases in which an array or other structure has items; then in an execution for some particular input data, the container happens to be empty, and everything blows up." --> "People will typically think of (and program for) cases in which an array or other structure has items, leading to errors in executions where it happens to be empty."

p. 372, the blue overlay box in ARRAY's `make' is ill-aligned.

p. 374, "For class ARRAY and others in this chapter the following notations, using brackets, are available:" --> "The following notations use brackets and are available for class ARRAY and others in this chapter:"

p. 375, rephrase "In such cases including several occurrences of array elements, especially with mathematical operations involved, [5] is better and follows mathematical practice."

p. 376, "execution a fixed lower and upper bounds," --> "execution fixed lower and upper bounds,"

p. 377, "the very fast, O (1) cost of a standard" --> "the very fast O (1) cost of a standard"

p. 378, "If after creation the bounds lower and upper do not change, or change only rarely, the implementation is highly efficient, since every access to the function, or modification of the function’s value for a certain index in the interval, is O (1) and very fast." --> "The implementation is very efficient, since every access to the function or modification of the value for a given index in the interval has O(1) complexity."

p. 378, the last parenthesis of "(O (count))" should be black.

p. 378 in the summary table, the word "indices" is used. "indexes" would be more consistent with the rest of the content.

p. 379, "third of type PERSON, assumed to be an existing class" --> "third of type PERSON, which is assumed to be an existing class"

p. 379, "as a data structure — the way arrays" --> "as a data structure — in the way arrays"

p. 384 top, the figure is quite distorted.

p. 385, "for non-empty list." --> "for non-empty lists."

p. 385, "go_i_th (i: INTEGER" --> "go_i_th (i: INTEGER)"

p. 386, "Iterating on a list" could also be "Iterating over a list"

p. 386, "your_list." has a big blue full-stop

p. 390, "bottom object is an instance of LINKED_LIST [T]" -- isn't it the top object in the picture?

p. 391, in the figure at the bottom there is a small yellow strip in the `right' field of the new LINKABLE.

p. 392, "this example illustrates the earlier discussion about the delicate nature of programming with references is delicate" --> "this example illustrates the delicate nature of programming with references mentioned before"

p. 392, "with item value "La_Motte" at" --> "with item value "Lourmel" at"

p. 394 top, "the first traversal takes n" --> "the first traversal takes count"

p. 394, "overall number of iterations is count (count – 1) / 2" --> "overall number of iterations is count (count + 1) / 2"

p. 395, reverse algorithm: c := c + 1 should be placed in the loop body, and `count' in the variant actually designates the original count upon routine entry. A local variable could be created to store its value.

p. 396, the right arrows in the figure are quite low in the linkables, and the third and fourth linkables are quite far apart from each other.

p. 397, code box at top: "go_i_th (count – 1)" --> "go_i_th (index – 1)". This code assumes "index - 1" is a valid argument for `go_i_th', i.e. that `back' was never called when index was 0. A test might be needed around the call to `go_i_th' to remove this restriction.

p. 398, closing parenthesis needed in figure caption: "(Compare with the singly linked list in the figure)"

p. 399 in the figure, the `index' arrow's base is purple and its head is pink.

p. 400, "go_ith (i)," --> "go_i_th (i),"

p. 400 in the figure, the '[' should be blue in "BI_LINKABLE [ARRAYED_LIST" .

p. 404, "8 billions," --> "8 billion,"

p. 405, "not (has (k)" --> "not (has (k))"

p. 407, the "Comments" column in the table is unused.

p. 408, "put (x: G; i: INTEGER): G" --> "put (x: G; i: INTEGER)"

p. 408, "after putting a coin" --> "after inserting a coin"

p. 410, last word: "this:." --> "this:"

p. 412, "which ....; at" --> "which ...; at"

p. 412, "underlies the run-time support of every modern programming language implementation" ... implementations of most functional programming languages do not use call stacks because of closures.

p. 413 middle, there are random characters in the figure.

p. 415, it is unclear what the arrow and "T" are denoting in the figure. Perhaps the "Top"?

p. 415, "remove has the precondition is_empty" --> "remove has the precondition not is_empty"

p. 416, in the top figure, "T" and "S" could be replaced by "Top" and "Growth direction" respectively. The same is true of "To" and "S" in the bottom figure.

p. 417, there is also a "T" in the figure

p. 418, in the first figure, "Producer" and "Consumer" are mangled. The same is true for the figure at the bottom of the page (this time "In" and "Ac").

p. 419, the second figure has mangled annotations.

p. 420, in the code box: "then grow end" --> "then rep.grow end"

p. 424, "a single array can use two stacks" --> "a single array can host two stacks"

p. 424, "make setting up the queue as empty of any items" --> "make setting up an empty queue"

p. 424, "Reverting lists" --> "Reversing lists"

</strike>

<br>Corrections by Annie Meyer<br><strike>
Page 358

 

so are validity rules

(also called static semantics) are defined for syntactically correct texts.

 

Retirer un des deux are

 

(Original figure on page 46.)

 

Mettre sur deux lignes

 

Page 361

 

Many of their basic operations are the same: insert or remove an item, find if a particular item if present, find the number of items¼.

 

............... item is present, .......

 

One of the operations will we need for each kind of container is to find out whether a a container is empty (has no items).

 

2 fois a

 

Page 365

 

Computers have big memories; there are few more stupid program events than hitting a fixed limit and not being able to reallocate the structure.

Even our arrays will be resizable.

 

Cette phrase me semble bizarre.

 

Page 366

 

It is not enough to measure concrete performance on specific examples and report that “on average item took 10 nanoseconds for arrays and 40 nanoseconds for linked lists”:

 

On or an ? ou on average item X took ?

 

Cette phrase n'est pas claire pour moi.

 

Page 373

 

For cases such as

simple_array the choice of 0 or 1 as starting index is partly a matter of taste If you are like me you think of your thumb as the first finger on your hand, not the zeroth, and of your middle finger as the third, not the second.

 

Il manque un point après taste et avant If de If you are like me

 

 

Page 376

 

To change the value of

an item, the default mechanism is put (v, i) with the precondition we’ve seen:

valid_index (i).

 

with the precondition that we have seen serait mieux je pense.

 

 

If you misestimate, you may be the

algorithm will fail.

 

Retirer you may be

 

 

Unlike put, procedure force has no precondition and so is always applicable. If i falls outside of the interval lower..upper, it will call resize to accommodate the requested entry.

 

Pourquoi lower n'est-il pas en bleu dans lower..upper et pourquoi n'y a-t-il que .. et pas ...

 

 

Page 378

 

An array of type ARRAY [G] represents a total function from the integer interval lower..upper to G.

 

.. ou ... ?

 

Page 391

 

Deuxième boite. Il y a un x en noir au lieu de bleu

 

Below is a picture of how class LINKED_LIST implements the command put_right, which as specified earlier must add an element to the right of the cursor without moving the cursor. For a linked list, it suffices to create a new LINKABLE cell and update the linking:

 

 

Which, as specified earlier, must

 

Les virgules manquent

 

Tu pourrais aussi en rajouter une avant, without moving the cursor

 

Page 396

 

You should test your understanding of the reversal algorithm by writing its variants for other implementations studied next: arrayed lists and two-way lists

 

. le point final manque.

 

 

The complexity is O (1) for operations that need only perform operations at the cursor position: put_right, remove_right.

 

... operations that need only to perform ....

 

Le to manqué

 

Operations that may need to traverse the list are O (count). This is the case, as we already saw independently of the choice of implementation, for search and has.

 

 

...independently of the choice of implementation ...

 

Pourquoi of the choice?

 

 

The procedure reverse as just seen is also O (count). This is also the complexity of general cursor movement, go_i_th, as well as finish (implemented as go_i_th (count).

 

Deux fois also. Retire celui de la deuxième phrase  

 

 

Page 397

 

which is O (n) (with a a previous attribute you can perform one back in O (1), but only one, invalidating the value of previous, so this not very useful).

 

Deux fois a  with a a previous

 

 

Page 398

 

The manager (Roger Osmond) asked a senior developer to check the code, uncovering that it was performing back operations again and again — on instances of LINKED_LIST. Replacing this by TWO_WAY_LIST yielded an instant speedup factor of 23 (that is, the code ran twenty-three times faster). The programmers lived happily ever after, and never a single time did they raise their voices again about the speed of the generated code.

 

Pourquoi mentionner le nom du manager?  Ce n'est pas comme si c'était Tony Hoare ou Knuth que tout le monde connait.

 

Page 399

 

ARRAY such as item and put. Internally, as shown in the figure, lower is 1, so as a result of the array invariant capacity = upper –- lower + 1 the upper bound lower is capacity.

 

upper –- lower  Il y a un problème avec le trait entre ces deux mots.

 

 

Page 400

 

Then an arrayed list provides the benefits of arrays both in space (no need for reference fields such as right and left in the earlier solutions) and also speed if some random access will be needed;

 

both in space ..... and in speed    plutot que also ou also in speed

 

Page 404

 

You may use it form example to declare a hash table of objects representing persons, indexed by their names, as

 

For example le m est en trop.

 

Page 405

 

If

you are too far below the real need, you will just pay for one more resizing (automatic, of course) at run time

 

Ajoute un . après time

 

Page 408

 

then to retrieve an item you have no any influence on which one you will get; the basic query is

 

Je ne comprends pas cette phrase

 

Page 409

 

The next two sections covers stacks and queues.

 

Retirer le s a covers

 

Page 410

 

Figure manquante ?

 

Page 411

 

the –

operators applies to the previous two operands,

 

Retirer le  s a operator

 

Page 412

 

Consider a programming language, Eiffel or any other, where a routine can call a routine, which can call a routine, which ¼.; at execution this yields a call chain:

 

Pourquoi ajouter  ...., Eiffel or any other, ?

 

 

Page 415

 

In class ARRAY the number of items is known as both count and capacity, with an invariant stating they are equal.

 

Stating that they are equal, non?

 

This should not be confused with the count of stacks, which gives the number of stack items—in the arrayed implementation, the number of array positions occupied by stack elements.

 

Cette phrase me semble bizarre.

 

 

Of course, the available memory is limited in the end, so you still have to ensure the total size of your data structures remains within control.

 

.... to ensure that the total size of your ....

 

Je trouve que c'est mieux de mettre that. Je trouve que ca rend la phrase plus facile à lire.

 

 

Page 418

 

 

a assembly line producing cars from parts,

 

n missing an assembly line

 

(with the obvious implementation of remove as out_index := out_index + 1 and put (v) as in_index := in_index + 1; rep [in_index] := v, where rep is an array), since we would quickly run out of space after a few put even if, as a result of one or more remove space remains unused at the beginning of the array:

 

ajouter une , après remove sur la dernière ligne.

 

 

When we increment in_index in the highlighted instruction, we do it modulo capacity: i \\ j is the integer remainder of i by j, as i // j is their integer quotient.

 

Après capacity faut-il : ou ; ?

 

Page 421

 

As we have seen, a common need on such structures, it to apply a certain operation repeatedly to all these objects.

 

.....structures, it ??? to apply ....

 

Il manqué un mot.

 

Page 422

 

Apply an to all items until the first one that satisfies, or does not satisfy, a certain condition.

 

Apply an ????? to all items

 

Il manque un mot.

 

Page 423

 

Dispensers let you access, insert and remove elements at only one place. A Last-In First-Out policy yields stacks, First-In First-Out yields queues.

 

Peux-tu verifier que c'est bien cela que tu veux dire. Ce n'est pas une critique mais comme c'est important et que je ne comprends pas assez pour juger je veux juste être sure.
</strike>

===14 Recursion and trees===
The following notes are from Raphaël Meyer <br><strike>

page 427, paragraph starting with "For our immediate purpose ...": "and Conditional, in turn involves ... " should read "and Conditional in turn involves ..."

page 428, "Touch of History" textbox: "played the key role" is generally stated this way: "played a key role"

page 440, second paragraph, first sentence: "Any node C other than the root fall into" should read "Any node C other than the root falls into"

page 443, top of the page, first paragraph: "an assigner command for the the corresponding" should read "an assigner command for the corresponding"

page 443, final paragraph: it would be clearer and easier to read if commas were added, like so: rather than "Traversals such as preorder which always go as deep into a tree before trying other nodes are also known as depth-first." ... instead it should read "Traversals such as preorder, which always go as deep into a tree before trying other nodes, are also known as depth-first.

page 445, paragraph starting with "Our example binary ...": the final clause of this sentence doesn't make sense to me nor does it seem complete. "... all the values in the left subtree are less than the root value, 35, all those in the right subtree are greater, and again recursively in every subtree." Consider revising the final clause.

page 447, middle of the page: it seems to me that the O in "O (h)" should be bolded instead of italicized, right?

page 454, first paragraph underneath "Minimax" heading: "of backtracking algorithm," should read "of the backtracking algorithm,"

page 454, paragraph starting with "A primitive evaluation": "to be worth three as much" should read "to be worth three times as much"

page 455, paragraph starting with "Each player uses": "alternatively represent moves" should read "alternatively represent the moves"

page 455, paragraph starting with "In the figure": "choose, among the moves available from the current position (three in the figure) the" should read "choose, among the moves available from the current position (three in the figure), the"

page 455, M2: "The value of an internal node from which the moves are Maxi’s are the maximum" should read "The value of an internal node from which the moves are Maxi’s is the maximum"

page 458, final paragraph: "the adversary, which uses ..." should read "the adversary, who uses"

page 460, paragraph in the middle of the page: "Each player now stops exploring its alternatives whenever it finds" should read "Each player now stops exploring his alternatives whenever he finds"

page 460, paragraph starting with "Minimax and alpha-beta": "defined by a large search spaces" should read "defined by large search spaces"

page 462, paragraph starting with "We have seen": "Others such hanoi" should read "Others such as hanoi"

page 464, bulletpoint starting with "the body of Hanoi": "first argument. and also" should read "first argument, and also"

page 466, paragraph starting with "The value for ...": "Yet it has not obvious variant" should read "Yet it has no obvious variant"

page 471, paragraph starting with "here and in subsequent steps": "and each Fi+1 for i > 0, is defined as h (Fi)" should read "and each Fi+1 for i > 0 is defined as h (Fi)"

page 472, first paragraph starting with This immediately justifies": "never gets any more pair," should read "never gets any more pairs,"

page 475, second paragraph: "notion of recursion variant." should read "notion of a recursion variant."

page 480, third bulletpoint towards the bottom of the page: "activation record at top of the stack" should read "activation record at the top of the stack"

page 480, final paragraph: "of recursion in a high-level language we have learned" needs a comma. it should read "of recursion in a high-level language, we have learned"

page 481, paragraph starting with "(Instead of a full-fledged ...": "the context of a call: number of disks" should read "the context of a call: the number of disks"

page 483, point 2: "exclusively on the local." should read "exclusively on the local variable."

page 486, paragraph starting with "This simplification applies": "in the first case you must pop the other values (count, x, y, z), in the second you don’t." should read "in the first case you need to pop the other values (count, x, y, z), in the second you don’t."

page 487, second bulletpoint. The first sentence is a run-on. Consider revising.

page 489, point H3: there is an open parentheses "(" but it is never closed.

page 490, fourth bulletpoint: "Any loop can be expressed into an equivalent recursive form" should read "Any loop can be expressed in an equivalent recursive form"

page 493, problem 14-E.9: "This exercise requires a mathematical analysis," can be written "This exercise requires mathematical analysis,"

page 494, problem 14-E.12: the problem ends with a closed parentheses ")" that was never opened.

page 494, problem 14-E.13: "(Only you have solve the previous exercise.)" should read "(Only if you have solve the previous exercise.)" or "(Only when you have solve the previous exercise.)"

page 494, problem 14-E.15: "This exercise requires a basic knowledge of linear algebra" should read "This exercise requires basic knowledge of linear algebra"

page 494, problem 14-E.15: "and B a vector." should read "and B is a vector."
</strike>

Comments by Annie


<strike>
Page 425

 

 ... still doing very well thank you, is an example of a structure defined recursively, in the following sense:

 

Je retirerais le "thank you"

 

L'exemple est vraiment bien trouve c'est très spirituel mais le thank you gache un peu les choses.

 

 

Page 427

 

as in a Laughing Cow scheme.

 

Pourquoi a et pas the ?

 

Page 429

 

A man put a pair of rabbits in a place surrounded on all sides by a wall.

How many pairs of rabbits can be produced from that pair in a year if every month each pair begets a new pair which from the second month on becomes productive?

 

A man put or puts?

 

Page 430

 

There are indeed many such problems. One that concentrates many of the interesting properties of recursion with the least irrelevant detail arises from an attractive puzzle: the Tower of Hanoi.

 

Trop de many  tu peux remplacer le deuxième par plenty

 

Page 431

 

When all is over, the tower

and the Brahmins will fall, and it will be the end of the worlds.

 

... the end of the worlds ou the end of the world

 

Page 434

 

send an SMS to the cell

phone of the appropriate priest or an email to her Blackberry, directing her to move a disk from source to target. For the rest of us you can write move as a procedure that displays a one-disk-move instruction in the console:

 

Ton histoire de pretre, pretresse avec le her me parait bizarre.

 

Page 436

 

Recursion also shares

properties with a loop solution, since it approximates the solution to the whole problem by solutions covering part of the data, but it is more general, since each step may combine more than one such partial solution.

 

Deux fois since. Tu peux remplacer le deuxième pas as

 

 

Page 443

 

In practice it is convenient to specify replace as an assigner command for the the corresponding query, by changing the declarations of this query to

item: G

making it possible to write bt.item := x rather than bt.put (x).

 

Retirer le deuxième the a la fin de la première ligne.

 

Page 454

 

• It is a two-player game. We assume two players called Minnie and Maximilian, the latter familiarly known as Maxi.

 

• To evaluate the situation at any time during a game, you have an evaluation function with a numerical value, devised so that a lower value is better for Minnie and a higher one for Maxie.

 

C'est Maxi pas Maxie

 

 

Page 455

 

Each player uses the minimax strategy to choose, from a game position, one of the legal moves. The tree model represents possible games; successive levels of the tree alternatively represent the moves of each player.

 

 

This assumption of symmetry is essential to the minimax strategy, which performs a depth-first traversal of the tree of moves to assign a value to every node:

 

Tu es sur de vouloir utiliser le mot "minimax" sans le mettre en bleu dans le texte.

 

M2 The value of an internal node from which the moves are Maxi’s is the maximum of the values for the node’s children.

 

????? Je ne comprends pas cette phrase. Il manque quelque chose mais je ne sais pas quoi.

 

 

Page 457

 

The auxiliary functions worst and better are there to switch between Minnie’s and Maxie’s viewpoints: the player is minimizing for any odd level l and maximizing for any even l.

 

un e en trop a Maxi, devrait etre Maxi's

 

 

Dans la marge

 

 

To avoid the repeated

use of the TUPLE

type,you may instead

define a small class

GAME_RESULT with

integer attrbutes value

and choice.

 

Ajouter un espace après la , et devant you

 

Ajouter un i a attributes

 

 

Page 489

 

Il y a une marque noire dans la marge de gauche.

 

Page 491

 

Our litte language is called WASO (acronym for With Abstract Syntax

Only) and has the following properties:

 

Ajoute un l pour little

 

 

From this class and the rules [] and [13] defining the function graph in the bottom-up interpretation of recursion, write a program that produces the i-th approximation of the graph, Hi, for any i. The algorithm may use loops, but it may not use recursion.

 

Est-ce normal que après the rules [] soit vide.
</strike>

===15 Devising and engineering an algorithm: Topological Sort===
<strike>

 In section 16.1, just after the first figure: 
 Money, Pass, Map, Louvre, Orsay
 Money, Pass, **Louvre, Map**, Orsay
 Money, Map, Pass, Louvre, Orsay
 
 The second one is wrong. -- Luchin Doblies, 1.12.2008.


 Section 16.3, topic "Cycles in the constraints", line 4-5:
 "A topological sort program gets its input **in the form individual ordering constraints**, ..." 
 
 Missing "of": "in the form of" -- L.D., 1.12.2008


 Section 16.4, topic "The Loop", second last line of the code-square:
 if “Any elements remain” then-- Report cycle:
 cycle_found := True
 “Insert these elements into **cyclist**”
 end
 
 I believe cyclist should be plural, "cyclists". -- L.D., 1.12.2008


 Section 16.4, topic "The Candidates", second page, line 4: 
 "What concrete **date** structure should we use for candidates?"
 
 "date structure" instead of "data structure". -- L.D., 1.12.2008


 Section 16.7, second line:
 "..., such as the "<“ relation on numbers."
 
 The quotes do not match in font. -- L.D., 1.12.2008
</strike>

Corrections by Raphaël Meyer<br><strike>
page 499, in the "Definition: Relation" text box: (unnecessary dash): "set A (short for binary relation)—is a set of" can simply be written "set A (short for binary relation) is a set of"

page 505 first paragraph starting with "The relation ...": (extra s) "Our relations on points" should be "Our relation on points"

pages 508 and 509, entire pages: (formatting): it seems like there is excessive space in between paragraphs on these pages. is that normal?

page 512, bottom of the page: (missing word "the") "As new exit condition, we’ll simply have" should be "As the new exit condition, we’ll simply have"

page 514, in the code, feature "Access", sorted "List": (missing word "be") "the elements that can ordered in that way" should read "the elements that can be ordered in that way"

page 517, paragraph starting with "For our first attempt": (missing word "do") "(declared secret, as all .." should read "(declared secret, as do all ...)"

page 519, bottom of the page: (missing comma) "For example the" should read "For example, the"

page 520, formatting: why is there so much white (empty) space on this page?

page 522, paragraph starting with "we must also": (the "do" is unnecessary) "if you do want to do that" should read "if you want to do that"

page 523, paragraph starting with "There remains T1": (need to add "that" to sentence for clarity) "or report there isn’t any" should read "or report that there isn’t any"

page 525, towards the top: (formatting) shouldn't there actually be a piggy bank here, rather than just text saying that there should be a piggy bank?

page 533, "Touch of Heuristics" textbox: (need to remove the "s" on "structures") "into an internal data structures carefully" should read "into an internal data structure carefully"
</strike>

===PART IV: OBJECT-ORIENTED TECHNIQUES ===

===16 Inheritance===
====Corrections by Raphaël Meyer====
<strike>page 541, paragraph starting with "Order is what science ...": I think that "seek" here should be "seeks", since you are essentially talking about "science": therefore, "that science, and with it engineering, seek systematic" should be "that science, and with it engineering, seeks systematic"

Page 545, middle of the page: (missing diagram) there should be a diagram here but there isn’t.

 

Page 545, paragraph starting with “If the class”: (“do” should be “does”) “If the class do not exist” should read “If the class does not exist”

 

Page 546, paragraph starting with “From now on”: (missing comma) “from its parents if any.” Should read “from its parents, if any.”

 

Page 546, paragraph starting with “How then can”: (awkward wording) “(let the tooltip guide you to find it):” should read either “(let the tooltip help you find it):” or “(use the tooltip as a guide while finding it):”

 

Page 546, paragraph starting with “the result looks like”: (“comments” needs to be “comment”) “note a new kind of comments, here” should read “note a new kind of comment, here”

 

Page 547, paragraph starting with “Accumulating features”: (extra s needs to be removed) “inheritance mechanisms’s” should read “inheritance mechanisms’”

 

Page 548, bottom of the page, small paragraph starting with “Remember that”: (typo) “(atrributes, local variables)” should read “(attributes, local variables)”

 

Page 548, bottom of the page, paragraph starting with “’Polymorphism’ is the …”: (awkward wording) “with dynamic binding to be studied next” should read “with dynamic binding (to be studied next)” or alternatively “with dynamic binding, to be studied next.”

 

Page 549, paragraph starting with “As the definition notes”: (missing word in sentence) “not only from assignment but from argument passing” should read “not only from assignment but also from argument passing.”

 

Page 549, last sentence of the paragraph starting with “where the actual”: (wording needs to be changed and typo) “that have not be devised yet” should read “that have not yet been devised”

 

Page 549, paragraph starting with “In spite of its”: (awkward wording) “meaning, from its Greek roots, ‘ability’” should read “in Greek, ‘ability’”

 

Page 549, same paragraph: (awkward wording) “polymorphism involves neither any run-time change of objects nor any creation of objects with different types.” Should read “polymorphism involves neither run-time object changes nor the creation of objects with different types.”

 

Page 549, paragraph starting with “As a matter of fact”: (bad wording) “As a matter of fact you” should read “In fact you”

 

Page 550, paragraph starting with “We will not explore”: (bad wording) “ambiguity over” should read “ambiguity regarding”

page 550, paragraph starting with "But then plymorphism": (bad wording) "possibility of my_vehicle_for_today itself being polymorphic" should read "possibility that my_vehicle_for_today is polymorphic"

page 551, paragraph starting with "is of type Vehicle": (awkward sentence structure that leaves the sentence unclear) "vehicle type, and you don’t know. Nor do you need to know, since" should be divided differently. I would write "vehicle type. You don’t know which particular type it is, but don't need to know since"

page 551, paragraph starting with "Just calm down": (add the word "to" for clarity and sentence structure) "if it is, subject it to" should read "if it is, to subject it to"

page 553, paragraph starting with "As you have probably": (missing word "of") "to the type flexibility" should read "to the type of flexibility"

page 554, paragraph starting with "A consequence of the": (rewording: it is better to suggest that you have used descendant, rather than the chapter, therefore this needs to be rewritten) "(which has enabled this chapter to use just “descendant” so far)" should read "(which has enabled me to only use “descendant” so far in this chapter)"

page 554, paragraph starting with "All this just to": (typo, I don't know what "sas" means, I can't recommend another word): "it is the one we sas, but"

page 555, bottom half of the page underneath "Looking up the list of features": missing diagram.

page 556, paragraph starting with "We say that": (missing s on "features") "two kinds of feature" should read "two kinds of features"

page 557, towards the bottom of the page: (add the word "that" for clarity): "The reason move_next is" should read "The reason that move_next is"

page 558, paragraph starting with "This prohibits us": (add comma for clarity) "or VEHICLE, for example in create my_vehicle_for_today with the" should read "or VEHICLE, for example in create my_vehicle_for_today, with the"

page 558, paragraph starting with "Because creation", end of second sentence: (typo: the comma should be a semicolon, and "This" should not be capitalized) "view), This" should read "view); this"

page 558, paragraph starting with "Eiffel allows you": ("feature" is missing an s) "any deferred feature." should read "any deferred features."

page 558, bulletpoint starting with "the EiffelBase library": (missing word) "LINEAR (structures that can traversed one-way)" should read "LINEAR (structures that can be traversed one-way)"

page 558, bulletpoint starting with "The Eiffelvision graphics library": ("feature" should be plural) "concrete kinds of figure" should read "concrete kinds of figures"

page 558, very bottom of the page: (offers should be offer) "notably Java and C#, offers a language" should read "notably Java and C#, offer a language"

pages 558-559, sentence starting with "It is like a class": (tense is wrong) "It is like a class where all features would be deferred (and would not have any contracts)" should read "It is like a class where all features are deferred (and do not have any contracts)"

page 565, paragraph starting with "All this discussion": (clarity/style issue) "It does not address well the" should read "It does not effectively address the"

page 566, paragraph starting "Such references": (missing the word "the") "the concept of stored-program computer:" should read "the concept of the stored-program computer:"

page 567, paragraph starting with "You can trace in the figure": The second sentence in this paragraph ("Following the ...") is not a complete sentence. Please revise.

page 567, bottom paragraph starting with "Explanation:" : (period should be a comma) "C routine. which we apply" should read "C routine, which we apply"

page 568, paragraph starting with "The time overhead": ("bound" should be "bind"): "to bound it by a" should read "to bind it by a"

page 569, paragraph starting  "The above code": ("an" should be "a") "than an starting address" should read "than a starting address"

page 570, paragraph starting with "In these cases": (wrong word order) "programmer mistakenly to assume" should read "programmer to mistakenly assume"

page 570, paragraph starting with "The rule to remember": (formatting) "is that dynamic binding" should read "is that dynamic binding" i.e. the "d" needs to be bolded as well.

page 570, paragraph starting with "These observations complete": (typo: "into" should be "to") "if you want to get into the" should read "if you want to get to the"

page 571, paragraph starting with "You will also": (sentence missing a "that" or a "the" to make it complete) "This will also reveal that heir may" should read "This will also reveal that that/the heir may"

page 573, towards the bottom of the page: (incomplete sentence; revision needed because the sentence does not end coherently) "In other words, T, as a subcontractor, is breaching the contract to which the original contractor S, the only known to clients such as C."

page 575, final sentence of paragraph starting with "When writing a deferred": (unnecessary comma that distorts meaning of the sentence) "which descendants may refine, but never contradict." should read "which descendants may refine but never contradict."

page 576, paragraph starting with "The Contract": (sentence missing "as") "specify, broadly or narrowly as you wish," should read "specify, as broadly or narrowly as you wish,"

page 578, paragraph starting with "Inheritance is specialization": (I think you should add an "a" to this sentence since you are writing in language here without any mention of code): "vehicles specialize the notion of moving object," should read "vehicles specialize the notion of a moving object,"

page 578, same paragraph, same sentence: (I think you should add an "a" to this sentence since you are writing in language here without any mention of code): "taxis specialize the notion of vehicle." should read "taxis specialize the notion of a vehicle."

page 581, paragraph starting with "but not,": (add a "with" for clarity and correctness) "but not, of course, a1.first_f, since" should read "but not, of course, with a1.first_f, since"

page 581, paragraph starting with "but not,": (reorder words for clarity) "the above two calls would" should read "the two calls above would"

page 582, paragraph starting with "Apart from": (incorrect wording) "renaming is useful to get" should read "renaming helps you get"

page 585, second bulletpoint: (replace "itself" with "it too") "A list is a special kind of “chain”and itself has more" should read "A list is a special kind of “chain”and it too has more"

page 586, paragraph starting with "Sorting algorithms": (add "that" for clarity) "assuming what we are" should read "assuming that what we are"

page 588, bulletpoint starting with "If you define": (shouldn't "operation" be plural here?) "it provides all the required operation" should read "it provides all the required operations"

page 588, paragraph starting with "to specify that": ("parameters" should be singular) "an actual generic parameters," should read "an actual generic parameter,"

page 589, paragraph starting with "constrained genericity": (wrong word order) "Other language approaches are possible to the problem discussed here" should read "Other language approaches to the problem discussed here are possible"

page 590, first bulletpoint: (sentence missing the word "at") "you cannot introduce it a higher level" shuold read "you cannot introduce it at a higher level"

page 593, first bulletpoint: (add comma for clarity and flow) "if the object test appears as the condition of an if the scope" should read "if the object test appears as the condition of an if, the scope"

page 596, paragraph starting with "In such cases": (add comma for clarity) "If you are discriminating between a whole range of types you are" should read "If you are discriminating between a whole range of types, you are"

page 596, paragraph starting with "Assume for example": (sentence missing the word "the") "with facility for flashing" should read "with the facility for flashing"

page 597, two bulletpoint at the top of the page: revision needed - they should both speak of "can" or both speak of "could", but should not be left as they are right now (i.e. the first bulletpoint speaks of "can" and the second  of "could")

page 597, paragraph starting with "As another example": (typo) "a program formater," should read "a program formatter,"

page 598, paragraph starting with "The features are not": (missing words) "better collect them in a" should read "it is better to collect them in a"

page 602, first small paragraph at the top of the page: (add word "but" to make the sentence complete) "comments, not relevant" shuold read "comments, but not relevant"

page 603, last bulletpoint: (consider revising this sentence; it does not seem to make grammatical sense) "the type of any object to which a variable may be come attached at run time"

page 603, same bulletpoint: (add a comma for clarity) "This ensures that in any assignment or argument passing the type" should read "This ensures that in any assignment or argument passing, the type"

page 606, bulletpoint starting with "A conditional": (unclear sentence, consider revising) "A conditional if the form" should read "A conditional is of the form"

page 606, step 1 at the bottom of the page: (Capitalize first word) "1. using" should read "1. Using"

page 606, step 1 at the bottom of the page: (replace the comma with a "but") "not using multiplication, using Euclid’s algorithm" should read "not using multiplication but using Euclid’s algorithm

page 607, paragraph starting with "Check the output": there is an open-parenthesis that is not closed anywhere. Please close it.
</strike>



===17 Operations as objects: agents and lambda calculus===
(Comments by Annie Meyer)
<strike>Page 653

It has been particularly successful for Graphical User Interfaces (GUI), which we’ll use as our primary example.

Tu avais dit que tu voulais retirer toutes les contractions. 


Page 654

Welcome to the modern world. If you write a program with a GUI, you let users choose, at each step, what they want to do, out of many possibilities — including some unrelated your program, since a user may go to another window, for example to answer an email.

Unrelated to your program ?   le to manque

Page 655

Figure à ajouter

but this suffers from all the problems we have seen with multiple-choice algorithm structures (as part of the justification for dynamic binding): it’s big and complex, and highly sensitive to any change in the setup.We want a simpler and more stable architecture, which we won’t have to update each time there is a new control.

Ajouter un espace apres setup. et We

Page 656

Such a system might have
sensors monitoring temperature, pressure, humidity; any new recording, or just those exceeding some preset values, may trigger an event which some elements of the software are prepared to handle.

Deux fois some   

Tu peux remplacer le deuxième par other

Page 657

Usually there’s more:
when and where did Columbus sail? What were the cursor coordinates? But in some cases all that matters is that the event occurred, as with a timeout event indicating that a previously set deadline has passed.


it’s an operation that makes information (the arguments a, b, c) available to a software element (the feature f ).



Page 658

The term “argument” highlights the similarity with routines. Pushing this similarity further, we’ll assume that the arguments are grouped in an ordered list, like the arguments in a call x.f (a, b, c).



The notification model is more flexible and we’ll assume it from now on.

 

before it’s triggered the
event does not exist, and afterwards it’s too late to subscribe to it!



after you’ve spotted the headline on


Page 659

Although we might define an event type for each key on the keyboard, it’s more attractive to use a single “key press” event type of signature [CHARACTER], where the argument is the key code.

 


As always when you are hesitating about introducing a class, the criterion is “is this a meaningful data abstraction, with a set of well-understood operations applicable to all instances?”. Here:

Il y a un point en trop avant Here:

If we decided to build a class to represent a particular event type, its instances would be events of that type; but they have no useful features.
True, each event has its own data (the arguments), but there’s no meaningful operation on the event other than accessing such data.



Page 660

E3 At any time, a publisher can trigger an event. This will cause execution of actions registered by subscribers for the event’s type. These actions will can use the event’s arguments

c'est will ou can? La phrase est terminée ou pas?


Page 661

E2 A subscriber is any element that needs to handle such GUI events; it registers the routines it wants to execute in response For example you may register, for the mouse click event type on a button that says “OK” in a file saving dialog, a routine that saves the file.

Il manqué un point avant For example

the other way around it’s more a matter
of methodology, and we will see how various architectural solutions fare against this criterion.



Page 662

It is not possible (points 1, 5) to subscribe to an event; as we have seen, the event does not exist until it has been raised, and when it has been raised that’s too late. (Nice idea, though: wouldn’t you like to subscribe retroactively to the event “IBM’s shares rise by at least 5%”?) A subscriber subscribes to an event type — to declare that it wishes to be notified of any event of that type raised during execution.



“A subscriber can handle multiple events from multiple publishers” (point
2): this might seem to suggest some sophisticated concurrent computation scheme, where a subscriber catches events from various places at once, but

in reality is just a mundane observation: a given subscriber may register for

several event types, and several publishers may trigger events of a given type.

In reality it is just ......, le it manque non?


Point 5 states that when “an event” has multiple subscribers, each will handle it synchronously (meaning right away, blocking further processing) when “an event” is raised. Read literally, this would suggest that two

“events” are involved! That’s not the idea: the sentence is simply trying to

say that when multiple subscribers have registered for a certain event type, they handle the corresponding events synchronously. It uses a single word, in the same breath, with two different meanings.

Je continue à te signaler les contractions si tu veux les retirer.

Page 663

Definition: Context
In event-driven design, a context is a boolean expression specified by a subscriber at registration time, but evaluated at triggering time, such that the

registered action will only be executed if it the evaluation yields True.

Un mot en trop "it"?

Page 665

you’ll have to add some program text, often called “glue code”; the less of it the better.
The last requirement is critical to the quality of a system’s architecture, especially when the goal is to build user interfaces: you shouldn’t have to design the core of an application differently because of a particular interface.


Page 671

it’s easy to ease the
restrictions later if you find that new classes need the features.

Page 672

We’ll call such descendants
“subscriber classes” and their instances “subscribers”.

Page 673


With handle as written above you woll only find them at run time, through the tests
                                 Will?
on the size and element types of args; that’s too late to do anything serious about the issue, as reflected by the rather lame “Do nothing, or report error” above: doing nothing means ignoring an event (is that what we want, even if the event is somehow deficient since it doesn’t provide the right arguments?); and if we report an error, report it to whom? The message should be for the developers — us! — but it’s the poor end user who will get it.

Pourquoi "poor" end user?  Je trouve ce mot inutile. 

Page 674

The only missing part of the Observer pattern’s implementation is the body of the publish procedure in PUBLISHER, although I hope you have already

composed it in your mind. It’s where the pattern gets really elegant:


Subscribers directly subscribe to publishers. This causes undesirable coupling between the two sides: subscribers shouldn’t have to know which

Page 676

it’s also much simpler. The key
boost comes from the agent and tuple mechanisms.


We won’t have PUBLISHER or
SUBSCRIBER classes any more, but just one class — yes, a single class solves the entire problem — called EVENT_TYPE.

Page 677


Of course we’ll explore the implementation too, as I am sure you’ll want to see it. (It will actually be more fun if you try to devise it yourself first.)

One of the advantages is that
you don’t need to worry about when to create the object; whichever part of the execution first uses left_click will (unknowingly) do it.
We’ll see in just a moment where this declaration of the event type should appear; until then let’s assume that subscriber and publisher classes both have access to it.

Page 678

Whenever the context is relevant — subscribers don’t just subscribe to an event type as in [41], but to events occurring in a context, as in [42]—the proper architectural decision is to declare the relevant event types in the corresponding context classes.

For events that are relevant independently of any context information, declare the event type in a generally accessible class.)

Parenthèse ou pas? Ou une en trop ou une manquante.

Page 680

In an environment with manual memory
reclamation (C, C++), it’s even worse. In either case we have a source of “memory leak”: as execution fails to return unneeded space, memory occupation continues to grow.

Page 682

MVC revisited
One of the consequences of the last design is to simplify the overall architecture suggested by the Model-View-Controller paradigm. The Controller part is “glue code” and it’s good to keep it to the strict minimum.

Page 683

This solution achieves complete uncoupling between model and view; in a typical application the controller will still be still a small component, achieving

still 2 fois 


(So from the order of events it’s really the “Subscribe-Publish” paradigm.)


Page 685

you
shouldn’t use client elsewhere if the conditions are the same. Consistency is also particularly important for an API, to ensure that once programmers have learned to use a certain group of classes they can expect to find similar conventions in others.
Such tasks can be carried out to improve existing designs, an activity known as refactoring. It’s indeed a good idea always to look at existing software critically, but prevention beats cure. 


Touch of Methodology:
Assessing software architectures
When examining possible design solutions for a given problem, discuss alternatives critically. The key criteria, are: reliability, extendibility, reusability, and simplicity.

Pourquoi une , avant are?


18.8 FURTHER READING

Il n'y a pas de consistence dans les espaces entre les articles ou livres cites et les commentaires que tu ajoutes. 

Le plus simple serait de rajouter des espaces plutôt de d'en retirer car sinon cela va modifier la pagination puisque la page 688 est blanche.
</strike>

===18 Event-driven design===
Corrections by Raphaël Meyer  (6 March 2009)

<strike>
page 656, paragraph starting with "where read_line": (need to delete the word "it") "read_line if it there are" should read "read_line if there are"

page 656, final sentence of paragraph starting with "Consider the screen": (remove "or any other, such as" because it is not necessary) "to click the button, or any other, such as selecting a menu" should read "to click the button, or to select a menu"

page 657, top: screenshot missing.

page 659, bulletpoint starting with "Certain": (I think a comma, rather than a semicolon, is sufficient here) "events; or" should read "events, or"

page 659, text next to "Definitions" box: (add "an" for clarity) "Remember that an event is defined as operation to be executed." should read "Remember that an event is defined as an operation to be executed."

page 661, bulletpoint starting with "for an event type": (add a comma for clarity and flow) "without arguments the signature" should read "without arguments, the signature"

page 661, paragraph starting with "In our model, then": (add a comma for clarity) "“Delete all?”) is an object" should read "“Delete all?”), is an object"

page 662, top paragraph: (add an "s" on "wood") "get us out of the wood" should read "get us out of the woods"

page 663, point E2: (add a hyphen to clarify that you are referring to the dialogue, not the file) "file saving dialog" should read "file-saving dialog"

page 665, paragraph starting with "Even though that": (replace "that" with "it") "Even though that was not event-driven programming" should read "Even though it was not event-driven programming"

page 665, same sentence: (add comma for clarity) "such as do_if which" should read "such as do_if, which"

page 666, bulletpoint starting with "Any event triggered": (replace "and" with "or" since this is a "for example" list) "changes, and a security system" should read "changes, or a security system"

page 666, bulletpoint starting with "The subscribers": (replace "they" with the actual noun to avoid using "them" in reference to two different nouns in the same sentence) "where they come from" should read "where these event types come from"

page 667, paragraph starting with "While the application": (add an "and" to the list of functions) "computes salaries, updates" should read "computes salaries, and updates"

page 670, paragraph starting with "A side comment": (I would finish this sentence with a colon, since it is not a complete sentence and is only intended as a lead-in to the next sentence) "serving as general advice. Too" should read "serving as general advice: Too"

page 670, end of the same paragraph: (I would replace "it" with something a little more specific, since you could just be referring to "each symbol", which is not the case) "and document it." should read "and document your work"

page 670, paragraph starting with "A design pattern": (the final sentence ends awkwardly; consider revising) "them independently: 'best practices'" should read "them independently as 'best practices'"

page 671, first paragraph: (this paragraph has several colons and semicolons, so I suggest removing the semicolon in the first sentence to make it a little easier to read as a whole. In addition I think breaking it up another way may be more logical. My suggestion is listed here) "good; we will analyze its limitations. But you should" should read "good. We will analyze its limitations, but you should"

page 673, final sentence of first paragraph: (specify where the exercise is) "it is the subject of an exercise." should read "it is the subject of an exercise at the the end of this chapter."

page 673, paragraph starting with "Apart from subscribers": (shouldn't there be a "to" here?) "which indeed need to subscribe and unsubscribe the corresponding objects" should read "which indeed need to subscribe and unsubscribe to the corresponding objects"

page 674, paragraph starting with "To subscribe to": (similar issue as above. I may be misunderstanding this but I am pointing it out for your review to be certain) "to subscribe the current object" should read "to subscribe to the current object"

page 674, paragraph starting with "each observer": (add "any" for clarity) "accessing arguments if any" should read "accessing any arguments"

page 675, paragraph starting with "With handle": (I suggest spelling out what "them" is for clarity since it costs nothing) "you will only find them at run time" should read "you will only find these errors at run time"

page 675, paragraph starting with "It was noted": (change wording to clarify which programs the designer is in charge of) "outside, not those" should read "outside rather than those"

page 677, bulletpoint starting with "The last problem": (Is this the last problem you are going to talk about, or are you referring to the "previous" problem?) "The last problem" should read "The previous problem" OR "The problem mentioned in the previous bulletpoint"

page 677, paragraph starting with "All these problems": (I think this sentence would be more correct if the first half were in the present tense) "All these problems have not prevented designers" should read "All these problems do not prevent designers"

Page 679, paragraph starting with "This defines": (typo) "that’s where once come in handy" should read "that’s where once comes in handy"

Page 680, bulletpoint starting with "Note, however": (add "are" for clarity; i know it could be left out but the sentence will flow better if you include it) "and the corresponding features such as left_click just ordinary" should read "and the corresponding features such as left_click are just ordinary"

Page 680, final sentence of the paragraph starting with "Whenever the context": (should "once" in this sentence be highlighted in blue? I was not sure about this so I wanted to flag it just in case) "The once mechanism ensures"

Page 681, second sentence at the top: (Unclear what this sentence means; please revise) "It remains to see the implementation of EVENT_TYPE."

Page 681, paragraph starting with "(where, as before)": (add comma for flow and clarity) "for a better one look up" should read "for a better one, look up"

page 681, same paragraph: (remove comma) "but simply agents, with a precise type" should read "but simply agents with a precise type"

page 682, second paragraph: (typo) "The solution just describes" should read "The solution just described"

page 682, paragraph starting with "If you apply"; (I suggest rewording this sentence for clarity) "you should be aware of a performance issue, leading to potentially disastrous 'memory leaks' but easy to avoid" should read "you should be aware of a performance issue that can/could lead to potentially disastrous 'memory leaks' but is easy to avoid"

page 683, paragraph starting with "Subscribing through": (add comma for correctness) "(agent p) ensures" should read "(agent p), ensures"

page 686, second bulletpoint: ("this" is more appropriate) "At that stage" should read "At this stage"

page 687, paragraph starting with "Such tasks": (move the word "always") "It is indeed a good idea always to look" should read "It is indeed a good idea to always look"

page 687, "Touch of Methodology" box: (remove comma for correctness) "The key criteria, are" should read "The key criteria are"

page 688, bulletpoint starting with "the observer": (missing the word "an"?) "the action to be executed in response to event" should read "the action to be executed in response to an event"

page 688, next bulletpoint: ("allows" should be "allow") "Agents, constrained genericity and tuples allows" should read "Agents, constrained genericity and tuples allow"

page 688, next bulletpoint: (remove comma) "architectures, and" should read "architectures and"
</strike>

=== PART V: TOWARDS SOFTWARE ENGINEERING===
===19 Introduction to software engineering===
Corrections by Raphaël Meyer  (10 March 2009)

<strike>
page 698, bulletpoint starting with "Quality constraints": (all the other bulletpoints in this list start with a colon; I would suggest starting this bulletpoint with the same style) "Quality constraints as discussed next;" should read "Quality constraints (discussed next):"

page 698, bulletpoint starting with "Quality constraints": (add an "and" or "or" to make the sentence flow better) "correct results, will perform" should read "correct results, and will perform"

page 698, bulletpoing starting with "Duration constraints": (remove unnecessary comma) "kept operational, and regularly updated" should read "kept operational and regularly updated"

page 699, paragraph starting with "The term 'maintenance': (add "or") "a coffee machine, a house." should read "a coffee machine, or a house."

page 700, first paragraph: (since you mention "programming" earlier in the sentence, I think this word needs to be modified. I realize that the corresponding bulletpoint/section is called "Implement", but consider revising nonetheless) "(“Implement”, the second part)." should read "(“Implementing”, the second part)."

page 700, "Manage" paragraph: ("a" is unnecessary) "ensuring a smooth interaction" should read "ensuring smooth interaction"

page 700, very bottom of the page: (the second to last sentence is awkward, since it has three phrases separated by 2 semicolons. Consider revising using only one semicolon and a period, or one semicolon and a comma)

Page 701, sentence starting with "Issues of software": (consider revising wording for clarity) "Issues of software engineering involve two complementary aspects" should read "There are two complimentary aspects of software engineering issues"

page 701, first bulletpoint under previous sentence: (typo) "software projects adds" should read "software projects add"

page 701, same bulletpoint: (add "and") "documentation, installation" should read "documentation, and installation"

page 701, final bulletpoint: (replace "inasmuch" with "as long as") "are only useful inasmuch as they allow" should read "are only useful as long as as they allow"

page 702, first paragraph: (need to add "that" to make the two clauses of the sentence parallel) "imagine you are" should read "imagine that you are"

page 702, same sentence: (now, make the second part of the sentence in the same tense) "and that you track" should read "and that you are tracking"

page 702, next sentence: (add "or"): "200, 0?" should read "200, or 0?"

page 703, "Robustness" bulletpoint: (make all three portions of the sentence the same verb tense) "a sensor malfunctions" should read "a sensor malfunctioned"

page 704, "Ease of Use" bulletpoint: (change "for" to "in") "is a novice for some tools and an expert in others" should read "is a novice in some tools and an expert in others"

page 704, same bulletpoint: (reword for clarity) and "each of us, for each of the system in which we are an expert, was a novice once" should read "each of us was once a novice in the systems at which we are now an expert."

page 704, next sentence: (typo) "Ease of use" should read "Ease of us"

page 704, last two bulletpoints: (each of the previous bulletpoints started with a word and then a colon; these two do not. Consider revising)

page 704, paragraph starting with "Some product qualities": (add "the" for paralellism) "the software controlling brakes or the air bag" should read "the software controlling the brakes or the air bag"

page 704, paragraph starting with "Descriptions": (incomplete sentence sentence after a semicolon, revise) "the user'; the term that has acquired almost mythical connotations" should read "the user', a term that has acquired almost mythical connotations"

page 704, final bulletpoint: (add hyphen for correctness) "information hiding," should read "information-hiding,"

page 705: (the spacing seems to be greater in between lines on this page than on other pages. Please confirm that this is normal.)

page 705, final bulletpoint: (add comma for flow and clarity) "software components you can" should read "software components, you can"

page 706, first paragraph: (add "that" for clarity and correctness) "you to ensure your software" should read "you to ensure that your software"

page 706, paragraph starting with "From the global": (reword for clarity) "the relevant product factors are the external ones just discussed as they are relevant to customers" should read "the external product factors just discussed are the most relevant to customers."

page 706, "Production speed" bulletpoint: (reword for correctness) "in a short time." should read "in a short amount of time."

page 707, second bulletpoint: (reorder wording) "the inclusion in the process of mechanisms and procedures" should read "the inclusion of mechanisms and procedures in the process"

page 707, next sentence: (replace comma with semicolon) "decreed and attempted, it" should read "decreed and attempted; it"

page 707, "Predictability" bulletpoint: (typo) "time,." should read "time."

page 707, "Reproducibility" bulletpoint: (add "an" to keep the clause parallel) "not assembly-line" should read "not an assembly-line"

page 707, next sentence: (replace "no one" with "none" or "no software",because "no one" suggests a person or human being, which in this case is not right) "no one will ever achieve"

page 707, final bulletpoint: (reword for clarity and correctness) "the inclusion in the process specification of mechanisms to qualify and improve the process itself" should read "the inclusion of mechanisms to qualify and improve the process within the process itself."

page 707, final sentence: (typo) "adapting it a result" should read "adapting it to a result"

page 708, first sentence: (add parentheses for clarity and readability) "as CMMI studied next" should read "as CMMI (studied next)"

page 708, paragraph starting with "one of the characteristics": (missing a space after "essential") "where it’s not essential—" should read "where it’s not essential —"

page 709, second bulletpoint: (add "and" to complete the sentence) "usage, security" should read "usage, and security"

page 709, same bulletpoint: “impact on the system’s environment and consequences” should read “the impact on a system’s environment and the consequences”

page 709, paragraph starting with “Documentation”: (add comma for flow and clarity) “for users it may” should read “for users, it may”

page 710, first bulletpoing: (phrase can be shortened) “at the level of implementation,” should read “at the implementation-level,”

page 710, paragraph starting with “It has become”: (awkwardly worded sentence; consider revising) “It has become a common practice, reflective perhaps of the lack of rigor of process model definitions, to represent them in graphical form.” should read “It has become common practice to represent them in graphical form, which perhaps reflects the lack of rigor of process model definitions.”

Page 712, first line of text underneath the graphic: (the top of this line of text is partly covered up by the graphic. This needs to be fixed)

Page 712, next sentence: (add comma for clarity and flow) “becomes untenable the” should read “becomes untenable, the”

Page 712, same sentence: (remove comma and replace “which” with “that”) “shipping a prototype, which” should read “shipping a prototype that”

Page 713, paragraph starting with “the tasks appearing”: (add “or” for correctness) “insufficient contracts, imperfect” should read “insufficient contracts, or imperfect”

Page 713, next sentence: (replace “as well as” with “while also”) “as well as providing” should read “while also providing”

Page 714, second bulletpoint: (remove unnecessary comma which only makes the sentence confusing) “Collaboration, between developers” should read “Collaboration between developers”

Page 714, “Small increments” bulletpoint: (“rather than waiting … and running) “and run the risks” should read “and running the risk”

Page 714, next bulletpoint: (awkward and confusing wording; consider rewording) “to force making the thinking process explicit” should read “to make the thinking process explicit” or “to ensure and explicit thinking process”

Page 714, paragraph starting with “The original”: (typo) “at time” should read “at the time”

Page 715, first bulletpoint: (typo) “to be build” should read “to be built”

Page 715, paragraph starting with “this is a short”: (remove comma and reword for clarity and flow) “advice, and when writing requirements to follow the recommended structure, widely used in practice” should read “advice and to follow the recommended structure, widely used in practice, when writing requirements.”

Page 715, next sentence: (replace semicolons with commas, and add the word “and”) “introduction; overall description; specific requirements” should read “introduction, overall description, and specific requirements”

Page 715, next sentence: (add the word “and”) “dependencies; apportioning” should read “dependencies; and apportioning”

Page 715, next sentence: (since you say “including”, I don’t think “in particular” is necessary here, especially since it just makes the sentence confusing) “including in particular sections” should read “including sections”

Page 716, first paragraph: (typo) “do the requirement cover” should read “do the requirements cover”

Page 716, paragraph starting with “note the terminology”: (add “in” for correctness) “as each of these examples” should read “as in each of these examples”

Page 717, last paragraph: (add comma for clarity) “if they cannot implement the required functionalities the” should read “if they cannot implement the required functionalities, the”

Page 717, same paragraph: (replace semicolon with a comma) “the purse strings); and the head” should read “the purse strings), and the head”

Page 719, final paragraph: (typo) “Too often, requirements document fail” should read “Too often, requirements documents fail”
</strike>

=== PART VI: APPENDICES===
===A Using the EiffelStudio environment===
===B Eiffel syntax specification===
===C An introduction to C++ (from material by Nadia Polikarpova)===

 <strike>p. 770, Section "Derived types": "since it is possible to assigned a dereferenced" --> "since it is possible to assign a dereferenced"
 -- Stephan 18/2/2009

 p. 777, "a::x" --> "A::x"
 -- Stephan 18/2/2009

 p. 780, "trying to access a non-existen object" --> "trying to access a non-existing object"
 -- Stephan 18/2/2009

 p. 782, in "exception through throw ()).", the full-stop should be black (not blue)
 -- Stephan 18/2/2009

 p. 783 top, "If no matching try block" --> "If no matching catch block"
 -- Stephan 18/2/2009

 p. 789 bottom, "assert b" --> "assert b;"
 -- Stephan 18/2/2009

 p. 793 top, "Blocks correspond to Eiffel compound and consists of" --> "Blocks correspond to Eiffel compounds and consist of" or "Blocks correspond to Eiffel compound statements and consist of"
 -- Stephan 18/2/2009

 p. 794, top box: "for (init_statement expression;" --> "for (init_statement; expression;"
 -- Stephan 18/2/2009

 p. 798 top, in "a fraction part, an e symbol, followed by an optionally signed": the e symbol is also optional.
 -- Stephan 18/2/2009</strike>

===D An introduction to Java (from material by Marco Piccioni)===

Comments by Stephan v S:

<strike>
General comment: check the indentation style of code in boxes!

p. 717, second last bullet: "O-O part of the type system does not include basic types" is wrong. The O-O part of the type system also includes classes that "box" primitive types. One can write a valid Java program using only integer literals (i.e. numbers) and class Integer.

p. 718, in the box at the bottom, the "}" should be removed after "... Other class declarations ... }".

p. 719, bottom, just before "Program execution": "package originating with our group (domain name se.ethz.ch)" --> "package from an institution with domain name se.ethz.ch might be called". This is consistent with "names that start with the institution’s..."

p. 720 in the box: "... Code" is indented very deeply

p. 720 first paragraph of "The Java type system": "hierarchy stands a class called Object" --> "hierarchy is class Object"

p. 720 second paragraph of "The Java type system": "affects basic types" --> "concerns basic types"

p. 721 just before the box at the bottom: "contains examples of all" --> "contains examples of members".

p. 721 in box right at the bottom: "Constant" --> "Constant field"

p. 721 in box right at the bottom & in box of p. 720 top: find a consistent indentation style for // comments.

p. 722 in the box at top: the closing brace "}" of constructor "D() {" should be properly indented. 

p. 722 right at bottom: "directly access to fields" --> "directly access fields"

p. 723 first line: "This flies in the face of information hiding principles" --> "This is against information hiding principles.

p. 723 first paragraph: the blue "and" should maybe be black and italicized.

p. 723 first paragraph of "Static members": "Another of the Java concepts" --> "Another Java concept"

p. 724 in the boxes, the indentation style should be consistent with others used in Touch of Class.

p. 724, 5 lines from the bottom: "of the same number" --> "or the same number"

p. 726, in I8: "Execute all non-static block initializers are executed." --> "Execute all non-static block initializers"

p. 727 in the top box: "Defines an array of integers" --> "Declares an array of integers"

p. 727 in the second box: a semicolon should be added after the statement "arr = new int[size]"

p. 727 second line after the third box: "be careful to note" --> "note". Later in the same sentence: "will be that of" --> "will be"

p. 727 right after the third box, the sentence should rather read: "The expression arr.length (length is a read-only field) yields the number of elements in arr; note that after the above allocation its value will be equal to size."

p. 728 third line: arithmetic overflow does not cause an exception. Marco verified this.

p. 728, in the paragraph after the second block: "The finally part is executed in all cases, exception or not" --> "The finally part will be executed irrespective of whether an exception occurred or not"

p. 729 last paragraph: arithmetic overflows will not trigger exceptions.

p. 731 in the first box: a semicolon should follow "super(m)"

p. 732 in the first box of "Genericity": the highlighted section cuts away the characters in the formal generic parameters. In this same box, "Class declaration" --> "Class body"

p. 733 right after the first box: "this could be a function" --> "this could be a method"

p. 734 in the top box: should the `case' statements be indented?

p. 735 in the last box: "for(variable: collection)" --> "for (variable: collection)"

p. 737 in the discussion of nested classes: it's a more standard practice to emulate multiple inheritance through delegation and not through nested classes. The standard solutions looks like this (referring to p. 738 top): create an interface Q and a class T that implements it. Let R extend P and implement Q. An instance of T is referenced by a private field of R, and calls to methods of Q are directly delegated to this instance. The advantage of this solution is that R conforms to both P and Q, and that T can also be extended in a subclass, whereas nested classes cannot be inherited from.

p. 739 bottom box: there should be a semicolon after "perform(e.args)", and the closing brace "}" for the `build' method is missing.

p. 740 in the discussion of listeners, "encumber our system with a new class fulfilling a local role only" - this is not the only solution: U can implement ClickListener, making a new class unnecessary.

p. 740, second paragraph: "class that inherits from ClickListener" --> "class that implements ClickListener"

p. 742, third line after the first box: "and it must come at the end" --> "and it must be at the end"

p. 743 in the second box: should "x.getAnnotations" not be "x.getAnnotations()"?

p. 744 in the "Operators" box: "==" --> "+=" in "Assignment:"</strike>

Corrections by Raphaël Meyer (6 March 2009)


<strike>
page 718, paragraph starting with "Java Programs": (reword for clarity and correctness) "which however are an organizational concept, not a language mechanism)." should read "which are not a language mechanism but instead an organizational concept)."

page 718, paragraph starting with "packages": "allow organizing classes" should read "allow you to organize"

page 719, paragraph starting with "in their third role": (change "as" to "that") "conflicts as may arise" should read "conflicts that may arise"

page 719, paragraph startin with "The package mechanism": (reword for correctness) "components being listed in reverse order" should read "listing components in reverse order"

page 722, bulletpoint starting with "protected": (reword for correctness) "but no other classes" should read "but not to any other classes"

page 722, very bottom of page: (reword to make sense) "This means that you can directly access to" should read "This means that you have direct access to"

page 723, first paragraph: (add a hyphen) "information hiding principles" should read "information-hiding principles"

page 723, same paragraph: (add words for clarity and correctness) "methodological practice of never exporting fields, keeping them private instead and equipping each of them with a getter function and a setter procedure." should read "methodological practices of never exporting fields, keeping the fields private instead and equipping each of them with a getter function and a setter procedure."

page 723, paragraph starting with "To use": "and will use" should read "and you will use"

page 723, same paragraph: (reorder words for correctness) "To denote the current object (Current in Eiffel) use the keyword this." should read "Use the keyword this to denote the current object (Current in Eiffel)."

page 723, paragraph starting with "java": (reword and make certain nouns plural) "any non-static method or field (since it would" should read "any non-static methods or fields (since they would"

page 723, paragraph starting with "The main program": (reword for correctness) "which defines execution as creating an object and calling a creation procedure on it" should read "which defines execution as the creation of an object and a call to create a procedure on it"

page 724, paragraph starting with "Another difference": (reword for clarity and correctness) "whose members would all be" should read "whose members are all"

page 725, first pagraph: (add comma to separate ideas) "inheritance overloading" should read "inheritance, overloading"

page 725, paragraph starting with "a new expression": (put "had" in the present tense) "Class D indeed had two constructors" should read "Class D indeed has two constructors"

page 725, same sentence: (replace ";" with ",") "one with no arguments; one with" should read "one with no arguments, and one with"

page 726, point I8: (sentence does not make sense; revise) "Execute all non-static block initializers are executed."

page 726, paragraph starting with "Step I9": (reorder sentence for correctness) "the Java rule that every object creation must invoke, in addition to a constructor of the given class (possibly the default constructor), a parent constructor" should read "the Java rule that every object creation must invoke a parent constructor in addition to a constructor of the given class (possibly the default constructor),"

page 726, first bulletpoint under previous paragrah: (simplify wording) "The text of the local constructor" should read "The local constructor text"

page 726, same bulletpoint: (change wording for clarity) "so this will cause a call" should read "so this will result in a call"

page 726, next bulletpoint: (add "in" for parallel construction, and remove the ",") "the parent, or its default" should read "the parent or in its default" (additional note: you might want to replace "its" with "the parent's" to make this more clear)

page 727, paragraph starting with "Array access": (incomplete sentence; revise) "You may assign to an array element, as in"

page 728, first paragraph: (replace "are" with "include") "Typical causes of exceptions are" should read "The typical causes of exceptions include"

page 728, same paragraph: (reword for clarity and conciseness) "It is also possible in Java to trigger a developer exception explicitly through" should read "You can also explicitly trigger a developer exception in Java through"

page 728, paragraph starting with "where e": (run on sentence; please revise) "where e is of an exception type, which should be a descendant of the Throwable library class; more commonly, it is a descendant of Exception, one of the two heirs of Throwable, intended for programmer exceptions."

page 728, paragraph startin with "If execution": (reword and reorder for clarity and correctness) "If execution of the try block triggers an exception of one of the types listed" should read "If an exception of one of the types listed is triggered upon execution of the try block"

page 728, same sentence: (reword and remove "here") "here ET1, ET2, ¼ execution immediately transfers (without completing the try block) to the corresponding catch block." should read "the execution of ET1, ET2, ¼ immediately transfers to the corresponding catch block without completing the try block." (this sentence is still confusing and does not appear to be a complete sentence.)

page 728, next paragraph: "Occurrence of an exception creates an exception object, accessible to the program in the corresponding catch clause through the specified exception name, such as e." - this is very unclear and should be written "An exception object is created each time an exception occurs; this object is accessible to the program in the corresponding catch clause through the specified exception name, such as e."

page 728, next sentence: (reword for clarity) "This makes it possible to access such properties as the human-readable name of the exception and the state of the call stack," should read "This allows you to acces such properties as the exception's human-readable name or the state of the call stack,"

page 729, paragraph starting with "These techniques": (i suggest reordering for better flow) "to defeat the purpose of the mechanism by writing a perfunctory catch clause that pacifies the compiler but does nothing" should read "to write a perfunctory catch clause that pacifies the compiler but does nothing, thereby defeating the purpose of the mechanism"

page 729, same paragraph, second to last sentence: (change to present tense) "did not retain checked exceptions" should read "does not retain checked exceptions"

page 730, paragraph starting with "the redefinition": (use "cannot" instead of "may not") "The overriding method may not be static" should read "The overriding method cannot be static"

page 730, next paragraph: (reword for clarity and change the first comma to a ";") "You have to be careful about keeping an identical signature, since any change in type or number of arguments would be considered overloading and so would not produce a compilation error" should read "You have to be careful about keeping an identical signature; any change in type or number of arguments will be considered overloading, and therefore no compilation error will be produced"

page 730-731: (paragraph spacing) it appears that the line spacing on page 731 is greater than on page 730. please confirm.

page 734, paragraph starting with "To obtain": (reorder words for clarity) "If you omit them control will flow, when a branch terminates, to the next branch" should read "If you omit them, when a branch terminates control will flow to the next branch"

page 734, same paragraph: (remove comma) "if conditionals, and loops" should read "if conditionals and loops"

page 735, towards the bottom of the page: (typo) "The langauge" should read "The language"

page 735, very bottom of the page: there is a close-parentheses ")" that was never opened. i think it needs to be deleted.

page 736, paragraph starting with "Java has no": (add "the" for clarity) "such as C# delegates" should read "such as the C# delegates"

page 737, paragraph starting with "For a long time": (reword for correcness) "succeeds to demonstrate" should read "succeeds in demonstrating"

page 741, paragraph starting with "java provides": (reword for clarity, conciseness, and correctness) "converting values between values of different primitive types" should read "converting between different primitive type values"

page 741, paragraph starting with "You can use": the grammar in this paragraph is incorrect. There should be a period (".") after "float to double", then "You" should be capitalized, and then the semicolon after "1=s" should be a comma.

page 743, paragraph starting with "Java uses": (remove second "all") "all break characters (blanks, tabs, new lines) are all equivalent" should read "all break characters (blanks, tabs, new lines) are equivalent"

page 743, next paragraph: (reword for clarity and correctness)"but may not start with a digit, include / or –." should read "but can neither start with a digit nor include / or –."

page 743, paragraph starting with "Comments": ("specially" is not a word) "specially" should read "specifically"
</strike>

finished chapter on 4 March 2009.

===E An introduction to C# (from material by Benjamin Morandi)===
<strike> p. 742, 4th line from the bottom: "reclaims an object;." --> "reclaims an object."
 -- Stephan 16/2/2009

 p. 743, 2nd line from the top: "No overloading here;" --> "There is no overloading here" or "Destructors may not be overloaded"
 -- Stephan 16/2/2009

 p. 743, Last line of text: "use at your own risk" --> "use them at your own risk"
 -- Stephan 16/2/2009

 p. 744, Get consistency among "One-dimensional array" and "Two dimensional arrays", i.e. use "Two-dimensional array"
 -- Stephan 16/2/2009

 p. 746, There is a black line in the margin next to the top box.
 -- Stephan 16/2/2009

 p. 746, "C [G, H –> T create make end" --> "C [G, H –> T create make end]"
 -- Stephan 16/2/2009

 p. 748, in "do {statements} while (condition)", the first curly brace should be blue.
 -- Stephan 16/2/2009

 p. 748, "Typical causes of exception" --> "Typical causes of exceptions"
 -- Stephan 16/2/2009

 page 756: Title of "INHERITANCE" section should be de-capitalized like in "Inheritance" for consistency with other section titles.
 -- MP 14/2/2009

 p. 757, Just before B.5: "if (exp is T)" --> "if (exp is U)"
 -- Stephan 16/2/2009

 p. 760, "The rest as before ...]" --> "The rest as before ...}"
 -- Stephan 16/2/2009

 p. 761, "returns into an array" --> "returns in an array" or "returns an array of attributes"
 -- Stephan 16/2/2009
</strike>

Corrections by Raphaël Meyer

<strike>
page 746, final line: (formatting) the word "consumers" is surrounded by quotes, but one of them is on the line above. these quotation marks should be on the same line as the word itself.

page 748, paragraph starting with "A member": (modify word "fields" to make it match up with other points in the list) "property (fields equipped" should read "property (field equipped"

</strike>

=== New appendix D - From C++ to C ===

<strike> p. 801 bottom, "compilers, including for Eiffel" --> "compilers, including Eiffel compilers" or "compilers, including ones for Eiffel"
 -- Stephan 18/2/2008</strike>

=== Typos reported by Ernst Leisi (no chapter numbers given) ===
<strike> (Second version [the one with 910 pages])


s. 51 - What this tells us is that the objects our programs manipulate classify              ... sounds kind of strange... the objects our programs
       themselves naturally into certain classes


s. 59 - Line8.i_th (2) is “La_Motte” and so on.                                              ... there is no La_Motte on the picture



s. 61 - Line8.remove_all_remove_all_segments                                                 ... why two times remove_all ?
                   


s. 69 - invariant (where * denotes multiplication:                                           ... missing " ) "



s. 84 - (a = b) or (c and ((not d) = e)))                                                    ... the last " ) " is one too much or there should be one at the beginning ( " ( " )



s. 97 - Line8.i_th (2)).is_exchange                                                           ... " ) " in both examples



s. 98 - mathematicians often use a period “.” or a comma “,”;                                 ... the last ->  "  <-  is not written with normal "style" :O



s.100 - {3, 7, 911, 13, 15}:                               				      ... missing " , " between 9 and 11



s.111 - The first thing we need in our class is a feature representing the line to be built.  ... "We call it (the feature) fancy_line... but the feature is " build_a_line " i guess
        We call it fancy_line.


s.121 - line_exists: s /= Void                                                                ... line_exists: l /= Void



s.125 - instruction as executed by clients is jot just create stop1                           ... jot ? ^^



s.125 - line_exists: s /= Void								      ... line_exists: l /= Void
 


s.128 - 1 • he precondition of its creation procedure.                                        ... missing " T "



s.132 - One immediate question is how > you will you < specify the root class and root creation procedure of a system.



s.134 - This is true of unqualified calls:                                                    ... true for ?



s.136 - made of components to be developed autonomously and combined in may different ways.   ... many



s.141 - 687 + 42 = 29                                                                         ... 729



s.146 - It is the control structure we have been using implicitly in all the examples so far, ... they would be executed    (i guess)
        since we have been writing instructions under the assumption that they would
        executed in the order given.

s.151 - full.extend (metro_1)]                                                                ... " ] "



s.152 - this is true in both its “” and its “”.                                               ... its what?



s.162 - Afterexecution									      ... After execution



s.163 - If you have ever try to use a program only to see it “hang”, it might very            ... tried



s.171 - Of course this convention is not there by accident, but intended                      ... to ensure ?
        precisely ensure that the typical iteration scheme on a list


s.183 - chosen by the programmer, who lets the compiler maps them to memory                   ... lets the compiler map them
        locations.


s.192 - part of the loop, The loop correctness rules                                          ... , T



s.195 - interations                                                                           ... (maybe iteration?)



s.195 - In the discussion of data structures.we will see that it is possible, without         ... " . "  ... " constrol " ... " to to "
	new constrol constructs, to to define powerful iterators applicable to a wide 
	range of object structures.

s.197 - In addition, as yo may have							      ... you



s.199 - The rationale for this policy—which may appear surprising at first—is that a          ... " lists " maybe ?!
	Multi-branch explicitly list a set of expected cases and their desired treatment.


s.208 - The last example of our study of conditionals provide a good case for defining        ... " provides "
	a “functional abstraction” in the form of a routine.
</strike>

=== Comments on the overall text ===
Annie Meyer 6 March 2009:

Page 53. Il manque une ligne noire en bas pour terminer la figure, non?

Page 60. La Motte c'est La Motte-Picquet-Grenelle. Pourquoi est-ce raccourci?

Page 67. La figure n'est pas jolie (la première)  Voir figure parfaites pages 125, 129, 130

Page 112. Figure pas parfaite.

Page 113. Figure pas parfaite.

Page 115. Figure manquante.

Page 117. Figure pas parfaite.

Page 120.  "

Page 122.  "

Page 132. Figure manquante.

Page 135. "

Page 147. Sous la photo de 2005 il y a une date 1976. Il doit manquer quelque chose, non?

Page 155. Figure pas parfaite.

Page 203. Figure pas parfaite.

Page 316. Image manquante.

Page 325. Pourquoi la ligne courbe n'est-elle pas parfaite comme les autres?

Page 390. Figure pas parfaite.

Page 405. Je ne suis pas une fan de tes courbes.

Page 408. that_person.name  la couleur n'est pas bien appliqué.

Page 444. Presque parfaite mais celle de la page 447 est parfaite. Ce sont les mêmes, non?
Celle de la page 451 est parfaite aussi.

Page 491. Toujours les courbes.

Page 500 et 507. "

Page 502. "

Page 505. "

Page 545. Pas parfaites les deux boites.

Page 547. Une figure semble manquer.

Page 557. "

Page 619. C'est normal le petit rond?

Page 637. Courbe à nouveau.

Page 657. Copie d'écran manquante.

Page 708. Quelques paragraphes manquent.

Page 773. Bizarre le grand blanc sous la boite.
Return to Touch of class typos.
Retrieved from "https://dev.eiffel.com/Touch_of_class_typos"
View source for Touch of class typos

Navigation

Development

Wiki

Search

Tools
