-
Notifications
You must be signed in to change notification settings - Fork 108
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
showMessage and related functions use Haskell not C string escaping conventions #45
Comments
I have a fix in the works. |
mikegunter
pushed a commit
to mikegunter/proto-lens
that referenced
this issue
Sep 9, 2016
mikegunter
pushed a commit
to mikegunter/proto-lens
that referenced
this issue
Sep 14, 2016
…ping as Protobuf distribution The Unicode escaping that the Protocol Buffer distribution supports is not implemented for now. Add tests.
judah
pushed a commit
that referenced
this issue
Sep 15, 2016
Merged
Fixed by #46. |
blackgnezdo
added a commit
that referenced
this issue
Aug 17, 2018
The script can now be run with, e.g. `env STACK_RESOLVER=lts-7.3 ci_build/outer_launch_tests.sh` and will use the specified version of the resolver. We can't quite enable this for lts-7.3 as the code is not pedantically clean. We will reconsider when 8.0.2 is available which removes `-Wredundant-constraints` from `-Wall`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
showMessage and the related pprintMessage and showMessageShort functions use the Haskell string escaping conventions instead of the C ones. This means that non-printing characters get written as, e.g. "\SOH", which https://github.com/google/protobuf/blob/master/src/google/protobuf/io/tokenizer.cc#L1039 won't parse. Worse, in Haskell the escape "\101" means decimal 101 whereas the tokenizer.cc code (following C convention) interprets that as octal, i.e. decimal 97.
The text was updated successfully, but these errors were encountered: