Newsgroups: comp.lang.c
Path: utzoo!utgpu!jarvis.csri.toronto.edu!dgp.toronto.edu!flaps
From: flaps@dgp.toronto.edu (Alan J Rosenthal)
Subject: Re: Why you should use puts(3) when you don't need printf(3)
Message-ID: <8803160314.AA18582@explorer.dgp.toronto.edu>
Organization: University of Toronto
References: <2304@uvacs.CS.VIRGINIA.EDU>
Date: Tue, 15 Mar 88 22:14:36 EST


rwl@uvacs.CS.VIRGINIA.EDU (Ray Lubinsky) writes:
>But what ever happened to run time-efficiency?  The point of using
>fputs(3) is that it just pushes bytes to the output!  Fprintf(3) has to
>scan its first argument and gyrate around to get to the point where it
>pushes bytes.

On the Amiga using the Manx Aztec C compiler (v3.20a), puts() takes a
noticeable amount of time and printf() does not.  Your efficiency theories
are wrong.  (I have no idea what puts() is doing for so long.)

ajr
-- 
If you had eternal life, would you be able to say all the integers?