Ok, now I understand what the warning is supposed to say (I didn't realize that "integer" includes "char"). Not sure whether "integer" is used elsewhere. Maybe using the actual type would be better.
I'm also a bit skeptical about the warning itself. I understand that casts between float*/double* and say 32 bit integer*/64 bit integer* are bad. But casts between float*/double* and char* are actual quite common. Casting to char* does not necessarily imply access to individual bytes, maybe it is just treated as an opaque data block. This idiom can be found a lot in old code bases with C heritage. OTOH it is just a "style" warning, and it can be disabled. Fair enough. Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
