Xref: utzoo comp.sys.m6809:736 comp.lang.c:8334
Path: utzoo!mnetor!uunet!husc6!cca!g-rh
From: g-rh@cca.CCA.COM (Richard Harter)
Newsgroups: comp.sys.m6809,comp.lang.c
Subject: Re: Don't use Scanf()
Message-ID: <25742@cca.CCA.COM>
Date: 19 Mar 88 18:08:44 GMT
References: <2401@ihwpt.ATT.COM> <320@c10sd1.StPaul.NCR.COM> <1185@ucsfcca.ucsf.edu> <9241@sunybcs.UUCP> <1140@csun.UUCP> <296@aiva.ed.ac.uk>
Reply-To: g-rh@CCA.CCA.COM.UUCP (Richard Harter)
Organization: Computer Corp. of America, Cambridge, MA
Lines: 21
Keywords: C stdio library

In article <296@aiva.ed.ac.uk> richard@uk.ac.ed.aiva (Richard Tobin) writes:

>Of course, printf() vs write() is also a portability question, but I'm sure
>there will be plenty of comments on that...

Since you asked :-).  People who mix printf and write are likely to be
visited by things from Binkley's anxiety closet when they leave the safe
haven of UNIX.  If your software is going to run under any operating 
system other than UNIX, don't even think about doing this!

Paranthetically, it is good practice to gather all of your fopens, opens,
etc, together in a few well defined places in portable code.  Life will
be much simpler if you do.  [It may be best to use standardized macros
which are machine dependent, but I've never made the effort to do.  If
anyone has worked these out for VMS, UNIX, and PRIMOS and posts them, I
will bless them.]
-- 

In the fields of Hell where the grass grows high
Are the graves of dreams allowed to die.
	Richard Harter, SMDS  Inc.