868 reputation
1712
bio website
location
age
visits member for 2 years, 5 months
seen Sep 5 at 7:56

Independent Software Professional:

  • Win32 API
  • Windows internals, Shell Extensions
  • MFC/WPF
  • DirectX/DirectShow/Expression Encoder
  • 3D: WPF 3D, Java 3D, Direct3D, PDF3D

Jun
1
accepted Inheritance vs containment while extending a large legacy project
May
27
awarded  Excavator
May
27
revised Packages organisation with MVC design pattern
typo fixed
May
27
suggested suggested edit on Packages organisation with MVC design pattern
May
27
revised Inheritance vs containment while extending a large legacy project
added 689 characters in body
May
27
comment Inheritance vs containment while extending a large legacy project
Sorry, but it seems you misunderstood my question. I do not inject an existing behavior in my new class, quite vice versa, I am injecting a new behavior into an existing class. Like a Duck that was trained to jump. Then I ask all my Ducks to jump. Those who can - jump. Those who cannot do nothing which is perfectly OK with me.
May
26
revised Inheritance vs containment while extending a large legacy project
added 22 characters in body
May
26
revised Inheritance vs containment while extending a large legacy project
added 47 characters in body
May
26
revised Inheritance vs containment while extending a large legacy project
deleted 6 characters in body
May
26
comment Inheritance vs containment while extending a large legacy project
@gnat edited my question. All new functionality sits inside the ExistingClassExtension class.
May
26
revised Inheritance vs containment while extending a large legacy project
added 195 characters in body
May
26
revised Inheritance vs containment while extending a large legacy project
edited title
May
26
asked Inheritance vs containment while extending a large legacy project
Apr
6
awarded  Yearling
Apr
6
awarded  Yearling
Feb
19
awarded  Caucus
Jan
21
awarded  Booster
Jan
20
awarded  Booster
Jan
19
awarded  Announcer
Jan
19
awarded  Announcer