User contributions
From CSSEMediaWiki
(Latest | Earliest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
- 02:59, 27 September 2008 (diff | hist) N Quick Reference (New page: (moving content from Exam Quick Reference))
- 06:59, 25 September 2008 (diff | hist) Separation of concerns
- 06:53, 25 September 2008 (diff | hist) N Exam Quick Reference (New page: Note: * The intention of this guide is to be succinct. Don't use this for extended explanation, just note brief points. People can follow links for explanation. * Don't be too specific. ...)
- 06:27, 25 September 2008 (diff | hist) User:RobertLechte
- 04:02, 25 September 2008 (diff | hist) N Avoid becomes (New page: Because inheritance is traditionally viewed as an "IS A" relationship, it's tempting to use it to model changing aspects of code as subclasses, for instance, subclassing Frog into Tadpole ...)
- 03:47, 25 September 2008 (diff | hist) N Beware value switches (New page: Switching of values is bad, boys and girls, because it's not transparent. A typical bad example is: class Bird { int bird_type; const int EAGLE = 1; const int DOVE = 2; const in...)
- 03:17, 25 September 2008 (diff | hist) User:RobertLechte
- 02:55, 25 September 2008 (diff | hist) User:RobertLechte
- 02:23, 25 September 2008 (diff | hist) N Composite (New page: The Composite pattern is useful whenever one has a class which may contain instances of itself. Common computer science examples are nodes in a tree structure, or shapes in a graphical mod...)
- 01:50, 25 September 2008 (diff | hist) User:RobertLechte
- 01:46, 25 September 2008 (diff | hist) User:RobertLechte
- 00:21, 25 September 2008 (diff | hist) Design by contract
- 00:19, 25 September 2008 (diff | hist) User:RobertLechte
- 00:17, 25 September 2008 (diff | hist) N File:Rle41 oo design.jpg (top)
- 06:37, 24 September 2008 (diff | hist) User:RobertLechte
- 06:34, 24 September 2008 (diff | hist) User:RobertLechte
- 02:14, 24 September 2008 (diff | hist) User:RobertLechte
- 01:47, 24 September 2008 (diff | hist) User:RobertLechte
- 00:58, 24 September 2008 (diff | hist) N File:Rle41 original design.jpg (Design Study pic) (top)
- 04:49, 23 September 2008 (diff | hist) N Polymorphism (New page: Polymorphism is merely the ability of subclasses to act as an instance of their superclass or interface, for instance a Car or Boat instance being used as a Vehicle instance, or a Java cla...)
- 11:20, 17 September 2008 (diff | hist) Design by contract
- 11:20, 17 September 2008 (diff | hist) Design by contract
- 11:06, 17 September 2008 (diff | hist) N Design by contract (New page: The "Contract" part of Design by Contract is a metaphor relating real-world contracts. For instance, a Acme Construction may sign a business contract to build a skyscraper, for a price of...)
- 09:27, 20 August 2008 (diff | hist) User:RobertLechte
- 01:12, 20 August 2008 (diff | hist) Monsters design
- 04:51, 19 August 2008 (diff | hist) Monsters design (→Spot the GoF pattern)
- 04:04, 19 August 2008 (diff | hist) User:RobertLechte
- 03:54, 19 August 2008 (diff | hist) User:RobertLechte
- 03:18, 19 August 2008 (diff | hist) Project ideas
- 23:01, 18 August 2008 (diff | hist) N Memento (New page: The Memento pattern is a way to store historical records of the state (or some portion of the state) of an object. A memento can be thought of as a souvenir. Much as a Mickey Mouse soft t...)
- 03:59, 18 August 2008 (diff | hist) N Avoid inheritance for implementation (New page: The core idea here is not to create a subclass merely to access the functionality of the superclass. An example: class Grapher extends DataList Now the Graphing class can use all the fun...)
- 03:40, 18 August 2008 (diff | hist) m Avoid downcasting
- 03:17, 18 August 2008 (diff | hist) N Avoid downcasting (New page: Typically one downcasts when one has a collection of mixed objects of a certain superclass (for instance, several Cars and several Bicycles, and several Trains, all subclasses of Vehicle)....)
- 07:08, 16 August 2008 (diff | hist) N Avoid side effects (New page: A "side effect" in this context is any operation which modifies the program state. Functions should avoid doing this as the function then carries out two inseperable tasks (returning the v...)
- 01:19, 14 August 2008 (diff | hist) N Minimize accesses to variables (New page: The more we can keep our code separate from the underlying data respresentation, the more "abstract" the class is. "Abstract" in this sense means more general, and hence more reusable. J...)
- 00:45, 12 August 2008 (diff | hist) N Separation of concerns (New page: '''Nothing is particularly hard if you divide it into small jobs.''' - Henry Ford Separation of concerns is rather self-explanatory: Each of the different parts/tasks/roles/jobs of a prog...)
- 06:18, 31 July 2008 (diff | hist) Frogs design (→Go export yourself)
- 06:17, 31 July 2008 (diff | hist) Frogs design (→Go export yourself)
- 06:13, 31 July 2008 (diff | hist) Frogs design (→Go export yourself)
- 04:52, 29 July 2008 (diff | hist) User:RobertLechte
- 04:51, 29 July 2008 (diff | hist) Wiki users
- 04:50, 29 July 2008 (diff | hist) N User:RobertLechte (New page: Hi! I'm Robert, and I care about conversations.)
(Latest | Earliest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
