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

Escape NULL terminator in strings with correct glyph #104

Merged
merged 1 commit into from
Nov 16, 2017

Conversation

iv-mexx
Copy link
Contributor

@iv-mexx iv-mexx commented Nov 14, 2017

As discussed in Carthage/Carthage#2252 (comment)

Two questions:

  • The function is currently called escapingWhitespaces. Should we rename it or could NULL be considered a Whitespace?
  • I've used the glyph directly (␀) - is this fine or is it better to use the unicode codepoint? (U+2400)?

@jdhealy

@NachoSoto
Copy link
Contributor

Looks great! I don't have strong opinions on those 2 questions so I'll let others give their input :)

Copy link
Member

@mdiep mdiep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me too.

@ikesyo @jdhealy Any thoughts?

Copy link
Member

@ikesyo ikesyo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

@NachoSoto NachoSoto merged commit f3cd5da into Carthage:master Nov 16, 2017
@jdhealy
Copy link
Member

jdhealy commented Nov 16, 2017

used the glyph directly

I usually favor using the glyph directly — most people would investigate an outputted glyph by copy-pasting into Xcode or github.com search, so good to include it as-glyph in source.

Just merged Carthage/Carthage#2252 which avoids an instance of the incomplete output fixed with this PR.

Thanks for both, and the discovery, and the other work, @iv-mexx 🎉

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.

5 participants