From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ffe7b9269a00c843 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1993-03-30 14:26:13 PST Newsgroups: comp.lang.ada Path: sparky!uunet!destroyer!gatech!usenet.ins.cwru.edu!agate!linus!linus.mitre.org!linus!mbunix!emery From: emery@goldfinger.mitre.org (David Emery) Subject: Re: Ada cost breakpoints In-Reply-To: crispen@eight-ball.boeing.com's message of 29 Mar 93 15:35:33 GMT Message-ID: Sender: news@linus.mitre.org (News Service) Nntp-Posting-Host: goldfinger.mitre.org Organization: The Mitre Corp., Bedford, MA. References: <9303291535.AA16997@eight-ball.boeing.com> Date: Tue, 30 Mar 1993 21:28:21 GMT Date: 1993-03-30T21:28:21+00:00 List-Id: Open, Read, Write, pipes, Fork and Exec are included in POSIX standards. Sockets, for instance, are not currently in any approved POSIX standards. Therefore, code written using sockets is *NOT* guaranteed portable in a POSIX environment (e.g. Open VMS, CTOS or POSIX-compliant MVS, for instance). Sockets are a BSD extension (which is now included in System V). Sockets packages exist for other operating systems, but they're not "open" in the sense of formally standardized. Your semantics may vary... >It occurs to me that it might be sensible for programs to require >that all OS interfaces which are not pre-defined in the language (e.g., >Text_IO, task stuff) be defined in Posix syntax. Could you please explain this? What is "Posix syntax"? I'm not familiar with that term... dave (IEEE P1003.5 POSIX/Ada Binding Technical Editor)