Open dvojtise opened 5 years ago
In addition to correctly deal with these type, we should also consider having a better error message when the trace constructor fails with an unknown type. For example, it could print its name and the name of the attribute/reference that use it.
@ebousse do you think #89 is enough to close this issue or should we also implement for other ecore primitive data types (EShort, EByte, EDate, EBigInteger, ...)
For my simulation (Logo) I need to code some attributes using EDouble in order to have correct precision in the simulation.
When enabling the generic trace addon, it fails with various messages (going from null pointer to 'no null' constraint is violated)
When analysing the error I looked into GenericTraceConstructor class which apparently does not deal with various Ecore primitive type such as EDouble
for example: getGenericValue or addNewObjectToState