- In the bridging header, I often use
uint
. This does not now compile, as the module isn’t included. Changeuint
touint32_t
.
2 Likes
[quote=“caroline, post:1, topic:205221”] ed fin
In the bridging header, I often use uint
. This does not now compile, as the module isn’t included. Change uint
to uint32_t
.
[/quote]
It’s quite common to encounter issues with uint not being recognized in certain contexts, especially when working with Swift and Objective-C interoperability. While uint may work in some cases, it’s not guaranteed to be available, and it’s often safer to use the more explicitly defined uint32_t from stdint.h when working with C-based libraries. Changing uint to uint32_t ensures that your code is more portable and avoids potential issues across different platforms or environments where the definition of uint might vary.
1 Like