| Summary: | Attribute with initial values | ||
|---|---|---|---|
| Product: | [Modeling] eTrice | Reporter: | Thomas Jung <tj> |
| Component: | Core | Assignee: | Project Inbox <etrice.core-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | hrr, ts |
| Version: | 0.1.0 | Flags: | hrr:
indigo+
|
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | 0.1.0 | ||
|
Description
Thomas Jung
In this context there are several things to be discussed. - data classes could be initialized (in the default constructor) - data class members in data classes and actor classes should be instantiated For the actor class data can be initialized in the top level initial transition. This would be the "state machine way" to do it. Also, we could offer a possibility to init data in the constructor. But as our experience with the precursor tool Trice shows the static initialization per class falls too short. In general data vary from instance to instance and the whole configuration problem has to be solved on the application level. My opinion is that we should add data class initialization but don't offer an initialization mechanism for actor classes. done with ee93b9edd438fb8bf338a927b4ee4e651fcd400f closed resolved bug |