library/GSM_RR_Types: remove misleading PADDING attributes
Unfortunately, TITAN has a weird (and often unusable) model of
defining padding in records. According to its reference guide,
padding length is counted from the beginning of the message.
So if the 'MeasurementResults' is a part of another record, and
there are other fields preceeding it, the encoded representation
of the 'MeasurementResults' may still be shorter than 16 octets.
Change-Id: Ia1c87ae85ee402369dad0dfd81159f179095c8d2
diff --git a/library/GSM_RR_Types.ttcn b/library/GSM_RR_Types.ttcn
index f7b00e1..f45784c 100644
--- a/library/GSM_RR_Types.ttcn
+++ b/library/GSM_RR_Types.ttcn
@@ -650,8 +650,7 @@
NcellReports ncell_reports optional
} with { variant (no_ncell_m) "LENGTHTO(ncell_reports)"
variant (no_ncell_m) "UNIT(elements)"
- variant "PADDING(yes)"
- variant "FIELDLENGTH(16)"
+ /* FIXME: pad to 16 octets */
};
type record NcellReport {