Xcode 14.2 "new" warnings: Implicit conversion loses integer precision (int to long)

[melcher....@googlemail.com]

Since I updated Xcode, I get 116 warning for Implicit conversion loses integer precision. Since the other platforms do not get these warning, I'd like to ask for the right procedure: I can verify and add 166 casts from `int` to `long`, or I can disable this particular warning for CMake/Xcode. 

Any opinions?

Xcode 14.2 (clang 14.0.0 for arm64-apple-darwin22.1.0, CMake default settings, Xcode build environment)

[Bill Spitzak]

Since when does casting int to long lose precision????

--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/fe85cdea-f2c4-4a61-a00d-1417fc738708n%40googlegroups.com.

[Manolo]

Le mercredi 21 décembre 2022 à 21:40:34 UTC+1, spi...@gmail.com a écrit :

Since when does casting int to long lose precision????

That's because these are casts from long to int, really.

[melcher....@googlemail.com]

Thanks Manolo, yes, long to int, not the other way around.

[Manolo]

Le mercredi 21 décembre 2022 à 21:21:29 UTC+1, Matthias a écrit :

Since I updated Xcode, I get 116 warning for Implicit conversion loses integer precision. Since the other platforms do not get these warning, I'd like to ask for the right procedure: I can verify and add 166 casts from `int` to `long`, or I can disable this particular warning for CMake/Xcode. 

Any opinions?

This looks like the ideal situation to show the usefulness of our new CMP rule allowing static_cast (or whatever it's called).

[imm]

On Thu, 22 Dec 2022, 09:42 Manolo wrote:

This looks like the ideal situation to show the usefulness of our new CMP rule allowing static_cast (or whatever it's called).

A simple "long" to "int" cast should be a static_cast, it doesn't need anything fancier.

The generated compiler output should be identical, we're simply telling the compiler that it's as intended.

--
Ian
From my Fairphone FP3
  

[Bill Spitzak]

I agree, just use long(x) or (long)(x) there is no need for the c++ syntax for such simple things.

--

You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/CAGFM6da7-ca9aDaDn6p_0kmqZa0fZCs15KVHEtQ0W34z2QcKvw%40mail.gmail.com.