Composition instead of inheritance
Ben Finney
ben+python at benfinney.id.au
Thu Apr 28 23:44:11 EDT 2011
More information about the Python-list mailing list
Thu Apr 28 23:44:11 EDT 2011
- Previous message (by thread): Composition instead of inheritance
- Next message (by thread): Composition instead of inheritance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ethan Furman <ethan at stoneleaf.us> writes: > Carl Banks wrote: > > That's not what we mean by composition. Composition is when one > > object calls upon another object that it owns to implement some of > > its behavior. Often used to model a part/whole relationship, hence > > the name. > > Hmmm. Okay -- any ideas for a better term? Something that describes > taking different source classes and fusing them into a new whole, > possibly using single-inheritance... Frankenstein, maybe? ;) (Remember that Frankenstein was not the monster, but the scientist.) “Hybrid”? -- \ “If sharing a thing in no way diminishes it, it is not rightly | `\ owned if it is not shared.” —Augustine of Hippo (354–430 CE) | _o__) | Ben Finney
- Previous message (by thread): Composition instead of inheritance
- Next message (by thread): Composition instead of inheritance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list