On Tue, 26 Apr 2005, Aaron Sherman wrote:

It also might be useful for roles to be able to delete members and
methods from a class like so:

        role foo {
                has $.x;
                has not $.y;

But that brings up the issue of who has the final authority. In class composition, a method defined in the class hides those in the roles, and in this sense it is the boss on "adding decisions". I like this a lot because I think it makes it possible for me to read a class description and have a sense of what is going on. With the "has not" proposal, it seems that the role would need to be the boss on "deleting decisions". Could get pretty confusing!


Abhijit Mahabal http://www.cs.indiana.edu/~amahabal/

Reply via email to