Skip to content

Commit 8a8cade

Browse files
committed
Fix #259.
1 parent 4b1821f commit 8a8cade

File tree

3 files changed

+11
-10
lines changed

3 files changed

+11
-10
lines changed

book/observer.markdown

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -83,11 +83,11 @@ entirely decoupled. But in architecture, we're most often trying to make systems
8383
</aside>
8484

8585
The achievement system registers itself so that whenever the physics code sends
86-
a notification, the achievement receives it. It can then check to see if the
87-
falling body is our less-than-graceful hero, and if his perch prior to this new,
88-
unpleasant encounter with classical mechanics was a bridge. If so, it unlocks
89-
the proper achievement with associated fireworks and fanfare, and it does all of
90-
this with no involvement from the physics code.
86+
a notification, the achievement system receives it. It can then check to see if
87+
the falling body is our less-than-graceful hero, and if his perch prior to this
88+
new, unpleasant encounter with classical mechanics was a bridge. If so, it
89+
unlocks the proper achievement with associated fireworks and fanfare, and it
90+
does all of this with no involvement from the physics code.
9191

9292
<span name="tear">In fact</span>, we can change the set of achievements or tear
9393
out the entire achievement system without touching a line of the physics engine.

html/observer.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -102,11 +102,11 @@ <h2><a href="#achievement-unlocked" name="achievement-unlocked">Achievement Unlo
102102
</aside>
103103

104104
<p>The achievement system registers itself so that whenever the physics code sends
105-
a notification, the achievement receives it. It can then check to see if the
106-
falling body is our less-than-graceful hero, and if his perch prior to this new,
107-
unpleasant encounter with classical mechanics was a bridge. If so, it unlocks
108-
the proper achievement with associated fireworks and fanfare, and it does all of
109-
this with no involvement from the physics code.</p>
105+
a notification, the achievement system receives it. It can then check to see if
106+
the falling body is our less-than-graceful hero, and if his perch prior to this
107+
new, unpleasant encounter with classical mechanics was a bridge. If so, it
108+
unlocks the proper achievement with associated fireworks and fanfare, and it
109+
does all of this with no involvement from the physics code.</p>
110110
<p><span name="tear">In fact</span>, we can change the set of achievements or tear
111111
out the entire achievement system without touching a line of the physics engine.
112112
It will still send out its notifications, oblivious to the fact that nothing is

note/log.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
2014-08-17 - fix #252
12
2014-08-16 - merge object pool changes
23
2014-08-15 - email, set up group for translators
34
2014-08-14 - finish dirty flag, renumber front matter

0 commit comments

Comments
 (0)