Date: Sat, 31 May 1997 21:43:53 -0800 (AKDT) From: Steve Howe <un_x@anchorage.net> To: freebsd-hackers <hackers@freebsd.org> Subject: signed/unsigned cpp Message-ID: <Pine.BSF.3.95q.970531213558.2061A-100000@aak.anchorage.net>
next in thread | raw e-mail | index | archive | help
how can this be? i changed my argument to "signed char *" and gcc doesn't like it. so i change it to "unsigned char *" and gcc doesn't like it either! gcc wants to have it's cake and eat it too! it doesn't mind "char *" though. so what's wrong with adding "signed" or "unsigned"? unix.cpp: In function `long unsigned int flen(unsigned char *)': unix.cpp:249: warning: passing `signed char *' as argument 1 of `fopen(const char *, const char *)' changes signedness unix.cpp: In function `long unsigned int flen(unsigned char *)': unix.cpp:249: warning: passing `unsigned char *' as argument 1 of `fopen(const char *, const char *)' changes signedness ------------------------------------------------------------------------- Sleep: a sign a caffeine deprivation ... http://www.anchorage.net/~un_x -------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970531213558.2061A-100000>