Anonymous | Login | Signup for a new account | 2021-01-21 08:07 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000933 | Taste | [All Projects] Tastegui | public | 2020-09-04 08:40 | 2020-09-23 15:07 | ||||||
Reporter | maxime | ||||||||||
Assigned To | ellidiss | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Summary | 0000933: Raise an error with context parameters have no default value | ||||||||||
Description | 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 | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|
(0003739) ellidiss (developer) 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 : We can do something, have a map somewhere for all base type and try to take the range into account
MyChoice ::= CHOICE { |
(0003740) maxime (administrator) 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. |
![]() |
|||
Date Modified | Username | Field | Change |
2020-09-04 08:40 | maxime | New Issue | |
2020-09-04 08:40 | maxime | Status |
new => assigned |
2020-09-04 08:40 | maxime | Assigned To |
=> ellidiss |
2020-09-23 14:49 | ellidiss | Note Added: 0003739 | |
2020-09-23 15:07 | maxime | Note Added: 0003740 |
Copyright © 2000 - 2011 MantisBT Group |