22 Aug
2012
22 Aug
'12
2:09 p.m.
Right now, we have
FAMIXException>>exceptionClass
<MSEProperty: #exceptionClass type: #FAMIXClass>
^ exceptionClass
And then we have three subclasses: FAMIXCaughtException,
FAMIXDeclaredException, FAMIXThrownException.
At the moment, exceptionClass does not have an opposite, but we should
add one. Like this we would know if a class is caught, declared or
thrown. But, to know that we would need define three properties in
FAMIXClass, and to redefine the exceptionClass in the three subclasses
of FAMIXException such that the declaration points the opposite to the
right FAMIXClass property.
So something like:
FAMIXDeclaredException>>exceptionClass
<MSEProperty: #exceptionClass type: #FAMIXClass opposite:
#exceptionsWithClassAsDeclared>
...
FAMIXClass>>exceptionsWithDeclaredClass
<MSEProperty: #exceptionsWithClassAsDeclared type:
#FAMIXDeclaredException opposite: #exceptionClass>
...
Cheers,
Doru
On Wed, Aug 22, 2012 at 12:57 PM, Stéphane Ducasse
<stephane.ducasse(a)inria.fr> wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
This
would also imply that we would define the implementation of
exceptionClass in all subclasses of Exception.
what do you mean by that sentence because I could not get it clear enough.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev