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
Macro Strings are considered as Utf8 by default, but we have no way to know the encoding used.
E.g the Linux POSIX API uses Extended ASCII in their macro strings.
We should add a config to let the user specify the encoding to use.
Perhaps something like this -
macros:
...encoding:
- 'TXIP_.*': ascii # options
We should support these options at very least - ascii, utf8(default).
Another config option could be raw which generates a Uint8List instead of a String.
The text was updated successfully, but these errors were encountered:
* Add example
* Skip methods that have incomplete types
Also change how method return types are parsed
* Update bindings
* Fix overly generic method return types
* Fix tests
* Bit field test
* Fix the bug
* Fix warning wording
* Update bindings
* Remove the need for a dylib
* Update README.md
* Update examples readme
* Nits
* Add test
* Fix analysis error
* Fix more analysis errors
* Fix test
Macro Strings are considered as Utf8 by default, but we have no way to know the encoding used.
E.g the Linux POSIX API uses Extended ASCII in their macro strings.
We should add a config to let the user specify the encoding to use.
Perhaps something like this -
We should support these options at very least -
ascii
,utf8
(default).Another config option could be
raw
which generates aUint8List
instead of a String.The text was updated successfully, but these errors were encountered: