|
From: | GNU bug Tracking System |
Subject: | bug#43987: closed (strerror return value) |
Date: | Wed, 03 Nov 2021 18:23:01 +0000 |
Your message dated Wed, 3 Nov 2021 19:22:17 +0100 with message-id <C5A33343-7A76-4B9F-AE63-0990E0273C96@sarc.name> and subject line Re: strerror return value has caused the debbugs.gnu.org bug report #43987, regarding strerror return value to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 43987: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43987 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: strerror return value Date: Wed, 14 Oct 2020 13:23:22 +0200 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 This is just a very minor issue. libguile contains two calls to strerror where the result is used to initialize a char *. However, according to the strerror specification, the string returned by strerror should never be changed, so I think it would be better to use const char * instead. Philippguile-strerror-const.patch
Description: Text Data
--- End Message ---
--- Begin Message ---Subject: Re: strerror return value Date: Wed, 3 Nov 2021 19:22:17 +0100 Patch applied in ab9c0c9ca787da60ac9b956fdbcf4c1fa68c3300. Thanks!
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |