Re: Inheritance hierarchies

"Ashley at Metamaxim" <[email protected]> Tue, 17 Apr 2007 07:58:47 +0100

Newsgroups	gmane.comp.programming.aspect.general
Message-ID	<004501c780bd$d937de40$4001a8c0@Ashley>

Hi

Our research on behavioural aspects suggests that a mixin paradigm is better suited to aspect based modelling than an inheritance hierarchy (see www.metamaxim.com/download/documents/AOSD.pdf ).

I think that the fundamental issue is that aspects are compositional. The inheritance paradigm suits refinement and the mixin paradigm suits composition.

Best regards
Ashley
  ----- Original Message ----- 
  From: Donisthorpe C (AT) 
  To: [email protected] 
  Sent: Monday, April 16, 2007 4:16 PM
  Subject: [aosd-discuss] Inheritance hierarchies


  Hi

  I think system aspects can adversley impact software design by creating unique inheritance hierarchies from original crosscuts.  This effect could originate from system-level crosscut influences and contaminate the lower-level software design.

  Q. Under these circumstances, how does EA analysis cater for system level aspects? 



  Regards

  Charles



------------------------------------------------------------------------------


  _______________________________________________
  discuss mailing list    -    [email protected]

  To unsubscribe and change options, go to:
  http://aosd.net/mailman/listinfo/discuss_aosd.net

  Check out the AOSD.net Wiki: http://aosd.net/wiki

_______________________________________________
discuss mailing list    -    [email protected]

To unsubscribe and change options, go to:
http://aosd.net/mailman/listinfo/discuss_aosd.net

Check out the AOSD.net Wiki: http://aosd.net/wiki