|
Hi,
I am discovering TopCaseD, and I think I found a
problem with the extend functionality in AADL diagram:
- in the graphical composition it is possible to
make a cyclic inheritance with a least 2 implementations (then eclipse crash
with a stack overflow)
- in the property panel it is event possible to
make an implementation to extend itself (then eclipse crash with a stack
overflow)
After the crash the workspace can be reopened and
crash only if you try to enter one of the faulty implementation (when TopCaseD
try to process the inheritance diagram).
In the OSATE perspective, their is an error message
on the AAXL because of the cycle of 2 or more implementations. No message in
case of implementation inheriting from itself.
regards,
Arnaud Schach
|
_______________________________________________ Topcased-mm-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-mm-users
