[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dealing with bad warnings
From: |
Paul Eggert |
Subject: |
Re: Dealing with bad warnings |
Date: |
Wed, 07 Sep 2011 11:17:47 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Thunderbird/3.1.12 |
On 09/07/11 11:01, Gary V. Vaughan wrote:
>> static inline char *
>> > my_tigetstr (char const *capname)
>> > {
>> > return tigetstr ((char *) capname);
>> > }
>> > #undef tigetstr
>> > #define tigetstr my_tigetstr
> Not that I've tried it, but surely you now get a warning in every file
> that includes system.h about how the cast is discarding a const
Such casts are common in gnulib anyway
(else how could one implement something like strchr?)
so it shouldn't be a problem in practice -- people either
don't compile with that particular warning enabled,
or they ignore such warnings.