Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site baylor.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!rochester!rocksvax!rocksanne!sunybcs!kitty!baylor!peter From: peter@baylor.UUCP (Peter da Silva) Newsgroups: net.lang.c Subject: Re: Re: Re: casts to (void) Message-ID: <363@baylor.UUCP> Date: Mon, 12-Aug-85 15:58:11 EDT Article-I.D.: baylor.363 Posted: Mon Aug 12 15:58:11 1985 Date-Received: Thu, 15-Aug-85 00:13:17 EDT References: <441@brl-tgr.ARPA> <261@kitty.UUCP> <549@brl-tgr.ARPA> Organization: Ancient Illuminated Seers of Bavaria Lines: 31 > > > If you are trying to write code that runs unmodified both in > > > standard environments and on 4.2BSD (not recommended), ... > > > > Why not? I try to make sure my code runs on K&R, 4.2, SV, and MS-DOS > > without modification. Apart from system calls I'm usually successful. > > The reason why not is, you have to limit yourself to a fairly puny > common subset and implement your own replacements for such useful > functions as drand48(), hsearch(), tempnam(), getopt(), etc. etc. Our native library doesn't have drand48, hsearch or getopt, and tempnam is just a throwback to the days before sprintf. > Also, it is hard to use the basic utilities via popen() since they > don't behave the same in many cases. You also cannot exploit the I don't use popen either. It doesn't run on non-UNIX systems. > more powerful features of "make", you have a "ranlib" problem, etc. I don't even have MAKE on my IBM-PC. And before you flame me about using an IBM-PC, it's a requirement of the job. The remainder of your message suffers from the same flaws. Not everyone has access to all those neat bells & whistles... this group is for 'C' standards, not UNIX standards. 'C' isn't an integral part of UNIX any more... Semiflame: And SV isn't automatically THE STANDARD ENVIRONMENT either. -- Peter da Silva (the mad Australian) UUCP: ...!shell!neuro1!{hyd-ptd,baylor,datafac}!peter MCI: PDASILVA; CIS: 70216,1076