🚀 go-pugleaf

In article <1992Sep4.204457.25043@muddcs.claremont.edu> jason@jarthur.claremont.edu (Jason Merrill) writes:
+../../../libg++/src/../g++-include/string.h:28: declaration of `int  strlen
+(const char *)'
+
+<built-in>:0: conflicts with built-in declaration `long unsigned int
+strlen (const char *)'
+-----
+
+Why does gcc think that strlen should return long unsigned int, rather than
+int?  How does it go about deciding the return type for these built-in

Because ANSI C library definitions have:

size_t strlen( const char *);


+functions?  I haven't been able to find the place in the make process where
+this happens.

Look at the file 'sys-protos.h' in the gcc-2.2.2 directory.

+I am working on a Sequent Symmetry running Dynix.  The string.h we are
+using comes, I believe, from the AT&T C++ translator v1.2, and looks like
+this:
+
+
+/*	@(#)string.h	1.2	*/
+extern char
+	*strcpy(),
+	*strncpy(),


Appears to be non-ANSI standard string declarations. Get the book,
'The Standard C Library' by P.J. Plauger which describes the various
declarations for the ANSI library functions.
-- 

John Clark
jclark@ucsd.edu