topical media & game development

---

[] readme course(s) preface I 1 2 II 3 4 III 5 6 7 IV 8 9 10 V 11 12 afterthought(s) appendix reference(s) example(s) resource(s) _

---

object-oriented programming

This chapter has introduced the idioms and patterns of object-oriented programming. We looked at a polymorphism in Java and C++, and discussed assertions in C++ and canonical class idioms.

---

Polymorphism

1

• inheritance and delegation in Java
• polymorphism in C++
• assertions in C++
• canonical class idioms

---

slide: Section 2.1: Polymorphism

---

In section 2, we proceeded with a fairly detailed discussion of the idioms in hush, which illustrate basic solutions to problems occurring in the development of frameworks.

---

Idioms in hush

2

• the handle/body idiom
• virtual self-reference
• dynamic role switching
• the art of hush programming

---

slide: Section 2.2: Idioms in hush

---

Further, we looked at how these idioms are related to patterns that provide a solution on the level of design.

---

A catalogue of design patterns

3

• creational patterns
• structural patterns
• behavioral patterns

---

slide: Section 2.3: A catalogue of design patterns

---

Following the treatment of idioms and patterns in hush, section 3 gave an overview of the catalogue of design patterns presented in  [GOF94]. The catalogue includes creational, structural and behavioral patterns.

---

Event-driven computation

4

• the Reactor pattern
• abstract event systems

---

slide: Section 2.4: Event-driven computation

---

In section 4, we discussed the reactor pattern, which provides a generalization of event-driven software architectures. We concluded with looking at an example of a simple temperature-monitoring system, implemented using events to maintain internal consistency.

---

[] readme course(s) preface I 1 2 II 3 4 III 5 6 7 IV 8 9 10 V 11 12 afterthought(s) appendix reference(s) example(s) resource(s) _

---

(C) Æliens 04/09/2009

You may not copy or print any of this material without explicit permission of the author or the publisher. In case of other copyright issues, contact the author.