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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8dea6f46dfb95f66 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Standard libraries (Was: Environment variables) Date: 1996/11/16 Message-ID: #1/1 X-Deja-AN: 196991181 references: <55819q$mql@newslink.runet.edu> <327A32A3.2DD0@itg-sepg.logicon.com> <1996Nov2.173625.1@eisner> <55kmb1$3m6@top.mitre.org> <56do9g$1v5@fozzie.sun3.iaf.nl> <56kocf$65k@fozzie.sun3.iaf.nl> organization: New York University newsgroups: comp.lang.ada Date: 1996-11-16T00:00:00+00:00 List-Id: Geert said 'As far as I have seen (looking at forest, I don't have the standard you mention as it is not public) this binding is very Unix specific and only meant for Unix systems. So rather than defining an interface that defines a consistent subset of the functionality most common platforms have, it takes one (Unix) and wraps a thin layer around the standard C library so it can be used in Ada." Well it is POSIX specific rather than Unix specific, many non-Unix systems have promised Posix compliance (including incidentally at one point OS/2). Certainly for example NT provides POSIX compliance and so does VMS. Yes, it is not necessarily portable to arbitrary non-POSIX compliant environments but this discussion arose in the context of environment variables, which are particular to Unix and Unix-like systems in any case.