Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rfl::yaml::read<uint8_t> is parsed as a character instead of a number #270

Open
lhruby opened this issue Nov 20, 2024 · 1 comment
Open

Comments

@lhruby
Copy link

lhruby commented Nov 20, 2024

When parsing a uint8_t as a yaml using rfl::yaml::write, the value is correctly parsed as dummy_uint8_t=48. Note, 48 is the ASCII code for '0'.

Reading the value back using rfl::yaml::read<uint8_t> does however yield dummy_uint8_t=0, as 48 is now interpreted as a character instead of a number.

@liuzicheng1987
Copy link
Contributor

Interesting, thanks for pointing it out. I will take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants