| commit | d8f28e6d19563fc629e2e242e7c4e3cdb7515dcb | [log] [tgz] |
|---|---|---|
| author | Vadim Yanitskiy <axilirator@gmail.com> | Tue Sep 10 18:11:52 2019 +0200 |
| committer | Vadim Yanitskiy <axilirator@gmail.com> | Wed Sep 11 14:04:07 2019 +0200 |
| tree | 66d14aeec30e72360f0253f989a8720ee8c4e599 | |
| parent | e5f4a91576bf979109efba55c053a85819871850 [diff] |
Revert "library/PCUIF_Types.ttcn: inform RAW codec about PADDING in PCUIF_data" This reverts commit dd6d5d1baa62dc9d50fa90ef01fccb8a10284d53. The PADDING seems to be a very experimental feature of TITAN. It works very well for decoding of messages, so the padding bytes are getting recognized as expected, but encoding is broken. Not only the data buffer and its length are encoded in a wrong way, but other fields too. Change-Id: Ieefa61232eb215a19a02e490255332e28e23b8f8