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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Victor Porton Newsgroups: comp.lang.ada Subject: Re: Accessing Shell Variables Date: Wed, 28 Dec 2016 23:38:41 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <35dadef7-2aee-4cd9-b774-ab54f4698d64@googlegroups.com> NNTP-Posting-Host: 7uJPbDcSpErJPiv/8313dw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.14.10 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:32971 Date: 2016-12-28T23:38:41+02:00 List-Id: Simon Wright wrote: > Victor Porton writes: > >> ahlan.marriott@gmail.com wrote: >> >>> I can access Windows, Linux and Osx environment variables using >>> Ada.Environment_Variables.Value However Linux and Osx also have Shell >>> variables. How can I access these? >> >> You cannot access a shell variable unless it is exported. Exported shell >> variable becomes and environment variable: >> >> xxx=yyy >> ./my-program # my-program cannot (at least in an easy way) access $xxx >> >> export xxx=yyy >> # or >> xxx=yyy >> export xxx >> ./my-program # my-program cannot access xxx environment variable > > This variant is the one that *can* access the environment variable. Yes, my typo. -- Victor Porton - http://portonvictor.org