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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: "Norman H. Cohen" Subject: Re: Environment variables Date: 1996/11/13 Message-ID: <328A44B6.62FB@watson.ibm.com>#1/1 X-Deja-AN: 196441123 references: <55819q$mql@newslink.runet.edu> <327A32A3.2DD0@itg-sepg.logicon.com> <1996Nov2.173625.1@eisner> <55kmb1$3m6@top.mitre.org> content-type: text/plain; charset=us-ascii organization: IBM Thomas J. Watson Research Center mime-version: 1.0 reply-to: ncohen@watson.ibm.com newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; I) Date: 1996-11-13T00:00:00+00:00 List-Id: Robert Dewar wrote: > Very few remote target (embedded) runtime systems have environment > variables and many operating systems do not. If they were standard > they would be in the standard libraries. > > They are standard in ANSI, but with entirely implementation defined > semantics. > ANSI => ANSI C The ANSI C standard specifically acknowledges that the C standard library need not be supported on an embedded target. Section 2.1.2 defines two kinds of execution environments, "hosted" and "freestanding". Subsection 2.1.2.1 describes a freestanding environment as follows: In a freestanding environment (in which C program execution may take place without benefit of an operating system), the name and type of the function called at program startup are implementation-defined. There are otherwise no reserved external identifiers. Any library facilities available to a freestanding program are implementation-defined. -- Norman H. Cohen mailto:ncohen@watson.ibm.com http://www.research.ibm.com/people/n/ncohen