Why you should use puts(3) when you don't need printf(3)

[Frank Adams]

In article <2304 at uvacs.CS.VIRGINIA.EDU> rwl at uvacs.CS.VIRGINIA.EDU (Ray Lubinsky) writes:
>OK -- I'm not saying that using *printf where *puts is appropriate is going to
>break the bank.  But it's good practice to only use what you need; anything
>else is just lazy programming.

There is a time and a place for careful programming to maximize speed.  And
there is a time and a place for lazy programming.  For code which is only
going to be run a few times, or code whose execution time is dominated by
physical I/O time (or user response time), lazy programming is the way to go.
-- 

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Ashton-Tate          52 Oakland Ave North         E. Hartford, CT 06108