This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/20422] warning: passing arg 1 of `mymalloc' from incompatible pointer type
- From: "pbijdens at storagelabs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Mar 2005 17:02:15 -0000
- Subject: [Bug c/20422] warning: passing arg 1 of `mymalloc' from incompatible pointer type
- References: <20050311100700.20422.pbijdens@storagelabs.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pbijdens at storagelabs dot com 2005-03-11 17:02 -------
Invalid or not, the request for changing the error message in the other case
still stands for reasons mentioned: It's impossible currently to distinguish
between the two mentioned cases.
Compiler warnings should help the developer improve their code, not make life
mor difficult and even force developers to create unsafe situations. The value
of these warning messages would greatly improve when a distinction would be made
between the two cases mentioned.
This is especially true because this is a commonly used construct in
environments where coding guidelines are in place that require function return
values to be status codes only.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20422