Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.std.c
Subject: Re: Escape sequences for printf() defined by SVID
Keywords: escape sequences printf SVID
Message-ID: <32609@news.Think.COM>
Date: 4 Jan 90 01:44:05 GMT
References: <1990Jan3.144808.6319@sssab.se> <1974@crdos1.crd.ge.COM>
Sender: news@Think.COM
Distribution: comp
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 16

In article <1974@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) writes:
>For that matter, what has SVID got to do with the C
>language, and why are they even mentioning this? X3J11 didn't respecify
>the unix calls ;-)

At the time the SVID was being developed, there was no C standard, so
apparently AT&T included some standard libraries as part of the System V
spec.  Otherwise, a system could claim to be compatible with System V even
though its C libraries are incompatible.  Since most programs use more than
just the system calls, specifying just the Unix system calls would be
insufficient to promote a decent amount of portability.
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar