TASTE bugtrack - Taste
View Issue Details
0000933Taste[All Projects] Tasteguipublic2020-09-04 08:402021-06-30 13:51
maxime 
ellidiss 
normalminoralways
closedduplicate 
0000933: Raise an error with context parameters have no default value
Otherwise it causes a build error One exception: Timer type, in that case the tool should not require/display a default value, an put 0 by itself in the AADL model
No tags attached.
duplicate of 0000630closed ellidiss Default value shall be mandatory for context parameter 
Issue History
2020-09-04 08:40maximeNew Issue
2020-09-04 08:40maximeStatusnew => assigned
2020-09-04 08:40maximeAssigned To => ellidiss
2020-09-23 14:49ellidissNote Added: 0003739
2020-09-23 15:07maximeNote Added: 0003740
2021-06-30 13:44ellidissNote Added: 0003790
2021-06-30 13:50maximeNote Added: 0003791
2021-06-30 13:51maximeRelationship addedduplicate of 0000630
2021-06-30 13:51maximeNote Added: 0003792
2021-06-30 13:51maximeStatusassigned => closed
2021-06-30 13:51maximeResolutionopen => duplicate

Notes
(0003739)
ellidiss   
2020-09-23 14:49   
the correct default value depends on the datatype chosen i think. The pb is to get the correct default value which can be quite difficult : our dataview parser is far too simplistic to be able to get this value trough a hierarchy of type : * if we have this kind of definition : MyInteger ::= INTEGER (0..255) We can do something, have a map somewhere for all base type and try to take the range into account * for this, it can be tricky (impossible?) with our current parser : MySeq ::= SEQUENCE { a MyInteger, b ENUMERATED { taste(1), welcomes(2), you(3) } } MyChoice ::= CHOICE { a BOOLEAN, b MySeq }
(0003740)
maxime   
2020-09-23 15:07   
Agreed, that's why I suggest to raise an error only if the field is empty. If the type is "Timer", however instead of raising an error, set automatically the value "0" as this parameter is not needed/not used.
(0003790)
ellidiss   
2021-06-30 13:44   
after some research, the default value is already mandatory in the dialog box (the button stay inactive if there is no value ) this was fixed in the 630 ticket . Which are the use cases that allow to have a function with context parameters without a default value?
(0003791)
maxime   
2021-06-30 13:50   
What do you mean? There are no use cases, that's why I want an error message if there is no value set. However since it is implemented (OK button is greyed when there is no value) I think we can close the ticket.
(0003792)
maxime   
2021-06-30 13:51   
Covered by 0000630