This issue was copied from the upstream repository google/emboss.
Original issue: google#22
Original state: closed, created at: 2021-12-06T21:54:12Z, updated at: 2022-04-05T21:00:14Z, by @fsareshwala
Original description
Emboss supports overlapping fields; fat fingering an incorrect offset is completely valid but an easy mistake to make. It would be nice to be able to have syntax to simply say that this field is placed directly after the previously defined one.
Potential Implementation
The .emb language syntax is updated to indicate a field should be placed directly after the previous one. The generated C++ code follows this guidance and computes the offset of a field automatically. Overlapping field syntax is retained for backwards compatibility.
This issue was copied from the upstream repository
google/emboss.Original issue: google#22
Original state: closed, created at: 2021-12-06T21:54:12Z, updated at: 2022-04-05T21:00:14Z, by @fsareshwala
Original description
Emboss supports overlapping fields; fat fingering an incorrect offset is completely valid but an easy mistake to make. It would be nice to be able to have syntax to simply say that this field is placed directly after the previously defined one.
Potential Implementation
The .emb language syntax is updated to indicate a field should be placed directly after the previous one. The generated C++ code follows this guidance and computes the offset of a field automatically. Overlapping field syntax is retained for backwards compatibility.