RE: facet-oriented programming

What I'm interested in is change of design. When we change the design of a module, some parts of several classes must change together, that just like a facet.

Design always changes, and if the new design not work, we want change back, if just part of it works, we want keep the good part. We need to manage the change, as smooth as posible, 

In the view of managing change, all programs are facet-oriented.

> Date: Sun, 9 Nov 2014 08:44:56 +0100
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: facet-oriented programming
> 
> Excerpts from 郭雪松's message of 2014-11-09 06:06:07 +0100:
> > I remember some of you wrote a paper about facet-oriented programming, I
> > cannot find it. Can anybody send it to me ?
> 
> http://pike.lysator.liu.se/docs/docs/MikaelAmborn_Facet_Thesis.pdf
> 
> i have read the paper some time ago, and found that it's mainly useful to
> enforce implementation of certain classes and class relationships.
> 
> i guess it helps reasoning about the code, like if you know a facet, and see a
> class that implements that facet then you can assume certain things without
> checking the whole inheritance tree.
> 
> i didn't see it helping in writing any less code, and i guess that is part of
> why it didn't get used more.
> 
> i am curious how your work relates to facets, and what you are trying to achieve.
> 
> greetings, martin.
> 
> -- 
> eKita                   -   the online platform for your entire academic life
> -- 
> chief engineer                                                       eKita.co
> pike programmer      pike.lysator.liu.se    caudium.net     societyserver.org
> BLUG secretary                                                 beijinglug.org
> foresight developer  foresightlinux.org                            realss.com
> unix sysadmin
> Martin Bähr          working in china        http://societyserver.org/mbaehr/
>