You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As one can see from Xcode's GUI for editing .xcdatamodel files, Core Data supports signed 16, 32, and 64 bit integers for attributes types. In turn, mogenerator creates accessors that return scalars for these attributes. The types returned are: short, int, and long long. These are correct for the current Mac OS ABI.
However, it would be even more correct to return int16_t, int32_t, and int64_t instead.
We once tried to make this change, but it was tricker than I thought because IIRC it assumed that there are NSNumber methods named Value, like 'shortValue' but there is no int16_tValue method.
The text was updated successfully, but these errors were encountered:
[NEW] Better return value types: `int16_t`/`int32_t`/`int64_t` instead of `short`/`long`/`long long` and `id` instead of `NSObject*`. closesrentzsch#2, rentzsch#85 (Rob Rix)
As one can see from Xcode's GUI for editing .xcdatamodel files, Core Data supports signed 16, 32, and 64 bit integers for attributes types. In turn, mogenerator creates accessors that return scalars for these attributes. The types returned are: short, int, and long long. These are correct for the current Mac OS ABI.
However, it would be even more correct to return int16_t, int32_t, and int64_t instead.
We once tried to make this change, but it was tricker than I thought because IIRC it assumed that there are NSNumber methods named Value, like 'shortValue' but there is no int16_tValue method.
The text was updated successfully, but these errors were encountered: