🚀 go-pugleaf

In article <lauten.727351645@Physik.TU-Muenchen.DE> lauten@Physik.TU-Muenchen.DE (Markus Lautenbacher) writes:
>--------
>w.c: In function `main':
>w.c:5: warning: implicit declaration of function `printf'
>--------
>
>I thought by writing "#include <stdio.h>" I have already taken care of
>the proper declaration of printf() !?
>Any hints whether I have missed something or whether gcc is incorrect
>here are welcome. Should I care about the warning at all ?

man pages on neither our local next boxes nor ibm pc/rt's list a return
type for printf (therefore, will default to type int).  In my (extremely
limited) experience, some compiler installations don't bother prototyping
functions that return int.  (Also, I believe a function, by default, is
assumed to have at one or more argurments, ala printf, so no need to
prototype there either).  If gcc is installed to use the default 
include files and libraries, it's quite possible that the orginal stdio.h
file didn't have a prototype for printf().  Should be fairly easy to 
grep the file looking for it.  

I believe that the gnu library (well, I guess stdio is really UCB)
includes prototypes for printf() and relatives.

btw, my turbo-c manual lists the return value for printf (of type int)
to represent the number of bytes output to the stream.  Is this 
standard on unix machines? (Neither of the man pages mentioned any
thing about it).

hope this answers your question.  Moreover, I hope it makes sense, 
as it's 5:45am and I'm not just getting up :->

regards,
mrc
-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle@cs.umr.edu     and be right all the time, or not work at all
S087891@UMRVMA.UMR.EDU   and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen