Skip to content
New issue

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

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

Already on GitHub? # to your account

Use bool instead of _Bool (may cause compilation error for Objective-C++ code) #69

Merged
merged 1 commit into from
May 21, 2014

Conversation

nickynick
Copy link
Contributor

Apparently, Objective-C++ code may have troubles with understanding _Bool type. I guess it has something to do with <stdbool.h> not being included. Or maybe not. Anyway, I believe it should be fine to just use bool instead. It's not like all this makes much sense for Masonry, but still.

I also moved float and double a bit higher because they do make sense for us :)

@cloudkite
Copy link
Contributor

thanks :)

cloudkite added a commit that referenced this pull request May 21, 2014
Use bool instead of _Bool (may cause compilation error for Objective-C++ code)
@cloudkite cloudkite merged commit 198622e into SnapKit:master May 21, 2014
@nickynick
Copy link
Contributor Author

@cloudkite Perhaps this might be worthy of a new tag (0.5.1)? Because it leads to compilation error for some people.

@nickynick nickynick deleted the bool-fix branch May 21, 2014 10:21
@cloudkite
Copy link
Contributor

@nickynick yup just waiting on cocoapods trunk, which is coming end of this week apparently https://twitter.com/CocoaPods/statuses/469170830048759810

@nickynick
Copy link
Contributor Author

Yeah, it's a bit of a bummer, I was just about to submit a new pod :)

@cloudkite
Copy link
Contributor

pushed to trunk ;)

dan-rodrigues pushed a commit to dan-rodrigues/Masonry that referenced this pull request Oct 18, 2014
Use bool instead of _Bool (may cause compilation error for Objective-C++ code)
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants