[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61730: 30.0.50; Compiler warnings for delq and delete
From: |
Richard Stallman |
Subject: |
bug#61730: 30.0.50; Compiler warnings for delq and delete |
Date: |
Sun, 26 Feb 2023 22:24:27 -0500 |
> In Emacs maintenance and development, the two cases are actually one.
> We rebuild Emacs so frequently that even a "rare" warning appears all
> the time and is annoying. It is not a coincidence that we usually
> don't tolerate warnings during the build of Emacs.
I am surprised -- I didn't do that when I was the main maintainer. In
recent years, ISTR seeing warnings in the build often enough.
If you intend to make a change to prevent each such warning, that
implies that each spurious warning is a bigger pain in the neck. That
makes a stronger argument for making fewer warnings rather than more.
I resent it when a compiler takes up my time pressuring me to prove to
it that I know something isn't a bug, and I usually tell that compiler
(inside my head) where it can take those warnings.
> What's your opinion about the case of non-destructive functions - is it
> ok if we would always warn about thrown away return values of calls of
> them?
Either make it an optional feature (and disabled by default), or do
not implement them.
When I implemented the options that enable such warnings in GCC, I
urged people NOT to use those options by default. To enable them by
default in a makefile is to impose systematic harassment on every
contributor to the code. You end up with a program as your
taskmaster, haranguing you continually to insert proof that you didn't
make some mistake.
I never used those options.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
- bug#61730: 30.0.50; Compiler warnings for delq and delete, (continued)
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Richard Stallman, 2023/02/24
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Eli Zaretskii, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Michael Heerdegen, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Eli Zaretskii, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Michael Heerdegen, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Michael Heerdegen, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Eli Zaretskii, 2023/02/25
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Richard Stallman, 2023/02/26
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Michael Heerdegen, 2023/02/27
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Eli Zaretskii, 2023/02/27
- bug#61730: 30.0.50; Compiler warnings for delq and delete,
Richard Stallman <=
- bug#61730: 30.0.50; Compiler warnings for delq and delete, Eli Zaretskii, 2023/02/27
bug#61730: 30.0.50; Compiler warnings for delq and delete, Mattias EngdegÄrd, 2023/02/24