Thanks, I'll check it out.
On Wed, Mar 20, 2019 at 2:23 AM Ian Denhardt wrote:
> This might be more directly what you're after:
>
> https://kaitai.io/
>
> Though disclaimer, I haven't used it myself.
>
> Quoting Wojciech S. Czarnecki (2019-03-19 20:25:08)
> > On Mon, 18 Mar 2019 09:59:59 -07
This might be more directly what you're after:
https://kaitai.io/
Though disclaimer, I haven't used it myself.
Quoting Wojciech S. Czarnecki (2019-03-19 20:25:08)
> On Mon, 18 Mar 2019 09:59:59 -0700 (PDT)
> R Srinivasan wrote:
>
> > my intial attempts to define the data structures have hit
On Mon, 18 Mar 2019 09:59:59 -0700 (PDT)
R Srinivasan wrote:
> my intial attempts to define the data structures have hit a roadblock -
> support for data types such as uint16, int16, uint8, int8. Is this an
> inherent protobuf limitation or am i overlooking something.
Yep. Protobuf is an excha
Yes, the way to think of the topic here is: first, write your own code to
decode the legacy format, then arrange the data in a struct of your design,
and *then* persist the struct or slice of structs using an encode/decode
mechanism of choice, such as gob, protobuf, json, etc.
Step one here is you
On Mon, Mar 18, 2019 at 10:00 AM R Srinivasan wrote:
> i am investigating the use of go+protobuf for reading binary files of a
> legacy design.
>
> my intial attempts to define the data structures have hit a roadblock -
> support for data types such as uint16, int16, uint8, int8. Is this an
> in
