Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!headwall.Stanford.EDU!lm From: lm@stanford.edu (Larry McVoy) Newsgroups: comp.unix.bsd,comp.unix.wizard Subject: Re: Summary of differences between BSD, SYSV and POSIX Date: 4 Aug 1994 05:14:50 GMT Organization: Computer Science Department, Stanford University. Lines: 31 Message-ID: <31ptga$1mr@Times.Stanford.EDU> References: <Ctxx8C.Dv3@un.seqeb.gov.au> NNTP-Posting-Host: sunburn.stanford.edu X-Newsreader: Tin 1.1 PL5 ANTHONY LEE (al012@un.seqeb.gov.au) wrote: : Dear all, : : Could someone please point me to any articles, reports which : summarizes differences between BSD, SYSV and POSIX ? : : I am particularly interested in C functions and the values : they return e.g. in SYSV sprintf returns the number of : characters printed but BSD doesn't. I would suggest that you get access to a SunOS 4.1 system and do a man 7 posix This will point you to a list of man pages (posix, ansi c, bsd, sunos, svidii, svidiii, and xopen) and lint libraries that may be used to check your code. I wrote these in 1989 so they may well be out of date (especially the svidiii stuff, that was under construction). I personally restrict myself to svidii + SunRPC + BSD Socket interfaces and have very few portability problems. The lint libraries are in /usr/lib/lint and /usr/5lib/lint. They were shipped in source form so that users could use them in any way they saw fit. If other systems were to pick up these libs, I don't think Sun would object. I purposely did not copyright them. There may be bugs in the libraries but noone has complained so far. -- -- Larry McVoy lm@sun.com ==> lm@sgi.com (415) 821-5758