Bad assignment for records with optional fields
Submitted by Ãkos Buzás
Link to original bug (#537328)
Description
The 'empty'/'{}' assignment is not correct for record only with optional fields: the value is always unbound instead of being bound.
TITAN Product number: CRL 113 200/5 R5A
Example:
... type record r { integer f1 optional, integer f2 optional } ...
var r e1 := {}; ...
value of 'e1' is <unbound>
instead of {f1 := <unbound>
, f2 := <unbound>
}