Timeline for Understanding the bridge design pattern
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Nov 23, 2019 at 7:15 | history | edited | doubleYou | CC BY-SA 4.0 |
fixed spelling and grammar
|
S Nov 23, 2019 at 7:15 | history | suggested | V. S. | CC BY-SA 4.0 |
fixed spelling and grammar
|
Nov 22, 2019 at 21:44 | review | Suggested edits | |||
S Nov 23, 2019 at 7:15 | |||||
Jun 12, 2017 at 2:43 | comment | added | wangdq | This line "the two different abstractions, train transport and acceleration" helps, point out what is the two hierarchies and what we try to solve is to make them vary independently. | |
S Sep 3, 2016 at 5:44 | history | suggested | ErikE | CC BY-SA 3.0 |
Spelling and comment syntax--attempted to make no changes to personal style, only changes for comprehension and clarity
|
Sep 2, 2016 at 22:29 | comment | added | ErikE |
For what it's worth, I think it should be Monorail since it's not really two words, it's a single (compound) word. A MonoRail would be some subclass of Rail instead of a different kind of rail (which it is). Just like we wouldn't use SunShine or CupCake , they would be Sunshine and Cupcake
|
|
Sep 2, 2016 at 22:27 | review | Suggested edits | |||
S Sep 3, 2016 at 5:44 | |||||
Nov 13, 2013 at 5:22 | comment | added | zzfima | Very nice example. I would add my two cents: this is very good example of preferring composition over inheritance | |
Dec 10, 2011 at 17:16 | history | answered | Thurein | CC BY-SA 3.0 |