Library mechanism for components
Especially in the component-based descriptions in mode-diagrams, it
makes no sense to define the basic components (like sum, mult,
>/<, switch, etc) anew for each instance. Here a library-mechanism
as in Simulink is absolutely necessary for applicability of AF3. In a
first version, a instance-concept (application of the library via
instantiation leads to copy) is absolutely sufficient.
If it is not possible to introduce user-defined libraries, at least a
pre-defined library is necessary.
(from redmine: issue id 694, created on 2012-03-05, closed on 2013-01-24)
- Relations:
- child #1155 (closed)
- child #1156 (closed)
- child #1179 (closed)