<div dir="ltr">Thanks! ...that muddies the water for me more. :)<div><div><br></div><div>Who are the users of these platform conditionals? I would assume most likely folks that are interfacing swift code with C code? In side of the Swift "sandbox" you should be isolated otherwise, right?</div><div><br></div><div>If that is the case then the width of various C types change depending on OS/OS variant, CPU architecture and potentially other factors. It seems like conditional evaluating the size of given standard C type may be needed?</div><div><br></div><div>bitwidth(cptr: 32/64)</div><div>bitwidth(cint: 32/64)</div><div>bitwidth(clong: 32/64)</div><div>bitwidth(cdouble: 32/64)</div><div>etc.</div><div><br></div><div>-Shawn</div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Mar 15, 2016 at 1:15 PM William Dillon <<a href="mailto:william@housedillon.com">william@housedillon.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Here’s an example of the kind of thing that’s common: <a href="https://github.com/apple/swift-corelibs-foundation/pull/264/files#r53730929" target="_blank">22 days ago</a></div><div>There’s another good one in NSRange: <a href="https://github.com/apple/swift-corelibs-foundation/blob/master/Foundation/NSRange.swift#L90-L94" target="_blank">https://github.com/apple/swift-corelibs-foundation/blob/master/Foundation/NSRange.swift#L90-L94</a></div><div>There are FAR too many to list in stdlib, runtime, and (compiler) tests.</div><div><br></div><div>- Will</div></div><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Mar 15, 2016, at 10:06 AM, Shawn Erickson <<a href="mailto:shawnce@gmail.com" target="_blank">shawnce@gmail.com</a>> wrote:</div><br><div><div dir="ltr">On Tue, Mar 15, 2016 at 9:51 AM William Dillon <<a href="mailto:william@housedillon.com" target="_blank">william@housedillon.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The vast majority of special cases I’ve seen and written are due to the size of Int, not a pointer per se. To clear up the confusion, how about we rename bitwidth to intwidth or intsize?<br>
<br>
- Will<br>
<br>
> On Mar 15, 2016, at 9:40 AM, Shawn Erickson via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> I guess the fuzziness in my mind is when considering LP64, LLP64, etc. I believe swift attempts to avoid that by defining either 32 bit or 64 bit model. If that is universally the case then I think bitwidth is fine. If not then pointerwidth may be more correct. Those bridging to C would have to consider information from the C world to deal with the variations of type size based on platform and 32/64.<br></blockquote><div><br></div><div>I am curious to see some examples of checking Int size to better understand the situation.</div><div><br></div><div>-Shawn</div><div> </div></div></div>
</div></blockquote></div><br></div></blockquote></div></div></div></div>