From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olivier Galibert <Olivier.Galibert@mines.u-nancy.fr>
To: egcs@cygnus.com
Subject: warning: passing `char' to argument 2 of `strcpy(char *, const char *)' lacks a cast
Date: Fri, 10 Oct 1997 22:58:00 -0000
Message-id: <19971011075407.15923@renaissance.loria.fr>
X-SW-Source: 1997-10/msg00450.html

Shouldn't these warnings being errors instead ? I see no case where
it can be something else than a typo and in a big compilation a
meaningful warning can go unnoticed within meaningless ones.

renaissance.loria.fr:~/dvp/gally/magna #437 >cat >blah.cc
#include <string.h>

int main()  
{
  char tab[5];
  strcpy(tab, 'a');
  return 0;
}
renaissance.loria.fr:~/dvp/gally/magna #438 >g++ blah.cc -o blah
blah.cc: In function `int main()':
blah.cc:6: warning: passing `char' to argument 2 of `strcpy(char *, const char *)' lacks a cast
renaissance.loria.fr:~/dvp/gally/magna #439 >gcc blah.cc -o blah
blah.cc: In function `int main()':
blah.cc:6: warning: passing `char' to argument 2 of `strcpy(char *, const char *)' lacks a cast


renaissance.loria.fr:~/dvp/gally/magna #440 >gcc -v
Reading specs from /users/model/galibert/lib/gcc-lib/sparc-sun-solaris2.5.1/egcs-2.90.12/specs
gcc version egcs-2.90.12 971008 (gcc2-970802 experimental)

  OG.