Xref: utzoo comp.std.c:969 comp.lang.c:17310 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!indri!nic.MR.NET!eta!com50!jhereg!mark From: mark@jhereg.Jhereg.MN.ORG (Mark H. Colburn) Newsgroups: comp.std.c,comp.lang.c Subject: Re: realloc Message-ID: <740@jhereg.Jhereg.MN.ORG> Date: 31 Mar 89 03:55:59 GMT References: <10170@bloom-beacon.MIT.EDU> Reply-To: mark@jhereg.MN.ORG (Mark H. Colburn) Followup-To: comp.std.c Organization: Minnetech Consulting, Inc., St. Paul, MN Lines: 27 In article davidl@intelob.intel.com (David Levine) writes: >The System V Interface Definition (which, despite its many flaws, IS >an established standard, unlike the pANS which is still only a "draft >proposed standard") doesn't require this behavior. One of the SVID's biggest flaws is that it is NOT a standard: it was never balloted and approved by anyone. It is an interface specification for a particular implementation of Unix. It should be noted that there few companies, if any, which have SVID conforming interfaces; even AT&T doen't conform to their own interface specification. The SVID is one of the base documents for some of the P1003 working groups because it represents one of the most comprehensive descriptions of Unix currently available. The SVID along with work done by /usr/group provided a lot of groundwork for p1003, which IS a standard, and provided some impetus for X3J11 which is currently jumping through the final hoops to become a standard. If the SVID were a standard, there would have been no need for P1003. Unfortunately, there were a couple of hole in the SVID which you could drive trucks through, hence P1003. -- Mark H. Colburn "Look into a child's eye; Minnetech Consulting, Inc. there's no hate and there's no lie; mark@jhereg.mn.org there's no black and there's no white."