Closed philip-alldredge closed 11 years ago
Commit 2c7a9526da should correct this bug. May you please try it? Thanks
Not quite. It doesn't look like the component type is actually renamed. If I try to create an implementation or a subcomponent with it, it does not work. I've modified my test case to reproduce is:
Output:
test_renames_a.aadl:13:01: Test_B.impl (component implementation) implements a component type that does not exist
Cannot analyze AADL specifications
test_renamed_a.aadl
package test_renames_a
public
with test_renames_b;
Test_B renames system test_renames_b::B;
system A
end A;
system implementation A.impl
subcomponents
b1: system Test_B;
end A.impl;
system implementation Test_B.impl
end Test_B.impl;
end test_renames_a;
test_renames_b.aadl
package test_renames_b
public
system B
end B;
end test_renames_b;
OK, I must also update Ocarina to support legality rule 4.4 (N1)
Testcase is now validated. If there is a similar issue, please open a separate ticket with a specific test case.
Ocarina produces an error for models that have an alias declaration renaming a component type.
Error:
test_renames_a.aadl:
test_renames_b.aadl