int and uint changes #470
Replies: 2 comments 1 reply
-
|
Hi, Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
Look, I have to admit, I've struggled to decide which is best myself. I asked about the use of uint in the Dx channel. TBH I wasn't that impressed with the response - I mean, what they said is fine, but it's just so subjective. However. Making it compatible with Dx I suppose is fine. I'd like to hear from others who have much larger code bases than mine or who are more experiences. You are certainly a better programmer than me, your grasp of native is much stronger. So, I will follower your lead. But there may be some things we can do to make it go smoother. For example, make sure that all the interactive types use uint as well. For example... IWICBitmapSource uses uint in Dx, but Vortice returns a SizeI (integer type). If those cases are covered, maybe the error count could be reduce. There's probably no getting around the mess that is created by the change. I just have to go through and decide case by case what to do. |
Beta Was this translation helpful? Give feedback.
-
|
My Vortice program and my coding experienceis are both not large but I did the conversion in 2 hours work. I was using -1 as significative value so I had to change strategy. |
Beta Was this translation helpful? Give feedback.
-
I'm getting hundreds of errors due to some changes with methods asking for uint now and not being compatible with various code that interacts with them. For example...
IWICBitmapSourceSize.Width - integer
But PixelFormat.GetStride(Guid guid, uint width)
Was this change intentional? Usually, integer is selected for its broad compatibility, even though uint might make more sense as a container for valid values.
Or are we just expect to go through and type (uint) hundreds of times? (225 for me). And even making a few changes, It has ballooned out to 300. This is a nightmare.
What's the rationale in using int or uint in any situation?
Beta Was this translation helpful? Give feedback.
All reactions