Guh, not function arguments, but not constants either… anyways, I don’t have a problem if someone does fix these but it can be a nuisance.
From: Allegro-developers [mailto:[email protected]] On Behalf Of Trent Gamblin Sent: December 2, 2015 8:36 PM To: 'Elias Pschernig' <[email protected]>; [email protected] Subject: Re: [AD] allegro (image addon) build on 64-bit windows Actually it’s not exactly like that. It’s function arguments. You can’t pass an int to a fuction that takes a float or you get: C:\Users\Trent\code\Nooskewl_Engine\src\Nooskewl_Engine\map_entity.cpp(770): warning C4244: 'argument' : conversion from 'int' to 'float', possible loss of data Here it is on MSDN https://msdn.microsoft.com/en-us/library/th7a07tz.aspx From: Allegro-developers [mailto:[email protected]] On Behalf Of Trent Gamblin Sent: December 2, 2015 8:18 PM To: 'Elias Pschernig' <[email protected] <mailto:[email protected]> >; [email protected] <mailto:[email protected]> Subject: Re: [AD] allegro (image addon) build on 64-bit windows I think it might be better to set the error level a little lower if possible. I fixed all the warnings in one of my games, and I found out that some of them from MSVC are crazy… even Microsoft itself says they’re a nuisance. Such as: int i = 0; float f = i; or float f = 1; Is a warning of a “dangerous” cast from int to float… fixing them can really be ugly. I kind of regret that I did because now I have to fix every new one and it’s very common. From: Allegro-developers [mailto:[email protected]] On Behalf Of Elias Pschernig Sent: December 2, 2015 2:29 PM To: [email protected] <mailto:[email protected]> Subject: Re: [AD] allegro (image addon) build on 64-bit windows On Wed, Dec 2, 2015 at 3:50 PM, Peter Hull <[email protected] <mailto:[email protected]> > wrote: Also there are a lot of warnings when compiling 64-bit*, most of which AFAICS are benign. Unfortunately CMake spews such a lot on to the screen and cmd.exe is so poor at keeping scrollback history, it might well be there's something significant there. Is there any plan to address these warnings? I can have a look; there are a few on OS X too which might be the same ones. Pete *. quite a few on 32-bit too but I think CMake sets warning level 4 which is a bit OTT! In general I think it would be best to have zero warnings - like we have with gcc (on both 32 and 64 bit). I think in Linux clang warned about a few things gcc would not and they all were good things to fix, so it might be the same with MSVC. Now I wonder if there's a way to have mingw64 use clang instead of gcc...
_______________________________________________ Allegro-developers mailing list [email protected] https://mail.gna.org/listinfo/allegro-developers
