Re: Aspect Modelling and wide interfaces

Richard MacDonald wrote:
> Note: I'm basing this on the standard OO idea of making the client
> interfaces simple, meaning the complexity has to be moved "inside" the
> object. So internal behavior is much more complicated than external
> behavior.

Agree on the external interfaces, but I also want to isolate facets internally in the same way superclass/subclass behaviour can be separated.  

> Well, post away.

Ok, I'll start, but before I do, I had intended to publish some working tools and examples on a new website (I registered aspectdesign.org), but I'm waiting on an IP disclaimer from my work before publishing code. Anyhow, I put together the attached little diatribe for the front page of the site, as a quick intro to what I'm getting at. I have implemented a data definition language called ADL - Aspect Definition Language - in Ruby, but it has no procedural content. My initial goal was to generate SQL schemas and data management API code, documentation and test cases in various languages before looking at procedural extensions to ADL or aspect oriented extensions to some other language.

--
Clifford Heath





application/octet-stream attachment: aspectdesign.txt