Re: Need help with incompatible pointer types on i686

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michael J Gruber wrote:
> numpy definitely needs to fix this. You cannot just go by bitsize and
> signedness. You never could and now you can't ;)

You actually had to before C99, where stdint.h was introduced. On some 
platforms or compilers, such as MSVC, you still cannot use C99, only 
C89/C90. (They support new C++ standards, but not new C standards.) So auto-
detecting one's own uint32_t is still the only way there.

Of course, what the software SHOULD do is to check for stdint.h and use that 
if it exists, only defining its own type if it does not. But it is still not 
a good idea for GCC to make this typically harmless warning an error by 
default (and I have already complained about that, pointing out exactly this 
use case, when the Change was discussed; sadly, my objection was dismissed).

        Kevin Kofler
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux