Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

integer precision warnings #73

Closed
incanus opened this issue Feb 19, 2014 · 3 comments
Closed

integer precision warnings #73

incanus opened this issue Feb 19, 2014 · 3 comments

Comments

@incanus
Copy link
Contributor

incanus commented Feb 19, 2014

Xcode generates a lot of integer precision warnings related (mostly) to size_t return types vs. int32_t assignments:

screen shot 2014-02-19 at 12 03 07 pm

Should we be worried about this? What's the rationale for use of int32_t and how does it impact other platforms?

@springmeyer
Copy link
Contributor

definitely worth fixing but not likely anything to worry about.

@incanus
Copy link
Contributor Author

incanus commented Feb 19, 2014

Yeah, clearly works but I'm in with the Objective-C community habit of getting rid of all warnings on build with Xcode.

Low priority.

@kkaefer
Copy link
Member

kkaefer commented Mar 4, 2014

I think I fixed those errors in our code. There are still a few in libtess2, but I'm not going to modify that code.

@kkaefer kkaefer closed this as completed Mar 4, 2014
acalcutt pushed a commit to acalcutt/mapbox-gl-native that referenced this issue Apr 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants