-
Notifications
You must be signed in to change notification settings - Fork 163
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
strings that contain null characters #4120
Comments
I tend to classify it as a bug resp. a limitation of how printing was done for a long time in GAP -- but actually some changes we made in the last year or so should allow us to fix it! In a nutshell, the C function The simplest fix would be to change it to query the string length in both cases -- while this leads to a performance regression when printing C strings, reality is that those are almost always very short, meaning that the extra call to |
I'm not sure if this should be considered as a bug. Is it really sensible to print strings with 0-characters? Of course, you can always write arbitrary byte sequences to your terminal (or other file) with
|
Just for the sake of a cross-reference: The origin of the issue is oscar-system/GAP.jl/issues/527. |
So, |
Meanwhile
|
@nskeip no not at all, it works just fine here. Just the printing code gets "confused". |
see the source here: gap-system#4120 (comment)
@fingolfin hey, I tried to fix it in #5546 - can you check out and give a feedback on how it should behave? (skip NULLs or print someting?) |
The following happens in released versions of GAP and in the current master branch.
Is this a bug or a feature?
(In the latter case, it should become documented.)
The text was updated successfully, but these errors were encountered: