Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

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

 



...
> > Concretely, as an upstream  maintainer, what should they do to test
> > the behaviour of their code ?  Is there more to it than just
> > setting CFLAGS="-std=gnu99", if they want to validate this in their
> > upstream CI ahead of GCC 14 arriving ?
>
> It's -Werror=implicit-int -Werror=implicit-function-declaration.  Best
> to throw in -Werror=int-conversion -Werror=strict-prototypes
> -Werror=old-style-definition.  -Werror=int-conversion should really be a
> no-brainer, the other two are about the removal of old-style function
> definitions and declarations that are not prototypes from C2X (also
> mentioned in the proposal).  I can probably spell this out in the
> proposal.

Even better: could you put together an RPM macro we can use in
specfiles to essentially opt-in early to the F40 Change?
_______________________________________________
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