Skip to content

Conversation

@FLHerne
Copy link
Contributor

@FLHerne FLHerne commented Oct 31, 2020

Unfinished, but does this look sane?

See changes in regression/expected.

@glx22
Copy link
Contributor

glx22 commented Nov 1, 2020

Changes in regression/expected are correct. I like how ASCII values are printed, but full numerical values looked better with dxXXXXXXXX

@FLHerne
Copy link
Contributor Author

FLHerne commented Nov 1, 2020

Changes in regression/expected are correct. I like how ASCII values are printed, but full numerical values looked better with dxXXXXXXXX

You mean the ones like "\12\34\56\78"? That's where the input NML happened to use all escaped bytes in a string-literal, e.g. in this case

// also override some other grf, this time not setting our own grfid explicitly
engine_override("\12\34\56\78");

I think this is probably helpful because it makes it clearer where the value came from, and that adding some heuristic would be confusing.

This should never affect numeric values that weren't strings in the source code.

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

Successfully merging this pull request may close these issues.

2 participants