The more I use binarylang the more I like it, there's no way back now :)
I have to deal with fields that are not supported out of the box by binarylang and requires further processing after decoding, so I'm ending up writing some operations, like reading strings containing hex encoded bytes in little-endian order into integers
in binarylang open for contributions in this direction, to cover more common cases like this, or is it intended to stay lean and clean and let users provide their own ops?
Thank you for using binarylang! The answer to your question is "both". You should make an MR with your template definitions. They will become part of the binarylang template library.
The more I use binarylang the more I like it, there's no way back now :)
I have to deal with fields that are not supported out of the box by binarylang and requires further processing after decoding, so I'm ending up writing some operations, like reading strings containing hex encoded bytes in little-endian order into integers
for example for uint8 and uint16
in binarylang open for contributions in this direction, to cover more common cases like this, or is it intended to stay lean and clean and let users provide their own ops?
thanks