Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!cuuxb!ltuxa!ll1a!nesac2!jec
From: jec@nesac2.UUCP (John Carter ATLN SADM)
Newsgroups: comp.cog-eng,comp.unix.xenix,comp.unix.wizards
Subject: Re: Request for human interface design anecdotes
Message-ID: <834@nesac2.UUCP>
Date: Wed, 18-Nov-87 15:41:07 EST
Article-I.D.: nesac2.834
Posted: Wed Nov 18 15:41:07 1987
Date-Received: Sun, 22-Nov-87 10:11:41 EST
References: <101@ateng.UUCP> <1402@cuuxb.ATT.COM> <1689@rayssd.RAY.COM> <3032@phri.UUCP>
Organization: A.T.&T. NTSC, Lisle, Ill.
Lines: 21
Summary: smarter cc
Xref: mnetor comp.cog-eng:301 comp.unix.xenix:1182 comp.unix.wizards:5526

In article <3032@phri.UUCP>, roy@phri.UUCP (Roy Smith) writes:
> In article <1689@rayssd.RAY.COM> dhb@rayssd.RAY.COM (David H. Brierley) writes:
> > Just the other day I wiped out a weeks worth of work by typing
> > "cc -o pgm.c" on my AT&T unix-pc.
> 
> 	This may sound harsh, but I really have little sympathy in this
> case.  That zapping a source file wipes out a week's worth of work implies
> that you don't make daily backups.  Even on a PC, doing backups should be
> routine every day; there really is little excuse for not doing so.

My multi-user systems get daily backups - my PC gets infrequent
backups, except for some critical items (my LAN database).

However, in the original case, it appears that the  unix-pc has an
old and rather braindead compiler - the ones I use (DEC 11/70, AT&T
3B2, 3B5) respond to 'cc -o file.c' with 'would overwrite source'
and then abort.  Getting 'cc -o' instead of 'cc -O' is very easy.
-- 
USnail: John Carter, AT&T, Atlanta RWC, 3001 Cobb Parkway, Atlanta GA 30339
Video:	...ihnp4!cuea2!ltuxa!ll1!nesac2!jec    Voice: 404+951-4642
(The above views are my very own. How dare you question them? :-)