You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possibly. It feels more logical to transfer data using big-endianness, but some projects may have little-endian data that needs to be parsed. In those cases, this library cannot be used.
Solution
Just like #10, a custom parser may be created with configuration the currently package-level functions bound to it.
Alternatives
Currently, there is a private variable called parser that holds the ByteOrder used by the library. Allowing changes to this variable through a setter function would be the quickest fix. Also see #10 for caveats with multiple parsers with different configuration.
The text was updated successfully, but these errors were encountered:
Is the feature related to a problem?
Possibly. It feels more logical to transfer data using big-endianness, but some projects may have little-endian data that needs to be parsed. In those cases, this library cannot be used.
Solution
Just like #10, a custom parser may be created with configuration the currently package-level functions bound to it.
Alternatives
Currently, there is a private variable called
parser
that holds theByteOrder
used by the library. Allowing changes to this variable through a setter function would be the quickest fix. Also see #10 for caveats with multiple parsers with different configuration.The text was updated successfully, but these errors were encountered: