Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!bloom-beacon!gatech!rutgers!mtune!codas!usfvax2!chips
From: chips@usfvax2.UUCP (Chip Salzenberg)
Newsgroups: comp.sys.ibm.pc,comp.misc
Subject: Re: Obnoxious software (was Re: C license agreements)
Message-ID: <803@usfvax2.UUCP>
Date: Mon, 27-Jul-87 00:01:26 EDT
Article-I.D.: usfvax2.803
Posted: Mon Jul 27 00:01:26 1987
Date-Received: Tue, 28-Jul-87 01:30:05 EDT
References: <8387@brl-adm.ARPA> <6146@brl-smoke.ARPA> <870@bsu-cs.UUCP>
Organization: AT Engineering, Tampa, FL
Lines: 29
Summary: Make MS-C shut up
Xref: mnetor comp.sys.ibm.pc:6076 comp.misc:888

In article <870@bsu-cs.UUCP>, dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
} In article <6146@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn) writes:
} >I think Ken & Dennis would have croaked anybody who tried to make
} >UNIX utilities print out identifying messages etc.
} 
} If you use Microsoft's make utility to compile a collection of say
} 20 C files using Microsoft's C compiler, and then link them with
} Microsoft's linker, you get a steady barrage of obnoxious copyright
} messages:
}      one from the make program when it starts up
}      20 from the C compiler, one for each file compiled
}      one from the linker

Well, you can get rid of the 20 C compiler messages.  Use the "-nologo"
option to "cl".  No, it's not documented; but it works anyway.  :-)
 
} Now, a solution for the paranoid.  You CAN display a copyright message
} without harrassing the user.  Just do it only if your program is
} invoked without the proper arguments.

I like this idea.  And send it to standard error, just in case the standard
output is piped elsewhere.

} Rahul Dhesi         UUCP:  {ihnp4,seismo}!{iuvax,pur-ee}!bsu-cs!dhesi

-- 
Chip Salzenberg            UUCP: "uunet!ateng!chip"  or  "chips@usfvax2.UUCP"
A.T. Engineering, Tampa    Fidonet: 137/42    CIS: 73717,366
"Use the Source, Luke!"    My opinions do not necessarily agree with anything.