Replies: 1 comment
-
No, the lack of int32 support in Clipper2 has nothing to do with stability, but due to the assuption that most applications are now compiled for 64bit processors where int64 calculations are faster than int32. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
i want to migrate from clipper1 to clipper2. the question is clipper2 is only support int64, but in clipper1 is use int32 for memory. If all int32 are changed to int64, the amount of changes will be very large. Can int32 be added to Clipper2, such as path32 and point32? In this way, the changes will be relatively small. Is the reason why Clipper2 does not support int32 due to stability?
Beta Was this translation helpful? Give feedback.
All reactions