.net - Combine separate classes to superclass or not? -


i have following class structures

category(mustinherit) 

the following classes inherits category

strongperson weakperson 

then have class

job (mustinherit) 

the following classes inherits job

craft deskjob 

now user can can choose come characteristics , create person (in example craftsman).

sub start()     'person     dim s new strongperson(...)     dim j new craft(...) sub end 

my questions:

  1. i used program procedually , sub start() reminds me lot of it. approach choose one? if not why? better use interfaces , build class person (using multi inheritance)?
  2. since there many more categories , jobs going quite complex categories * job posibilities. doese there exist recommendable design pattern? field of design patterns quite big , read through lot couldnt find apropriate one.


Comments

Popular posts from this blog

PHPMotion implementation - URL based videos (Hosted on separate location) -

javascript - Using Windows Media Player as video fallback for video tag -

c# - Unity IoC Lifetime per HttpRequest for UserStore -