GNU bug report logs - #61730
30.0.50; Compiler warnings for delq and delete

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: mattias.engdegard <at> gmail.com, 61730 <at> debbugs.gnu.org, rms <at> gnu.org, monnier <at> iro.umontreal.ca
Subject: bug#61730: 30.0.50; Compiler warnings for delq and delete
Date: Sat, 25 Feb 2023 17:48:48 +0200

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: rms <at> gnu.org,  mattias.engdegard <at> gmail.com,  61730 <at> debbugs.gnu.org,
>   monnier <at> iro.umontreal.ca
> Date: Sat, 25 Feb 2023 16:09:40 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > > 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?
> >
> > What are "non-destructive functions" in this context?
> 
> I mean all functions with either no side effects or such which may alter
> original list structures but in unpredictable ways so that only the
> return value is ever useful.

Thanks.  I guess this should be okay, but a test run over our sources
would be prudent before the final decision.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.