Xref: utzoo comp.sys.m6809:701 comp.lang.c:7837
Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!hubcap!ncrcae!ncr-sd!ncrlnk!ncrcce!c10sd3!c10sd1!johnson
From: johnson@c10sd1.StPaul.NCR.COM (Wayne D. T. Johnson)
Newsgroups: comp.sys.m6809,comp.lang.c
Subject: Re: Don't use Scanf()
Message-ID: <320@c10sd1.StPaul.NCR.COM>
Date: 4 Mar 88 19:44:35 GMT
References: <2401@ihwpt.ATT.COM>
Reply-To: johnson@ncrcce.StPaul.NCR.COM (Wayne D. T. Johnson)
Organization: NCR Comten, St Paul
Lines: 11
Keywords: C stdio library

In article <2401@ihwpt.ATT.COM> knudsen@ihwpt.ATT.COM (mike knudsen) writes:
>Don't use Scanf() from the C Standard Library if you care
>about the size of your object program.  It uses 5K
>(yes, 5000 bytes) of text space, plus over 200 bytes of Data.
>Ripping it out of my huge music editor really opened things
>up for new features this weekend.

I've also noticed that printf is somwhat bulky.  If you know what you
are going to print out, why not print it out your self instead of
using a (simple) interpreter to do it for you.

Real programmers don't use printf ;-)